Verify that an intrusion policy has been applied to access control rules. Step 1: Navigate to Configuration >> ASA FirePOWER Configuration >> Policies >> Access Control Policy. The Access Control Policy page appears. Step 2: Click the edit icon next to the access control policy configured for intrusion inspection using access control rules. Step 3: Click the edit icon next to the rule you want to view. The access control rule editor appears. Step 4: Verify that the rule action is set to Interactive Block or Interactive Block with reset. Step 5: Select the Inspection tab. The Inspection tab appears. Step 6: Verify that a system-provided or custom intrusion policy has been selected. Note: An access control policy can have multiple access control rules associated with intrusion policies. --------------------------------------------------- Verify that the ASA is configured to redirect all traffic to the FirePOWER service module. Step 1: Verify that the FirePOWER service module has been deployed in inline mode as shown in the example below. policy-map global_policy class FIREPOWER_SFR sfr fail-open Step 2: Verify that all traffic is redirected. access-list FIREPOWER_REDIRECT extended permit ip any any … … … class-map FIREPOWER_SFR match access-list FIREPOWER_REDIRECT Note: Inbound and outbound traffic that is allowed by the ASA firewall is forwarded to the FirePOWER module. If the Cisco ASA FirePOWER module is configured in inline mode, the packet is inspected and dropped if it does not conform to access control policies. If the packet is compliant with access control policies, it is sent back to the ASA firewall for processing. If the ASA is not configured to block outbound traffic containing DoS attacks by ensuring an intrusion prevention policy has been applied to outbound communications traffic, this is a finding.