Question 120
The working hypothesis concerns STIX structured sharing. The initial finding is: Threat objects lack standardized relationships and machine-readable semantics. Which evidence should investigators prioritize?
- Indicator first-seen, last-seen, source confidence and current ownership
- TAXII collection metadata, authentication and poll cursor behavior
- Shared objects' types, relationships and version identifiers
- TIP indicator history, source mappings, expiration and enrichment records
- Report markings, intended audience and partner distribution agreement
Explanation
Correct Answer
C:Schema consistency is necessary for downstream systems to interpret evidence. This is particularly useful after the initial sign of threat objects lack standardized relationships and machine-readable semantics; the two forms of evidence test different parts of the case.
Incorrect Answers
A:This relates to IOC expiration: temporal context determines whether a reputation claim remains relevant; the STIX structured sharing question instead requires independently corroborating the suspected behavior, specifically shared objects' types, relationships and version identifiers.
B:For TAXII feed transport, collection scope and checkpoints ensure reliable controlled ingestion; here the narrower objective is independently corroborating the suspected behavior in STIX structured sharing, best addressed by shared objects' types, relationships and version identifiers.
D:A coherent indicator lifecycle supports reliable downstream decisions, which would be relevant to threat intelligence platform, but not the STIX structured sharing scenario that requires shared objects' types, relationships and version identifiers.
E:Release decisions must reflect both markings and contractual restrictions; prioritizing that TLP handling mechanism would leave this STIX structured sharing decision unresolved because shared objects' types, relationships and version identifiers is the direct fit.
Question 121
During an investigation of MITRE ATTACK mapping, the SOC validates this finding: A broad malware label does not describe the detected adversary technique. What should the response owner do next?
- Tune deviation thresholds against the developer's established normal behavior
- Map the detection to the supported ATT&CK technique and note telemetry prerequisites
- Treat generated logic as an untrusted draft requiring human review and backtesting
- Translate the rule and test it against native SIEM events
Explanation
Correct Answer
B:Adding many ATT&CK tags without evidence inflates coverage metrics. For safe case progression, preserve the evidence and later verify technique simulations produce mapped alerts and the mapping survives peer review.
Incorrect Answers
A:Permanent broad exclusions would hide malicious shifts in the same role; this evidence or action is associated with behavioral baselines, whereas the case concerns MITRE ATTACK mapping and calls for map the detection to the supported ATT&CK technique and note telemetry prerequisites.
C:For AI-generated SIEM logic, automatically deploying AI output risks false negatives and operational noise; here the narrower objective is choosing the immediate operational response in MITRE ATTACK mapping, best addressed by map the detection to the supported ATT&CK technique and note telemetry prerequisites.
D:The alternative concerns sigma rule portability: copying a query without checking source schemas can produce silent misses; however, the described MITRE ATTACK mapping situation calls for map the detection to the supported ATT&CK technique and note telemetry prerequisites.
Question 122
The working hypothesis concerns MITRE ATTACK mapping. The initial finding is: A broad malware label does not describe the detected adversary technique. Which evidence should investigators prioritize?
- Rule condition and ATT&CK technique evidence with stated assumptions
- Real ingestion schema, known-positive events and adversarial negative examples
- Search job runtime, scanned byte count and result cardinality
- Sigma selectors, logsource categories and target schema field mapping
Explanation
Correct Answer
A:A technique tag must match observed behavior, not an unsupported kill-chain claim. This is particularly useful after the initial sign of a broad malware label does not describe the detected adversary technique; the two forms of evidence test different parts of the case.
Incorrect Answers
B:Field validation and test data reveal hallucinated query behavior, which would be relevant to AI-generated SIEM logic, but not the MITRE ATTACK mapping scenario that requires rule condition and ATT&CK technique evidence with stated assumptions.
C:Performance data identifies whether the rule is computationally sustainable; prioritizing that analytic query cost mechanism would leave this MITRE ATTACK mapping decision unresolved because rule condition and ATT&CK technique evidence with stated assumptions is the direct fit.
D:Transportable syntax alone does not guarantee equivalent logs across platforms; that is suited to investigating sigma rule portability, whereas the MITRE ATTACK mapping case requires rule condition and ATT&CK technique evidence with stated assumptions for independently corroborating the suspected behavior.
Question 123
A responder investigating data-integrity validation has corroborated this finding: Application availability does not prove data completeness or integrity. What action belongs next in the approved workflow?
- Restrict vulnerable exposure and track a dated remediation exception
- Apply time-bounded heightened detection across impacted systems
- Validate directory security state and rotate affected secrets before reopening access
- Reconcile data against known-good transaction sources before declaring recovery
Explanation
Correct Answer
D:A green database service light is insufficient for business assurance. Operational success is not assumed until critical records and transactions match approved recovery tolerances, the relevant outcome for this response.
Incorrect Answers
A:For compensating controls, merely accepting risk verbally provides no technical protection or accountability; here the narrower objective is choosing the immediate operational response in data-integrity validation, best addressed by reconcile data against known-good transaction sources before declaring recovery.
B:Prematurely disabling all rules at closure removes visibility during reinfection risk; this evidence or action is associated with postincident monitoring, whereas the case concerns data-integrity validation and calls for reconcile data against known-good transaction sources before declaring recovery.
C:The alternative concerns recovered identity service: only checking domain-controller uptime ignores remaining unauthorized privileges; however, the described data-integrity validation situation calls for reconcile data against known-good transaction sources before declaring recovery.
Question 124
A SOC analyst is investigating tactical threat intelligence and records this observation: A repeatable adversary technique is more durable than one destination IP. Which source or comparison would most directly corroborate it?
- Process trees, known technique descriptions and observed telemetry fields
- Sourced industry trends, adversary targeting and confidence assessments
- Payment-system threat scenarios, asset exposure and stakeholder decisions
- Campaign reporting, victimology and ATT&CK behavior mapping
Explanation
Correct Answer
A:Technical behavior must be mappable to available enterprise data. Linking these records back to a repeatable adversary technique is more durable than one destination IP reduces reliance on an isolated indicator.
Incorrect Answers
B:Decision-makers need credible context and uncertainty instead of raw indicators; this evidence or action is associated with strategic threat intelligence, whereas the case concerns tactical threat intelligence and calls for process trees, known technique descriptions and observed telemetry fields.
C:Useful requirements start with protected services and expected consumer actions; that is suited to investigating priority intelligence requirement, whereas the tactical threat intelligence case requires process trees, known technique descriptions and observed telemetry fields for independently corroborating the suspected behavior.
D:For operational threat intelligence, verified TTPs are more durable context than isolated expiring indicators; here the narrower objective is independently corroborating the suspected behavior in tactical threat intelligence, best addressed by process trees, known technique descriptions and observed telemetry fields.
Question 125
A TIP feed will automatically enrich SIEM alerts and sometimes trigger blocks. Which THREE safeguards protect decision quality? Choose THREE.
- Discard all intelligence source names to make the feed visually shorter
- Expire or revalidate time-sensitive indicators before continued enforcement
- Never test an indicator policy against known benign business services
- Include confidence and contextual risk thresholds for disruptive actions
- Block every feed entry without inspecting its intended target or age
- Retain source provenance and evidence for each indicator
Explanation
Correct Answers
B:Addresses and domains can change ownership, so permanent deny decisions can affect innocent parties. Lifecycle management reduces stale matches.
D:A low-confidence feed hit should not carry the same response as verified active compromise. Policy should reflect impact and uncertainty.
F:Analysts must know why a match was labeled malicious and whether independent sources corroborate it. Attribution-less entries are poor enforcement input.
Incorrect Answers
A:Removing provenance prevents later credibility review and incident audit. Compact display should preserve source metadata behind the scenes.
C:Skipping negative tests allows false positives to disrupt important applications. Validation must include legitimate traffic.
E:Unconditional enforcement amplifies erroneous and poisoned indicators. Context-aware validation is especially important for shared infrastructure.
Question 126
Analysts confirm the following observation: Incoming events accumulate while searchable event volume stays flat. Supporting material includes: Collector receipts, indexing queue metrics and storage pressure. Which operational action addresses the issue most directly?
- Use a managed scalable deployment with volume budgets and tiering
- Deploy the required SIEM processing and storage within the controlled facility
- Design, test, approve and version the rule before production activation
- Increase processing capacity or resolve the indexing bottleneck
- Assign maintenance ownership and retire or revise outdated rule conditions
Explanation
Correct Answer
D:Changing detection logic cannot repair a blocked indexing stage. The response must subsequently be checked by confirming a generated canary event becomes searchable within latency objectives; otherwise the original exposure may persist.
Incorrect Answers
A:Scaling alone cannot correct noisy or unnecessary telemetry collection, which would be relevant to cloud SIEM elasticity, but not the collector versus search tier scenario that requires increase processing capacity or resolve the indexing bottleneck.
B:For on-premise SIEM tradeoff, an internet-only administration plane fails the site's isolation constraint; here the narrower objective is choosing the immediate operational response in collector versus search tier, best addressed by increase processing capacity or resolve the indexing bottleneck.
C:An unreviewed query risks blind spots or uncontrolled false positives; prioritizing that SIEM rule lifecycle mechanism would leave this collector versus search tier decision unresolved because increase processing capacity or resolve the indexing bottleneck is the direct fit.
E:This relates to security use case owner: a SOC needs lifecycle governance rather than accumulating permanent unused searches; the collector versus search tier question instead requires choosing the immediate operational response, specifically increase processing capacity or resolve the indexing bottleneck.
Question 127
An automated client overwhelms a login API with rapid failed requests across many accounts. The team takes this action: Apply adaptive throttling and strengthen account abuse detections. Which check most directly verifies the intended outcome?
- Cross-tenant requests return denial and authorized tenant reads still succeed
- Exploit tests fail and database access confirms no further unauthorized reads
- Legitimate sign-in works while simulated abuse receives appropriate limits
- No unapproved executable files remain and upload controls reject the exploit pattern
Explanation
Correct Answer
C:Measure both attack suppression and normal-user success. That verification specifically tests whether the intervention to apply adaptive throttling and strengthen account abuse detections corrected the issue rather than merely hiding an alert.
Incorrect Answers
A:A passing authentication test does not validate authorization, which would be relevant to broken object authorization, but not the API rate-limit incident scenario that requires legitimate sign-in works while simulated abuse receives appropriate limits.
B:A hidden error page is not evidence of secure query construction; that is suited to investigating active SQL injection, whereas the API rate-limit incident case requires legitimate sign-in works while simulated abuse receives appropriate limits for demonstrating that the remediation or control took effect.
D:For web shell discovery, a clean front page does not demonstrate web-tier security; here the narrower objective is demonstrating that the remediation or control took effect in API rate-limit incident, best addressed by legitimate sign-in works while simulated abuse receives appropriate limits.
Question 128
The working hypothesis concerns stored XSS incident. The initial finding is: Untrusted stored markup is rendered as active script for visitors. Which evidence should investigators prioritize?
- Web server file metadata, process ancestry, access logs and upload path
- Stored record, browser evidence, CSP reports and affected users
- Access logs with actor, requested object and owner tenant
- Web request payloads, database statement logs and affected record counts
Explanation
Correct Answer
B:Victim execution and persistence must be verified separately. The result can be compared with untrusted stored markup is rendered as active script for visitors to verify that the suspected mechanism is actually present.
Incorrect Answers
A:The artifacts identify initial access and all subsequent commands; that is suited to investigating web shell discovery, whereas the stored XSS incident case requires stored record, browser evidence, CSP reports and affected users for independently corroborating the suspected behavior.
C:The impact depends on which unauthorized resources were accessed; this evidence or action is associated with broken object authorization, whereas the case concerns stored XSS incident and calls for stored record, browser evidence, CSP reports and affected users.
D:Backend access evidence is needed to establish what the attacker retrieved; applied to this stored XSS incident case, it addresses active SQL injection instead of the required step: stored record, browser evidence, CSP reports and affected users.
Question 129
During an investigation of distributed denial of service, the SOC validates this finding: A multi-origin traffic surge exhausts service or upstream capacity. What should the response owner do next?
- Investigate the originating process and restrict suspicious domain resolution
- Engage upstream DDoS mitigation and activate rate or challenge controls
- Quarantine the offending switch port and correct trusted gateway bindings
- Check whether the source is an approved scanner and isolate if malicious
Explanation
Correct Answer
B:Filtering at a saturated local link alone may not restore availability. The response must subsequently be checked by confirming legitimate user success rates and backend capacity return to baseline; otherwise the original exposure may persist.
Incorrect Answers
A:The alternative concerns DNS tunneling: simply blocking one record type may miss alternate DNS-based command channels; however, the described distributed denial of service situation calls for engage upstream DDoS mitigation and activate rate or challenge controls.
C:Stopping forged ARP announcements removes the immediate layer-two redirection path; applied to this distributed denial of service case, it addresses ARP cache poisoning instead of the required step: engage upstream DDoS mitigation and activate rate or challenge controls.
D:This relates to vertical port scan: authorization context prevents disruption of legitimate scheduled assessments; the distributed denial of service question instead requires choosing the immediate operational response, specifically engage upstream DDoS mitigation and activate rate or challenge controls.
Question 130
Responders suspect database audit records based on this observation: Database audit trails capture statements or object access by principal. Which artifact should be examined first?
- Message-ID, Authentication-Results and URL-scanning verdicts
- Apache request target, vhost, client IP and status with server error logs
- Database principal, statement type, table and transaction timing
- IIS URI stem, query, status, client IP and application error log
Explanation
Correct Answer
C:Query contents and authorization context distinguish routine reports from extraction. The result can be compared with database audit trails capture statements or object access by principal to verify that the suspected mechanism is actually present.
Incorrect Answers
A:Joining headers and delivery outcomes distinguishes spoofing from legitimate aliases; prioritizing that mail transport logs mechanism would leave this database audit records decision unresolved because database principal, statement type, table and transaction timing is the direct fit.
B:For Apache access logs, a 404 alone is not proof of exploitation or filesystem access; here the narrower objective is independently corroborating the suspected behavior in database audit records, best addressed by database principal, statement type, table and transaction timing.
D:Cross-source analysis separates malicious requests from application defects; this evidence or action is associated with IIS request logging, whereas the case concerns database audit records and calls for database principal, statement type, table and transaction timing.