Question 40
During an approved content promotion readiness review for Mariner Consulting in its production SOC telemetry repository, an incident automation engineer reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: An external incident-response contractor sees sensitive third-party records outside the approved investigation scope. The authorized diagnostic packet is NGSIEM-LAB-0010. The test environment uses nonproduction endpoints and no live employee credentials. Do not disable production detections without authorized approval. Which repeatable safeguard BEST prevents this specific SIEM engineering failure from recurring?
Explanation
Correct Answer
Option D is best answer to this recurrence prevention question. The repeatable safeguard is: Periodically audit access scope and service-user entitlements against contract and data-classification changes. It mitigates The user's Falcon SIEM role and accessible data scope were never reviewed against the contractual need-to-know, which produced the observed failure (An external incident-response contractor sees sensitive third-party records outside the approved investigation scope). It should continue to be monitored using direct evidence such as An approved test principal sees only authorized search results while a forbidden administrative operation remains denied.
Incorrect Answers
Option A would guard against a different condition: A new SIEM operator can edit correlation rules and data connection settings although their responsibility is to run read-only investigations. The failure mechanism here is: The user's Falcon SIEM role and accessible data scope were never reviewed against the contractual need-to-know. The directly relevant recurrence control is: Periodically audit access scope and service-user entitlements against contract and data-classification changes.
Option B would guard against a different condition: A parser developer needs to validate sample events but must not modify production correlation rules. The failure mechanism here is: The user's Falcon SIEM role and accessible data scope were never reviewed against the contractual need-to-know. The directly relevant recurrence control is: Periodically audit access scope and service-user entitlements against contract and data-classification changes.
Option C would guard against a different condition: One shared Falcon identity is used by engineering, threat hunting, and help-desk staff for SIEM changes. The failure mechanism here is: The user's Falcon SIEM role and accessible data scope were never reviewed against the contractual need-to-know. The directly relevant recurrence control is: Periodically audit access scope and service-user entitlements against contract and data-classification changes.