List view
Quick Start
Quick Start
User Guide
User Guide
Policies & GuardRails
Policies & GuardRails
Witness Anywhere: Remote Device Security
Witness Anywhere: Remote Device Security
Witness Attack
Witness Attack
Administrator Guide
Administrator Guide
Palo Alto Networks NGFW Configuration
Network device integrations have been updated in WitnessAI v2.0. Devices configured for WitnessAI v1.5 will need a minor update to support v2.0. Some new features will not activate until your devices are updated.
Existing v1.5 network devices will continue to work without interruption in v2.0.
See the network integration guides in the Integrations menu for details.
Have questions? Our support team will be happy to assist.
Prerequisites
Backup Your Configuration
Always create a backup of the firewall configurations before implementing new changes. For instructions on how to backup the configs, please refer to:
Verify licenses
WitnessAI requires Palo Alto NGFW have licenses for Advanced URL Filtering (1), and Threat Prevention (2).
Verify licenses and check expiration dates in the configuration console.
Install WitnessAI Root Certificate
- Go to Device β Certificate Management β Certificates
- Click Import β Import cert provided by Account Team
3. Once the cert is imported, Click on it and Select Trusted Root CA and click OK
Β
Setup EDL Certificate Profile
- Certificate will be provided by support.
- Go to Device β Certificates and click on Import
- Give the certificate name as Witness-AI-CA and upload the CA certificate by clicking on Browse
- Go to Device β Certificate Profile Β and click on Add
- Give the name as Witness-AI-CP and click on the Add button under CA Certificates
- Select the Witness-AI-CA certificate and click OK
- Use this certificate Profile for the EDL Configuration.
Create External Dynamic List
This section will focus on creating the WitnessForwardDomainList, which are LLM projects that traffic will be forwarded to WitnessAI.
1. Go to Objects β External Dynamic Lists β Add
Β
2. Click Add and enter the following configurations:
Name β WitnessForwardDomainList
Type β Domain List
Source β https://api.[tenantID].[region].witness.ai/v1/edls/forwardlist.txt
Check for Updates β Every five minutes
Click OK
Create Custom Application for Office
Create a Custom Application for traffic towards augloop.office.com as Palo Alto Firewall identifies this as a WebSocket connection and fails to insert HTTP headers.
- Go to Objects β Applications
- Click Add and name the application augloop
- Select the basic properties as per the below values:
a. Category β general-internet
b. Subcategory β internet-utility
c. Technology β browser-based
d. Parent App β ms-office365-copilot
e. Risk β 1
- Go to the Advanced tab and select Port
- Add the port information as below:
a. tcp/443
b. tcp/80
- Go to the Signatures tab and click Add
- Configure the following settings:
a. Name β AugloopSig
b. Scope β Session
c. Select Add Or Condition
d. Operator β Pattern Match
e. Context β http-req-headers
f. Pattern β (augloop.office.com)
g. Click OK and Click OK again
Redirect AI Traffic to WitnessAI
Create an Anti-Spyware Profile to redirect any DNS request from the WitnessForwardDomainList to WitnessAI.
- Go to Objects β Security Profiles β Anti-Spyware β Click Add
- Set the following settings:
Name β WitnessAI_Sinkhole
DNS Policies β Set the Policy Action as sinkhole for WitnessForwardDomains EDL.
Sinkhole IPv4 β See instructions below:
Note: To obtain the sinkhole IPv4 address, ping the following:
connect.[tenantID].[region].witness.ai
connect.[tenantID].[region].witness.ai
Click OK
URL Filtering Profile to add User Info
Create a URL Filtering Profile and configure HTTP Header Insertion to add the user email address in the X- Authenticated-User Header field.
- Go to Objects β Security Profiles β URL Filtering β Add
- Configure the following settings:
- Name β WitnessAI_URL-Filtering
- Under External Dynamic URL Lists, select WitnessURLs and change Site Access to alert.
- Note: This will ensure that URL filtering logs are created for any traffic matching these URLs.
- Click on the HTTP Header Insertion tab and click Add
- Configure the following settings:
- Name β X-Auth-User
- Type β Dynamic Fields
- Domain β
- Header β X-Authenticated-User
- Value β ($user)@($domain)
- Check the Log box
Create Decryption Profile & Policy
- Go to Object β Decryption β Decryption Profile β Add
- Set the following configurations:
- Name β Witness-Decrypt
- Enable Strip ALPN
3. Click SSL Protocol Settings and configure the following:
- Min Version β TLSv1.0
- Max Version β TLSv1.2
4. Go to Policies β Decryption
5. Create a new decryption policy for decrypting all SSL traffic going towards the AI URLs maintained by Witness AI.
- Source Zone β LAN/GP Zone
- Destination Zone β WAN
- URL Category βΒ WitnessURLs
- Action β Decrypt
- Type β SSL Forward Proxy
- Decryption Profile β Witness-Decrypt
Note: Create a new Profile and make sure that the Strip ALPN checkbox on the Decryption Profile is enabled
Create Security Policy for DNS Sinkhole
Use the URL Filtering Profile and Anti-Spyware Profile in a security Policy created for allowing access to AI URLs maintained by Witness AI.
- Go to Policies β Security
- Create a new security policy for allowing traffic towards AI URLs maintained by WitnessAI.
- Source Zone β LAN/GP Zone
- Destination Zone β WAN
- Action β Allow
- Anti-Spyware Profile β WitnessAI_Sinkhole
Create Security Policy for URL Filtering
Use the URL Filtering Profile and Anti-Spyware Profile in a security Policy created for allowing access to AI URLs maintained by Witness AI.
- Go to Policies β Security
- Create a new security policy for allowing traffic towards AI URLs maintained by WitnessAI.
- Source Zone β LAN/GP Zone
- Destination Zone β WAN
- URL Category β WitnessURLs
- URL Filtering β WitnessAI_URL-Filtering
Implement Block for Quic Protocol
Quic is a Google developed protocol which uses UDP for web connections and limits the firewall visibility and ability to analyze and apply security actions.
- Note: If the Quic protocol is not already blocked, please perform this step.
- Go to Policies β Security
- Click Add to create a new security policy for blocking quic protocol.
- Name the rule Quic Block.
4. Block any quic protocol traffic from LAN/GP Zone towards the internet.
- Source Zone β LAN/GP Zone
- Destination Zone β WAN
- Application β quic
- Action β Deny
5. Click OK
6. Move the Quic Block rule to the top.
Commit Change
The last step is to commit the change to the firewall. This will implement and enable the configuration changes made.
- Click Commit
- Review changes and implement the configuration changes.
Palo Alto Networks NGFW ConfigurationPrerequisitesBackup Your ConfigurationVerify licensesInstall WitnessAI Root CertificateSetup EDL Certificate ProfileCreate External Dynamic ListCreate Custom Application for OfficeRedirect AI Traffic to WitnessAIURL Filtering Profile to add User InfoCreate Decryption Profile & PolicyCreate Security Policy for DNS SinkholeCreate Security Policy for URL FilteringImplement Block for Quic ProtocolCommit Change
Β
Β