JUSX-DM-000039 - The Juniper SRX Services Gateway must allow only the ISSM (or administrators/roles appointed by the ISSM) to select which auditable events are to be generated and forwarded to the syslog and/or local logs.

Information

Without the capability to restrict which roles and individuals can select which events are audited, unauthorized personnel may be able to prevent the auditing of critical events. Misconfigured audits may degrade the system's performance by overwhelming the log. Misconfigured audits may also make it more difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one.

The primary audit log permissions are set on the Syslog server, not the Juniper SRX. However, it is a best practice to also keep local logs for troubleshooting and backup. These logs are subject to access control requirements.

This configuration is a two-step process. Part of the configuration must be performed on the AAA server. After a user successfully logs on, the AAA sever passes the template or role of the user to the Juniper SRX. Each AAA template or role is mapped to a login class on the Juniper SRX.

On the Juniper SRX, the class name, audit-admin, is recommended as a best practice because it follows the naming convention used in NIAP testing and is self-documenting.

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

Solution

Configure the Juniper SRX to allow only the ISSM user account (or administrators/roles appointed by the ISSM) to select which auditable events are to be audited. To ensure this is the case, each ISSM-appointed role on the AAA must be configured for least privilege using the following stanzas for each role.

For audit-admin role:

[edit]
set system login class audit-admin permissions [ security trace maintenance ]
set system login class audit-admin allow-commands '^clear (log|security log)'
set system login class audit-admin deny-commands '^clear (security alarms|system login lockout)|^file (copy|delete|rename)|^request (security|system set-encryption-key)|^rollback|^set date|^show security (alarms|dynamic-policies|match-policies|policies)|^start shell'
set system login class audit-admin security-role audit-administrator
set system login user audit-officer class audit-admin

For the crypto admin role:

[edit]
set system login class crypto-admin permissions [ admin-control configure maintenance security-control system-control trace ]
set system login class crypto-admin allow-commands '^request system set-encryption-key'
set system login class crypto-admin deny-commands '^clear (log|security alarms|security log|system login lockout)|^file (copy|delete|rename)|^rollback|^set date|^show security (alarms|dynamic-policies|match-policies|policies)|^start shell'
set system login class crypto-admin allow-configuration-regexps 'security (ike|ipsec) (policy|proposal)' 'security ipsec ^vpn$ .* manual (authentication|encryption|protocol|spi)' 'system fips self-test after-key-generation'
set system login class crypto-admin security-role crypto-administrator

For the security-admin role:

[edit]
set system login class security-admin permissions all
set system login class security-admin deny-commands '^clear (log|security log)|^(clear|show) security alarms alarm-type idp|^request (security|system set-encryption-key)|^rollback|^start shell'
set system login class security-admin deny-configuration-regexps 'security alarms potential-violation idp' 'security (ike|ipsec) (policy|proposal)' 'security ipsec ^vpn$ .* manual (authentication| encryption|protocol|spi)' 'security log cache' 'security log exclude .* event-id IDP_.*' 'system fips self-test after-key- generation'
set system login class security-admin security-role security-administrator

For the ids-admin role:

[edit]
set system login class ids-admin permissions [ configure maintenance security-control trace ]
set system login class ids-admin allow-configuration-regexps 'security alarms potential-violation idp' 'security log exclude .* event-id IDP_.*'
set system login class ids-admin deny-commands '^clear log|^(clear|show) security alarms (alarm-id|all|newer-than|older- than|process|severity)|^(clear|show) security alarms alarm-type (authentication|cryptographic-self-test|decryption-failures|encryption-failures| ike-phase1-failures|ike-phase2-failures|key-generation-self-test| non-cryptographic-self-test|policy|replay-attacks)|^file (copy|delete|rename)|^request (security|system set-encryption-key)|^rollback|^set date|^show security (dynamic-policies|match-policies|policies)|^start shell'
set system login class ids-admin deny-configuration-regexps 'security alarms potential-violation (authentication|cryptographic-self-test|decryption-failures|encryption-failures|ike-phase1-failures|ike-phase2-failures|key-generation-self-test|non-cryptographic-self-test|policy|replay-attacks)'
set system login class ids-admin security-role ids-admin

For the crypto-officer class:

[edit]
set system login user crypto-officer class crypto-admin
set system login user security-officer class security-admin
set system login user ids-officer class ids-admin

Item Details

Audit Name: DISA Juniper SRX Services Gateway NDM v2r1

Category: ACCESS CONTROL, CONFIGURATION MANAGEMENT

Plugin: Juniper

Control ID: 0dc29152445a3cb8738f76e7b9b60ea7f0f4608a95630b7acfef4431ad58c459

Detections

Analytics

JUSX-DM-000039 - The Juniper SRX Services Gateway must allow only the ISSM (or administrators/roles appointed by the ISSM) to select which auditable events are to be generated and forwarded to the syslog and/or local logs.

Information

Solution

See Also

Item Details