About Remediation vs Mitigation
Remediation vs Mitigation is a reference on one choice about a security finding: fix it, reduce it for now, or accept it with a date. First edition 19 Nov 2026. It holds 13 situations, 9 controls and a 15-field risk acceptance form, all read from sources on that date.
On this page
What is on the site
- The Decision Table: 13 situations, each with the response the sources point to and the quotes behind it.
- Nine compensating control entries, each with what it changes, what it does not fix, how to verify it and the evidence to keep.
- The Risk Acceptance Form and the exception register: 15 fields, who may sign, and the longest durations any source sets.
- Guides that answer single questions, such as the difference between remediation and mitigation, workaround vs mitigation and what to do when no patch exists.
The site is about security findings only: a vulnerability or weakness found in software, a device or a service. It does not cover environmental cleanup, building work or any other meaning of the two words.
What it leaves out
It does not compare products in a list order, explain how vulnerabilities get severity numbers, or teach vulnerability management as a program. Those subjects have their own references. The site also gives no exploit code, proof-of-concept steps or payloads; a control is described by what it changes and how to verify it, never by how to attack the flaw.
How it is hosted
The site is a set of static files stored on Amazon S3 and served by Amazon CloudFront. It sets no cookies, runs no analytics and loads no third-party scripts. The decision tool and the risk acceptance form run in the browser and send nothing to a server. CloudFront access logs go to a private bucket and are deleted after 400 days; the privacy page lists the fields.
Data and forms are published under Creative Commons Attribution 4.0 (CC BY 4.0). Cite as: Remediation vs Mitigation, "<page title>", first edition 19 Nov 2026, remediationvsmitigation.com. Quoted passages from standards stay under their issuers' terms; see the terms.
Method and contact
Every fact carries a source URL and the read date 19 Nov 2026. The editorial policy sets the rules for sources and wording. Questions and corrections go to editor@remediationvsmitigation.com; the contact page says what to include.
Sources
- AWS, CloudFront standard logging reference, read 19 Nov 2026
- Creative Commons, Attribution 4.0 International deed, read 19 Nov 2026
Last reviewed