Party Bus Retention Policies
Purpose
This document describes the Party Bus retention policies.
Tool Retention Policies
| Policy Name | Resource/Tool | Timeframe | Responsibility |
|---|---|---|---|
| EBS Volume Snapshot | AWS | 15 Days | Party Bus Operations |
| Deployment Image | Gitlab | 15 Days | Mission DevOps Team (MDO) |
| Data Retention | RDS S3 Buckets Gitlab Repos | 3 Years | Mission DevOps Team (MDO) |
Cyber Enforcement
| Policy Name | Action | Timeframe | Responsibility |
|---|---|---|---|
| 7-Day Pipeline Execution | Automation execution of pipelines every 7 days. | Every 7 days | Mission DevOps (MDO) |
| Crictical CVEs | Enforce fixing or whitelisting Critical and High CVEs. | Every day | Mission DevOps Team (MDO) |
| CtF Expired Enforcement | Validated Signed CtF and CtF Expiration Date < 1 year. | Every time a production deployed is executed. | Mission DevOps Team (MDO) |
Note
For information on Collab Tools retention policies (i.e. Jira, Confluence, and Mattermost), please reference Collab Tools documentation