JUEX-NM-000390 - The Juniper EX switch must be configured to enforce organization-defined role-based access control policies over defined subjects and objects.

Information

Organizations can create specific roles based on job functions and the authorizations (i.e., privileges) to perform needed operations on organizational information systems associated with the organization-defined roles. When administrators are assigned to the organizational roles, they inherit the authorizations or privileges defined for those roles. RBAC simplifies privilege administration for organizations because privileges are not assigned directly to every administrator (which can be a significant number of individuals for mid- to large-size organizations) but are instead acquired through role assignments. RBAC can be implemented either as a mandatory or discretionary form of access control.

The RBAC policies and the subjects and objects are defined uniquely for each network device, so they cannot be specified in the requirement.

NOTE: Nessus has provided the target output to assist in reviewing the benchmark to ensure target compliance.

Solution

Configure the network device or its associated authentication server to enforce role-based access control policy over defined subjects and objects.

set system login class <name> permissions <permission sets or 'all'>
set system login class <name> deny-commands <appropriate commands to deny>
set system login class <name> deny-configuration-regexps <appropriate configuration hierarchy to deny>

set system login user <account name> class <name>

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Juniper_EX_Switches_Y24M07_STIG.zip

Item Details

Category: ACCESS CONTROL, CONFIGURATION MANAGEMENT

References: 800-53|AC-3(7), 800-53|CM-6b., CAT|II, CCI|CCI-000366, CCI|CCI-002169, Rule-ID|SV-253916r987662_rule, STIG-ID|JUEX-NM-000390, Vuln-ID|V-253916

Plugin: Juniper

Control ID: f06a57158e17a15f087ec281f0b4e6c940610d079fca9c8832d54f16172b974d