V3R3 changes
Juniper SRX Services Gateway ALG STIG V3R3 (2025-01-30) replaced V3R2 (2024-10-24): 1 check updated. It has 24 checks, against 24 in V3R2.
V3R3 checklistV3R2 checklist Compare V3R2 and V3R3 in STIG Compare
- 0 added
- 0 removed
- 1 updated
Updated fields: Check text 1Discussion 1
Updated in V3R3 (1)
V-214538CAT IThe Juniper SRX Services Gateway Firewall must continuously monitor outbound communications traffic for unusual/unauthorized activities or conditions.Check text, Discussion
Check text
For each outbound zone, verify a firewall screen or security policy is configured.
[edit]
show security zones
show security policies
If communications traffic for each outbound zone is not configured with a firewall screen or security policy, this is not a finding.
Discussion
If outbound communications traffic is not continuously monitored, hostile activity may not be detected and prevented. Output from application and traffic monitoring serves as input to continuous monitoring and incident response programs.
The Juniper SRX is a highly scalable system whichthat can provide stateful or stateless continuous monitoring when placed in the architecture at either the perimeter or internal boundaries. Unusual/unauthorized activities or conditions may include unusual use of unusual protocols or ports and attempted communications from trusted zones to external addresses.
How these changes are found
Checks are matched across the two releases by V-number. A check counts as updated when DISA gave it a new rule revision (the r number in its SV-…_rule id) and its title, severity, check text, fix text, discussion, CCIs or other fields changed — the same comparison STIG Compare makes. Added checks are new V-numbers; removed checks are V-numbers V3R3 no longer has.
Comparing other releases, or this one against an older release? Pick any two in STIG Compare.