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

Define communications strategy (blog posts, social media posts...) after a CVE is released #63

Open
Tracked by #59
mx-psi opened this issue Aug 13, 2024 · 1 comment
Assignees

Comments

@mx-psi
Copy link
Member

mx-psi commented Aug 13, 2024

For CVE-2024-36129 we also published a blog post to spread the word and provide further ciontext about a vulnerability. This may be a good practice (specially for High/Critical security vuilnerabilities). Having a guideline about the content and timing of such blog posts as well as when they are advisable would be helpful.

@jpkrohling
Copy link
Member

I'll work on a paragraph for this as part of "Fix Disclosure Process" once we sort out #61 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants