# About Remediation vs Mitigation

Canonical: https://remediationvsmitigation.com/about/

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.

## What is on the site

- The [Decision Table](https://remediationvsmitigation.com/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](https://remediationvsmitigation.com/risk-acceptance-form/) and the [exception register](https://remediationvsmitigation.com/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](https://remediationvsmitigation.com/guides/difference-between-remediation-and-mitigation/), [workaround vs mitigation](https://remediationvsmitigation.com/guides/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](https://remediationvsmitigation.com/privacy/) lists the fields.

Data and forms are published under [Creative Commons Attribution 4.0](https://creativecommons.org/licenses/by/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](https://remediationvsmitigation.com/terms/).

## Method and contact

Every fact carries a source URL and the read date 19 Nov 2026. The [editorial policy](https://remediationvsmitigation.com/editorial-policy/) sets the rules for sources and wording. Questions and corrections go to [editor@remediationvsmitigation.com](mailto:editor@remediationvsmitigation.com); the [contact page](https://remediationvsmitigation.com/contact/) says what to include.

## Sources

- AWS, CloudFront standard logging reference: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/standard-logs-reference.html (read 19 Nov 2026)
- Creative Commons, Attribution 4.0 International deed: https://creativecommons.org/licenses/by/4.0/ (read 19 Nov 2026)

Last reviewed 19 Nov 2026

## Related

- [Editorial Policy: Sources, Labels and Corrections](https://remediationvsmitigation.com/editorial-policy/index.md)
- [Privacy: Cookies, Logs and the 400-Day Limit](https://remediationvsmitigation.com/privacy/index.md)
- [Decision Table: Remediate, Mitigate or Accept by Situation](https://remediationvsmitigation.com/decision-table/index.md)
