Files
nexus/sreweekly/markdown/183/03-for-cas-what-makes-a-good-incident-response.md
2026-09-12 17:23:01 +08:00

18 lines
701 B
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# For CAs: What makes a Good Incident Response?
- **期号**: SRE Weekly Issue #183(2019-09-01)
- **作者**: Ryan Sleevi
- **链接**: https://groups.google.com/forum/#!topic/mozilla.dev.security.policy/oP8XuNXrANw
## 简介
This is aimed at Certification Authorities dealing with TLS certificate misissuance issues and the like, but it very much applies to any kind of incident.
BONUS CONTENT: An incident report from LetsEncrypt just a few days later included this gem, exactly in line with what Ryan wrote:
> After initially confirming the report we reached out to multiple other CAs that we believed would also be affected.
## 正文
> ⚠️ 抓取失败:trafilatura returned empty