P.K. SHARMA

Cyber security intelligence, AI governance, practitioner analysis

Cloud and subscribed services

On-demand function (serverless): what it is and how it is attacked

A small piece of code that runs only when something asks for it, with no server to look after.

Also known as

  • serverless
  • Lambda
  • Azure Functions
  • Cloud Run
  • FaaS

Typing any of them into the editor finds this object.

Why it matters on a security diagram

It carries an identity of its own, so what it can reach is settled by permissions rather than by where it sits. It appears on no network diagram and in no server inventory, while holding access that reaches real data.

How it gets attacked, and what reduces it

How it gets attacked

  • Permissions attached to the code that are far wider than the job it does
  • Set going by content from outside, so untrusted input reaches it directly
  • Gone in seconds by design, leaving little behind unless records were arranged in advance

What reduces it

  • Scope the identity to the one job, since there is no host to constrain it
  • Treat trigger content as untrusted, because that is how it arrives
  • Arrange logging in advance; there is nothing to examine afterwards

Where it sits

Group
Cloud and subscribed services · Things that only exist because somebody else runs the platform underneath them.
Whose side, by default
Ours · Belongs to the organisation the diagram is about.
Catalogue identifier
serverless-function

Reviewed . CC BY 4.0.

Others in cloud and subscribed services

The cloud and subscribed services group lists all 12 of them side by side.

On-demand function on your own diagram

Open the editor, press N, and type serverless. The object is placed and connected to whatever was selected, and Tab adds the next one already joined to it. Nothing is uploaded: the page is served with a Content Security Policy that forbids the browser from making any outbound request at all.

Open the diagram maker