Cisco ASA Firewall STIG Version Comparison
Cisco ASA Firewall Security Technical Implementation Guide
There are 17 differences between versions v1 r0.1 (Dec. 15, 2020) (the "left" version) and v1 r2 (April 27, 2022) (the "right" version).
Check CASA-FW-000020 was added to the benchmark in the "right" version.
This check's original form is available here.
The Cisco ASA must immediately use updates made to policy enforcement mechanisms such as firewall rules, security policies, and security zones.
By default, when you change a rule-based policy such as access rules, the changes become effective immediately. With transactional model configured, the rules are not active until after compilation. Review the ASA configuration and verify that the following command is not configured. asp rule-engine transactional-commit access-group If transactional-commit access-group has been configured, this is a finding.
Information flow policies regarding dynamic information flow control include, for example, allowing or disallowing information flows based on changes to the Ports, Protocols, Services Management (PPSM) Category Assurance Levels (CAL) list, vulnerability assessments, or mission conditions. Changing conditions include changes in the threat environment and detection of potentially harmful or adverse events.
Remove the command asp rule-engine transactional-commit access-group ASA(config)# no asp rule-engine transactional-commit access-group