Prisma AIRS
Network Channels
Table of Contents
Network Channels
Secure network traffic and enforce security policies across diverse environments with
the Network Channels.
| Where Can I Use This? | What Do I Need? |
|---|---|
|
|
Network Channels is a secure connection solution that enables AI Red Teaming to
safely access and analyze your internal endpoints without requiring IP whitelisting or
opening inbound ports. This enterprise-grade solution puts you in complete control of
the connection, allowing you to initiate and terminate access at will while maintaining
your security perimeter.
Network channels help you achieve the following:
- Enhanced Security—No need to expose internal endpoints or modify firewall rules.
- Complete Control—Initiate and terminate connections on demand.
- Easy Setup—Simple client installation process.
- Flexible Management—Create and manage multiple secure channels for different environments.
- Reusability—Use the same connection for multiple targets.
- Enterprise Ready—Designed for organizations with strict security requirements.
Network Channels consists of two main components client and server:
Client
- It is a lightweight daemon that runs in your infrastructure.
- It initiates and outbound webSocket connection to AI Red Teaming servers and maintains it.
- Once websocket connection is established, it proxies the requests from the server to your internal endpoints.
- It consumes minimal system resources.
Server
AI Red Teaming's server-side component that:
- Manages WebSocket connections from client.
- Handles authentication.
- Routes requests from red teaming workers to the targets through the established websocket connections.
Here’s what the AI Red Teaming system architecture looks like with network channel
enabled:
Network Channels Technical Flow
- Client initiates secure WebSocket connection to server.
- Server authenticates client.
- Persistent connection is established.
- AI Red Teaming services make requests through the server.
- Requests are forwarded to the client via the websocket.
- Client forwards request to target endpoint.
- Responses follow reverse path.
