Skip to content

Commit aa2260c

Browse files
DaanHooglandDaan Hoogland
andauthored
update expectation management (#437)
Co-authored-by: Daan Hoogland <dahn@apache.org>
1 parent aee878b commit aa2260c

1 file changed

Lines changed: 10 additions & 6 deletions

File tree

‎src/pages/security.md‎

Lines changed: 10 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -39,12 +39,16 @@ team](https://www.apache.org/security/) via email to
3939
vulnerability, how it might be exploited, and any additional information that
4040
might be useful.
4141

42-
Upon notification, the ASF security team will work with the CloudStack PMC
43-
through validation and fixing the issue. If the issue is validated, it generally
44-
takes 2-4 weeks from notification to public announcement of the vulnerability.
45-
During this time, the team will communicate with you as they proceed through the
46-
response procedure, and ask that the issue not be announced before an
47-
agreed-upon date.
42+
Upon notification, the ASF security team will work with the CloudStack
43+
PMC through validation and fixing the issue. If the issue is
44+
validated, it will still take time to fix the issue. The amount of
45+
time depends on the availability of volunteers and number people
46+
involved that have a stake in the issue. In later years it has turned
47+
out to take up to six months, from notification to public announcement
48+
of the vulnerability, due to parallel work on multiple issues. During
49+
this time, the team will communicate with you as they proceed through
50+
the response procedure, and ask that the issue not be announced before
51+
an agreed-upon date.
4852

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

0 commit comments

Comments
 (0)