Mitigate vs manage risk
Managing risk is the process NIST describes as framing, assessing, responding to and monitoring risk. Mitigating is one response inside it, beside accepting, avoiding, sharing and transferring. SP 800-40 Rev. 4 uses four responses for software flaws. One Cisco ISE flaw, CVE-2026-76460 (16 Sep 2026), is carried through every step below.
On this page
Managing is the process, mitigating is one response
NIST SP 800-39 names the process by its four parts: "frame, assess, respond to, and monitor risk". The glossary entry for risk response lists what the respond part can choose: "Accepting, avoiding, mitigating, sharing, or transferring risk to organizational operations, organizational assets, individuals, other organizations, or the Nation." Risk mitigation is defined in SP 800-30 Rev. 1 as "Prioritizing, evaluating, and implementing the appropriate risk-reducing controls/countermeasures recommended from the risk management process. A subset of Risk Response." (risk response, risk mitigation)
So the two words sit at different levels. "Manage" covers all four steps and every response. "Mitigate" is a choice made in step three. A register that has a column called "risk management" next to a column called "mitigation" is mixing a process with one of its outputs.
The four responses for a software vulnerability
SP 800-40 Rev. 4, Section 2.1, reduces the five to four. It also says that "By default, an organization accepts the risk posed by using its software."
| Response | SP 800-40 Rev. 4 wording | What it looks like on a finding |
|---|---|---|
| Accept | "Accept the risk from vulnerable software as is, such as by relying on existing security controls to prevent vulnerability exploitation or by determining that the potential impact is low enough that no additional action is needed" | A signed, dated exception |
| Mitigate | "Reduce the risk by eliminating the vulnerabilities (e.g., patching the vulnerable software, disabling a vulnerable feature, or upgrading to a newer software version without the vulnerabilities) and/or deploying additional security controls to reduce vulnerability exploitation" | A patch, a disabled feature or a control placed in front |
| Transfer | "Reduce the risk by sharing some of the consequences with another party, such as by purchasing cybersecurity insurance or by replacing conventional software installations with software-as-a-service (SaaS) usage where the SaaS vendor/managed service provider takes care of patching" | Insurance, or a move to a hosted service; see risk transfer vs risk acceptance |
| Avoid | "Ensure that the risk does not occur by eliminating the attack surface, such as by uninstalling the vulnerable software, decommissioning assets with the vulnerabilities, or disabling computing capabilities in assets that can function without them" | Uninstall or decommission; see the decommission row |
Inside this frame, patching is mitigation of the strongest kind: the publication says installing a patch or upgrading "are the only forms of risk response that can completely eliminate the vulnerabilities without removing functionality".
One finding taken through all four steps
On 16 Sep 2026 Cisco published advisory cisco-sa-ISE-ABP-VNSW7Tn5 for CVE-2026-76460, an authentication bypass in an Identity Services Engine (ISE) API. Cisco rates it CVSS base 10.0 and says its PSIRT is aware of active exploitation. CISA added it to KEV the same day with a due date of 19 Sep 2026. The advisory header reads "No workarounds available", but its Workarounds section adds: "However, there is a mitigation", which is to use infrastructure access control lists (iACLs) "to allow only required management and control plane traffic that is destined to the affected device". The estate below is invented: four ISE nodes, two on 3.3 Patch 11 and two on 3.4 Patch 6. Both are affected, one patch below the fixed releases in Cisco's advisory (3.3 Patch 12 and 3.4 Patch 7), and NVD lists them as the highest affected patches. The vendor and CISA dates are real.
| Date | Step | Owner | Record it leaves | How it usually fails |
|---|---|---|---|---|
| Before 16 Sep | Frame: the tolerance that the later decision uses | Risk owner | Acceptance criteria approved earlier: known-exploited flaws on a network-reachable system are never accepted without a compensating control | Tolerance written after the finding, so it is fitted to the answer wanted |
| 16 Sep | Assess: which nodes, how exposed | Vulnerability analyst | Four-node list with build, and the advisory ID. Every unpatched node is affected whatever its configuration, so the question is who can reach the API | Version list built but reachability left unanswered |
| 16 Sep | Respond, decide: mitigate in two parts, iACL now and patch by 19 Sep. Accept is out (exploited, a due date exists). Avoid is out (the nodes enforce network access). Transfer is out (no hosted service can replace them in three days) | Risk owner signs | Decision record: response, control, two dates, signer | Choice made in a chat with no signer or end date |
| 16 Sep | Respond, implement the iACL | Network engineer | Change ticket with the ACL text; a test from a network not on the list showing the API no longer answers. Cost: any admin station or integration not listed loses access | ACL written, never tested, or it blocks an integration that was never inventoried |
| 17 to 18 Sep | Respond, implement the fix: 3.3 Patch 12 and 3.4 Patch 7, two nodes at a time | ISE administrator | Build output per node after restart | One node missed because it sat in a lab VLAN |
| 18 Sep | Monitor: look for signs of compromise using Cisco's log-review steps | Security operations | Review note; if compromise is suspected Cisco recommends re-imaging the node | Patching treated as proof the node was clean |
| 19 Sep | Monitor: close the remediation, keep the ACL as hardening | Risk owner | Register line closed with four build numbers; residual risk noted on the residual risk page | Closing on the change ticket, not on the build output |
Cisco states the policy that makes this two-part: "Cisco considers any workarounds and mitigations (if applicable) to be temporary solutions until an upgrade to a fixed software release is available." The iACL is therefore a bridge with its own end date, not a closing state. See verifying a mitigation works for the test in the fourth row.
Writing the word in a register
SP 800-40 counts patching as mitigation; BOD 26-04 and FedRAMP's 2026 rules keep the words apart. In a register that auditors in either regime will read, put "remediate" on the line for a fix and "mitigate" on the line for a control, and never mark a finding closed on a mitigation alone. The quotations are in the difference guide.
Tactical and strategic
SP 800-39 adds a time scale. "Some risk response measures are tactical in nature (e.g., applying patches to identified vulnerabilities in organizational information systems) and may be implemented rather quickly." Lower-priority risks are not ignored, but "fewer resources might be directed" to them or they might be "addressed at a later time". The ISE case is tactical. The tolerance set in step one is the strategic part, and no single finding settles it. Inherent and residual risk on the record are covered in inherent versus residual risk.
Sources
- NIST CSRC glossary, risk response, read 19 Nov 2026
- NIST CSRC glossary, risk mitigation (SP 800-30 Rev. 1), read 19 Nov 2026
- NIST SP 800-40 Rev. 4, Section 2.1, read 19 Nov 2026
- NIST SP 800-39, Tasks 3-3 and 3-4, read 19 Nov 2026
- Cisco advisory cisco-sa-ISE-ABP-VNSW7Tn5 (CVE-2026-76460), read 19 Nov 2026
- CISA KEV entry for CVE-2026-76460, read 19 Nov 2026
- NVD record, CVE-2026-76460 (affected patch levels), read 19 Nov 2026
- CISA KEV feed, catalogVersion 2026.11.18, read 19 Nov 2026
Last reviewed