- SOC analyst
- Junior
- 30 min
Unique failed login events
For failed authentication login actions, count distinct event IDs as attempts, grouped by src. Authentication exports can contain a duplicate of the same event. Count distinct event IDs when the task asks for attempts, and group by the source address. A failed logout must not become a login attempt. The boundary matters because an inflated count can make a benign source cross a detection threshold. Search the fictional records for the behavior described below. Return the fields or aggregate named in the task. If neither is specified, return every matching record with every field.
Skills and rubricUnique failed login events
- Authentication exports can contain a duplicate of the same event. Count distinct event IDs when the task asks for attempts, and group by the source address. A failed logout must not become a login attempt. The boundary matters because an inflated count can make a benign source cross a detection threshold.
- I rerun the behavior-based query against the new records and check the time window, fields and evidence identifiers because the old event IDs do not establish the same behavior in new data. I keep the required source and output scope.
- I retain the original records, the exact scope, my test and its result, plus the decision owner and unresolved limitation. That record lets another engineer repeat the check because a summary alone can hide a wrong filter, a missing source or an untested assumption.