OpenControls Logo

STIG Viewer

STIGViewer Support

Symantec ProxySG must configure SNMPv3 so that cryptographically-based bidirectional authentication is used.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-94699SYMP-NM-000240SV-104529r1_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 ProxySG NDM Security Technical Implementation Guide2019-12-20

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-104529r1_chk)

Verify only SNMPv3 (which supports authentication) is configured on the Symantec ProxySG. 1. Log on to the Web Management Console. 2. Click Maintenance >> SNMP. 3. Ensure that only "Enable SNMPv3" is checked. 4. Click on "SNMPv3 Users" and ensure that a user exists in the list. If SNMPv3 (which supports authentication) is not configured or is not the only one configured on the Symantec ProxySG, this is a finding.

Fix Text (F-100817r1_fix)

Enable only SNMPv3 (which supports authentication) on the Symantec ProxySG. 1. Log on to the Web Management Console. 2. Click Maintenance >> SNMP. 3. Uncheck "Enable SNMPv1" and "Enable SNMPv2c" and check "Enable SNMPv3". 4. Click on "SNMPv3 Users", click "New" and enter the desired username, credentials, and authorization settings, click "OK". 5. Click "SNMPv3 Traps", click "New", enter the IP address/FQDN for the SNMP receiver. 6. Click "OK", click "Apply".