risk acceptance
A written decision, owned by someone with the authority to make it, to live with a known risk instead of fixing it now.
In more detail
Accepting a risk is a legitimate answer to an open threat model question or a scanner finding with no fix, but only with a named owner, a reason and a date to revisit it. A risk written down and assigned to nobody is documented, not managed.
Examples
MAY_ACCEPT = {"low": {"IT manager", "CISO"}, "medium": {"CISO"}, "high": {"CISO", "risk committee"}}EX-103 bastion01 IT manager cannot accept high riskRelated terms
- risk treatment — The choice of what to do about a risk: reduce it with controls, transfer it, avoid it, or accept it.
- exemption — Formal, written permission for one system, person or group to depart from a policy or standard, usually for a limited time.
- risk owner — The named person accountable for managing a particular risk, including choosing its treatment and acting when it moves outside tolerance.
- risk appetite — The broad amount and type of risk an organisation's leaders are willing to take on while pursuing their goals.
- security exception — A recorded, time-limited decision to let a known finding through a gate, with a reason, an owner and an expiry date.
- threat model — A short, structured look at a design that asks what could go wrong and what you will do about it, before the thing is built.
Taught in
- Security Governance vs Security Management — Cybersecurity Fundamentals, GRC & Cryptography
- Enterprise Risk Registers & Treatment Plans — Cybersecurity Fundamentals, GRC & Cryptography
- The Threat Model Habit — Application Security & Threat Modeling for Engineers
- Image Scanning And Trivy — Application Security & Threat Modeling for Engineers
- How To Stop Drowning In Findings — Application Security & Threat Modeling for Engineers