Security Guide · Platform Hygiene

Patched by default, not by project.

entityOS.cloud runs on AWS managed services. The software underneath the platform — the operating system, the language runtime, the execution environment — is kept current by AWS, not by anyone having to remember to do it. A whole class of “stale, unpatched server” risk is removed from the platform before any access control is even applied.

Managed Runtimes Shared Responsibility Automatic Patching Supported Versions Defence in Depth
The Core Idea

AWS curates and applies security updates to the runtime — so there is no stale server to patch.

Operating system & system libraries

The underlying operating system and its shared libraries are patched by AWS. Nobody logs in to the platform to apply an update.

The language runtime

The managed Node.js interpreter itself — and its built-ins — is kept current as part of the Lambda service.

The execution environment

The host and isolation layer that runs each platform function are maintained and patched by AWS, invisibly to the platform.

entityOS.cloud runs with the patch cadence of a dedicated platform team — without having to field one.

THE MECHANISM Lambda, as the worked example

What AWS patches beneath the platform.

When an entityOS function runs on a Lambda managed runtime — for example Node.js — AWS is responsible for curating and publishing security updates for all supported managed runtimes, and applies them automatically to the functions that use them. Three layers the platform never has to touch.

CVE published upstream
AWS curates the fix
New runtime version published
applied automatically (Auto mode)
Platform functions migratedno redeploy required
Running on patched software

Lambda takes on the operational burden of patching the runtime — security fixes, bug fixes, performance improvements.

What that covers

  • The Amazon Linux OS and system libraries beneath the runtime.
  • The managed language runtime itself — the Node.js interpreter and its built-ins.
  • The execution environment, host and isolation layer.
  • Published as new runtime versions; platform functions are migrated onto them automatically.
The timing caveat

As with any patching, there is typically a short interval between a CVE being published and the corresponding patch being applied across the fleet. It is fast — not instant.

The shared responsibility model

What entityOS manages on top.

Runtime patching does not cover everything. AWS secures the infrastructure; entityOS secures what it deploys onto it. The line is clean, and the right-hand side is the part the platform owns.

AWS handles

Security of the cloud

  • Operating system & system libraries
  • The managed language runtime (Node.js)
  • Execution environment & host
  • Scaling, isolation & availability
Curated, published and applied automatically for every supported runtime.
entityOS manages

Security in the cloud

  • Platform application code
  • Bundled dependencies (npm / node_modules)
  • Lambda Layers, lockfiles & SBOMs
  • Staying on a supported runtime version
A runtime update does not fix a vulnerable package bundled with the application. entityOS scans and patches those.

A vulnerable npm package behaves the same on Lambda as anywhere else. “AWS patches Node.js” holds only while the platform stays on a supported version of Node.js — once a runtime is deprecated, Lambda stops applying security patches and the upgrade becomes the platform’s responsibility.

The Key Idea

Current by default.

AWS secures the infrastructure — OS, managed runtime, execution environment — and applies those patches with no manual intervention from the platform.

entityOS secures what it deploys — its application code, its bundled dependencies, and its discipline in staying on a supported runtime.

Running on managed services means the platform everyone builds on is kept patched continuously. It removes a failure class for every entityOS.cloud customer — and it does not remove the access controls that decide who reaches the patched platform in the first place.