Skip to content

Shield WAF reference

Arcjet Shield WAF protects your application against common attacks, including the OWASP Top 10.

Shield is configured by specifying which mode you want it to run in.

The arcjet client can be configured with one or more Shield rules, which are constructed with the shield(options: ShieldOptions) function and configured by ShieldOptions:

type ShieldOptions = {
mode?: ArcjetMode | undefined;
};
type ArcjetMode = "LIVE" | "DRY_RUN";

Guards and routes

Arcjet can be integrated into NestJS in several places using NestJS guards or directly within the route controller:

  • Global guard: Applies Arcjet rules on every request, but doesn’t let you configure rules per route.
  • Per route guard: Lets you configure rules per route, but requires you to add the guard to every route and has limited flexibility.
  • Within route: Requires some code duplication, but allows maximum flexibility because you can customize the rules and response.

For Shield we recommend including it on the root module so it can analyze all requests.

Global guard

A global guard can be configured in src/app.module.ts.

This can then be added to the controller for all the routes you wish to protect with Arcjet.

Per route guard

A per route guard can be configured in the controller for each route you wish to protect with specific Arcjet rules. The client created in src/app.module.ts is automatically passed to the guard.

Arcjet applies the rules and returns a generic error if the result is DENY.

Within route

Call Arcjet from within the route controller to have maximum flexibility.

Arcjet provides a single protect function that is used to execute your protection rules. This requires a RequestEvent property which is the event context as passed to the request handler.

If you are using a global guard or per route guard then protect is called for you behind the scenes. If you add Arcjet within a route then you call it directly.

This function returns a Promise that resolves to an ArcjetDecision object. This contains the following properties:

  • id (string) – The unique ID for the request. This can be used to look up the request in the Arcjet dashboard. It is prefixed with req_ for decisions involving the Arcjet cloud API. For decisions taken locally, the prefix is lreq_.
  • conclusion (ArcjetConclusion) – The final conclusion based on evaluating each of the configured rules. If you wish to accept Arcjet’s recommended action based on the configured rules then you can use this property.
  • reason (ArcjetReason) – An object containing more detailed information about the conclusion.
  • results (ArcjetRuleResult[]) – An array of ArcjetRuleResult objects containing the results of each rule that was executed.
  • ip (ArcjetIpDetails) – An object containing Arcjet’s analysis of the client IP address. For more information, see the SDK reference.

To check whether a shield rule returned a deny conclusion, use decision.isDenied() and decision.reason.isShield() (JS) / decision.is_denied() and decision.reason_v2.type == "SHIELD" (Python).

You can iterate through the results and check whether a shield rule was applied:

for (const result of decision.results) {
console.log("Rule Result", result);
}

This example logs the full result as well as the shield rule:

Arcjet is designed to fail open so that a service issue or misconfiguration does not block all requests. The SDK also times out and fails open after 2000 ms by default. However, in most cases, the response time is less than 20 ms to 30 ms.

If there is an error condition when processing the rule, Arcjet returns an ERROR result for that rule and you can check the message property on the rule’s error result for more information.

If all other rules that were run returned an ALLOW result, then the final Arcjet conclusion is ERROR.

Arcjet runs the same in any environment, including locally and in CI. You can use the mode set to DRY_RUN to log the results of rule execution without blocking any requests.

We have an example test framework you can use to automatically test your rules. Arcjet can also be triggered based using a sample of your traffic.

For details, see the Testing section of the docs.