Deploy WAAS for Containers Protected By App-Embedded Defender
In some environments, Prisma Cloud Defender must be embedded directly inside the container it is protecting. This type of Defender is known as an App-Embedded Defender. App-Embedded Defender can secure these types of containers with all WAAS protection capabilities.
The only difference is that App-Embedded Defender runs as a reverse proxy to the container it’s protecting. As such, when you set up WAAS for App-Embedded, you must specify the exposed external port where App-Embedded Defender can listen, and the port (not exposed to the Internet) where your web application listens. WAAS for App-Embedded forwards the filtered traffic to your application’s port - unless an attack is detected and you set your WAAS for App-Embedded rule to
When testing your Prisma Cloud-protected container, be sure you update the security group’s inbound rules to permit TCP connections on the external port you entered in the WAAS rule. This is the exposed port that allows you to access your web application’s container. To disable WAAS protection, disable the WAAS rule, and re-expose the application’s real port by modifying the security group’s inbound rule.
To embed App-Embedded WAAS into your container or Fargate task:
Create a rule for App-Embedded
- Open Console, and go toDefend > WAAS > *App-Embedded.
- ClickAdd rule.
- Enter aRule NameandNotes(Optional) for describing the rule.
- Choose the ruleScopeby specifying the resource collection(s) to which it applies.Collections define a combination of App IDs to which WAAS should attach itself to protect the web application:
- Savethe rule.
Add an App (policy) for App-Embedded
- Select a WAAS App-Embedded rule to add an App in.
- ClickAdd app.
- In the App Definition tab, specify the endpoints in your web application that should be protected. Each defined application can have multiple protected endpoints. If you have a Swagger or OpenAPI file, click Import, and select the file to load. Otherwise, skip to the next step to manually define your app’s endpoints.
- If you don’t have a Swagger or OpenAPI file, manually define each endpoint by specifying the host, port, and path.
- In theEndpoint Setuptab, click onAdd Endpoint.
- Specify endpoint details:
- EnterApp port (required)Specify the TCP port protected app listens on, WAAS sends traffic to your app over this port.
- EnterWAAS Port (required).The external port is the TCP port for the App-Embedded Defender to listen on for inbound HTTP traffic.
- EnterHTTP host(optional, wildcards supported).HTTP host names 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.com", "docs.example.com", "www.example.com:8080", etc.
- EnterBase path(optional, wildcards supported):Base path for WAAS to match on when applying protections.Examples: "/admin/", "/" (root path only), "/*", /v2/api/", etc.
- If your application uses TLS, setTLStoOn.WAAS must be able to decrypt and inspect HTTPS traffic to function properly.To facilitate that, after creating all endpoints click onView TLS settingsin the endpoint setup menuTLS 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).
- Minimum TLS version- A minimum version of TLS can be enforced by WAAS to prevent downgrading attacks (the default value is "1.2").
- HSTS- The HTTP Strict-Transport-Security (HSTS) response header lets web servers tell browsers to use HTTPS only, not HTTP. When enabled, WAAS adds the HSTS response header to all HTTPS server responses (if not already present) with the preconfigured directives - max-age, includeSubDomains, and preload.
- If your application uses gRPC, setgRPCtoOn.
- If your application uses HTTP/2, setHTTP/2toOn.
- ClickCreate Endpoint
- Click on theResponse headerstab to add or override HTTP response headers in responses sent from the protected application.
- Continue toAccess Controltab and select access controls to enable.
- Continue toDoS protectiontab and configure DoS protection thresholds.
- Continue toBot protectiontab and select bot protections to enable.
- You should be redirected to theRule Overviewpage.Select the new rule to displayRule Resourcesand for each application a list ofprotected endpointsandenabled protections.
- Test protected container using the following sanity tests.
- Go toMonitor > Events, click onWAAS for App-Embeddedand observe the events generated.
Recommended For You
Recommended videos not found.