Question 720
During an approved content promotion readiness review for Orion Cloud Services in its central logging workspace, a security telemetry analyst reviews the Falcon Next-Gen SIEM workflow. The concrete observation is: A shared SIEM dashboard displays full authentication tokens from raw application logs to staff outside the need-to-know group. The authorized diagnostic packet is NGSIEM-LAB-0180. The source owner has provided a dated format contract and a controlled representative sample. Maintain the intended search-domain and data-retention boundary. Which repeatable safeguard BEST prevents this specific SIEM engineering failure from recurring?
Explanation
Correct Answer
Option A is best answer to this recurrence prevention question. The repeatable safeguard is: Audit dashboard sharing and field projection for sensitive-data leaks. It mitigates Panel field selection exposes secret-bearing raw fields beyond the legitimate analytic purpose, which produced the observed failure (A shared SIEM dashboard displays full authentication tokens from raw application logs to staff outside the need-to-know group). It should continue to be monitored using direct evidence such as Read-only viewers can analyze login errors without seeing raw tokens.
Incorrect Answers
Option B would guard against a different condition: A trend panel graphs categorical severity as a continuous numeric measurement and misleads reviewers. The failure mechanism here is: Panel field selection exposes secret-bearing raw fields beyond the legitimate analytic purpose. The directly relevant recurrence control is: Audit dashboard sharing and field projection for sensitive-data leaks.
Option C would guard against a different condition: A custom source dashboard loses all host counts after its parser maps hostName to a normalized host field. The failure mechanism here is: Panel field selection exposes secret-bearing raw fields beyond the legitimate analytic purpose. The directly relevant recurrence control is: Audit dashboard sharing and field projection for sensitive-data leaks.
Option D would guard against a different condition: An engineer has endpoint and firewall records linked by an IP but searches each source separately and misses the full timeline. The failure mechanism here is: Panel field selection exposes secret-bearing raw fields beyond the legitimate analytic purpose. The directly relevant recurrence control is: Audit dashboard sharing and field projection for sensitive-data leaks.