Network Security
Policy Object: Traffic Objects
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
Policy Object: Traffic Objects
Create traffic objects to specify cloud entities within specific clusters or VPC
endpoints to enforce customized security policy rules.
This feature is part of the
AI Runtime Security licensing. The AI traffic from the zone is routed to the AI
Runtime Security instance for inspection.
Where Can I Use This? | What Do I Need? |
---|---|
|
Prerequisite
Configure a Cluster ID in the Kubernetes
environment and configure the PAN-CNI plugin on a Kubernetes cluster to allocate the
network interfaces on each pod. To configure the PAN-CNI plugin for your Kubernetes
cluster, you need three YAML files: `pan-cni-configmap.yaml`, `pan-cni.yaml`, and
`pan-cni-multus.yaml`. These files are essential for setting up and managing the
PAN-CNI plugin to secure your Kubernetes clusters with the CN-Series firewall.
To create a policy object
of type Traffic objects:
- Go to Manage > Configuration > NGFW and Prisma Access > Objects > Traffic Objects.
- Select Add Traffic Object
- Enter a Name for the Traffic Object.
- Write a Description.
- Select the Type as K8s Cluster ID or VPC Endpoint ID.
- In the Traffic Object ID, enter the K8s Cluster ID or the VPC Endpoint ID.
- If the type is K8s Cluster ID, the traffic object ID values can be between 1-2048
- If the type is VPC Endpoint ID, the Traffic Object ID format is:vpc-xxxxxxxxxxxxxxxxx (with 17 alphanumeric characters)
- Select the existing ingress Zone for the traffic object or create a new zone.
- Select Save to create the traffic object.This creates a sub-interface using the zone and the K8s Cluster ID and we map the sub-interface to the zone. This zone is used to define granular security policies on the cloud assets within a zone.Next, go to Security Services > Security Policy to create a security policy rule and attach this zone to the policy rule to enforce the security rule to all the cloud entities enclosed within the traffic object.