STIGViewer Support

The Cisco ASA must be configured to conduct backups of system-level information contained in the information system when changes occur.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-239941CASA-ND-001350SV-239941r1205824_ruleCCI-000537medium
Description
System-level information includes default and customized settings and security attributes, including ACLs that relate to the network device configuration, as well as software required for the execution and operation of the device. Information system backup is a critical step in ensuring system integrity and availability. If the system fails and there is no backup of the system-level information, a denial-of-service condition is possible for all who utilize this critical network component. This control requires the network device to support the organizational central backup process for system-level 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.
STIGDate
Cisco ASA NDM Security Technical Implementation Guide2026-05-01

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 4 hops (12) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

BCD-11Data Backups
1.00
BCD-11.1Testing for Reliability & Integrity
1.00
BCD-11.5Test Restoration Using Sampling
1.00
BCD-11.6Transfer to Alternate Storage Site
1.00
BCD-13Backup & Restoration Hardware Protection
1.00
BCD-13.1Restoration Integrity Verification
1.00
CFG-02Secure Baseline Configurations
1.00
CRY-01Use of Cryptographic Controls
1.00
CRY-01.1Alternate Physical Protection
1.00
CRY-05Encrypting Data At Rest
1.00

+2 more (top 10 by confidence shown)

NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (3) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

AU-4(1)Transfer to Alternate Storage
1.00
CM-6Configuration Settings
1.00
CP-9System Backup
1.00
NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (1) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

3.8.9
1.00
CCI1 mapping
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (4) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

Who does this work

11 NICE work roles and 10 EC-Council certifications.

This is an inference across published mappings, not a single claim by anyone. This check maps to a control, which maps to a Cybersecurity Framework outcome, which NIST assigns to the work roles below. EC-Council separately maps its certifications to those same roles.

A certification prepares someone for a role. It is not evidence that a holder is qualified, and neither NIST nor EC-Council has stated that any certification here addresses this check.

Work-role assignments published by NIST (NICE Framework Components 2.2.0 and the CSF 2.0 OLIR crosswalk). Certification mappings published by EC-Council.

Details

Check Text (C-239941r1205824_chk)

Review the Cisco ASA configuration to verify it is compliant with this requirement. The example configuration below will send the configuration to an SCP server when a configuration change occurs. event manager applet BACKUP_CONFIG event syslog id 111010 action 1 cli command "copy startup-config scp://userx:xxxxxxx@10.1.48.10//opt/config_backup" action 2 syslog priority informational msg "Configuration backup was executed" Note: Tools such as Cisco Security Manager, Cisco Prime Infrastructure, Firemon, or Tripwire can be used to back up the configuration. If the Cisco ASA is not configured to conduct backups of the configuration when changes occur, this is a finding.

Fix Text (F-43133r1205823_fix)

Configure the Cisco ASA to send the configuration to an SCP server when a configuration change occurs as shown in the example below. ASA(config)# event manager applet BACKUP_CONFIG ASA(config-applet)# event syslog id 111010 ASA(config-applet)# action 1 cli command " copy startup-config scp://userx:xxxxxxx@10.1.48.10//opt/config_backup” ASA(config-applet)# action 2 syslog priority informational msg "Configuration backup was executed" ASA(config-applet)# end