Zum Hauptinhalt springen

Threat Model a Serverless Function

Identify trust boundaries and controls for a serverless workflow.

cloud-security5 min read

A webhook-triggered cloud function writes to a queue and calls a payment API. Trust boundary -> abuse case -> control -> evidence Assuming short serverless code is automatically low risk misses the permissions attached to it. Draw the path External webhook -> function -> queue -> payment API. The path reveals where untrusted input becomes trusted action. Name abuse cases Spoofed webhook, replayed event, payload tampering, and overbroad secret access. Abuse cases connect architecture to attacker behavior. Select controls Signature verification, replay window, schema validation, narrow role, and secret-specific access. Controls should interrupt the abuse path directly. Define evidence Test…

Read the full lesson

Sign up free: one personalized lesson every day, matched to your role and goals.

← Back to library

Kontakt aufnehmen