# Contact

Canonical: https://remediationvsmitigation.com/contact/

Mail editor@remediationvsmitigation.com for corrections, a source the site should read, or a question about reuse under CC BY 4.0. There is no contact form, because the site stores nothing from visitors; a message exists only in the mailbox. First edition 19 Nov 2026.

## Where to write

The one address is [editor@remediationvsmitigation.com](mailto:editor@remediationvsmitigation.com). The site has no contact form, no chat widget and no tracking script, so a message you send reaches only that mailbox and the mail systems that carry it. The decision tool and the risk acceptance form run in the browser; nothing typed into them is transmitted, so there is nothing to attach from them.

Four reasons to write and what to include. Read 19 Nov 2026.

| You want to | Put in the message | Where it is handled |
|---|---|---|
| Report an error | Page address, the sentence, the source URL with the right text, the date you read it | [Corrections](https://remediationvsmitigation.com/corrections/) |
| Suggest a source | The document, its URL, and the situation or control it bears on | [Editorial policy](https://remediationvsmitigation.com/editorial-policy/) |
| Reuse data or a form | What you will reuse and where the credit line will sit | [Terms](https://remediationvsmitigation.com/terms/) |
| Ask about log data | The date and time range, to match against CloudFront access log entries | [Privacy](https://remediationvsmitigation.com/privacy/) |

## What helps a report get checked

- Quote the exact text you think is wrong, not a summary of it.
- Give the source URL and the date you read it. Directives such as CISA BOD 26-04 and rules such as FedRAMP's 2026 consolidated rules can change, and the first edition reads them as of 19 Nov 2026.
- Say which situation or control the point bears on, for example the nine compensating control entries.
- Leave out exploit code, payloads and live vulnerability details; the site does not publish them and a report does not need them.

## What the address does not do

It does not give case-by-case advice on whether to patch, mitigate or accept a particular finding; the pages report where published guidance points, and the [decision table](https://remediationvsmitigation.com/decision-table/) shows the sources. A message and your address are kept in the mailbox like any email. Nothing is added to a mailing list. See the [privacy page](https://remediationvsmitigation.com/privacy/) for what the web server logs and for how long.

## Sources

- AWS, CloudFront standard logging reference: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/standard-logs-reference.html (read 19 Nov 2026)
- CISA, BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk (read 19 Nov 2026)
- FedRAMP, Consolidated Rules 2026: https://www.fedramp.gov/2026/providers/rev5/rules/vulnerability-detection-and-response/ (read 19 Nov 2026)

Last reviewed 19 Nov 2026

## Related

- [Corrections Log: How to Report an Error](https://remediationvsmitigation.com/corrections/index.md)
- [Privacy: Cookies, Logs and the 400-Day Limit](https://remediationvsmitigation.com/privacy/index.md)
- [Terms of Use and CC BY 4.0 License](https://remediationvsmitigation.com/terms/index.md)
