Update CA reaction rotation process to include FedRAMP vuln triage instructions
Why is this change being made?
This change does the following:
- Add instructions on completing the triage with the automation CLI on the 23rd of every month as defined by https://gitlab.com/gitlab-com/gl-security/security-assurance/security-compliance-commercial-and-dedicated/fedramp/fedramp-certification/-/issues/104+
- Add quick links to filter vulnerability reports by the
no longer detected
activity filter. This aids in prioritizing automatically fixed vulnerabilities to be marked as remediated.
- Add quick links to filter vulnerability reports by the
- Add a reference to the SLAs defined in the handbook.
- Update links to the analyzer and upstream reports to include container scanning projects now under CA.
Author Checklist
-
Provided a concise title for this Merge Request (MR) -
Added a description to this MR explaining the reasons for the proposed change, per say why, not just what - Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
-
Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI) - If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
Maintained by
section on the page being edited - If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
- If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the
-
If the changes affect team members, or warrant an announcement in another way, please consider posting an update in #whats-happening-at-gitlab linking to this MR - If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.
Edited by Oscar Tovar