Witness Anywhere Overview

In hybrid and remote environments, users often access AI tools from locations or devices that do not communicate through enterprise proxies or Secure Service Edge (SSE) infrastructure.

Witness Anywhere protects remote devices by applying our proxy automatic configuration (PAC) settings, which directs devices to send all their AI traffic to your organization’s dedicated WitnessAI instance.

Anywhere provides complete visibility, control, and protection for all AI application usage across remote laptops, desktops, and mobile devices. It supports monitoring across more than 4,000 AI application URLs and captures relevant conversational context to enable auditing and analysis, while aligning with privacy and compliance requirements.

Deployment Options

Witness Anywhere is designed for enterprise-grade scalability, offering multiple deployment pathways tailored to the needs of large organizations.

💡

Note: When Enterprise Firewall or SASE endpoint agents are deployed on user devices, Witness Anywhere may not be required.

Please see full details below.

EDR Integration

For companies already leveraging CrowdStrike, Witness/Anywhere can be seamlessly integrated to enhance observability and control without disrupting existing workflows.

Mobile Device

Management (MDM) Solutions like Jamf, Kandji, and Fleet allow IT teams to centrally deploy Witness Anywhere across diverse device ecosystems.

Active Directory (AD)

Using tools such as Group Policy Objects (GPO) or Microsoft Intune, enterprises can deploy Witness Anywhere quickly and securely to devices managed through AD.

Firewall/SASE Endpoint Agents Co-Residing with Witness Anywhere

During WitnessAI deployment, our integrations will be configured on your Enterprise Firewall and SASE solutions. Depending on how network Endpoint Agents are configured on your devices, you may or may not need to deploy Witness Anywhere on them.

“Always ON” Firewall/SASE Endpoint Agents

When Firewall/SASE endpoint agents are configured in “Always On” mode, Witness Anywhere is not required. The Firewall/SASE integration seamlessly handles proxy chaining to the WitnessAI proxy.

“On-Demand” Firewall/SASE Endpoint Agents

When Firewall/SASE endpoint agents are configured in “On-Demand” mode, or when users have the ability to disable the agent, it is recommended to deploy Witness Anywhere (W/A). This ensures that AI traffic is properly forwarded to the Witness AI Proxy even when the Firewall/SASE agent is not active.

To maintain seamless connectivity when the Firewall/SASE agent is enabled, configure your Firewall or SASE solution to allow traffic to the following domains and ports:

Allow traffic toapi.{tenant-id}.{region}.witness.aion port 443
Allow traffic to*.proxy.{tenant-id}.{region}.witness.aion port 8443
Allow traffic tocdn.witness.aion port 443

If the Firewall or SASE solution performs SSL inspection for these destinations, ensure that the WitnessAI Proxy CA certificate is imported and trusted by the Firewall/SASE solution.

Unsupported Scenarios

Users with Multiple Accounts on a Device

On Windows machines with multiple user accounts (e.g., managed and local administrator accounts), Witness Anywhere registration will fail if the user is signed in with a local or personal account at the time of registration.
This occurs because the username or email associated with the local account does not match any entries in the WitnessAI Console user database.

Witness Anywhere Co-Resident with other PAC-Based Solutions

Since Witness Anywhere relies on the system PAC file to forward remote device AI traffic to the WitnessAI in stance, other firewall or agent solutions that modify the system's proxy or PAC configurations requires install ing the Witness Anywhere may interfere with Witness Anywhere’s traffic forwarding logic.

Maintenance Life Cycle

💡

Note: See the Maintenance & Support page for full details.

Installation

Witness Anywhere uses script-based deployment using installation PAC tokens.
Scripts are not persistent agents. Scripts do not self-update. Any script updates require redeployment using the customer’s endpoint management system.
Logs are written to system temporary directories. Script exit codes indicate success or failure. Fleet-level monitoring should be handled by the customer’s endpoint management platform.

Installation PAC Tokens

Tokens are used to generate installation scripts. Once a device is successfully registered, the token is no longer required. Token expiration does not affect existing installations. Expired tokens only prevent new device registrations with the expired token..
To onboard additional devices after token expiration, generate a new token in the WitnessAI Console.

Installation Updates & Backward Compatibility

Installations rarely require updating after initial installation. When updates are required, WitnessAI will publish notice in the current Release Notes, and our Customer Success Team will notify the appropriate customer contacts.
When WitnessAI releases updated installation scripts, existing installations are not modified automatically. Updates require explicit redeployment by administrators.

Proxy Enforcement

Witness Anywhere relies on system proxy and PAC configuration to enforce traffic routing.
WitnessAI highly recommends enforcing PAC configuration via MDM or Group Policy, Restricting local administrator access, and monitoring proxy configuration drift.
If users can modify proxy settings, enforcement may be bypassed.

Uninstallation/Removal

Witness Anywhere is removed with the flush script generated during during PAC Token creation.

Stunnel Maintenance

Witness Anywhere scripts automatically deploy Stunnel as a local encrypted proxy component. When Witness Anywhere is removed with the flush script, Stunnel is also removed.
Stunnel security or reliability updates are delivered through updated installation scripts provided by WitnessAI.

Witness Anywhere Overview Deployment Options EDR Integration Mobile Device Active Directory (AD)Firewall/SASE Endpoint Agents Co-Residing with Witness Anywhere “Always ON” Firewall/SASE Endpoint Agents “On-Demand” Firewall/SASE Endpoint Agents Unsupported Scenarios Users with Multiple Accounts on a Device Witness Anywhere Co-Resident with other PAC-Based Solutions Maintenance Life Cycle Installation Installation PAC Tokens Installation Updates & Backward Compatibility Proxy Enforcement Uninstallation/Removal Stunnel Maintenance