For local accounts created on the device, the Juniper SRX Services Gateway must automatically generate log records for account disabling events.

Severity	Group ID	Group Title	Version	Rule ID	Date	STIG Version
medium	V-223183	SRG-APP-000028-NDM-000210	JUSX-DM-000017	SV-223183r960783_rule	2024-12-20	3

Description
When device management accounts are disabled, user or service accessibility may be affected. Auditing also ensures authorized, active accounts remain enabled and available for use when required. Without this audit trail, personnel without the proper authorization may gain access to critical network nodes. An AAA server is required for account management in accordance with CCI-000370. Only a single account of last resort is permitted on the local device. However, since it is still possible for administrators to create local accounts either maliciously or to support mission needs, the SRX must be configured to log account management events. To log local account management events, ensure at least one external syslog server is configured to log facility any or facility change-log, and severity info or severity any.

Description

When device management accounts are disabled, user or service accessibility may be affected. Auditing also ensures authorized, active accounts remain enabled and available for use when required. Without this audit trail, personnel without the proper authorization may gain access to critical network nodes. An AAA server is required for account management in accordance with CCI-000370. Only a single account of last resort is permitted on the local device. However, since it is still possible for administrators to create local accounts either maliciously or to support mission needs, the SRX must be configured to log account management events. To log local account management events, ensure at least one external syslog server is configured to log facility any or facility change-log, and severity info or severity any.

ℹ️ Check
Verify the device logs change-log events of severity info or any to an external syslog server. [edit] show system syslog host <syslog server address> { any <info \| any>; source-address <device address>; } -OR- host <syslog server address> { change-log <info \| any>; source-address <device address>; } If an external syslog host is not configured to log facility change-log severity <info \| any>, or configured for facility any severity <info \| any>, this is a finding.

ℹ️ Check

Verify the device logs change-log events of severity info or any to an external syslog server. [edit] show system syslog host <syslog server address> { any <info | any>; source-address <device address>; } -OR- host <syslog server address> { change-log <info | any>; source-address <device address>; } If an external syslog host is not configured to log facility change-log severity <info | any>, or configured for facility any severity <info | any>, this is a finding.

✔️ Fix
Configure at least one external syslog host is configured to log facility change-log or any, and severity info or any. [edit system syslog] set host <syslog server address> any <info \| any> -OR- [edit] set host <syslog server address> change-log <info \| any>