V-253939

Discussion

Auditing and logging are key components of any security architecture. Logging the actions of specific events provides a means to investigate an attack; to recognize resource utilization or capacity thresholds; or to identify an improperly configured network device. If auditing is not comprehensive, it will not be useful for intrusion monitoring, security investigations, and forensic analysis.

Check Content

Determine if the network device generates audit log events for a locally developed list of auditable events.

Verify audit logging is enabled.
[edit system syslog]
file <file name> {
    any info;
}
host <external syslog address> {
    any info;
}
time-format year;

Note: Without the "structured-data" directive (as shown), syslog outputs in standard format. Add the "structured-data" command to all files and external syslog servers requiring that format. For example:
[edit system syslog]
file <file name> {
    any info;
    structured-data;
}

If the logging facility and level is too broad, Junos supports REGEX or string match conditions to filter events. If used, verify the match conditions capture the required events.
[edit system syslog]
file <file name> {
    any info;
    match <REGEX>;
    -or-
    match-strings [ "string 1" "string 2" ];
}
Note: When using match conditions, it may be necessary to use the "any" (debug) severity level, but this should not generate overwhelming numbers of messages because the filter will ignore all unmatched events.

If the network device is not configured to generate audit log events for a locally developed list of auditable events, this is a finding.