Cyber Essentials admin account requirements (v3.3, 2026)
Cyber Essentials v3.3 admin account rules: separate accounts for admin tasks only, no email or browsing, approval, tracking and review, leavers removed, MFA on cloud admins.
Cyber Essentials v3.3 requires administrators to use a separate account for administrative tasks only, with no email, web browsing or other everyday activity. Admin access must be approved through a formal process, tracked, reviewed regularly and removed when no longer needed, and every cloud administrator must use MFA. A No to A7.16 is an automatic fail.
- Requirement
- Use separate accounts to perform administrative activities only: no emailing, web browsing or other standard user activities
- Applies to
- Local administrator, network or domain administrator and cloud service administrator accounts, including third-party support accounts
- Lifecycle
- Approved creation (A7.1, A7.5), tracked (A7.8), reviewed regularly with unneeded admin access removed (A7.9), leavers disabled (A7.3)
- Automatic fail
- A No to A7.16, MFA for all cloud administrators
- CE Plus test
- Test case 5: check account separation
- What changed in 2026
- The v3.3 admin account rules are unchanged; under the Danzell question set a No at A7.16 (MFA on cloud administrators) became an automatic fail from 27 April 2026
What counts as an administrator account?
Any account that can install software, change system settings or create accounts and grant privileges.
These accounts typically allow the user to: execute software that can make significant and security-related changes to the operating system; make changes to the operating system for some or all users; create new accounts and allocate privileges. All types of administrators will have this kind of account, including domain administrators and local administrators.
A7.6 spells out the three kinds the question set covers: local administrator accounts, network or domain administrator accounts, and cloud service administrator accounts. A Global Administrator in Microsoft 365, a super administrator in Google Workspace, a local admin on a laptop and the owner role in a SaaS tool are all admin accounts for Cyber Essentials.
QuestionsA7.6
Why must admin accounts be separate from everyday accounts?
Because malware runs with the privileges of whoever opens it, so an admin account that reads email turns one bad attachment into a system-wide problem.
use separate accounts to perform administrative activities only (no emailing, web browsing or other standard user activities that may expose administrative privileges to avoidable risks)
Cloud service administration must be carried out using separate accounts.
v3.3 uses the example of Jody, who opens a malicious attachment while signed in as an administrator; the ransomware inherits admin rights and encrypts far more data than it could from a standard account. Separation means the account that reads email cannot change the system, and the account that can change the system never reads email.
Every administrator therefore needs two identities: a standard account for daily work and a separate admin account used only for admin tasks. That applies to the IT manager, the director who 'needs' Global Administrator and the outside support company.
How do you stop admin accounts being used for email and browsing?
With a written rule that staff follow, a technical control, or both: the A7.7 guidance says you may not need a technical control and that it could be based on good policy, procedure and regular training.
Software and update downloads should be performed as a standard user and then installed as an administrator. ... it could be based on good policy, procedure and regular training for staff.
Downloads happen as the standard user; the admin credentials are entered only at the install or elevation prompt.
QuestionsA7.7
How are admin accounts approved, tracked and reviewed?
Through three linked controls: an approval process (A7.5), a list of everyone with admin access (A7.8) and a regular review of that list that removes access no longer needed (A7.9).
You must have a process that you follow when deciding to give someone access to systems at administrator level. This process might include approval by a person who is an owner/director/trustee/partner of the organisation.
You must track all people that have been granted administrator accounts.
You must review the list of people with administrator access regularly. Depending on your business, this might be monthly, quarterly or annually. Any users who no longer need administrative access to carry out their role should have it removed.
The cadence is yours to choose, but each review should remove anyone who no longer needs the access, which matches the v3.3 rule to remove or disable special access privileges when no longer required. An admin register can be a short spreadsheet: name, account, systems, who approved it, date granted, date last reviewed. Directory exports, such as the Entra ID role assignments list, show who holds each role today.
What happens to accounts when people join, change role or leave?
Joiners get accounts only after approval, movers lose access they no longer need, and leavers are disabled or deleted.
have in place a process to create and approve user accounts ... remove or disable user accounts when they’re no longer required (for example, when a user leaves the organisation or after a defined period of account inactivity) ... remove or disable special access privileges when no longer required (when a member of staff changes role, for example)
The A7.1 guidance says approval is by a person with a leadership role in the business. A7.4 requires the principle of least privilege when someone changes role. A7.3 asks you to describe how leavers' accounts are deleted or disabled. The Secure Configuration control adds that unnecessary accounts, 'such as guest accounts and administrative accounts that won’t be used', must be removed or disabled, which A5.2 checks on devices and cloud services.
What if a SaaS tool has no separate admin role?
The scheme text does not cover this case directly. What it does say is that cloud service administration must be carried out using separate accounts (A7.6), and that administrative accounts must be used for administrative activities only.
QuestionsA7.6
Do IT support and MSP admin accounts count?
Yes: accounts your organisation owns are in scope even when an outside provider uses them.
this also includes third party accounts – for example, accounts used by your support services.
Each support engineer needs a named account (shared logins fail A7.2), the account appears on your admin register, it uses MFA, and it is removed when the contract ends. See MSPs and third-party accounts.
How do GDAP and delegated MSP access fit A7.6 to A7.9?
Treat each delegated relationship as admin access you have approved, and record it on the admin register (our guide for MSPs and IT providers covers the provider side): GDAP gives an MSP's own accounts admin roles in your tenant, so those accounts are your administrators for A7.8 and A7.16 even though they live in the partner's tenant.
Microsoft describes GDAP (granular delegated admin privileges) as giving partners 'granular and time-bound access' that 'customers must explicitly grant'. A Global Administrator can see which partners hold GDAP, and remove it, under Settings > Partner relationships in the Microsoft 365 admin center (customer-led removal). Microsoft's partner security requirements say partners 'must enforce multifactor authentication (MFA) on all user accounts in your partner tenants'.
QuestionsA7.5A7.8A7.9A7.16AUTO-FAIL
How does Cyber Essentials Plus test account separation?
By watching a standard user try to run an administrative process: a prompt for separate admin credentials is a pass, and a process that runs with the daily account is a fail.
If the test results in the user being prompted for an additional login and the process does not run using the user account details, then award a Pass. Otherwise, award a Fail.
Test case 5 runs on every sampled end user device, on servers that provide a user-interactive desktop, and on cloud environments where administrative processes can run. See CE Plus test case 5.
QuestionsA7.6
What should you write in the A7.6 notes field?
A7.6 asks how you make sure separate accounts are used for administrative tasks, across local, domain and cloud administration. Cover all three. A model you can adapt:
All staff use standard user accounts for daily work, with no local admin rights on their laptops. Our two IT staff each have a separate named admin account in Entra ID (for example admin.jsmith) with no licence and no mailbox, used only for Microsoft 365 and Intune administration and protected by MFA. Our IT provider administers the tenant through GDAP with the Exchange and User Administrator roles only; the relationship is on our admin register and the provider has confirmed in writing that MFA is enforced on its engineers' accounts. Local administrator passwords on Windows devices are unique per device and managed by Windows LAPS; they are retrieved only for installs and troubleshooting. Our accounting and HR SaaS tools each have a separate admin login held by the finance manager. Admin accounts are listed on our admin register and reviewed quarterly.
How do assessors check admin account answers?
Related requirements
- User access control requirementsThe control hub: every A7 requirement
- A7.6: separate admin accountsLocal, domain and cloud administration
- A7.7: no email or browsing as adminPolicy or technical control
- A7.9: reviewing admin accessMonthly, quarterly or annually
- CE Plus test case 5: account separationThe elevation prompt test
- Cyber Essentials MFA requirementsA7.16 covers every cloud administrator
- Cyber Essentials password requirementsLength, deny lists and brute-force limits
- Glossary: least privilegeAccess limited to what the role needs
- Glossary: Windows LAPSUnique local admin passwords
- Check your readinessTest your answers against the auto-fail questions first
Frequently asked questions
Yes. v3.3 requires separate accounts used to perform administrative activities only, with no emailing, web browsing or other standard user activities. Each administrator needs a standard account for daily work and a separate admin account, and the A7.6 guidance says cloud service administration must use separate accounts too.
The scheme does not mention mailboxes, but it bans email from admin accounts. Removing the mailbox makes that a technical fact rather than a policy, which is easier to evidence for A7.7. Microsoft says you don't need to license admin-only accounts in Microsoft 365, and without an Exchange Online licence there is no mailbox.
It can be. The A7.7 guidance says a technical control may not be needed and that it could be based on good policy, procedure and regular training for staff. A technical control is still easier to show an assessor.
The A7.9 guidance leaves it to you: monthly, quarterly or annually depending on your business. Choose a cadence, record each review's date and outcome, and remove admin access from anyone who no longer needs it for their role.
Yes. v3.3 says all types of administrators have privileged accounts, including domain administrators and local administrators, and A7.6 names local administrator accounts explicitly. Daily accounts should be standard users, with local admin credentials used only for installs and changes.
On cloud services, yes, and it is an automatic fail if not. A7.16 requires MFA on all administrators of your cloud services, with a password of at least 8 characters. v3.3 also says you should always use MFA to give administrative accounts extra security.
- NCSCCyber Essentials: Requirements for IT Infrastructure v3.3 · April 2026Read on ncsc.gov.uk (opens in a new tab)
- IASMECyber Essentials Danzell Question Set 2026Read on iasme.co.uk (opens in a new tab)
- NCSCCyber Essentials Plus Test Specification v3.2Read on ncsc.gov.uk (opens in a new tab)
- IASMEImportant update: changes to Cyber Essentials for April 2026 (MFA free, included or paid; automatic fail) · Checked 9 November 2026Read on iasme.co.uk (opens in a new tab)
- Microsoft LearnAdmin account security in Microsoft 365 for business · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- Microsoft LearnGranular delegated admin privileges (GDAP) introduction · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- Microsoft LearnCustomer-led removal of a granular admin relationship · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- Microsoft LearnPartner security requirements (MFA in partner tenants) · Checked 9 November 2026Read on learn.microsoft.com (opens in a new tab)
- knowledge.workspace.google.comGoogle Workspace Admin Help: Security best practices for administrator accounts · Checked 9 November 2026Read on knowledge.workspace.google.com (opens in a new tab)
- knowledge.workspace.google.comGoogle Workspace Admin Help: Deploy 2-Step Verification · Checked 9 November 2026Read on knowledge.workspace.google.com (opens in a new tab)