Question 290
A city transport operator forwards Windows security events. Observed: Forwarder inputs collect the wrong Windows Event Log channel and omit required security audit records. After the correction, which outcome establishes success for this case?
Explanation
Correct Answer
The specified outcome is: Newly generated test authentication events arrive with correct EventCode fields. It provides case-specific verification that the observed behavior (Forwarder inputs collect the wrong Windows Event Log channel and omit required security audit records) has changed appropriately.
Incorrect Answers
This result checks another issue, for which the observed symptom is: The new version fails to parse known sourcetypes because app-level props.conf was not migrated. It does not verify recovery for this situation: Forwarder inputs collect the wrong Windows Event Log channel and omit required security audit records. The relevant success check is: Newly generated test authentication events arrive with correct EventCode fields.
Option B would be useful evidence if the observed failure were “The universal forwarder runs but cannot read the target log because the service identity lacks filesystem permissions”: it checks “The forwarder reads the intended log without gaining broader filesystem privileges” after the action “Grant narrowly scoped file permissions and maintain the host's security model” addresses “File-monitor inputs require read access from the Splunk runtime identity”. But the current failure is “Forwarder inputs collect the wrong Windows Event Log channel and omit required security audit records”, linked to “Windows Event Log input channel selection determines collected event classes”. Here the targeted action is “Enable the specified Security channel and verify the relevant filters and permissions”, and the required proof is “Newly generated test authentication events arrive with correct EventCode fields”.
The proposed signal relates to: One client's HEC token defaults to an index not included in its role's write authorization. The evidence for this Splunk source case must instead show: Newly generated test authentication events arrive with correct EventCode fields.