Network Security
Repair Incomplete Certificate Chains (PAN-OS)
Table of Contents
Expand All
|
Collapse All
Network Security Docs
-
- Security Policy
-
- Security Profile Groups
- Security Profile: AI Security
- Security Profile: WildFire® Analysis
- Security Profile: Antivirus
- Security Profile: Vulnerability Protection
- Security Profile: Anti-Spyware
- Security Profile: DNS Security
- Security Profile: DoS Protection Profile
- Security Profile: File Blocking
- Security Profile: URL Filtering
- Security Profile: Data Filtering
- Security Profile: Zone Protection
-
- Policy Object: Address Groups
- Policy Object: Regions
- Policy Object: Traffic Objects
- Policy Object: Applications
- Policy Object: Application Groups
- Policy Object: Application Filter
- Policy Object: Services
- Policy Object: Auto-Tag Actions
- Policy Object: Devices
-
- Uses for External Dynamic Lists in Policy
- Formatting Guidelines for an External Dynamic List
- Built-in External Dynamic Lists
- Configure Your Environment to Access an External Dynamic List
- Configure your Environment to Access an External Dynamic List from the EDL Hosting Service
- Retrieve an External Dynamic List from the Web Server
- View External Dynamic List Entries
- Enforce Policy on an External Dynamic List
- Find External Dynamic Lists That Failed Authentication
- Disable Authentication for an External Dynamic List
- Policy Object: HIP Objects
- Policy Object: Schedules
- Policy Object: Quarantine Device Lists
- Policy Object: Dynamic User Groups
- Policy Object: Custom Objects
- Policy Object: Log Forwarding
- Policy Object: Authentication
- Policy Object: Decryption Profile
- Policy Object: Packet Broker Profile
-
-
-
- The Quantum Computing Threat
- How RFC 8784 Resists Quantum Computing Threats
- How RFC 9242 and RFC 9370 Resist Quantum Computing Threats
- Support for Post-Quantum Features
- Post-Quantum Migration Planning and Preparation
- Best Practices for Resisting Post-Quantum Attacks
- Learn More About Post-Quantum Security
-
-
-
- Investigate Reasons for Decryption Failure
- Identify Weak Protocols and Cipher Suites
- Troubleshoot Version Errors
- Troubleshoot Unsupported Cipher Suites
- Identify Untrusted CA Certificates
- Repair Incomplete Certificate Chains
- Troubleshoot Pinned Certificates
- Troubleshoot Expired Certificates
- Troubleshoot Revoked Certificates
Repair Incomplete Certificate Chains (PAN-OS)
- Find websites that cause incomplete certificate chain errors.
- Filter the Decryption log to identify Decryption sessions that failed because of an incomplete certificate chain.In the filter field, type the query (err_index eq Certificate) and (error contains ‘http’). This query filters the logs for Certificate errors that contain the string “http”, which finds all of the error entries that contain the CA Issuer URL (often called the URI). The CA Issuer URL is the Authority Information Access (AIA) information for the CA Issuer.
- Click an Error column entry that begins “Received fatal alert UnknownCA from client. CA Issuer URL:” followed by the URI.The NGFW automatically adds the selected error to the query and shows the full URI path (the full URI path may be truncated in the Error column).
- Copy and paste the URI into your browser and then press Enter to download the missing intermediate certificate.
- Click the certificate to open the dialog.
- Click Open to open the certificate file.
- Select the Details tab and then click Copy to File....Follow the export directions. The certificate copies to the folder you designated as your default download folder.
- Import the certificate into the NGFW.
- Navigate to DeviceCertificate ManagementCertificates and then select Import.
- Browse to the folder where you stored the missing intermediate certificate and select it. Leave the File Format as Base64 Encoded Certificate (PEM).
- Name the certificate, specify any other options you want to use, and then click OK.
- When the certificate has imported, select the certificate from the Device Certificates list to open the Certificate Information dialog.
- Select Trusted Root CA to mark the certificate as a trusted root CA, and then click OK.In DeviceCertificate ManagementCertificatesDevice Certificates, the imported certificate now appears in the list of certificates. Check the Usage column to confirm that the status is Trusted Root CA Certificate.
- Commit the configuration.
- You have now repaired the broken certificate chain.The NGFW doesn’t block the traffic because the CA issuer is now trusted. Repeat this process for all missing intermediate certificates to repair their certificate chains.