Identity & Access Management
Why sovereignty matters for data, infrastructure, supply chain – and above all, identity
01
Sovereignty is about control – not just where the servers are
Your data, your systems – and the logs that show how they are used.
Configuration, code, updates – and the access rights themselves.
A provider, a foreign authority, a sanctions list – or only you?
Sovereignty must hold at every layer – and identity sits above them all
02
Data is only as sovereign as the keys and the laws around it
01
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
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
Logs, telemetry and sign-in records reveal who works on what, from where and when. That is sensitive information in its own right.
03
If someone else can switch it off, it isn’t really yours
Every service you cannot move, rebuild or run without the vendor is a decision about who controls you in a crisis.
Can you move to another provider – or your own racks – without rewriting everything?
Does it keep running if the vendor, the network or the sanctions regime changes?
Can it run airgapped – in the field, on a vessel, or during a crisis?
Who has admin access to the platform – and who approves theirs?
04
You inherit the trust of everything you run
01
Can you read and audit the code?
02
Where is it built – and by whom?
03
Which registry, and who can push to it?
04
Who can roll a change into production?
05
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
Your identity provider is the master key to everything else
Identity provider
Who you are
What you may do
Whoever controls it can log in as anyone, grant access to anything – or lock everyone out.
When identity is outsourced, so is control
The provider can be legally compelled to grant access or hand over sign-in data.
Suspension, sanctions or an outage at the provider – and nobody can log in to anything.
Every sign-in reveals who, when, from where and to what. That is intelligence.
In 2023, a stolen Microsoft signing key let attackers forge tokens and read government email.
06
What good looks like – principles, not products
Self-hosted, or with a provider under your own jurisdiction.
OIDC, SAML, SCIM and LDAP keep identities portable.
Token-signing keys and secrets live in a vault you operate.
Fine-grained authorization as policy – not hard-coded roles.
Workloads get short-lived credentials, not static secrets.
Sign-in keeps working offline and in airgapped environments.
Sovereign identity from sign-in to secret – all on open source
01 · Authenticate
SSO and MFA, with one source of truth for users and groups.
e.g. authentik
02 · Authorize
Fine-grained, relationship-based permissions as policy.
e.g. SpiceDB
03 · Protect secrets
Keys, certificates and credentials in your own vault.
e.g. OpenBao
04 · Connect
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.
Five questions about your own identity setup