OpenControls Logo

STIG Viewer

STIGViewer Support

The Juniper SRX Services Gateway must use and securely configure SNMPv3 if SNMP is enabled.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-223211JUSX-DM-000111SV-223211r1056173_ruleCCI-000382high
Description
To prevent nonsecure protocol communications with the organization's local SNMPv3 services, the SNMP client on the Juniper SRX must be configured for proper identification and strong cryptographically based protocol for authentication. SNMPv3 defines a user-based security model (USM) and a view-based access control model (VACM). SNMPv3 USM provides data integrity, data origin authentication, message replay protection, and protection against disclosure of the message payload. SNMPv3 VACM provides access control to determine whether a specific type of access (read or write) to the management information is allowed. The Junos operating system allows the use of SNMPv3 to monitor or query the device for management purposes. Junos does not allow SNMPv3, of any type, to be used to make configuration changes to the device. SNMPv3 is disabled by default and must be enabled for use. SNMPv3 is the DOD-preferred method for monitoring the device securely. If SNMPv3 is not being used, it must be disabled. The commands in the Fix Text will configure SNMPv3. The Junos operating system allows the use of FIPS 140-2/140-3 validated protocols for secure connections.
STIGDate
Juniper SRX Services Gateway NDM Security Technical Implementation Guide2024-12-20

Related Frameworks

2 mappings across 5 frameworks
SCF0 mappings

No source states a mapping between these directly.

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

CFG-01Configuration Management Program
1.00
CFG-03Least Functionality
1.00
IAC-04Identification & Authentication for Devices
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (67) 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(1)Monitoring and Control
1.00
AC-17(10)Authenticate Remote Commands
1.00
AC-17(2)Protection of Confidentiality and Integrity Using Encryption
1.00
AC-17(9)Disconnect or Disable Access
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-2(4)Automated Audit Actions
1.00

+57 more (top 10 by confidence shown)

NIST 800-1710 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.

3.4.6
1.00
CCI2 mappings
CCI-000382
1.00
CCI-001967
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.

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

Who does this work

5 NICE work roles and 5 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-223211r1056173_chk)

If an SNMP stanza does not exist, this is not a finding. Verify SNMPv3 is enabled and configured. [edit] show snmp If versions earlier than SNMPv3 are enabled, this is a finding.

Fix Text (F-24872r1056100_fix)

Enable and configure SNMPv3 and configure a trap and community string. [edit] set snmp location <LOCATION-NAME> set snmp v3 usm local-engine user <USER-NAME> privacy-AES128 authentication-sha256 set snmp v3 vacm security-to-group security-model usm security-name <SECURITY-NAME> group <GROUP-NAME> set snmp v3 vacm access group <GROUP-NAME> default-context-prefix security-model usm security-level privacy read-view all set snmp v3 vacm access group <GROUP-NAME> default-context-prefix security-model usm security-level privacy notify-view all set snmp v3 target-address <target-address-name> tag-list <SNMP-trap-receiver> set snmp v3 target-address <TARGER-ADDRESS-NAME> target-parameters <PARMS-NAME> set snmp v3 target-parameters <PARMS-NAME> parameters message-processing-model v3 set snmp v3 target-parameters <PARMS-NAME> parameters security-model usm set snmp v3 target-parameters <PARMS-NAME> parameters security-level privacy set snmp v3 target-parameters <PARMS-NAME> parameters security-name <SECURITY-NAME> set snmp v3 target-parameters <PARMS-NAME> notify-filter device-traps set snmp v3 notify <SNMP-TRAPS> type trap set snmp v3 notify <SNMP-TRAPS> tag <SNMP-TRAP-RECEIVER> set snmp v3 notify-filter device-traps oid jnxChassisTraps include set snmp v3 notify-filter device-traps oid jnxChassisOKTraps include set snmp v3 notify-filter device-traps oid system include set snmp v3 notify-filter device-traps oid .1 include set snmp v3 notify-filter device-traps oid snmpMIBObjects include set snmp engine-id use-mac-address set snmp view all oid .1 include set snmp view all oid system include set snmp view all oid jnxBoxAnatomy include set snmp view all oid snmpMIBObjects include