Skip to content

Instantly share code, notes, and snippets.

View aarongable's full-sized avatar
🔏

Aaron Gable aarongable

🔏
View GitHub Profile
@aarongable
aarongable / ccadb-incident-report.md
Last active August 7, 2023 22:30
Draft proposal for overhauling the CCADB Incident Reporting Requirements (https://www.ccadb.org/cas/incident-report)

Incidents

Incidents happen. Things do not always go as planned, and that can be okay. However, when incidents occur, the underlying issue (i.e., root cause) should be identified and remediated to discourage the incident from occurring again. Formally documenting the incident in a report encourages an understanding of all contributing root cause(s), and it presents the opportunity to clearly communicate a remediation plan to reduce the probability of its reoccurrence.

Depending on the root programs in which a CA Owner participates, it may be required to:

These reports provide lessons learned and transparency about the steps the CA takes to address the immediate issue and prevent future issues. If the underlying problem goes unfixed, then other issues that share the same root cause will subsequently surfa

Keybase proof

I hereby claim:

  • I am aarongable on github.
  • I am aarongable (https://keybase.io/aarongable) on keybase.
  • I have a public key whose fingerprint is FA0D D92C 1DAD AAF7 54E0 51E1 64E1 6A8E 282F B4AA

To claim this, I am signing this object: