From Last week:
- We set the target release, even w/o approval.
- There are dedicated fields in Jira for tracking CSP approval, details, rejection comments, etc. We will fill these in as approval is requested and approved/rejected
- There's a bunch of administrative overhead (test plans, rollback, etc.) required prior to requesting approval for CSP inclusion... in some cases this paperwork is not yet ready, which is why we haven't requested CSP approval yet.
- If a Jira is specific to a single module, the responsible team's PO will request CSP approval
- If the Jira is cross-cutting/affects multiple modules, the Security Team will make the request (assuming it's security related!)
Denis Kovtun pulled together a document to help clarify this process and ensure everyone involved is aligned:
Clarification on CSP process related to security issues
Common Vulnerabilities and Exposures CVE treatment requires work in module(s) of one Development team
If Security team considers the vulnerability (CVE) as required for inclusion in CSP and CVE impacts only module(s) of one development team, they need to create a jira with the following data:
- label “security-reviewed”
- priority
- recommended release/CSP
- information on the CVE and its impact
- dependent tickets if any
- Security team has to add clarification to the ticket as much as possible
PO of the development team who is responsible for the module, will consult with TL/SA/QA and fill justification in CSP Request Details field according to process:
https://folio-org.atlassian.net/wiki/display/REL/Critical+Service+Patch+Process
Security team will need to fully support the team (consult) on CVE specifics (impact and treatment).
All the process logistics stays intact, that is it is PO who will need to drive request via approval and jira completion.
CVE treatment requires work in modules of several Development teams
If Security team considers the CVE as required for inclusion in CSP and CVE impacts modules of several development teams, Security team needs to create a jira(s) with the required data and seek approval from RMS panel according to the process.
In case Security team creates one “umbrella” ticket and gets approval for it, they need to prepare child jiras per impacted modules and link those with the parent. Security team needs to notify POs/SMs regarding the scope of work and provide necessary advice on a need basis.
Notes:
- Overall the team agrees to this process.
- Craig McNally to clarify with Denis whether or not it's acceptable to use existing JIRAs, or if we need to create dedicated ones per:
they need to create a jira with the following data
- Craig McNally clarified this point with Denis and it's acceptable to repurpose the Jira, or create additional jiras as needed, keeping the oringal one as an umbrella. This is essentially what we're already doing, so no changes are required on our side.