The F5 BIG-IP appliance must conduct backups of the configuration at a weekly or organization-defined frequency and store on a separate device.
Severity | Group ID | Group Title | Version | Rule ID | Date | STIG Version |
|---|---|---|---|---|---|---|
| medium | V-266096 | SRG-APP-000516-NDM-000341 | F5BI-DM-300060 | SV-266096r1024630_rule | 2024-09-20 | 1 |
| Description |
|---|
| Information system backup is a critical step in maintaining data assurance and availability. Information system and security-related documentation contains information pertaining to system configuration and security settings. If this information were not backed up, and a system failure were to occur, the security settings would be difficult to reconfigure quickly and accurately. Maintaining a backup of information system and security-related documentation provides for a quicker recovery time when system outages occur. This control requires the network device to support the organizational central backup process for user account information associated with the network device. This function may be provided by the network device itself; however, the preferred best practice is a centralized backup rather than each network device performing discrete backups. |
| ℹ️ Check |
|---|
| From the BIG-IP GUI: 1. System. 2. Archives. 3. Review the list of archives to verify backups are conducted in accordance with the local backup policy. From the BIG-IP console, type the following command: tmsh list sys ucs If the BIG-IP appliance is not configured to back up at system-level information weekly or at an organization-defined frequency this is a finding. |
| ✔️ Fix |
|---|
| Document this process in the system security plan (SSP) and perform periodic manual backups. This process backs up the current configuration. Backups must be weekly or a documented organization-defined frequency. From the BIG-IP GUI: 1. System. 2. Archives. 3. Create. From the BIG-IP console, type the following command: tmsh save sys ucs <name> |