Deploy WAAS Agentless
Table of Contents
Prisma Cloud Enterprise Edition
Expand all | Collapse all
-
- Getting started
- System Requirements
- Cluster Context
-
- Defender Types
- Manage your Defenders
- Redeploy Defenders
- Uninstall Defenders
-
- Deploy Orchestrator Defenders on Amazon ECS
- Automatically Install Container Defender in a Cluster
- Deploy Prisma Cloud Defender from the GCP Marketplace
- Deploy Defenders as DaemonSets
- VMware Tanzu Application Service (TAS) Defender
- Deploy Defender on Google Kubernetes Engine (GKE)
- Google Kubernetes Engine (GKE) Autopilot
- Deploy Defender on OpenShift v4
- Deploy Defender with Declarative Object Management
-
- Agentless Scanning Modes
-
- Onboard AWS Accounts for Agentless Scanning
- Configure Agentless Scanning for AWS
- Onboard Azure Accounts for Agentless Scanning
- Configure Agentless Scanning for Azure
- Onboard GCP Accounts for Agentless Scanning
- Configure Agentless Scanning for GCP
- Onboard Oracle Cloud Infrastructure (OCI) Accounts for Agentless Scanning
- Configure Agentless Scanning for Oracle Cloud Infrastructure (OCI)
- Agentless Scanning Results
-
- Rule ordering and pattern matching
- Backup and Restore
- Custom feeds
- Configuring Prisma Cloud proxy settings
- Prisma Cloud Compute certificates
- Configure scanning
- User certificate validity period
- Enable HTTP access to Console
- Set different paths for Defender and Console (with DaemonSets)
- Authenticate to Console with Certificates
- Customize terminal output
- Collections
- Tags
- WildFire Settings
- Log Scrubbing
- Permissions by feature
-
- Prisma Cloud Vulnerability Feed
- Scanning Procedure
- Vulnerability Management Policies
- Vulnerability Scan Reports
- Scan Images for Custom Vulnerabilities
- Base images
- Vulnerability Explorer
- CVSS scoring
- CVE Viewer
-
- Configure Registry Scans
- Scan Images in Alibaba Cloud Container Registry
- Scan Images in Amazon Elastic Container Registry (ECR)
- Scan images in Azure Container Registry (ACR)
- Scan Images in Docker Registry v2 (including Docker Hub)
- Scan Images in GitLab Container Registry
- Scan images in Google Artifact Registry
- Scan Images in Google Container Registry (GCR)
- Scan Images in Harbor Registry
- Scan Images in IBM Cloud Container Registry
- Scan Images in JFrog Artifactory Docker Registry
- Scan Images in Sonatype Nexus Registry
- Scan images in OpenShift integrated Docker registry
- Scan Images in CoreOS Quay Registry
- Trigger Registry Scans with Webhooks
- Configure VM image scanning
- Configure code repository scanning
- Malware scanning
- Windows container image scanning
- Serverless Functions Scanning
- VMware Tanzu Blobstore Scanning
- Scan App-Embedded workloads
- Troubleshoot Vulnerability Detection
-
- Compliance Explorer
- Enforce compliance checks
- CIS Benchmarks
- Prisma Cloud Labs compliance checks
- Malware Scanning
- Serverless functions compliance checks
- Windows compliance checks
- DISA STIG compliance checks
- Custom compliance checks
- Trusted images
- Host scanning
- VM image scanning
- App-Embedded scanning
- Detect secrets
- OSS license management
-
- Alert Mechanism
- AWS Security Hub
- Cortex XDR alerts
- Cortex XSOAR alerts
- Email alerts
- Google Cloud Pub/Sub
- Google Cloud Security Command Center
- IBM Cloud Security Advisor
- JIRA Alerts
- PagerDuty alerts
- ServiceNow alerts for Security Incident Response
- ServiceNow alerts for Vulnerability Response
- Slack Alerts
- Splunk Alerts
- Webhook alerts
- API
Deploy WAAS Agentless
WAAS agentless rules inspect HTTP requests and responses through a mirror of the traffic to provide WAAS detections.
To optimize the CPU utlization while using WAAS, Prisma Cloud scanner samples only a subset of the mirrored data to discover just the APIs and the scanner does not inspect the request body field, the sensitive request, and the response data.
WAAS can observe a mirror of HTTP traffic flowing to and from CSP (AWS) instances, even if they are not protected by a Prisma Cloud Compute Defender.
VPC Observer is an EC2 instance running a Host defender for VPC Traffic Mirroring.
The target instance is configured on a separate instance within the same VPC to receive Out-Of-Band traffic from the unprotected applications on the source instance. These Observers on the target instance inspect Out-Of-Band traffic and send audits of any events they identify to Prisma Cloud console.
To set up WAAS agentless with VPC traffic mirroring, specify the EC2 instances to mirror (exact names or using wildcards or tags) in a VPC, the ports to mirror, and other AWS parameters in a VPC traffic mirroring rule.
For each VPC traffic mirroring rule, a VPC Observer will be created in a VPC machine to receive the mirrored traffic (the VPC Observer is an EC2 instance running a host Defender).
Monitoring applications with WAAS agentless through VPC traffic mirroring is subject to limitations, quotas, and checksum offloading as defined in the AWS documentation.
Prerequisites
- To configure WAAS agentless with AWS VPC traffic mirroring, apply the permission template ending in agentless_app_firewall_permissions_template.yaml to AWS CloudFormation console for your account. For detailed instructions on how to apply cloud formation templates, refer to the AWS documentation.Amazon EC2 Auto Scaling is integrated with this AWS CloudFormation permission template.Edit the template and replace the "USER-agentless-app-firewall" value with the actual username that you want to grant these permissions.WAAS agentless permissions policies created in AWS:WAAS agentless resources stack deployed in AWS:
- Create an AWS Cloud account underCompute > Manage > Cloud accountsusing the Access key from your AWS account.Cloud accounts requireCloud discoveryto be enabled to discover the EC2 instances to mirror.
Create a WAAS Agentless Rule for VPC Traffic Mirroring
To deploy WAAS agentless with VPC traffic mirroring, create a new rule, configure VPC, define application endpoints, and select protections.
- Create a WAAS rule underDefend > WAAS > Agentless > Add rule.
- Enter aRule NameandNotes(Optional) for describing the rule.
- AddVPC Configurationto allow the mirrored traffic to flow from the source instance to the Prisma Cloud Observer deployed on the target instance.
- SelectConsole addressas the hostname of the Console to connect to.
- Select the credentials for the AWSCloud accountthat you configured underManage > Cloud accounts.
- Choose the AWSRegionwhere the mirrored VMs are located in.
- Enter theVPC IDto look for instances to mirror and to deploy the Observer in.
- Enter theVPC Subnet IDto look for instances to be mirrored only in the selected Subnet ID, and to deploy the Observer in.
- Specify theTagsor wildcards identifying the EC2 instances to mirror in any of the following format:
- <key:value> = Match tags by key and value pair.
- <key:> = Match tags with key and empty value (for example, AWS tags allow just a key, with no value (empty string)).
- * = Match all tags.
- EnterInstance namesor wildcards to identify the EC2 instances to mirror.The instance to mirror is mapped by machine tags:instance names.
- Enter thePortsto mirror.You can enter a maximum of 5 ports. Port ranges are not supported.
- Select theObserver Instance typeto use for the VPC Observer instance.
- EnableAuto scalingto automatically scale WAAS Observers to handle a large amount of traffic volume or sudden decrease in traffic volume. You can set a limit of maximum instances between 1 and 10.
- SelectAdd.The Deployment will be done using a dynamically constructed AWS CloudFormation template, programmatically with CloudFormation API. The WAAS rule is not immediately applied, there will be stages of the rules as the VPC configuration is being deployed in AWS. You can track the status of the deployment in the AWS CloudFormation stack, and also on Prisma Cloud Console.
- (Optional) Toggle to enableAPI endpoint discovery.When enabled, the Observer inspects the mirrored traffic to and from the remote applications. The Observer reports a list of the endpoints and their resource path inCompute > Monitor > WAAS > API discovery.
- Savethe rule.A scheduled scan runs every hour to check for new and deleted EC2 instances based on the VPC configurations instance names and tags. If a change is found in the list of EC2 instances to mirror, the AWS VPC traffic mirroring setup will be updated.To force a scan, you can clickUpdate.
Add an App (policy) to the Rule
- Select a WAAS rule to add an App in.
- SelectAdd app.
- In theApp Definitiontab, enter anApp ID.The combination ofRule nameandApp IDmust be unique across In-Line and Out-Of-Band WAAS policies for Containers, Hosts, and App-Embedded.If you have a Swagger or OpenAPI file, clickImport, and select the file to load.If you do not have a Swagger or OpenAPI file, manually define each endpoint by specifying the host, port, and path.
- InEndpoint Setup, selectAdd endpoint.
- Specify an endpoint in your web application that should be protected. Each defined application can have multiple protected endpoints.
- EnterHTTP host(optional, wildcards supported).HTTP hostnames are specified in the form of [hostname]:[external port].The external port is defined as the TCP port on the host, listening for inbound HTTP traffic. If the value of the external port is "80" for non-TLS endpoints or "443" for TLS endpoints, it can be omitted. Examples: "*.example.site", "docs.example.site", "www.example.site:8080", etc.
- EnterBase path(optional, wildcards supported) for WAAS to match.Examples: "/admin", "/" (root path only), "/*", /v2/api", etc.
- EnableTLSif your application uses the TLS protocol.
- SelectCreate.
- To facilitate inspection, after creating all endpoints, selectView TLS settingsin the endpoint setup menu.WAAS TLS settings:
- Certificate- Copy and paste your server’s certificate and private key into the certificate input box (e.g., cat server-cert.pem server-key > certs.pem).
- If your application requires API protection, select the "API Protection" tab and define for each path the allowed methods, parameters, types, etc. See detailed definition instructions in the API protection help page.
- Continue toApp Firewalltab, and select the protections as shown in the screenshot below:For more information, see App Firewall settings.
- Continue toDoS protectiontab and select DoS protection to enable.
- Continue toAccess Controltab and select access controls to enable.
- Continue toBot protectiontab, and select the protections as shown in the screenshot below:For more information, see Bot protections.
- Continue toCustom rulestab and select Custom rules to enable.
- Continue toAdvanced settingstab, and set the options shown in the screenshot below:For more information, see Advanced settings.
- SelectSave.
- You should be redirected to theRule Overviewpage.Select the created new rule to displayRule Resourcesand for each application a list ofprotected endpointsandenabled protections.
- Test protected endpoint using the following sanity tests.
- Go toMonitor > Events > WAAS for Agentlessto observe the events generated.For more information, see the WAAS analytics help page
VPC Configuration Status
Once the VPC configuration is saved, a CloudFormation template will be created and deployed in the selected region. You can track the stack deployment stages through Prisma Console.
- Deploying: The WAAS rule is getting ready as the Observer is being deployed in the AWS instance and the session is being established between the Observer and the resources.Refreshto view the updated deployment status.
- Ready: The WAAS rule is ready to be protecting the selected resources. The Observer will check for new instances (based on the selected tags or instance names) once every hour.
- Error: The rule is in error and the deployment failed. Fix the error, and clickUpdateto reapply the configuration.
- Deletion in progress: The Observer deployment is being torn down, and the session is being terminated.
- Deletion error: Error in tearing down the Observer setup on AWS VPC.

Use
Refresh
to see the updated status of the rules on the UI.When the VPC configuration is in
Error
status, an Update
is allowed to reapply the configuration.You can
Delete
an Agentless rule, that will tear down the entire VPC stack configuration and resources. Once the rule deletion is complete, the rule will disappear from the Console and the Observer will be uninstalled.The VPC Observer is installed under
Manage > Defenders > Deployed Defenders
. A VPC observer can only be deleted if you delete the rule from the Console.Update VPC Configurations
You can edit the VPC configurations only to update the Tags, Instance names, Ports, and Observer instance type. This will update the AWS CloudFormation template, and AWS will create/destroy only the updated AWS resources.
If you update the instance type of the VPC Observer, then AWS will recreate the EC2 instance and there will be a downtime.

Edit the fields and
Save
to reapply the configurations.WAAS Actions for Out-Of-Band Traffic
The following actions are applicable for the HTTP requests or responses related to the
Out-Of-Band traffic
:- Alert- An audit is generated for visibility.
- Disable- The WAAS action is disabled.
Limitations
Limitations for setting traffic mirroring imposed by AWS
- Not all AWS instance types support traffic mirroring, for example, T2 is not supported (relevant for both source and target EC2 instances).
- Some regions don’t currently support the 'm5n.2xlarge' and 'm5n.4xlarge' instance types, so these types cannot be used for VPC Observer (For example, Paris).
TLS Limitations
- TLS settings for agentless support TLS 1.0, 1.1, and 1.2.
- Only the following RSA Key Exchange cipher suites are supported:
- TLS_RSA_WITH_AES_128_CBC_SHA256
- TLS_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_RSA_WITH_RC4_128_SHA
- TLS connections using extended_master_secret(23) in the negotiation are not supported as part of this feature.
- Out-Of-Band does not support HTTP/2 protocol.
- DHKE is not supported due to a lack of information required to generate the encryption key.
- The full handshake process must be captured. Partial transmission or session resumption process inspection won’t be decrypted.
- Same VPC configuration cannot be used to inspect both HTTP and HTTPS traffic, you must create two different Agentless rules, one for each HTTP and HTTPS traffic monitoring.You must upgrade the VPC Observer throughManage > Defenders.
WAAS Agentless Limitations
- An EC2 instance can only be attached to one agentless rule.
- An agentless rule can only inspect machines from one VPC and Subnet combination.
- Each agentless rule can only have a maximum of 5 ports in the VPC configuration.
- Changing the VPC observer instance types involves downtime.
- Once the AWS setup is created/updated in the agentless rule, the Observer status is only available onManage > Defenders > Deployed defenderspage.
Troubleshoot VPC Traffic Mirroring Errors
When the configuration status shows the following error, as shown in the screenshot below, check the AWS CloudFormation stack events for the error.

Some scenarios in the AWS CloudFormation that may lead to the above error are as follows:
You are not authorized to perform this operation
This is because the selected AWS cloud account doesn’t have enough permissions for deployment.

- Modify the account with the correct permissions as mentioned in the agentless_app_firewall_permissions_template.json file, and selectUpdateto retry the deployment.
- Delete the rule in error and create a new rule in the AWS Cloud account with the permissions as mentioned in the agentless_app_firewall_permissions_template.json file to AWS CloudFormation console for your account.
SessionNumber 1 already in use for eni-*
Trying to mirror an already mirrored EC2 instance (either by WAAS or another product).

- Edit the VPC configuration and remove the instance from the tags or instance names list, and clickUpdateto retry the deployment.
- Remove the mirroring from the machine from the other rule/other product, and clickUpdateto retry the deployment.
WaitCondition received failed message: 'Defender deployment failed' for uniqueid: i-xxxx.
AWS CloudFormation stack failed to deploy the WAAS agentless resources because Prisma Console is not accessible from AWS.

- Make sure that the IP address of Prisma Console in the VPC configuration is public.
- Check if the Defender instance has a public IP address.
- Check if AWS account can connect with the Prisma Cloud Console with Console URL that you selected in the VPC configuration.
- If the Console is not reachable, delete the rule and create a new rule with a valid Prisma Cloud Console URL.
- If the Console is not reachable due to a firewall rule or other blocking rules, fix the rule to allow the connectivity to the Console, and clickUpdateto retry the deployment.
- Ensure that the Console’s IP address and the ports are reachable by the Defender. Also, the firewall is open with the relevant port and source IPs.
Failed to find VMs to mirror
The security token included in the request is invalid.

- Edit Configurationto ensure that the AWS cloud account exists for the user, and also ensure that a correct secret key is used,Savethe configuration.
- ClickUpdateto reapply the configuration.