Incident Event Codes—Security Services
Focus
Focus
Prisma SD-WAN

Incident Event Codes—Security Services

Table of Contents

Incident Event Codes—Security Services

Incident event codes in the Security Services category for troubleshooting in Prisma SD-WAN.
Where Can I Use This?What Do I Need?
  • Prisma SD-WAN (Managed by Strata Cloud Manager)
  • Prisma SD-WAN
The following table lists incident event codes in the Security Services category. In Strata Cloud Manager Incidents, these codes appear with the INC_SDWAN_ prefix.
Incident Event Codes—Security Services
INCIDENT CODEINCIDENT/ALERTSEVERITYEVENT TITLEEVENT DESCRIPTIONRELEASECATEGORYSUB-CATEGORYREMEDIATION
INC_SDWAN_DEVICESW_DNSSECCLOUDSERVER_DOWN
INCIDENTWarningThe connection between the ION and the DNS Security Cloud Server has been lost, preventing DNS Security cloud categorization and verdict retrieval for DNS requests.6.5.3-iSecurity ServicesDNS Security
Step 1: Review the incident details and record the affected tenant, site, ION, incident start time, duration, software version, and related incidents.
Step 2: In Strata Cloud Manager, navigate to Configuration > Prisma SD-WAN > Policies > Security > Security Profile Groups. Confirm that a DNS Security Profile is included in the applicable Security Profile Group and that the group is applied to the affected site.
If the Security Profile Groups option is not visible, confirm that the Branch Security subscription is assigned to the tenant.
Step 3: Navigate to Configuration > Prisma SD-WAN > Devices > Claimed Devices and hover over the affected device’s Online/Offline status. Review:
DNS Security Cloud Connection Status
URL Security Services Connection Status
Logging Service Connection Status
Config and Events
Analytics
Flows
Last Disconnected Time
Last Reboot Reason
Determine whether only DNS Security is disconnected or whether the ION has a broader cloud-connectivity problem.
Step 4: Access the ION through the Remote CLI Toolkit if the ION is online. If the controller connection is also down, use SSH or console. Run the following commands where supported:
dump overview
dump dns-security state json
dump dns-security agent status
dump dns-security config json
dump security-policy config profile-groups all
Step 5: Review the output and confirm:
DNS Security Server Connection in dump overview
enabled: true
configured_in_policy: true
initialization_complete: true
dnssec_agent_connected: true
service_status: Running
support_state: Active
connection_state: Connected
Recent last_receive_time and last_send_time
The last_reconnect_time and last_disconnect_reason
The selected source_interface
source_interface_selection_state: Completed
The configured DNS Security Cloud FQDN
The expected DNS Security Profile in the applicable profile group
Step 6: Check the interface selected by the DNS Security agent:
dump interface status <source_interface>
dump interface config <source_interface>
Confirm that the interface is operational and has a valid IP address, default route, gateway, and DNS server.
Step 7: Test DNS resolution and connectivity to the DNS Security Cloud endpoint reported by dump dns-security config json. The expected endpoint in the supplied output is dns.service.paloaltonetworks.com:
ping <source_interface> dns.service.paloaltonetworks.com
tcpping <source_interface> dns.service.paloaltonetworks.com:443
A hostname resolved to an IP address confirms that DNS resolution is working. A failed ICMP response alone does not prove the service is unreachable because ICMP may be blocked. The TCP 443 test is the primary connectivity check.
If hostname resolution fails, obtain the DNS server address from the interface-status output and run:
dig <source_interface> <dns_server_ip> dns.service.paloaltonetworks.com
Step 8: If the connectivity test fails, verify routing, DNS, NAT, and upstream firewall policies. Confirm that outbound TCP port 443 to the DNS Security Cloud is allowed and that a proxy or TLS-inspection policy is not interfering with the connection.
Step 9: If the CLI shows enabled: false, configured_in_policy: false, or a missing DNS Security Profile, correct the configuration in Strata Cloud Manager and push it to the ION. Do not modify the configuration locally from the toolkit on a claimed or assigned ION.
Step 10: After remediation, confirm:
connection_state: Connected
dnssec_agent_connected: true
last_receive_time and last_send_time continue to update
DNS Security Cloud Connection Status shows Online in SCM
The incident clears automatically
If SLS logging is licensed and enabled, review current DNS logs under Network > DNS or the Domains view in Activity Insights to confirm that DNS Security verdicts are being received.
Step 11: If the incident persists or repeatedly returns, save the command outputs and collect a support bundle:
dump-support all file=dns-security-cloud-down
For earlier releases that do not support the all option:
dump-support outputs file=dns-security-cloud-down
Attach the incident details, CLI outputs, reachability-test results, and support bundle to a Palo Alto Networks Support case. Do not restart the DNS Security agent or reboot the ION unless instructed by Support.
INC_SDWAN_SECURITY_POLICY_RULES_FAILED
ALARMCriticalOne or more security policy rules could not be created on the affected ION because of an internal error or insufficient available memory. The failed rules may not be enforced until creation succeeds.6.3.6Security Services
Step 1: Review the incident details and record the affected site, ION, incident time, software version, Security stack and set, failed rule identifiers, and reported failure reason.
Step 2: In SCM, go to Configuration > Prisma SD-WAN > Policies > Security > Security Stacks and review the affected Simple or Advanced policy and Security Set.
Step 3: Run inspect security-policy size and inspect memory summary. Review related SYSTEM_MEMORY_THRESHOLD_EXCEEDED or process incidents at the same time.
Step 4: If the failure followed a policy change and a rule is invalid or incomplete, correct it through SCM. If device memory is constrained, reduce unnecessary policy expansion while preserving required security behavior.
Step 5: Push the corrected policy and confirm that all required rules are created and the incident clears.
Step 6: If the failure is an internal error or persists with adequate memory and valid configuration, collect a support bundle and open a Palo Alto Networks Support case.
INC_SDWAN_DEVICESW_URLCLOUDSERVER_DOWN
INCIDENTURL Cloud Server UnreachableURL Cloud Server UnreachableThe ION cannot reach the URL Cloud Server used to categorize URL requests. URL categorization may be unavailable while the connection is down.Security ServicesURL Filtering
Step 1: Review the incident details and record the affected site, ION, incident time, software version, reported URL Cloud Server, and any recent Branch Security, DNS, routing, interface, or firewall changes.
Step 2: Go to Configuration > Prisma SD-WAN > Policies > Security > Security Profile Groups. Confirm that the expected URL Filtering profile is included in the Security Profile Group used by the affected site and that the associated security policy is bound to the site.
Step 3: Go to Configuration > Prisma SD-WAN > Devices > Claimed Devices and hover over the affected ION’s Device State. Review the Cloud Security Services Connection Status and determine whether other Branch Security cloud services are also disconnected.
Step 4: Run the following read-only commands:
dump url-filtering global-config
dump url-filtering server-status
Use dump url-filtering global-config to confirm the configured URL Cloud Server. Use dump url-filtering server-status to review its current connection state and any reported error.
Step 5: Verify that the ION can resolve and reach the reported URL Cloud Server. Confirm that the source interface is operational and that DNS, routing, NAT, firewall, and access-control policies permit the connection.
Step 6: After correcting the configuration or network issue, run dump url-filtering server-status again. Confirm that the Cloud Security Services Connection Status is operational and that the incident clears.
Step 7: If the connection remains down or the incident repeatedly returns, collect a support bundle and open a Palo Alto Networks Support case:
dump-support all file=<descriptive_filename>
For releases earlier than 6.4.1 that do not support the all option:
dump-support outputs file=<descriptive_filename>
Use a filename containing the event, ION name, and collection time, such as urlcloudserver_down_branch-ion1_20260819T1430.