Skip to content

updated expectation management on sec issues #437

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.

Sign up for GitHub

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

Open
DaanHoogland wants to merge 1 commit into
base: staging-site
Choose a base branch
from
Open

updated expectation management on sec issues #437

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions src/pages/security.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,12 +39,16 @@ team](https://www.apache.org/security/) via email to
vulnerability, how it might be exploited, and any additional information that
might be useful.

Upon notification, the ASF security team will work with the CloudStack PMC
through validation and fixing the issue. If the issue is validated, it generally
takes 2-4 weeks from notification to public announcement of the vulnerability.
During this time, the team will communicate with you as they proceed through the
response procedure, and ask that the issue not be announced before an
agreed-upon date.
Upon notification, the ASF security team will work with the CloudStack
PMC through validation and fixing the issue. If the issue is
validated, it will still take time to fix the issue. The amount of
time depends on the availability of volunteers and number people
involved that have a stake in the issue. In later years it has turned
Comment on lines +44 to +46
Copy link
Copy Markdown
Member

@raboof raboof Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might make sense to mention that the round-trip time also depends on the severity of the issue? Hopefully severe issues won't be open for six months ;)

out to take up to six months, from notification to public announcement
Copy link
Copy Markdown

@borisstoyanov borisstoyanov Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to be specific here? I don't think we need to mention this whole sentence at all

of the vulnerability, due to parallel work on multiple issues. During
Comment on lines +47 to +48
Copy link
Copy Markdown
Contributor Author

@DaanHoogland DaanHoogland Jun 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
out to take up to six months, from notification to public announcement
of the vulnerability, due to parallel work on multiple issues. During
out to take up more and more time from notification to public announcement
of the vulnerability, due to parallel work on multiple issues. During

@borisstoyanov @raboof ?

this time, the team will communicate with you as they proceed through
the response procedure, and ask that the issue not be announced before
an agreed-upon date.

**Please do not create publicly-viewable JIRA tickets related to the issue**. If
validated, a JIRA ticket with the security flag set will be created for tracking
Expand Down
Loading