OpenControls Logo

STIG Viewer

STIGViewer Support

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

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-279272SYME-ND-000780SV-279272r1172804_ruleCCI-000366medium
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 (DoS) 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. Satisfies: SRG-APP-000516-NDM-000340, SRG-APP-000516-NDM-000341
STIGDate
Symantec Edge SWG NDM Security Technical Implementation Guide2026-02-25

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-279272r1172804_chk)

1. Log in to the Edge SWG SSH CLI. 2. Enter "show archive-configuration". If no server is configured, this is a finding. If "Automatic upload" is not set to "Enabled", this is a finding. If "Upload interval" is not set for "every 10080 minutes", this is a finding.

Fix Text (F-83727r1172803_fix)

1. Log in to the Edge SWG SSH CLI. 2. Enter "enable" and "configure terminal". 3. Enter "archive-configuration archive-signing enforce-signed enable". 4. Enter "archive-configuration automatic-upload". 5. Enter "archive-configuration host" and add the IP address or hostname of the site's SCP backup server. 6. Enter "archive-configuration username" and add the username of the site's SCP backup server. 7. Enter "archive-configuration password" and add the site's password of the site's SCP backup server. 8. Enter "archive-configuration path" and add the site's backup server path (e.g., /home/tachyon-ftp/files/broadcom/). 9. Enter "archive-configuration filename-prefix SG_%l_%Y%m%d%H%M". 10. Enter "archive-configuration periodic-upload minutes 10080". 11. Enter "archive-configuration protocol scp". 12. Enter "archive-configuration scp-authentication password". 13. Enter "archive-configuration ssl-device-profile" and add the "SSL Device Profile" in use for the HTTPS-console and x509 authentication.