The Juniper SRX Services Gateway must generate log records when privileged commands are executed.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-223195JUSX-DM-000044SV-223195r961827_ruleCCI-000172low
Description
Without generating log 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.
STIGDate
Juniper SRX Services Gateway NDM Security Technical Implementation Guide2024-12-20

Related Frameworks

4 paths across 3 frameworks
NIST 800-531 mapping
AU-12
1.00
  • DISA · V3R3 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
NIST 800-1712 mappings
3.3.1
1.00
  • DISA · V3R3 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
3.3.2
1.00
  • DISA · V3R3 · disa_xccdf · related
  • DISA · 2025-01-23 · disa_cci_list · equivalent
  • NIST · Rev 2 (Feb 2020, errata Jan 2021) · nist_800_171_app_d · equivalent
CCI1 mapping
CCI-000172
1.00
  • DISA · V3R3 · disa_xccdf · related

Details

Check Text (C-223195r961827_chk)

Verify the device generates a log when login events occur. [edit] show system syslog host <syslog server address> { any any; source-address <device address>; } If an external syslog host is not configured to log, or configured for facility any severity any, this is a finding.

Fix Text (F-24856r513276_fix)

Configure at least one external syslog host to log facility any and severity info or any. There are multiple ways to accomplish this, the following is an example. [edit system syslog] set host <syslog server address> any any