Create a control for incident response procedures
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 166
- Forks
- 44
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 13
Description
In the discussion of #302 in this week's meeting, we agreed it was worth entertaining a proposal for a control to cover:
Incident Response - We talk about having a security policy (OSPS-VM-01, OSPS-VM-02) but don't talk about what to do/prepare for incidents? What happens if your keys get compromised? What do you do if someone breaks into your CI? We could add some instructions for folks to have prepared for the day when things go bad.
@david-a-wheeler specifically noted that he would like to see an example of an acceptable policy at the time a control is proposed.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with issue #302 and the meeting discussion referenced here; identify the expected scope for an incident-response control and review the OSPS-VM-01/02 policy context. Done means a proposed control includes an example of an acceptable incident-response policy, as requested by David Wheeler.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100