Skip to content
Promenaut

Promenaut joins forces with HSBC as strategic investor and design partner.Read More

For security

How is it secured, and who can see what?

The questions a review asks of Promenaut, answered from the platform itself, and everything built for them.

01Your review

The questions, in the order they come.

Each deployment declares its sign-in methods from email and password, LinkedIn, GitHub and SAML single sign-on; a method not declared has no routes at all.

  • Each deployment chooses how people sign inEach deployment declares which sign-in methods it offers, from email and password, LinkedIn, GitHub and SAML single sign-on.
  • SAML single sign-onThe platform runs as a SAML service provider with the full flow implemented: login, assertion consumer service, metadata publication and single logout.
  • Assertion security corpusSingle sign-on is tested against a corpus of hostile assertions covering signature wrapping, replay, expiry, tampering, audience and recipient mismatch and weak signature algorithms, with fixtures rebuilt at test time so signed assertions do not age out.

The full answer is in How Promenaut Is Secured.

Access is named permissions attached to roles, enforced in API middleware and mirrored in the interface.

  • Role and permission modelAccess is granted through named permissions attached to roles, enforced in API middleware and mirrored in the interface so users are not shown actions they cannot take.
  • Roles granted at team grainA role can be granted to a team, and the team's roles are copied into a person's own grants, at the scope of the team's own organisation (or its enterprise for an enterprise-level role), when they join it, or applied to all current members in one action, so a joiner picks up the team's entitlements without a sweep of individual grants.
  • Teams of peopleAn organisation is subdivided into teams of people, each with named members, a lead, a slug and a place in a team hierarchy.

The full answer is in How Promenaut Is Secured.

02Everything built for it

What the platform does for you, layer by layer.

Identity and access

  • OAuth sign-in
  • Teams of people
  • Roles granted at team grain
  • A module cannot speak for another module
  • A narrowed deployment cannot be asked about what it does not ship
  • Entitlement is applied before the message is understood
  • Explicit organisation scoping
  • The token says who you are, not what you may do
  • Role and permission model
  • Enterprise and organisation hierarchy
  • Each deployment chooses how people sign in
  • SAML single sign-on
  • Assertion security corpus
  • Safe operator actions without destructive authority
  • Open or closed catalogue, per organisation
  • Separated finance permissions
  • Least-privilege reporting access
  • A rendered document is branded for the tenant that owns it
  • What tenant resolution reaches, and what it deliberately does not
  • Editable agent classification ceiling
  • Who each agent acts as, across the fleet
  • Service identities are reviewed on a cadence
  • A module agent cannot write into another organisation
  • An administrator resets a password with a single-use link
  • Administrators act only within their enterprise and authority
  • Single-use links stored only as a digest
  • Modules switched on for an organisation or for one team

Approvals, decisions and containment

  • Dialled autonomy
  • Agent handbrake
  • Suspend an agent everywhere
  • Platform staff can block an outside MCP server for every organisation at once
  • An agent runs an approved public skill in a sandbox with no outside network, and its uses are recorded
  • Containment rules drain, quarantine, pause or block matching work
  • One governed door for stopping and containing work
  • A held run waits for the decision that holds it
  • Brakes on automatic control
  • Containing work by what it touches
  • A quarantined module's agents do not run anywhere
  • An agent that keeps failing on its own configuration is contained automatically
  • One place to govern MCP, in both directions
  • One checked, recorded door for the tools an agent offers a model
  • One Approvals screen for what the control engine is waiting on
  • An approval gate holds matching runs or calls until a person decides

Model risk

  • Model risk access audit
  • Pausing and stopping work is requested through control directives, not through model risk

Audit trails

  • Administrative audit trail
  • Seam calls leave an activity record
  • Old capability audit records are archived before they leave the database
  • Audit ledger anchored outside the database
More on Control →

Weighing us against the tools you already know? See how we compare, with sources →

03The pack

The full answers, written for you.

How Promenaut Is SecuredAbout 25 minutes

How Promenaut Governs KnowledgeAbout 12 minutes

Get the security pack

Bring your security team.

A session with the people who built it: identity, tenancy, what an agent may read, and the evidence kept.

Book a security review session