CyberKit

Serverless Function Security

Also called Function-as-a-Service security, FaaS security.

Securing short-lived, event-driven functions and their permissions and inputs.

What it is

The practice of securing event-driven functions that run on demand without managed servers, covering their attached permissions, dependencies, environment variables, and untrusted event inputs. The provider runs the host, but the function's code and grants belong to the customer.

Why it matters

Functions are ephemeral and leave little to image, so investigations lean heavily on logs and configuration, and an over-permissioned function can become a quiet pivot point.

In practice

A responder reconstructs abuse of a function whose role could write to every queue, using only its invocation logs since nothing persisted on disk.

What to look for

  • Functions with broad roles that only need one or two actions.
  • Environment variables holding secrets in plain text.
  • Unexpected invocations or new triggers added to a function.

Common mistake

Ignoring functions because they are short-lived. A function's role and code are persistent, even if each run is not.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Amazon GuardDuty Cloud service

    AWS threat detection that analyzes CloudTrail, VPC flow logs and DNS logs.

  • Microsoft Defender for Cloud Commercial

    Posture and threat protection for Azure, AWS and Google Cloud.

  • Wiz Commercial

    Maps cloud resources, identities and exposures into one graph of risk.

  • Prowler Open source

    An open source tool that checks cloud accounts against benchmarks such as CIS.

Read next

Sources