OpenControls Logo

STIG Viewer

STIGViewer Support

The ICS must be configured to support organizational requirements to conduct weekly backups of information system documentation, including security-related documentation.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-258612IVCS-NM-000380SV-258612r961863_ruleCCI-000366medium
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.
STIGDate
Ivanti Connect Secure NDM Security Technical Implementation Guide2025-09-09

Related Frameworks

1 mapping across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (8) 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.

CFG-01Configuration Management Program
1.00
END-01Endpoint Device Management (EDM)
1.00
END-04Malicious Code Protection (Anti-Malware)
1.00
END-06Endpoint File Integrity Monitoring (FIM)
1.00
MON-01Continuous Monitoring
1.00
MON-01.7File Integrity Monitoring (FIM)
1.00
CFG-02Secure Baseline Configurations
0.50
CFG-02.7Approved Configuration Deviations
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (100) 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.

AC-12Session Termination
1.00
AC-16(1)Dynamic Attribute Association
1.00
AC-17(1)Monitoring and Control
1.00
AC-2Account Management
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(3)Disable Accounts
1.00
AC-2(4)Automated Audit Actions
1.00
AC-24(1)Transmit Access Authorization Information
1.00
AC-25Reference Monitor
1.00

+90 more (top 10 by confidence shown)

NIST 800-1710 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) 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.4.1
1.00
3.4.2
1.00
CCI1 mapping
CCI-000366
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (5) 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.

DE.CM-09
1.00
PR.PS-01
1.00
PR.DS-10
0.50
PR.PSPlatform Security
0.50
PR.PS-05
0.50

Who does this work

10 NICE work roles and 9 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-258612r961863_chk)

In the ICS Web UI, navigate to Maintenance >> Archiving >> Archive Servers. 1. Under "Archive Settings" verify an archive server is configured. 2. Under "Archive Schedule" verify "Archive System Configuration", and "Archive User Accounts" are selected. 3. Under "Archive Schedule" verify "Archive System Configuration", and "Archive User Accounts" are configured at a specific time and day of the week. 4. Under "Archive Schedule", if "Archive System Configuration", and "Archive User Accounts" are configured with a password for backup encryption. If the ICS does not support organizational requirements to conduct backups of information system documentation, including security-related documentation weekly, this is a finding.

Fix Text (F-62261r930523_fix)

In the ICS Web UI, navigate to Maintenance >> Archiving >> Archive Servers. 1. Click "SCP" if using an SFTP/SCP server; other mechanisms may not be allowed due to local security policy. NOTE: Check with the ISSM before configuring anything other than SCP. 2. Under "Archive Server" type the hostname or IPv4/IPv6 address. 3. In "Destination Directory" type the path of the backup (e.g., "/backupfolder/ics/"). 4. In the "Username" field, type the username with SCP/SFTP permissions on the backup server. 5. In the "Password" field, type the password. 6. Under "Archive Schedule", select "Archive System Configuration", then click the day of the week and time when the backup should be sent. 7. Under "Archive System Configuration", ensure a password is given to encrypt the backup. 8. Under "Archive Schedule", select "Archive User Accounts", then click the day of the week and time when the backup should be sent. 9. Under "Archive User Accounts", ensure a password is given to encrypt the backup. 10. Click "Save Changes".