Party Bus Retention Policies
Overview
Use this document to understand 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 |
| Data Retention | RDS S3 Buckets GitLab Repos | 3 years | Mission DevOps Team |
Cyber Enforcement
| Policy Name | Action | Timeframe | Responsibility |
|---|---|---|---|
| 7-Day Pipeline Execution | Automation execution of pipelines every 7 days. | Every 7 days | Mission DevOps Team |
| Critical CVEs | Enforce fixing or whitelisting Critical and High CVEs. | Every day | Mission DevOps Team |
| CtF Expired Enforcement | Validated signed CtF and CtF expiration date < 1 year. | Every time a production deployment is executed. | Mission DevOps Team |
Note
For information on CollabTools retention policies (i.e., Jira, Confluence, and Mattermost), please reference CollabTools documentation.