incident
An unplanned event that degrades or interrupts a service for its users, or harms the security of systems or data.
In more detail
Declaring an incident is a decision: it names a lead, opens a record and starts the clock, and from then on the incident response process applies. Responding well starts with a shared description of impact, clear roles and one timeline. Afterwards a blameless review turns what happened into changes to the system.
Example
In AWS: An unplanned event that harms or threatens a service, such as an outage or a leaked credential, which people must respond to.Related terms
- runbook — A written, step-by-step procedure for a routine operation or for responding to a known kind of incident.
- AWS CloudTrail — The AWS service that records API calls made in an account: who called what, when, from where and with which result.
- on-call — Being the person responsible, for a set period, for responding when a production system raises an alert, often outside working hours.
- failed deployment recovery time — The time it takes to recover from a deployment that fails and needs immediate intervention in production.
- rollback — Returning a system to a previous known-good version after a bad change.
- outage — A period during which a service is unavailable or not working properly for its users.
- incident lifecycle — The stages of an incident: detection, declaration, mitigation, end of user impact and closure.
- postmortem — A written review after an incident that explains impact, timeline, contributing conditions and the follow-up actions that will change the system.
- incident commander — The person who coordinates an incident response: assigning roles, making decisions and keeping the response moving, rather than debugging.
- incident timeline — A timestamped record of what was observed, decided and done during an incident, from first symptom to recovery.
- event — Anything observable that happens on a system or network, such as one failed sign-in or one file being opened.
- adverse event — An event with a negative consequence, such as a crashed service or an account locked out by an attacker's guesses.
- incident response — The organised work of detecting, analysing, containing, removing and recovering from a security incident, then learning from it.
- CIA triad — The three core goals of security: confidentiality (only the right people see data), integrity (data is not wrongly changed) and availability (systems work when needed).
- observability — How well you can understand what a system is doing, and why, from the data it emits: mainly logs, metrics and traces.
Taught in
- Two Hundred Accounts And One Bad Deploy — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Recovery To RTO And RPO: Backups Nobody Could Delete — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Testing Resilience: The Experiment That Would Have Been The Outage — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Collecting Logs And Metrics: The Disk Nobody Measured — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Finding The Problem: The Composite Alarm That Stayed Quiet — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- EventBridge Rules: The Rule That Matched Nothing — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Remediation As Code: A Public Bucket Appears — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Troubleshooting Failed Deployments: Read The First Failure — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Incident Tooling: Eighteen Minutes To Find A Human — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Automating Data Protection: Keys, Secrets And A Partner Shortcut — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Security Hub, GuardDuty And Inspector: Signal, Noise And Response — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Auditing: Who Opened Port Twenty Two? — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Pipeline Security: The Build Role That Could Do Anything — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- Long-Stem Clinic: When Two Answers Both Work — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- The Full Mock And Your Review Plan — AWS Certified DevOps Engineer – Professional (DOP-C02) Exam Prep
- DORA Metrics: Measuring Your Pipeline — Continuous Integration & Continuous Delivery Pipelines
- Rolling Updates and Rollbacks — Continuous Integration & Continuous Delivery Pipelines
- Rolling Back Blue-Green — Continuous Integration & Continuous Delivery Pipelines
- Elasticity and Scale — Cloud Infrastructure & Hyperscaler Architecture
- The Shared Responsibility Model — Cloud Infrastructure & Hyperscaler Architecture
- IAM as the Foundation — Cloud Infrastructure & Hyperscaler Architecture
- Policies and Least Privilege — Cloud Infrastructure & Hyperscaler Architecture
- The Danger of Long-Lived Keys — Cloud Infrastructure & Hyperscaler Architecture
- Virtual Private Clouds — Cloud Infrastructure & Hyperscaler Architecture
- Subnets: Public and Private — Cloud Infrastructure & Hyperscaler Architecture
- Route Tables and Internet Gateways — Cloud Infrastructure & Hyperscaler Architecture
- Observability with CloudWatch — Cloud Infrastructure & Hyperscaler Architecture
- Metrics, Logs, and Alarms — Cloud Infrastructure & Hyperscaler Architecture
- Cost, Budgets, and Tagging — Cloud Infrastructure & Hyperscaler Architecture
- Infrastructure as Code (Handover to Terraform) — Cloud Infrastructure & Hyperscaler Architecture
- Instability: Change Fail Rate And Deployment Rework Rate — DevOps & Site Reliability Engineering
- Restoration: Failed Deployment Recovery Time — DevOps & Site Reliability Engineering
- On-Call And Incident Response — DevOps & Site Reliability Engineering
- The Incident Lifecycle — DevOps & Site Reliability Engineering
- The Blameless Postmortem — DevOps & Site Reliability Engineering
- Writing A Postmortem: The SRE Appendix — DevOps & Site Reliability Engineering
- Structured Logging And Why Text Fails — Full-Stack Observability: Metrics, Tracing & Logging
- Metric Types: Counters And Gauges — Full-Stack Observability: Metrics, Tracing & Logging
- Cardinality And How It Bankrupts You — Full-Stack Observability: Metrics, Tracing & Logging
- The Prometheus Exposition Format — Full-Stack Observability: Metrics, Tracing & Logging
- Dashboards That Answer Questions — Full-Stack Observability: Metrics, Tracing & Logging
- The OpenTelemetry Collector — Full-Stack Observability: Metrics, Tracing & Logging
- Alerting Rules And The For Duration — Full-Stack Observability: Metrics, Tracing & Logging
- On Call And Incident Command — Full-Stack Observability: Metrics, Tracing & Logging
- The Blameless Postmortem — Full-Stack Observability: Metrics, Tracing & Logging
- A Worked Example Postmortem — Full-Stack Observability: Metrics, Tracing & Logging
- SOC Operating Models, Tiers & Key Performance Metrics — Security Operations & Threat Hunting (SOC)
- SOC Runbooks, Shift Handoffs & Escalation Paths — Security Operations & Threat Hunting (SOC)
- YARA Rule Authoring & File Signature Matching — Security Operations & Threat Hunting (SOC)
- Cyber Kill Chain vs MITRE ATT&CK Framework — Security Operations & Threat Hunting (SOC)
- Adversary Tactics, Techniques & Procedures (TTP) Mapping — Security Operations & Threat Hunting (SOC)
- Indicator of Compromise Extraction & Threat Hunting Feeds — Security Operations & Threat Hunting (SOC)
- Tracking Advanced Persistent Threats & Profiles — Security Operations & Threat Hunting (SOC)
- Detecting Persistence: Tasks, Registry & Services — Security Operations & Threat Hunting (SOC)
- NIST SP 800-61 Incident Lifecycle & Management — Security Operations & Threat Hunting (SOC)
- Incident Triage, Severity Scoping & Communication — Security Operations & Threat Hunting (SOC)
- Containment & Eradication: Host, Net & Identity — Security Operations & Threat Hunting (SOC)
- Recovery & System Validation Testing — Security Operations & Threat Hunting (SOC)
- Post-Incident Review & Root Cause Analysis — Security Operations & Threat Hunting (SOC)
- Malware Triage: Hashes, Strings & Sandboxing — Security Operations & Threat Hunting (SOC)
- Requirements: The Constraints That Shape The System — Scalable System Design & Distributed Architecture
- Back Of The Envelope Estimation: Traffic And Throughput — Scalable System Design & Distributed Architecture
- Replication, Failover And Leader Election — Scalable System Design & Distributed Architecture
- Eventual Consistency And What It Costs A Product — Scalable System Design & Distributed Architecture
- Cache Invalidation And The Three Hard Cases — Scalable System Design & Distributed Architecture
- The Difference Between A Queue And A Log — Scalable System Design & Distributed Architecture
- Retries, Backoff And Jitter — Scalable System Design & Distributed Architecture
- Observability As A Design Input — Scalable System Design & Distributed Architecture
- Capacity Planning As A Design Input — Scalable System Design & Distributed Architecture
- Worked Design Three: A Metrics Ingestion Pipeline — Scalable System Design & Distributed Architecture
- Worked Design Three: Scaling The Metrics Pipeline — Scalable System Design & Distributed Architecture
References
- AWS Security Incident Response Guide
- NIST SP 800-61 Rev. 3: incident response recommendations
- Google SRE book: Managing incidents
- NIST glossary: incident
- Google SRE book: Being On-Call