Question 1080
Malware is removed from a privileged admin laptop, but a hidden persistence mechanism may remain after local cleanup. Which investigative step would most directly establish the relevant scope?
- Map credential dependencies before staged rotation
- Search across the prior attack chain for residual behavior
- Check credential exposure, boot integrity and persistence inventory
- Map delays to specific tooling, role and handoff failures
Explanation
Correct Answer
C:In the Trusted endpoint rebuild case, validation is needed before the device rejoins privileged networks; the observation “Malware is removed from a privileged admin laptop, but a hidden persistence mechanism may remain after local cleanup” makes this scope analysis choice the fitting one.
Incorrect Answers
A:This option addresses Credential recovery after domain compromise because service accounts and key trusts need sequencing to avoid production outages; the Trusted endpoint rebuild scope analysis question instead turns on the fact that validation is needed before the device rejoins privileged networks.
B:That option fits Incident eradication verification since verification should revisit each persistence, credential and network mechanism; it does not fit the Trusted endpoint rebuild scope analysis scenario, where validation is needed before the device rejoins privileged networks.
D:That option fits Post-incident lessons-learned review since actionable root causes produce changes that can later be tested; it does not fit the Trusted endpoint rebuild scope analysis scenario, where validation is needed before the device rejoins privileged networks.
Question 1081
An employee endpoint creates a new service on a peer after an unusual network logon from that workstation. How should the detection program improve coverage for this pattern?
- Alert on Office applications starting script interpreters
- Alert on rare bulk exports from sensitive repositories
- Detect unique-account counts in sliding source-IP windows
- Detect rapid file rewrites combined with recovery tampering
- Correlate rare remote service creation with new network logons
Explanation
Correct Answer
E:The Lateral movement via remote service evidence “An employee endpoint creates a new service on a peer after an unusual network logon from that workstation” is decisive for ongoing detection improvement because joining these events distinguishes administrative deployment from unauthorized movement.
Incorrect Answers
A:For ongoing detection improvement in Lateral movement via remote service, Malicious Office macro delivery is a different mechanism: parent-child telemetry detects abuse that signature-only attachment scanning may miss; here, joining these events distinguishes administrative deployment from unauthorized movement.
B:The choice is relevant to Insider bulk source-code copying, where user baselines and asset labels improve specificity over raw download volume; for ongoing detection improvement in Lateral movement via remote service, joining these events distinguishes administrative deployment from unauthorized movement.
C:For ongoing detection improvement in Lateral movement via remote service, Password spraying across employees is a different mechanism: fan-out detection catches attacks that never exceed individual-user failure thresholds; here, joining these events distinguishes administrative deployment from unauthorized movement.
D:The choice is relevant to Ransomware file encryption, where multiple signals improve detection confidence beyond file extension changes alone; for ongoing detection improvement in Lateral movement via remote service, joining these events distinguishes administrative deployment from unauthorized movement.
Question 1082
A nightly backup identity unexpectedly reads payroll data from a service it has never used. What security condition most directly explains the pattern?
- Possible data loss over removable storage
- Sensitive object exposure via link permissions
- Sensitive privilege change outside established role
- Audit-control evasion sequence
- Nonhuman identity scope deviation
Explanation
Correct Answer
E:Service principals should access only resources consistent with workload purpose and role grants; this is the relevant classification mechanism for Service principal unusual resource access given “A nightly backup identity unexpectedly reads payroll data from a service it has never used”.
Incorrect Answers
A:For the alternative DLP alert for removable media transfer situation, bulk copying to portable media increases exfiltration risk when sensitive files and role context align; by contrast, for Service principal unusual resource access classification, service principals should access only resources consistent with workload purpose and role grants.
B:In Public sharing policy violation, anonymous sharing can bypass named-recipient checks when a link grants broad access; the reported Service principal unusual resource access case calls for a different classification conclusion because service principals should access only resources consistent with workload purpose and role grants.
C:For the alternative Privileged identity rare administrative action situation, administrative grants by an unusual principal can indicate role abuse or credential compromise; by contrast, for Service principal unusual resource access classification, service principals should access only resources consistent with workload purpose and role grants.
D:In SIEM audit policy tampering, security telemetry configuration changes followed by sensitive activity can indicate deliberate concealment; the reported Service principal unusual resource access case calls for a different classification conclusion because service principals should access only resources consistent with workload purpose and role grants.
Question 1083
Several weak alerts together show credential theft and lateral activity, but the team continues closing them individually. Which scoping query or comparison best tests the working hypothesis?
- Verify responder identities using known alternate contact paths
- Assess affected assets, attacker progression and potential impact
- Confirm engagement prerequisites and evidence-transfer conditions
- Reconcile endpoint identity to hosting and application records
Explanation
Correct Answer
B:In the Incident declaration threshold case, a unified assessment distinguishes an active campaign from isolated benign matches; the observation “Several weak alerts together show credential theft and lateral activity, but the team continues closing them individually” makes this scope analysis choice the fitting one.
Incorrect Answers
A:That option fits Out-of-band crisis communications since channel trust must be established before sharing containment instructions; it does not fit the Incident declaration threshold scope analysis scenario, where a unified assessment distinguishes an active campaign from isolated benign matches.
C:That option fits Third-party incident retainer activation since delayed contracting and privacy questions can block urgent expert analysis; it does not fit the Incident declaration threshold scope analysis scenario, where a unified assessment distinguishes an active campaign from isolated benign matches.
D:This option addresses Incident readiness inventory because hostname ambiguity can delay targeted action or harm the wrong system; the Incident declaration threshold scope analysis question instead turns on the fact that a unified assessment distinguishes an active campaign from isolated benign matches.
Question 1084
One firewall records jsmith while the identity provider records a full principal name and correlation fails to join their events. The analyst has not yet established malicious intent or downstream impact. What caution prevents an unsupported inference from these records?
- No SIEM events from a sensor is not proof no activity occurred
- A technically valid rule can still produce misprioritized alerts
- A hostname alone is an unreliable global asset key
- A short username is not globally unique across domains
Explanation
Correct Answer
D:In the Cross-vendor user identifier normalization case, unqualified names can represent distinct accounts in separate identity namespaces; the observation “One firewall records jsmith while the identity provider records a full principal name and correlation fails to join their events” makes this interpretation limit choice the fitting one.
Incorrect Answers
A:In SIEM ingestion freshness gap, collection failure can produce the same empty search result as a quiet network; the reported Cross-vendor user identifier normalization case calls for a different interpretation limit conclusion because unqualified names can represent distinct accounts in separate identity namespaces.
B:For the alternative Context enrichment delay situation, missing business context changes impact assessment without changing the threat signal; by contrast, for Cross-vendor user identifier normalization interpretation limit, unqualified names can represent distinct accounts in separate identity namespaces.
C:In Cross-source entity duplication, names may be reused, duplicated or changed during provisioning; the reported Cross-vendor user identifier normalization case calls for a different interpretation limit conclusion because unqualified names can represent distinct accounts in separate identity namespaces.
Question 1085
Two organizations want to share machine-readable threat objects including indicator relationships and attack patterns. Which investigative step would most directly establish the relevant scope?
- Test incremental fetch and object-version handling
- Validate schema and relationship targets before import
- Cross-check recent behavior against other independent sources
- Compare confidence and last-observed time across contributors
- Seek an independent technical artifact or trusted witness
Explanation
Correct Answer
B:For scope analysis in STIX structured intelligence exchange, malformed references can degrade knowledge graphs and subsequent matching; this applies to the reported “Two organizations want to share machine-readable threat objects including indicator relationships and attack patterns”.
Incorrect Answers
A:For scope analysis in STIX structured intelligence exchange, TAXII intelligence distribution is a different mechanism: a client must handle additions and revisions without repeatedly ingesting all content; here, malformed references can degrade knowledge graphs and subsequent matching.
C:For scope analysis in STIX structured intelligence exchange, Threat feed confidence decay is a different mechanism: current local evidence should outweigh a stale single-provider label; here, malformed references can degrade knowledge graphs and subsequent matching.
D:The choice is relevant to Threat intelligence platform deduplication, where the strongest assessment depends on evidence quality and recency, not just feed count; for scope analysis in STIX structured intelligence exchange, malformed references can degrade knowledge graphs and subsequent matching.
E:For scope analysis in STIX structured intelligence exchange, Intelligence source circular reporting is a different mechanism: separate evidence streams provide stronger corroboration than repeated headlines; here, malformed references can degrade knowledge graphs and subsequent matching.
Question 1086
A newly created service principal uses application credentials to enumerate key vaults across several subscriptions. Which scoping query or comparison best tests the working hypothesis?
- Trace session issuer, external ID and cross-account trust policy
- Enumerate resources accessed and effective IAM privileges
- List publicly accessible objects and external access history
- Review application credentials, consent and RBAC scopes
Explanation
Correct Answer
D:The Azure automation identity misuse evidence “A newly created service principal uses application credentials to enumerate key vaults across several subscriptions” is decisive for scope analysis because broad grants or leaked secrets determine how widely the principal can act.
Incorrect Answers
A:This option addresses AWS unauthorized role assumption because authorization context establishes how the caller obtained effective permissions; the Azure automation identity misuse scope analysis question instead turns on the fact that broad grants or leaked secrets determine how widely the principal can act.
B:That option fits GCP service account key exposed since the scope of a leaked key is bounded by the service account's permissions; it does not fit the Azure automation identity misuse scope analysis scenario, where broad grants or leaked secrets determine how widely the principal can act.
C:This option addresses Cloud storage anonymous exposure because effective exposure may vary between bucket policy and individual object grants; the Azure automation identity misuse scope analysis question instead turns on the fact that broad grants or leaked secrets determine how widely the principal can act.
Question 1087
A laptop contacts a new external endpoint every sixty seconds with similarly sized HTTPS requests during user inactivity. How should the analyst classify the activity at this stage?
- Novel encrypted-traffic client behavior
- Internal lateral reconnaissance traffic
- Potential network exfiltration following credential misuse
- Periodic command-and-control beaconing
- Possible domain-generation infrastructure search
Explanation
Correct Answer
D:Given “A laptop contacts a new external endpoint every sixty seconds with similarly sized HTTPS requests during user inactivity”, regular low-volume egress from a host can reflect automated check-ins to remote control infrastructure; that best addresses classification in Regular command beacon intervals.
Incorrect Answers
A:That option fits Anomalous TLS client fingerprint since ClientHello features can help group malware-like TLS stacks when packet payloads are unavailable; it does not fit the Regular command beacon intervals classification scenario, where regular low-volume egress from a host can reflect automated check-ins to remote control infrastructure.
B:This option addresses East-west port scan detection because unusual destination breadth and port variation can indicate host and service discovery; the Regular command beacon intervals classification question instead turns on the fact that regular low-volume egress from a host can reflect automated check-ins to remote control infrastructure.
C:That option fits Unusual outbound data volume since high outbound volume becomes suspicious when linked to sensitive access and an unapproved destination; it does not fit the Regular command beacon intervals classification scenario, where regular low-volume egress from a host can reflect automated check-ins to remote control infrastructure.
E:That option fits Domain-generation algorithm surge since some malware cycles through algorithmically generated domain names to find an active command endpoint; it does not fit the Regular command beacon intervals classification scenario, where regular low-volume egress from a host can reflect automated check-ins to remote control infrastructure.
Question 1088
A critical host's process audit shows execve activity with unusual effective user IDs but syslog lacks command detail. The finding has been corroborated and the response team has authorization to act. Which operational remedy is best aligned to the verified issue?
- Investigate unauthorized sudo activity and restrict privilege grants
- Protect audit configuration and preserve relevant raw records
- Preserve relevant unified logs and examine persistence files
- Review the account and revoke unauthorized SSH access
- Increase sustainable logging capacity and tune high-volume sources
- Disable an unauthorized recurring task after preserving its definition
Explanation
Correct Answer
B:Tamper-resistant collection supports reliable reconstruction of execution; this is the relevant response decision mechanism for Linux auditd execution records given “A critical host's process audit shows execve activity with unusual effective user IDs but syslog lacks command detail”.
Incorrect Answers
A:In Linux sudo elevation audit, least privilege should be corrected after confirming the command and business purpose; the reported Linux auditd execution records case calls for a different response decision conclusion because tamper-resistant collection supports reliable reconstruction of execution.
C:In macOS unified log investigation, retention can be limited, so collection must precede cleanup; the reported Linux auditd execution records case calls for a different response decision conclusion because tamper-resistant collection supports reliable reconstruction of execution.
D:For the alternative Linux SSH authentication messages situation, response should address the compromised identity without disabling required remote administration universally; by contrast, for Linux auditd execution records response decision, tamper-resistant collection supports reliable reconstruction of execution.
E:In Linux dropped syslog messages, queue and rate adjustments address drop causes without turning logging off; the reported Linux auditd execution records case calls for a different response decision conclusion because tamper-resistant collection supports reliable reconstruction of execution.
F:For the alternative Linux cron persistence evidence situation, stopping the trigger prevents reexecution while leaving evidence available; by contrast, for Linux auditd execution records response decision, tamper-resistant collection supports reliable reconstruction of execution.
Question 1089
A trusted application receives a sudden increase in valid tokens for an account with no corresponding interactive logins. What record is most useful for confirming this specific pattern?
- MFA challenge outcomes aligned to session creation
- Identity token issuance and application sign-in audit
- Identity provider success logs with client IP and device IDs
- Historical sign-in activity with current admin role assignments
Explanation
Correct Answer
B:In the Unusual federation token issuance case, token and client information distinguishes silent renewal from fresh interactive authentication; the observation “A trusted application receives a sudden increase in valid tokens for an account with no corresponding interactive logins” makes this corroboration choice the fitting one.
Incorrect Answers
A:For the alternative MFA fatigue notification storm situation, approval status and post-authentication resource actions determine whether access was granted; by contrast, for Unusual federation token issuance corroboration, token and client information distinguishes silent renewal from fresh interactive authentication.
C:For the alternative Impossible travel sign-in correlation situation, successful sessions are needed to assess account use; failed attempts cannot establish actual movement; by contrast, for Unusual federation token issuance corroboration, token and client information distinguishes silent renewal from fresh interactive authentication.
D:In Dormant account revival, last-use history and privilege explain why the return to activity is risky; the reported Unusual federation token issuance case calls for a different corroboration conclusion because token and client information distinguishes silent renewal from fresh interactive authentication.
Question 1090
An external monitoring provider forwards high-severity notices but cannot explain who is permitted to isolate a customer workstation. Which source would most directly corroborate the observation?
- Cross-team case history and assignment changes
- After-hours alert arrival and acknowledgement records
- Shift handover notes with linked case artifacts
- Ticket schemas and severity mapping from each unit
- Provider statement of work and escalation matrix
Explanation
Correct Answer
E:In the Managed SOC provider accountability case, those documents reveal whether the provider may only notify or can execute authorized containment; the observation “An external monitoring provider forwards high-severity notices but cannot explain who is permitted to isolate a customer workstation” makes this corroboration choice the fitting one.
Incorrect Answers
A:For corroboration in Managed SOC provider accountability, Co-managed SOC handoff is a different mechanism: case records show missing attachments or ownership changes when identity and network alerts converge; here, those documents reveal whether the provider may only notify or can execute authorized containment.
B:The choice is relevant to In-house SOC staffing, where ticket timestamps expose the gap between event creation and a human taking responsibility; for corroboration in Managed SOC provider accountability, those documents reveal whether the provider may only notify or can execute authorized containment.
C:For corroboration in Managed SOC provider accountability, Follow-the-sun SOC transfer is a different mechanism: the notes should identify the owner, current hypothesis, containment status and next decision; here, those documents reveal whether the provider may only notify or can execute authorized containment.
D:The choice is relevant to Virtual SOC tool integration, where differences in mandatory fields or classifications explain why cross-unit prioritization fails; for corroboration in Managed SOC provider accountability, those documents reveal whether the provider may only notify or can execute authorized containment.