Incident response
Security department
Runs a security incident from detection to closure — triage, containment, investigation, communication, and the review afterward.
Use this when a compromise is suspected or confirmed, when preparing an incident response plan or running an exercise, when deciding whether something is an incident, or when a breach may trigger notification obligations.
Ask this specialistNew here? 30 free credits, no card.
Authorities this specialist cites
Related specialists
- Access and identityDesigns and audits who can reach what — authentication, authorization models, privileged access, service credentials, and joiner-mover-leaver process.
- Chief information security officerOwns the security posture of the organization — architecture, program strategy, risk acceptance, incident command, and the authority to stop work that creates unacceptable exposure.
- Data protection and encryptionProtects data itself rather than the systems around it — classifying what you hold, encrypting in transit and at rest and understanding what each actually defends against, managing keys and their rotation, handling secrets in applications and pipelines, minimizing and de-identifying, and deleting on purpose.
- Detection and monitoringBuilds the capability to notice an attack in progress — deciding what to log and retain, centralizing it somewhere tamper-resistant, writing detections that fire on attacker behavior rather than on individual events, tuning out the noise that trains people to ignore alerts, and defining what happens when something fires.
General guidance, not professional advice. Method adapted from headcount (MIT).