OpenControls Logo

STIG Viewer

STIGViewer Support

If SNMP is used, the ICS must be configured to use SNMPv3 with FIPS-140-2/3 validated Keyed-Hash Message Authentication Code (HMAC).

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-258602IVCS-NM-000090SV-258602r961506_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
Ivanti Connect Secure NDM Security Technical Implementation Guide2025-09-09

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-258602r961506_chk)

If SNMP is not used, this is not applicable. In the ICS Web UI, navigate to System >> Log/Monitoring >> SNMP. Under "SNMP version data", verify v2c is not selected. If the ICS does not use properly configured SNMPv3, this is a finding.

Fix Text (F-62251r930493_fix)

This is applicable if SNMP is enabled. Though the entire SNMP configuration is given to prevent misconfiguration, note that this requirement is focused on the use of v3. In the ICS Web UI, navigate to System >> Log/Monitoring >> SNMP. 1. Under "SNMP version data", select v3. 2. Under "Agent Properties", select SNMP Queries. 3. Define the System Name. 4. Define the System Location. 5. Define the System Contact. 6. Under "SNMPv3 Configuration" and "User 1" type the username. 7. Select the "Security Level" of Auth, Priv. 8. Select SHA as the Auth Protocol. 9. Type the Auth password. 10. Select "CFB-AES-128" as the Priv Protocol. 11. Type the Priv password. 12. Under Optional Traps, select "Critical and Major log events". 13. Click "Save Changes".