Security Incidents

Handling a security incident: close it, queue it, or contain it.

An alert has fired. What should be done?

Input
The alertwhat fired, on which asset, and when
The assetits environment, tier and owner
Open ticketschange requests and incidents already in flight
Registered devicesthe hardware this person is known to use
Scheduled maintenancework someone booked in advance
Standing authorizationswho may do what, and until when
Output one of
AUTO CLOSENOTIFY USERESCALATE TIER2KILL PROCESSDISABLE ACCOUNTESCALATE URGENT
Lens
Security Incidents: accuracy against cost and time
TypeSafeOpenAIAnthropicFireworksworkflowprompt
frontier: nothing is both cheaper and more accurate
10%30%50%70%$0.0001$0.001$0.01$0.1cost per case, USD (log)accuracyhaiku 4.5 · workflow · 58.8% · $0.0047 · 3.4 shaiku 4.5haiku 4.5 · prompt · 17.1% · $0.0068 · 4.6 shaiku 4.5opus 5 · workflow · 66.2% · $0.0574 · 15.1 sopus 5 · prompt · 62.9% · $0.0619 · 13.5 sopus 5sonnet 5 · workflow · 60.8% · $0.0271 · 18.9 ssonnet 5sonnet 5 · prompt · 51.7% · $0.0506 · 37.5 ssonnet 5DS v4 flash · workflow · 37.9% · $0.0032 · 37.4 sDS v4 flashDS v4 flash · prompt · 44.6% · $0.0037 · 41.9 sDS v4 flashDS v4 pro · workflow · 41.7% · $0.0234 · 60.0 sDS v4 proDS v4 pro · prompt · 37.1% · $0.0267 · 66.3 sDS v4 proluna · workflow · 52.1% · $0.0013 · 7.0 slunaluna · prompt · 29.6% · $0.0021 · 13.4 slunasol · workflow · 62.5% · $0.0295 · 8.5 ssol · prompt · 45.8% · $0.0472 · 14.0 ssolterra · workflow · 51.2% · $0.0119 · 5.7 sterraterra · prompt · 45.4% · $0.0140 · 7.1 sterraJev · workflow · 61.7% · $0.0001 · 0.3 sopus 5solJev

The workflow

1
Read the alert

Three questions about the alert and the records joined to it: was the activity unauthorized, does a record explain it, and how strong is the evidence?

2
Close, queue, or act

The code combines the three answers with how important the machine is and where it runs. Borderline identity alerts also notify the user.

3
The state of the incident

Acting opens eleven more questions: credentials, live sessions, mail, anything left behind to run later, processes, network traffic, and how far the activity spread.

4
Choose the response

The playbook takes the first group whose conditions are met, then the strongest step in it that still applies. When no group applies, the alert is escalated.

One alertthe alert · the asset it firedon · the tickets,registrations, schedules andauthorizations joined to itIs this unauthorized activity?Three readings of the alert:reads the alert and the records the pipeline joined to itsomeone was doing something they were not authorizedto doa specific record accounts for this activity, inadvancehow strong the evidence is, from speculative toconfirmedcode reads the asset's environment and tier, and the detector's domainClose, queue, or act?closeprobably authorized, a record explainsit, and not a domain controllerAUTO CLOSEqueueeverything in betweenAn identity alert inthe grey zone (0.15–0.60)?yesNOTIFY USERnoESCALATE TIER2act: probably unauthorized (P > 0.75)What state is the incident in?Eleven readings of the incident:reads the same alert and records, now describing the state of theincidentcredentials have reached someone unauthorizeda live session or token is being used by an attacker nowmalicious mail is sitting in inboxessomething would bring the activity back after a reboota malicious process or task is running right nowdata or command traffic is leaving to an attackerdestinationthe attacker changed configuration that persists on itsownit is happening now, or about to, rather than finishedit has reached beyond the entity that was flaggedhow far it reaches: one entity, a workgroup, or the wholeorganizationwhat kind of attack: host compromise, account takeover,mail campaign, or exfiltrationTake the first group that applies, then its strongest action whose conditions hold:1 · data is leaving now: the whole organization's reach blocks the destination;otherwise this asset's egressBLOCK DESTINATIONBLOCK EGRESS ASSET2 · the attacker has access: a spreading live session locks the account; leakedcloud credentials are revoked; else sessions; else re-authenticationDISABLE ACCOUNTREVOKE ACCESS KEYREVOKE SESSIONSREQUIRE REAUTH3 · malicious mail is delivered: a campaign in several mailboxes blocks the sender;clearly malicious mail is purged; else quarantinedBLOCK SENDERPURGE MAILBOXESQUARANTINE MESSAGE4 · the host is compromised: live persistence isolates the host, never a loneproduction system; else kill the process; else quarantine the fileISOLATE HOSTKILL PROCESSQUARANTINE FILE5 · configuration was changed: forwarding rules, delegations or consents are removedREMOVE FORWARDING RULESno group appliesESCALATE URGENT1READ THE ALERT2CLOSE, QUEUE, OR ACT3THE STATE OF THE INCIDENT4CHOOSE THE RESPONSE
ActionCloseQueuePageLight containmentHeavy containment
QuestionsNoulScoreChoice