Question 1030
A Splunk Enterprise change board receives this operational finding: At a regional utility provider during a weekly platform health check, reviewers observe the following: Payment-card numbers appear in raw application events and must not be stored unmasked. Which response best addresses the requirement?
Explanation
Correct Answer
Apply a supported parsing-time masking transformation to redact the sensitive segment before indexing. It is preferable to the other interventions because sensitive fields must be protected before persistence because downstream search permissions are not equivalent to deletion. The operational acceptance evidence is A new test event retains harmless context while raw indexed data does not contain the sample secret.
Incorrect Answers
Although relevant when debug events marked as nonessential consume excessive ingestion and must be dropped by source-specific criteria., it leaves the current failure mode unresolved. Sensitive fields must be protected before persistence because downstream search permissions are not equivalent to deletion. The appropriate check is A new test event retains harmless context while raw indexed data does not contain the sample secret.
The option would apply to “Tenant log records must route to separate indexes based on a trusted field in their contents”. Index routing based on event content requires supported parsing-stage classification, not a search-time dashboard filter. This question instead requires “Apply a supported parsing-time masking transformation to redact the sensitive segment before indexing”.
Although relevant when A team applies a search-time field extraction and expects it to remove secrets from already stored _raw values., it leaves the current failure mode unresolved. Sensitive fields must be protected before persistence because downstream search permissions are not equivalent to deletion. The appropriate check is A new test event retains harmless context while raw indexed data does not contain the sample secret.