cloud-functions.md

Google Cloud Functions

If you're using the @google-cloud/functions-framework package to register your handlers, your cloud function will be protected by Zen automatically:

require("@aikidosec/firewall/cloud-function"); // <-- Include this before any other code or imports

const functions = require("@google-cloud/functions-framework");

functions.http("handler", async (req, res) => {
  // ...
});

or ESM import style:

import "@aikidosec/firewall/cloud-function";

// ...

If you're using the exports.handler style, you'll need to wrap your handler manually.

At the very beginning of the file that contains your handler, add the following line:

const protect = require("@aikidosec/firewall/cloud-function"); // <-- Include this before any other code or imports

const dependency = require("dependency");

exports.handler = protect(async (event, context) => {
  // <-- Wrap your handler with protect
  // ...
});

or ESM import style:

import protect from "@aikidosec/firewall/cloud-function";

// ...

That's it! Your cloud function is now protected by Zen.

If you want to see a full example, check our cloud functions sample app.

Blocking mode

By default, the firewall will run in non-blocking mode. When it detects an attack, the attack will be reported to Aikido and continue executing the call.

You can enable blocking mode by setting the environment variable AIKIDO_BLOCKING to true.

It's recommended to enable this on your staging environment for a considerable amount of time before enabling it on your production environment (e.g. one week).

Debug mode

If you need to debug the firewall, you can run your cloud function with the environment variable AIKIDO_DEBUG set to true.

This will output debug information to the console (e.g. if the agent failed to start, no token was found, unsupported packages, ...).

Preventing prototype pollution

Zen can also protect your application against prototype pollution attacks.

Read Protect against prototype pollution to learn how to set it up.