On this page (6 sections)
The UK's National Cyber Security Centre (NCSC) has launched a new Cyber Adversary Simulation (CyAS) scheme, according to an NCSC news post published on 11 November 2026. The scheme assures suppliers who run realistic simulated attacks, so organisations can pick providers that meet a recognised standard.
This is a scheme announcement, not a vulnerability or a breach, so there is nothing to patch. It matters most to UK critical organisations and their overseers, but the ideas behind it are useful to any team that wants to know how its defences hold up in practice.
What the NCSC announced
CyAS is an NCSC Industry Assurance scheme. Commercial providers are assessed against an NCSC-defined standard, which the NCSC says gives buyers confidence that the service meets recognised requirements. The stated aim is to help organisations test their ability to prevent, detect and respond to realistic simulated cyber attacks.
The NCSC says CyAS was developed in partnership with Cyber Oversight Bodies, including regulators and Lead Government Departments, to create a common core standard and a more consistent way of demonstrating cyber resilience. A list of assured providers is published on the scheme's 'Find a Provider' page.
How adversary simulation differs from a typical pen test
The NCSC's Deputy Director Chris Ensor described CyAS as moving beyond traditional pen testing and auditing of controls, toward practically testing whether an organisation can protect, detect and respond. In plain terms, a pen test often asks "which weaknesses exist?", while an adversary simulation asks "could a determined attacker reach an agreed objective, and would we notice?".
According to the NCSC, the CyAS methodology has these notable features:
- Providers carry out reconnaissance to understand the customer's technology, exposure and threat landscape.
- That research feeds realistic, customer-specific attack plans.
- Testers take an adversarial mindset and use appropriate tools and techniques to reach agreed objectives.
- Testing is not driven by commercially procured threat intelligence and is not constrained by documented tactics, techniques and procedures (TTPs).
Who it is for
The NCSC positions the scheme for the UK's most critical organisations and for the bodies that oversee them. It complements the Cyber Assessment Framework (CAF) and the associated Cyber Resilience Audit (CRA) scheme, and the NCSC says these frameworks particularly help larger organisations, critical national infrastructure operators and government build a clearer picture of their resilience. Oversight bodies also get a trusted way to gather evidence across their sectors.
The announcement does not say that smaller businesses are in scope, and it does not give pricing, provider numbers or mandatory requirements. Treat anything beyond what the NCSC has published as unconfirmed.
What site owners and agencies can take from it
Even if you are not a critical organisation, the approach is a useful model. Realistic testing is only worth buying once the basics are in place, because simulated attackers will find the same easy gaps that real ones do.
- Fix the fundamentals first: patch CMS core, plugins and server software, and remove unused accounts and software.
- Run a read-only scan of your public sites to find exposed services, outdated software and missing headers before paying for deeper testing.
- Write down what you would want to detect and how fast, such as new admin users, changed files or unexpected outbound connections.
- Check that logging and alerting actually reach a person who will act on them.
- If you buy attack-simulation or pen testing, agree objectives and scope in writing, and ask how the provider is assessed or accredited.
- If you are a UK critical organisation or overseer, review the NCSC's scheme page and its list of assured providers.
Detection matters as much as prevention
A theme of the NCSC announcement is that testing should cover detection and response, not only prevention. After any exercise, review what your monitoring caught and what it missed. Continuous uptime, certificate and DNS monitoring can help surface unexpected changes between tests, but it complements, rather than replaces, deeper assessments. For what outside-in tools can and cannot see, read What outside-in malware detection can and cannot see.
What is still unknown
- How many providers are currently assured; the NCSC points to its Find a Provider page for the list.
- How the scheme will change when it moves beyond the MVP stage.
- Whether organisations outside the critical and oversight community will be able to use it in practice.
Only the NCSC's own announcement was available for this article, so there is no independent confirmation or commentary yet.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
