NightWatch NIGHTWATCH SOC
checking sign-in…

Events and sourcesEvery event a source reported, grouped by rule and subject, with the case each group was filed under. Read-only: cases are worked under Incidents.

What the sources sent in the last 24 hours, and whether every source is delivering.

Loading…

Event streamOne row per rule and subject: the events intake grouped under one correlation key and filed under one case. A failing security control is one row per control, account and region, so it can cover several assets; its title then names the control and says how many assets. Count is how many events the row holds in this window; first and last seen are when the sources observed them. New: its case is open and no person’s action is recorded on it. Triaged: a person acted on its case. Closed: its case closed with no person’s action recorded. No case: none was opened for these events. Rule provenance: where the rule its case was matched to came from, a Legacy Provider rule as handed off, one we adapted, or our own.

Operational · loading…

Loading events…

An event becomes an incident when a person declares it.Every event is filed under a case as it arrives, linked under Incident; it becomes an incident only when a person declares its case one on the case page, with a basis, and it is dismissed when a person closes its case as a false positive or as benign and expected.

Grouped events in the chosen view, one page at a time (25, 50 or 100 rows, or the first 500), in the order the summary above states. Open a row for its detail.
EventSourceSeverityStateCountSeenCaseActions
Loading events…
SOCIncidentsRespondHealth