Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create on-call runbook/playbook #23

Closed
pshiu opened this issue Mar 8, 2023 · 8 comments
Closed

Create on-call runbook/playbook #23

pshiu opened this issue Mar 8, 2023 · 8 comments
Assignees

Comments

@pshiu
Copy link

pshiu commented Mar 8, 2023

We need a runbook so it's clear to working group members how to respond to security disclosures.

Some open questions from: https://openedx.atlassian.net/wiki/spaces/COMM/pages/3624140816/Security+Working+Group+Private:

  • How will we keep track of who is on-call?
  • Is there a need for the community to know who is on-call?
  • What are the expectations for on-call? Will there really be CAT-1s?
  • How will we know who is the maintainer of what repository?
@pshiu pshiu converted this from a draft issue Mar 8, 2023
@pshiu pshiu self-assigned this Apr 26, 2023
@pshiu pshiu moved this from Todo to In Progress in Security Working Group Apr 26, 2023
@pshiu
Copy link
Author

pshiu commented May 16, 2023

Started to address "What are the expectations for on-call?" in new section On-Call Duties section on our "For working group members" Confluence page.

@pshiu
Copy link
Author

pshiu commented May 25, 2023

Added runbook on finding a maintainer in our Security Playbooks.

@pshiu
Copy link
Author

pshiu commented Jun 5, 2023

@pshiu
Copy link
Author

pshiu commented Aug 23, 2023

Added section Forward a report to an operator or Axim.

@pshiu
Copy link
Author

pshiu commented Oct 4, 2023

Next steps:

  • @pshiu & @alangsto meet to compare current 2U practices
  • Meet with @feanil to brainstorm future improvements
  • Draft runbooks for review

@pshiu
Copy link
Author

pshiu commented Nov 15, 2023

@alangsto & I met and compiled the current 2U practices. We now need to compare them.

@pshiu
Copy link
Author

pshiu commented Nov 28, 2023

@alangsto & I met and added details to Security Playbooks – for Security WG members.

@pshiu
Copy link
Author

pshiu commented Dec 4, 2023

@feanil & I met and we worked on Common Issues.

@alangsto alangsto moved this from In Progress to Done in Security Working Group Dec 13, 2023
@feanil feanil closed this as completed Jan 31, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants