Default 'interzone-default' & 'intrazone-default' not logging to Strata Logging Service from Cloud NGFW (CNGFW) for Aws or Azure

Default 'interzone-default' & 'intrazone-default' not logging to Strata Logging Service from Cloud NGFW (CNGFW) for Aws or Azure

4603
Created On 11/22/23 23:59 PM - Last Modified 03/12/25 04:00 AM


Symptom


  • There is a Cloud Next generation firewall or CNGFW for Aws or Azure setup managed by Panorama.
  • Administrator modified the default 'interzone-default' & 'intrazone-default' rules by overriding them on the Panorama. 
  • The Panorama integration is done to make sure all the logs generated by CNGFW's are sent to SLS (Strata Logging Service)
  • The rules interzone-default' & 'intrazone-default' have been modified to include the log forwarding profile for SLS.
  • But the CNGFW still do not send logs for rules interzone-default' & 'intrazone-default' to SLS.
  • However, the Admin can confirm traffic is hitting these rules and the logs are observed in Aws or Azure side


Environment


  • Cloud NGFW for Aws or Azure
  • Panorama with Strata Logging Service (Formerly Cortex Data Lake)


Cause


The behavior is expected for CNGFW on both Aws and Azure since there are predefined default rules on the firewall



Resolution


Workaround:

  1. Create identical  'interzone-default' & 'intrazone-default' rules in Pre-rule base Or Post-rule base with the desired logging profile.
  2. This will make sure that these rules are hit first and they will log to SLS as configured.
  3. Alternatively, add a new rule at the bottom of your rule stack with desired action and select the configured logging profile. 


Additional Information


About Rulestacks and Rules on Cloud NGFW for AWS

Actions
  • Print
  • Copy Link

    https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u0000008Vz0CAE&lang=en_US&refURL=http%3A%2F%2Fknowledgebase.paloaltonetworks.com%2FKCSArticleDetail