OpenControls Logo

STIG Viewer

STIGViewer Support

The Edge SWG must be configured to authenticate SNMP messages using a FIPS-validated Keyed-Hash Message Authentication Code (HMAC).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-279268SYME-ND-000710SV-279268r1170603_ruleCCI-001967medium
Description
Without authenticating devices, unidentified or unknown devices may be introduced, thereby facilitating malicious activity. Bidirectional authentication provides stronger safeguards to validate the identity of other devices for connections that are of greater risk. A local connection is any connection with a device communicating without the use of a network. A network connection is any connection with a device that communicates through a network (e.g., local area or wide area network, internet). A remote connection is any connection with a device communicating through an external network (e.g., the internet). Because of the challenges of applying this requirement on a large scale, organizations are encouraged to only apply the requirement to those limited number (and type) of devices that truly need to support this capability.
STIGDate
Symantec Edge SWG NDM Security Technical Implementation Guide2026-02-25

Related Frameworks

1 mapping across 4 frameworks
SCF0 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.

IAC-04Identification & Authentication for Devices
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (49) 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-17(10)Authenticate Remote Commands
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-18(1)Authentication and Encryption
1.00
AC-2(1)Automated System Account Management
1.00
AC-2(11)Usage Conditions
1.00
AC-2(2)Automated Temporary and Emergency Account Management
1.00
AC-2(3)Disable Accounts
1.00
AC-4(17)Domain Authentication
1.00
AC-7Unsuccessful Logon Attempts
1.00
AU-8Time Stamps
1.00

+39 more (top 10 by confidence shown)

CCI1 mapping
CCI-001967
1.00
NIST CSF 2.00 mappings

No source states a mapping between these directly.

Also reachable in 4 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.

PR.AA-01
0.50
PR.AA-03
0.50
PR.AA-05
0.50

Details

Check Text (C-279268r1170603_chk)

1. Log in to the Edge SWG SSH CLI. 2. Enter "show snmp". If the line for SNMPv1 and SNMPv2c does not say "disabled", this is a finding. Below is an example of what the line will look in a correct state: "SNMPv1 is disabled. SNMPv2c is disabled."

Fix Text (F-83723r1170602_fix)

1. In the Edge SWG Web UI, navigate to the Administration tab. 2. Select the "SNMP" and "SNMP" areas. 3. Under "V3 Users", click "Add User". 4. Enter the username. 5. Select "SHA" for authentication and type a passphrase. 6. Select AES and type a passphrase. 7. Under "V3 Traps and Informs", add a trap destination if applicable. 1. In the Edge SWG Web UI, navigate to the Configuration tab. 2. Select the "Services" and "Management Services" areas. 3. Enable SNMP, add the listener for both IPv4 and IPv6. 1. In the Edge SWG Web UI, navigate to the Visual Policy Manager. Note: Ensure the Admin Access Layer was created before moving on to this step. 2. Under the "Admin Access Layer", click "Add Rule". 3. Under "Source", select "Any". 4. Under "Service", select "Service Name: SNMP". 5. Under "Action", select "Allow Read-only Access". 6. Apply the policy.