Configuring Envoy proxy deployments

Support is available for the Envoy Proxy via builtin Envoy gRPC APIs implemented in the sigsci-agent running as a gRPC server. Envoy v1.11.0 or later is recommended, however, Envoy v1.8.0 or later is supported with limited functionality as noted in the documentation below.

Envoy (as of v1.11) does not support a bidirectional gRPC API for inspecting traffic. There are instead two separate gRPC APIs available to inspect traffic. The External Authorization HTTP filter (envoy.ext_authz) gRPC API allows the request to be held while waiting inbound request inspection, which allows for a request to be blocked if required. An additional gRPC AccessLog Service gRPC API can then be used to inspect the outbound request data. Using these two APIs together with the sigsci-agent running as a gRPC server allows for inspection in both directions using only Envoy builtin APIs. This allows web application inspection without installing a module for every upstream application. In this case the sigsci-agent is acting as the module.

Request allowed (normal) processing

Diagram showing requests allowed through Envoy and Next-Gen WAF as described below.

This is the flow for normal requests that the sigsci-agent allows through Envoy.

  1. Client request received by Envoy and routed to the Envoy External Authorization (ext_authz) HTTP filter where request metadata is extracted for processing via the sigsci-agent.
  2. Request metadata is sent to the sigsci-agent via gRPC ext_authz API
  3. The sigsci-agent sends back an 'allow request' response allowing the request through the ext_authz HTTP filter to continue normal Envoy request processing.
  4. Request makes it through any additional HTTP filters to the Handler, which processes the request and generates the response.
  5. Request/Response metadata is extracted via the Envoy gRPC AccessLog Service (als) asynchronously for processing via the sigsci-agent.
  6. In parallel, additional metadata, such as response headers and the HTTP status code, is sent to the sigsci-agent via gRPC als API for further processing while the response data is sent back to the originating client.

Request blocked processing

Diagram showing requests flowing through Envoy and blocked by Next-Gen WAF as described below.

This is the flow if the sigsci-agent blocks a request from being processed through Envoy.

  1. Client request received by Envoy and routed to the Envoy External Authorization (ext_authz) HTTP filter where request metadata is extracted for processing via the sigsci-agent.
  2. Request metadata is sent to the sigsci-agent via gRPC ext_authz API
  3. The sigsci-agent sends back a 'block request' response, disallowing the request to continue being processed by the HTTP filter chain.
  4. This triggers the ext_authz filter to generate a HTTP 406 response, blocking the request from any further processing.

Next-Gen WAF agent configuration

The sigsci-agent is normally installed as a sidecar via Kubernetes with a slightly different configuration than a normal install.

The sigsci-agent must be configured to run with an Envoy gRPC listener instead of the normal RPC listener. To do this, configure the Envoy gRPC listener via the envoy-grpc-address agent configuration option, which will then start instead of the default RPC listener.

Setting the configuration value in the sigsci-agent config file:

envoy-grpc-address = ""

Or setting the configuration value in the sigsci-agent environment:


Optionally, the sigsci-agent can be configured with TLS enabled. To do this, set the certificate and key files in the sigsci-agent configuration.

envoy-grpc-cert = "/path/to/cert.pem"
envoy-grpc-key = "/path/to/key.pem"



Additionally, it is recommended to enable response data processing. To do this, the sigsci-agent must be configured to expect response data from Envoy by setting the envoy-expect-response-data agent configuration option. By default, response data is ignored in the sigsci-agent as this is an optional Envoy configuration option in order to better support older versions of Envoy. If you are running Envoy v1.10 or higher, then you should enable this option.

Setting the configuration value in the sigsci-agent config file:

envoy-expect-response-data = 1

Or setting the configuration value in the sigsci-agent environment:


Some aspects of inspection in the sigsci-agent can be configured but generally should be left as the default. Check out inspection-* agent configuration for more details.

Envoy configuration

Envoy must to be configured with an External Authorization HTTP filter (envoy.ext_authz) before the main handler filter to process request data and (optionally, though recommended) a gRPC AccessLog Service to process response data. To do this, multiple configuration items must to be added to the Envoy configuration: a cluster to handle the gRPC calls via the sigsci-agent, the envoy.ext_authz HTTP filter before the main handler, and the envoy.http_grpc_access_log service added to the access_log section of the HTTP listener filter if response data is to be enabled.

Adding the Next-Gen WAF agent cluster

A cluster must be added which is configured with the Envoy gRPC address used in the sigsci-agent configuration. Currently load balancing will not work correctly if response data is enabled as there is not a way to enable consistent hashing for gRPC services in Envoy (yet), so it is recommended not to configure load balancing at this time unless only the envoy.ext_authz API is being used without response data inspection.

2 - name: sigsci-agent-grpc
3 connect_timeout: 0.2s
4 type: strict_dns
5 #lb_policy: LEAST_REQUEST
6 http2_protocol_options: {}
7 #tls_context: {}
8 ### You can also use 'hosts' below, but this is deprecated
9 load_assignment:
10 cluster_name: sigsci-agent-grpc
11 endpoints:
12 - lb_endpoints:
13 - endpoint:
14 address:
15 socket_address:
16 address: sigsci-agent
17 port_value: 8000

The address is a resolvable hostname or IP for the sigsci-agent and the port_value must match that configured in the sigsci-agent configuration for the envoy-grpc-address option.


The connect_timeout is the timeout to connect to the sigsci-agent (but not to process the data) and can be adjusted if required. The tls_context option must be defined if TLS is to be used. TLS can be configured in the sigsci-agent config via envoy-grpc-cert and envoy-grpc-key. If TLS is configured in the sigsci-agent, then just the empty tls_context must be configured (e.g., `tls_context: ) to let Envoy know to connect via TLS. If certificate validation is desired, thenvalidation_contextmust be configured in thetls_contextto specify atrusted_cafilename to use for validation. As gRPC services are HTTP/2 based, thehttp2_protocol_options: option is required so that traffic is sent to thesigsci-agent` cluster as HTTP/2.

Adding the Envoy External Authorization HTTP filter

The listener must have an External Authorization HTTP filter (envoy.ext_authz) added before the main handler which points at the sigsci-agent cluster.

2- name: envoy.filters.http.ext_authz
3 typed_config:
4 "@type":
5 transport_api_version: V3
6 grpc_service:
7 envoy_grpc:
8 cluster_name: sigsci-agent-grpc
9 timeout: 0.2s
10 failure_mode_allow: true
11 with_request_body:
12 # Maximum request body bytes buffered and sent to the sigsci-agent
13 max_request_bytes: 8192
14 # NOTE: If allow_partial_message is set false, then any request over
15 # the above max bytes will fail with an HTTP "413 Payload Too Large"
16 # so it is recommended to set this to true.
17 allow_partial_message: true
18 # NOTE: By default, envoy carries the HTTP request body as a UTF-8 string
19 # and it fills the body @ # field. To pack the request body as raw bytes,
20 # set pack_as_bytes to true.
21 pack_as_bytes: true
22- name: envoy.filters.http.router
23 typed_config:
24 "@type":

failure_mode_allow: true is so that this will fail open, which is recommended. And timeout allows failing with the defined failure mode (true for fail open, false for fail closed) after a given time duration. Once this is done, all HTTP requests will be first sent to the envoy.ext_authz filter handled by the sigsci-agent cluster. The sigsci-agent will then process requests and deny auth with a 406 HTTP status code if the request is to be blocked or allow the request through to the next HTTP filter if it is allowed. Any additional HTTP request headers are also added to the request as they are in other modules.

Adding the Envoy gRPC AccessLog Service


This is a recommended, but optional step. If it is configured in Envoy, then the agent must also be configured to expect response data by setting the envoy-expect-response-data agent configuration option as noted in the Next-Gen WAF agent configuration section. The Envoy External Authorization (envoy.ext_authz) HTTP Filter can only process request data. As the sigsci-agent needs the response data for full functionality, a gRPC AccessLog Service must be set up to send the response data to the sigsci-agent. To do this an access_log section must be added to the Envoy configuration under the listener filter (typically under the envoy.http_connection_manager filter) if it does not already exist. If it does exist, then it must be appended to.

Refer to the access_log configuration option of the HTTP Connection Manager for more details. An envoy.http_grpc_access_log entry must be added here (in addition to any other existing access log entries).

Recommended Configuration (see Limitations and considerations for further customizations to minimize limitations):

2- name: envoy.http_grpc_access_log
3 typed_config:
4 "@type":
5 common_config:
6 log_name: "sigsci-agent-grpc"
7 transport_api_version: V3
8 grpc_service:
9 envoy_grpc:
10 cluster_name: sigsci-agent-grpc
11 timeout: 0.2s
12 additional_request_headers_to_log:
13 # These sigsci-agent headers are required for correct processing:
14 - "x-sigsci-request-id"
15 - "x-sigsci-waf-response"
16 # Optionally, additional headers can be added that should be recorded:
17 - "accept"
18 - "content-type"
19 - "content-length"
20 additional_response_headers_to_log:
21 - "date"
22 - "server"
23 - "content-type"
24 - "content-length"

Limitations and considerations

Here are the current limitations when using the sigsci-agent with Envoy Proxy. As support for Envoy Proxy improves in the future, these limitations will be addressed and should be reduced.

No request bodies are processed by default

Prior to Envoy v1.10.0, the Envoy External Authorization did not send the request body. In all versions of Envoy, the request body is not included in the ext_authz call by default and it will not be inspected by the sigsci-agent unless configured.

For Envoy v1.10.0 or higher, support to include the request body is built in to the envoy.ext_authz configuration and it is now possible to configure the with_request_body in this section of the Envoy configuration as noted above.

For Envoy v1.11.0 or higher, support was extended to be able to detect partial bodies more accurately.

For HTTP/2 (and gRPC) support Envoy must be running a version later than v1.12.1. In Envoy v1.10.0 - v1.12.1 Envoy is not properly sending the request body using with_request_body.

However, it is possible to work around this Envoy limitation using Lua until an Envoy upgrade is possible. The following is an example Lua filter that can be used to pass on gRPC based bodies to the sigsci-agent for inspection:

To do this, the Lua HTTP filter (envoy.lua) HTTP filter can be configured before the envoy.ext_authz filter to add an internal x-sigsci-encoded-body header with this data. A small snippet of Lua code must be added to extract the body and add it to the request as follows:

2 - name: envoy.lua
3 config:
4 inline_code: |
5 -- Add a special header to pass the encoded body
6 function envoy_on_request(req)
7 local len = 0
8 local reqbody
9 -- Determine the body length
10 local cl = req:headers():get("content-length")
11 if cl ~= nil then
12 len = tonumber(cl)
13 end
14 -- gRPC does not have a content-length header to limit the body before buffering
15 if len == 0 and req:headers():get("content-type") == "application/grpc" then
16 -- Triggers buffering
17 len = req:body():length()
18 end
19 -- Limit body length sent to the agent (adjust as needed)
20 if len > 0 and len <= 8192 then
21 -- Triggers buffering
22 reqbody = req:body():getBytes(0, len)
23 -- Encode the body for use in a header value
24 local enc, t = string.gsub(reqbody, "[^%w]", function(chr)
25 return string.format("%%%02X",string.byte(chr))
26 end)
27 req:headers():add("x-sigsci-encoded-body", enc)
28 end
29 end
30 - name: envoy.ext_authz
31 config:
32 grpc_service:
33 envoy_grpc:
34 cluster_name: sigsci-agent-grpc
35 timeout: 0.2s
36 failure_mode_allow: true
37# with_request_body:
38# max_request_bytes: 8192
39# allow_partial_message: true
40 - name: envoy.router
41 config: {}

No TLS handshake metadata is extracted

There is not currently a means for the sigsci-agent to see the TLS handshake metadata (e.g., cipher and protocol version) used in the originating request as this is not (yet) available in Envoy. Any TLS handshake metadata based signals will not be seen in the product for this site.

The following system signals are currently not supported due to this limitation:


Only minimal request headers are recorded by default if there were only response-based signals

If the request was inspected by the envoy.ext_authz filter and no signals were issued, then the response will be processed by the envoy.http_grpc_access_log service. If a signal is found in the response data, then only minimal request headers will be recorded with the signal due to the API not being sent all request headers by default. However, if additional request headers are desired to be recorded, then these should be added via the additional_request_headers_to_log option of the access_log configuration in Envoy.

Currently these headers will automatically be added:

  • Host
  • User-Agent
  • Referer
  • X-Forwarded-For

Two sigsci-agent specific headers must be added. Additionally any additional request headers can be added explicitly via additional_request_headers_to_log:

2# These sigsci-agent headers are required for correct processing:
3- "x-sigsci-request-id"
4- "x-sigsci-waf-response"
5# Optionally, additional headers can be added that should be recorded:
6- "accept"
7- "content-type"
8- "content-length"
9- "x-real-ip"

No response headers are processed by default

Similar to above with minimal request headers not being processed by the envoy.http_grpc_access_log service, there are no response headers sent to this API by default. Any headers that are desired to be recorded must be explicitly listed in the additional_response_headers_to_log option of the access_log configuration in Envoy as there is not currently any means to wildcard this. The following are recommended.

2- "date"
3- "server"
4- "content-type"
5- "content-length"

Next steps

Verify the agent and module installation and explore module options.

Was this guide helpful?

Do not use this form to send sensitive information. If you need assistance, contact support. This form is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.