SV-214519r557389_rule
V-214519
SRG-NET-000492-ALG-000027
JUSX-AG-000036
CAT II
10
Include the log and/or syslog action in all term to log packets matching each firewall term to ensure the term results are recorded in the firewall log and Syslog. To get traffic logs from permitted sessions, add "then log session-close" to each policy. To get traffic logs from denied sessions, add "then log session-init" to the policy.
Firewall filter:
[edit]
set firewall family <family name> filter <filter_name> term <term_name> then log
Examples:
set firewall family inet filter protect_re term tcp-connection then syslog
set firewall family inet filter protect_re term tcp-connection then log
set firewall family inet filter ingress-filter-v4 term deny-dscp then log
set firewall family inet filter ingress-filter-v4 term deny-dscp then syslog
Security policy and security screens:
set security policies from-zone <zone_name> to-zone <zone_name> policy <policy_name> then log
Example:
set security policies from-zone untrust to-zone trust policy default-deny then log
To verify what is logged in the Syslog, view the Syslog server (Syslog server configuration is out of scope for this STIG); however, the reviewer must also verify that packets are being logged to the local log using the following commands.
From operational mode, enter the following command.
show firewall log
View the Action column; the configured action of the term matches the action taken on the packet: A (accept), D (discard).
If events in the log do not reflect the action taken on the packet, this is a finding.
V-214519
False
JUSX-AG-000036
To verify what is logged in the Syslog, view the Syslog server (Syslog server configuration is out of scope for this STIG); however, the reviewer must also verify that packets are being logged to the local log using the following commands.
From operational mode, enter the following command.
show firewall log
View the Action column; the configured action of the term matches the action taken on the packet: A (accept), D (discard).
If events in the log do not reflect the action taken on the packet, this is a finding.
M
4004