Free · Ungated · Anonymous

Root access on Linux is spread across sudo rules, SSH keys and service accounts. See where your estate stands.

The free Linux identity maturity assessment: twenty questions on the sudo rules, SSH keys, service accounts and access reviews behind who can do what on your Linux hosts. Answer for your estate as it is today and get a score out of 80, with the gaps that matter most and prioritised recommendations. They are also the controls NIS2, DORA and the CIS Benchmarks ask you to evidence. No form, no vendor pitch.

15 minutes5 capability domains · 20 questions · score out of 80For security, IAM and Linux infrastructure teams

What you'll get

A score out of 80 across 5 Linux identity domains, structured feedback on areas of focus, and specific gaps with prioritised recommendations — no vendor pitch attached.

How to answer

Answer for your Linux environment as it is today, not as it's planned. There are no wrong answers. Honest answers give the most useful results.

What we cover

Identity inventory, privilege control, access governance, service accounts and other non-human identities (including the accounts AI agents run as), and compliance and audit readiness across Linux systems.

0/ 80

0 of 20 answered

Not started

The foundation of Linux identity security is knowing what exists. Orphaned accounts, undocumented service users and shared credentials can easily predate the current team.

How complete is your current inventory of human accounts with Linux access?

Orphaned accounts are the single most common critical finding across Linux environments.

How quickly could you produce a complete list of every account with local login access to a given Linux server?

Audit teams and incident responders ask this question on short notice.

Accounts lose their owner through leavers, ended contracts and retired services. How do you find Linux accounts with no current owner today?

Accounts with no known owner are a common privilege escalation entry point.

How well do you understand group membership across Linux systems — specifically which users are in security-sensitive groups (sudo, wheel, docker, etc.)?

Over-permissive group membership is often invisible. Many privilege escalation paths exist through groups, not individual account settings.