STIGhubSTIGhub
STIGsSearchCompare

STIGhub

A free tool to search and browse the entire DISA STIG library. Saves up to 75% in security compliance research time.

Navigation

  • Browse STIGs
  • Search
  • Compare Versions

Resources

  • About
  • Release Notes
  • VPAT
  • DISA STIG Library
STIGs updated 5 hours ago
Powered by Pylon
© 2026 Beacon Cloud Solutions, Inc. All rights reserved.
← Back to Juniper Router NDM Security Technical Implementation Guide

V-217345

CAT II (Medium)

The Juniper router must be configured to generate audit records when successful/unsuccessful logon attempts occur.

Rule ID

SV-217345r961824_rule

STIG

Juniper Router NDM Security Technical Implementation Guide

Version

V3R2

CCIs

CCI-000172

Discussion

Without generating audit records that are specific to the security and mission needs of the organization, it would be difficult to establish, correlate, and investigate the events relating to an incident or identify those responsible for one. Audit records can be generated from various components within the network device (e.g., module or policy filter).

Check Content

Review the router configuration to verify that it is compliant with this requirement as shown in the examples below.

   syslog {
        file LOG_FILE {
            authorization info;
        }
    }

Note: The parameter "any" can be in place of "authorization" as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below.

system {
   syslog {
        host x.x.x.x {
            any info;
        }
    }

If the router is not configured to generate audit records when successful/unsuccessful logon attempts occur, this is a finding.

Fix Text

Configure the router to generate audit records when successful/unsuccessful logon attempts occur as shown in the example below.

[edit system]
set syslog file LOG_FILE authorization info

Note: The parameter "any" can be in place of authorization" as this will log everything. Also, a syslog server can be configured in addition to or in lieu of logging to a file as shown in the example below.

set syslog host x.x.x.x any info