Identity & Access Management

Who holds the keys?

Why sovereignty matters for data, infrastructure, supply chain – and above all, identity

01

Why sovereignty

Sovereignty is about control – not just where the servers are

Who can access it?

Your data, your systems – and the logs that show how they are used.

Who can change it?

Configuration, code, updates – and the access rights themselves.

Who can switch it off?

A provider, a foreign authority, a sanctions list – or only you?

If the honest answer is “someone else”, you have a dependency – not sovereignty.

Four layers

Sovereignty must hold at every layer – and identity sits above them all

  • IdentityDecides who – and what – may touch every other layer
  • Supply chainThe code, builds and updates you run and implicitly trust
  • InfrastructureThe compute, network and operations everything runs on
  • DataWhat you are ultimately trying to protect

02

Data

Data is only as sovereign as the keys and the laws around it

01

Location is not enough

Data stored in Norway can still fall under foreign law if the provider does. The US CLOUD Act (2018) lets US authorities compel US providers to disclose data wherever it is stored.

02

Keys decide

Encryption only protects you if you hold the keys. If the provider manages them, the provider – and anyone who can compel it – can read your data.

03

Metadata leaks

Logs, telemetry and sign-in records reveal who works on what, from where and when. That is sensitive information in its own right.

03

Infrastructure

If someone else can switch it off, it isn’t really yours

Dependency is a design choice

Every service you cannot move, rebuild or run without the vendor is a decision about who controls you in a crisis.

Exit

Can you move to another provider – or your own racks – without rewriting everything?

Continuity

Does it keep running if the vendor, the network or the sanctions regime changes?

Disconnected

Can it run airgapped – in the field, on a vessel, or during a crisis?

Administration

Who has admin access to the platform – and who approves theirs?

04

Supply chain

You inherit the trust of everything you run

  1. 01

    Source

    Can you read and audit the code?

  2. 02

    Build

    Where is it built – and by whom?

  3. 03

    Store

    Which registry, and who can push to it?

  4. 04

    Deploy

    Who can roll a change into production?

  5. 05

    Run

    What runs underneath – OS, images, firmware?

SolarWinds (2020): a backdoor shipped to customers through a trusted, signed update.

xz utils (2024): a backdoor came close to reaching stable releases of major Linux distributions.

05

Identity

Your identity provider is the master key to everything else

Identity provider

Who you are

What you may do

Email & documents
Chat & meetings
Source code & CI/CD
Data platforms
Cloud & clusters
Admin consoles
Secrets & certificates
Network access

Whoever controls it can log in as anyone, grant access to anything – or lock everyone out.

What’s at stake

When identity is outsourced, so is control

Jurisdiction

The provider can be legally compelled to grant access or hand over sign-in data.

Availability

Suspension, sanctions or an outage at the provider – and nobody can log in to anything.

Metadata

Every sign-in reveals who, when, from where and to what. That is intelligence.

Signing keys

In 2023, a stolen Microsoft signing key let attackers forge tokens and read government email.

06

Sovereign IAM

What good looks like – principles, not products

  1. 1

    Run it where you control it

    Self-hosted, or with a provider under your own jurisdiction.

  2. 2

    Use open standards

    OIDC, SAML, SCIM and LDAP keep identities portable.

  3. 3

    Own the keys

    Token-signing keys and secrets live in a vault you operate.

  4. 4

    Separate authN and authZ

    Fine-grained authorization as policy – not hard-coded roles.

  5. 5

    Machines are identities too

    Workloads get short-lived credentials, not static secrets.

  6. 6

    Works disconnected

    Sign-in keeps working offline and in airgapped environments.

End to end

Sovereign identity from sign-in to secret – all on open source

  1. 01 · Authenticate

    Who are you?

    SSO and MFA, with one source of truth for users and groups.

    e.g. authentik

  2. 02 · Authorize

    What may you do?

    Fine-grained, relationship-based permissions as policy.

    e.g. SpiceDB

  3. 03 · Protect secrets

    What is secret?

    Keys, certificates and credentials in your own vault.

    e.g. OpenBao

  4. 04 · Connect

    How do you get in?

    Private, encrypted network access for approved users and devices.

    e.g. Headscale

Every component open source, every key in your hands – running wherever you choose, even offline.

Ask yourself

Five questions about your own identity setup

  1. 1Where does your identity provider run – and under which jurisdiction?
  2. 2Who holds the keys that sign your tokens?
  3. 3Could your people still log in tomorrow if the provider cut you off?
  4. 4Can you export users, groups and MFA – and move?
  5. 5Who can see your sign-in logs?

Questions?

Talk to us about identity and access on your own terms.