The Blueprint

Identity and access.

Who can get into your systems and information, and how they prove it's them: named accounts, multi-factor sign-in, passwords, access by role, admin rights, and taking access away when it's no longer needed.

IDA 21 requirements

Foundation

RW-IDA-01Everyone has their own account

What
Give every person their own named account, and don't allow accounts to be shared between people.
Why
When each account belongs to one person, everything done can be traced back to whoever did it, and second factors, access reviews and leaver steps all work as intended, which they can't for a shared login.
Protects
Confidentiality · Integrity

RW-IDA-02Multi-factor sign-in

What
Require everyone to use a second factor, such as an authenticator app or a security key, as well as their password whenever they sign in to email, cloud services, remote access or systems holding important data, and whenever anyone signs in with an admin account.
Why
A second factor means that a password stolen through a phishing email, or in a data breach elsewhere, isn't enough on its own to get into your accounts, which stops the most common way attackers break in.
Protects
Confidentiality · Integrity

RW-IDA-03Passwords that resist guessing

What
Require passwords of at least 12 characters, or at least 8 where a second factor is also used, block commonly used and previously leaked ones, don't impose character rules or routine changes, and ask for a new password only when there is reason to think the old one has been exposed.
Why
Length and blocking the passwords attackers try first are what make accounts hard to break into by guessing, and dropping forced symbols and regular changes stops people falling back on predictable patterns, such as Summer2026!, or writing their passwords down, so the passwords they choose are both stronger and easier to remember.
Protects
Confidentiality · Integrity

RW-IDA-04Access granted by role

What
Give people only the access their role needs when they join or change role, remove any they no longer need when they move, and keep a record of each request for access.
Why
Keeping each person's access in line with their role limits what an attacker, or a careless or disgruntled insider, can reach through any one account, and the records let you spot and correct access that shouldn't be there.
Protects
Confidentiality · Integrity

RW-IDA-05Access removed and equipment returned on leaving

What
Remove all of a leaver's access, and collect their company devices, information and access cards, on their last day.
Why
Closing access as soon as someone leaves means former staff and contractors can't take or damage data after they've gone, and attackers can't quietly take over old accounts that nobody is watching any more.
Protects
Confidentiality · Integrity

RW-IDA-06Admin rights only where needed

What
Give admin rights only to the people whose work genuinely requires them.
Why
Admin accounts can change or delete almost anything, so keeping them to the fewest possible people reduces the number of accounts that could give an attacker control of your systems.
Protects
Confidentiality · Integrity · Availability

RW-IDA-07Separate accounts for admin work

What
Give everyone who needs admin rights a separate account for their admin work, and don't use that account for anything else, such as email or browsing the web.
Why
Most attacks begin through email and the web, so keeping admin rights off everyday accounts means a single successful phishing email or harmful website can't give an attacker control of your systems.
Protects
Confidentiality · Integrity · Availability

RW-IDA-08Repeated failed sign-ins limited

What
Slow down or temporarily block sign-in attempts to an account after a number of failed attempts.
Why
Limiting failed attempts stops an attacker from trying one password after another against an account until one of them works.
Protects
Confidentiality · Integrity

Established

RW-IDA-09A password manager for everyone

What
Provide everyone with an approved password manager and show them how to use it.
Why
A password manager lets people use a different, strong password for every service without having to remember them all, so a password stolen from one service can't be reused to break into others.
Protects
Confidentiality · Integrity

RW-IDA-10Access reviewed regularly

What
Have the owner of each important system regularly check who has access to it, and remove any access that is no longer needed.
Why
Regular reviews catch access that was missed when people joined, moved or left, so the number of people who could misuse a system, or whose accounts could be turned against it, stays as small as it should be.
Protects
Confidentiality · Integrity

RW-IDA-11Unused accounts switched off

What
Automatically disable accounts that haven't been used for a set period.
Why
Switching off accounts nobody is using removes easy targets that an attacker could otherwise use for months without anyone noticing, and closes the gaps between access reviews.
Protects
Confidentiality · Integrity

RW-IDA-12Machine credentials owned and protected

What
Give every service account, API key and other machine credential a named owner and only the access it needs, and keep its secret in a secure store rather than in code, scripts, shared documents or messages.
Why
Machine credentials often hold wide access, are rarely looked at and are easy to find when left in code or documents, so giving each one an owner, limiting what it can do and keeping its secret in a secure store means someone is responsible for it and an attacker who finds it can do far less.
Protects
Confidentiality · Integrity

RW-IDA-13Identity proved before a reset

What
Check the identity of anyone asking for a password or second factor to be reset, in a way agreed in advance such as calling them back on a number already on record, before you reset it.
Why
Checking identity first stops attackers who phone pretending to be locked-out staff from being handed an account, and its second factor, without having to break anything.
Protects
Confidentiality · Integrity

RW-IDA-14Risky sign-ins refused

What
Block, or ask for further proof of identity from, sign-in attempts that come from unrecognised devices, unexpected locations or sessions that appear to have been stolen.
Why
Checking where and how someone signs in catches stolen sessions, and stolen passwords used from elsewhere, which can otherwise get past a password and second factor.
Protects
Confidentiality · Integrity · Availability

RW-IDA-17A different local admin password on every computer

What
Give the built-in administrator account on every computer and server its own long, random password that a management tool changes automatically, or disable the account.
Why
If the built-in administrator account has the same password everywhere, an attacker who gets it from one computer can sign in to all the others. A different password on each one stops one break-in from spreading.
Protects
Confidentiality · Integrity

RW-IDA-18Accounts managed in one place

What
Manage staff accounts from one central directory, and connect your systems and cloud services to it for sign-in wherever they allow, so that access can be given and removed in one place.
Why
When every system has its own separate accounts, some are always missed when people leave or change role. Managing accounts from one directory means access is given and removed once, everywhere, and makes a second factor easier to require.
Protects
Confidentiality · Integrity

RW-IDA-19Admin activity reviewed

What
Review a record of what admin accounts have done at regular intervals, and follow up any action that has no clear reason.
Why
Admin accounts can change anything, so a mistake or misuse through one does the most harm. Reviewing what they have actually done catches changes nobody asked for, whether by someone inside or an attacker using a stolen account.
Protects
Confidentiality · Integrity

Read the guide: The tool that can reach every computer

RW-IDA-20A second factor for your customers

What
Offer a second factor, switched on by default, to customers and other outside users who sign in to online services you run that hold their sensitive data.
Why
People reuse passwords, and stolen ones are traded widely. A second factor that is on by default means a leaked password alone isn't enough to reach a customer's data in your service.
Protects
Confidentiality · Integrity

Advanced

RW-IDA-15Phishing-resistant sign-in for admins

What
Require admin accounts to sign in using a method that a fake sign-in page can't capture, such as a security key or a passkey.
Why
Security keys and passkeys only work with the genuine website, so even a phishing kit that captures passwords and one-time codes as they're typed gets nothing it can use to take over your most powerful accounts.
Protects
Confidentiality · Integrity · Availability

RW-IDA-16Emergency admin accounts locked away

What
Keep emergency admin accounts locked away for genuine emergencies, and check every occasion one is used.
Why
Emergency accounts are designed to get round normal controls, so keeping them out of everyday reach and checking every use stops them quietly becoming a back door for an insider or an attacker.
Protects
Confidentiality · Integrity · Availability

RW-IDA-21Admin rights only for as long as needed

What
Grant admin rights for a specific task and a limited time, with approval, so that they expire automatically when the time is up.
Why
Admin rights that are always on can be used by an attacker at any moment. Granting them only for a task, and letting them lapse on their own, leaves far less time in which a stolen account can do serious damage.
Protects
Confidentiality · Integrity · Availability