UK NCSC Cyber Essentials Plus (CE+) v3.3 Danzell — gap assessments, evidence checklists, remediation plans, and cross-framework mapping to ISO 27001 and NIST CSF.

version
0.1.0
GitHub stars
436

Install

/plugin install cyber-essentials-plus@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

UK NCSC Cyber Essentials Plus (CE+) Expert

Reference-depth expertise for UK NCSC Cyber Essentials Plus (CE+) v3.3 Danzell (effective 27 April 2026). This plugin bundles the SCF crosswalk (26 SCF controls → 5 CE+ controls) with framework-specific context.

Framework identity

  • SCF framework ID: emea-gbr-cyber-essentials-requirements-3-3
  • Region: EMEA
  • Country: GB
  • Regulator/Certifying bodies: UK National Cyber Security Centre (NCSC) and IASME Consortium (accredited certification body)

Framework in plain language

Cyber Essentials Plus is a UK government-backed certification scheme that requires organisations to demonstrate they have implemented five foundational technical security controls: Firewalls, Secure Configuration, User Access Control, Malware Protection, and Patch Management. CE+ is the independently-verified tier — unlike self-assessed Cyber Essentials, an accredited assessor conducts hands-on technical testing of the organisation's systems to verify the controls are in place and effective. The scheme is mandated for UK government supply chain contracts involving personal data or sensitive information, and is widely adopted as a baseline security standard across UK public and private sector organisations.

Territorial scope and applicability

Any organisation operating in the UK, or supplying to UK government, can pursue CE+ certification. There is no revenue, headcount, or sector threshold — sole traders through FTSE 100 companies all use the same question set. The certification applies to a defined boundary chosen by the applicant; the boundary must include all devices that can access organisational data or services. UK government contracts handling personal data or sensitive information require CE+ as a minimum; some contracts (particularly MOD and intelligence community supply chain) require Cyber Essentials Plus specifically. There is no territorial carve-out for organisations headquartered outside the UK if they operate systems within a UK boundary or bid for UK government contracts.

Mandatory artifacts

  • Completed Danzell v3.3 question set — self-assessment answers submitted to the certifying body before the assessor visit
  • Asset inventory — all in-scope devices, cloud tenants, and software
  • Network diagram — showing the certification boundary and firewall placement
  • Firewall rule sets — exported or screenshot, for all boundary and host-based firewalls
  • Patch status report — demonstrating critical patches applied within 14 days
  • MFA configuration evidence — for all cloud services in scope (mandatory under v3.3)
  • CE+ certificate — issued by the IASME-accredited certifying body upon successful assessment; valid for 12 months

Cadence and timelines

  • Annual recertification: CE+ lapses exactly 12 months after the certification date. There is no grace period.
  • Patch window: Critical and high-severity patches must be applied within 14 days of release. This is a hard requirement — patches overdue at the time of assessment will cause a failure.
  • Danzell v3.3 effective date: 27 April 2026. All assessments submitted on or after this date must use the v3.3 question set.
  • Assessor visit: Typically scheduled after the self-assessment answers are accepted; the assessor conducts technical verification on live systems.
  • No notification window: CE+ is a certification scheme, not a breach-notification regulation. Incident notification obligations (e.g. ICO under UK GDPR) are separate.

Regulator and enforcement

The NCSC owns the Cyber Essentials scheme and sets the technical requirements. The IASME Consortium manages the certification body network and accredits assessors. Enforcement is indirect — there is no regulatory penalty for not holding CE+ unless a contract or regulatory condition requires it. UK government procurement rules (published by DSIT / Cabinet Office) mandate CE+ for relevant contracts; failure to maintain certification can result in contract termination or disqualification from future tenders. Maximum financial exposure therefore flows from contract loss rather than direct fines.

Interaction with other frameworks

  • UK GDPR / GDPR: ICO guidance references CE+ as evidence of appropriate technical measures under Article 32. CE+ does not substitute for a full GDPR assessment but satisfies the baseline technical-security element. Run /cyber-essentials-plus:assess before a GDPR gap assessment to avoid re-covering the same ground.
  • ISO 27001: CE+ five controls align with ISO Annex A domains A.8, A.9, A.12, A.13. Organisations pursuing ISO 27001 should implement CE+ first — it is lower effort and provides demonstrable quick wins. Use /grc-engineer:map-controls-unified to identify overlaps.
  • NIST CSF: CE+ maps primarily to the Protect function (PR.AC, PR.DS, PR.IP, PR.PT). The CSF is broader; CE+ is a useful entry point for organisations not yet ready for a full NIST programme.
  • DSPT (Data Security and Protection Toolkit): NHS and health/social care organisations must complete the DSPT annually; CE+ certification satisfies several DSPT assertions and can simplify the DSPT submission.

Common misinterpretations

  1. "MFA is only required for admin accounts." Incorrect under Danzell v3.3 (effective 27 April 2026): MFA is mandatory for all user accounts accessing any cloud service within the certification boundary. This includes standard user accounts accessing Microsoft 365, Google Workspace, AWS, and any other SaaS platform in scope.

  2. "We can risk-accept unsupported software and stay in scope." Incorrect: unsupported or end-of-life software (OS or applications) must be removed from the boundary to achieve CE+ certification. A risk acceptance or compensating control is not sufficient — the system must either be updated, replaced, or excluded from the certification boundary.

  3. "CE (self-assessed) and CE+ are the same certification at different levels." They are different certifications. Cyber Essentials is self-assessed; CE+ requires independent technical verification by an accredited assessor who tests live systems. Many organisations discover gaps during CE+ verification that their self-assessment missed. This plugin covers CE+ only.

  4. "Our cloud provider's compliance certifications mean we're covered." Cloud provider certifications (AWS ISO 27001, Azure SOC 2, etc.) cover the provider's infrastructure, not the organisation's configuration of that infrastructure. The organisation is responsible for their tenant configuration — firewall rules, MFA settings, patch levels, and account controls in the cloud tenancy are in scope for CE+.

Command routing

  • /cyber-essentials-plus:scope — determine applicability and define certification boundary
  • /cyber-essentials-plus:assess — run a gap assessment against all five controls
  • /cyber-essentials-plus:evidence-checklist — enumerate evidence requirements by control

All three delegate to /grc-engineer:gap-assessment with SCF framework ID emea-gbr-cyber-essentials-requirements-3-3 for the control-by-control mechanics, and wrap the results in CE+-specific terminology.

Levelling up to Full

Full-depth plugins add framework-specific workflow commands tied to the audit ritual. Candidates for CE+:

  • /cyber-essentials-plus:question-set — walk through the Danzell v3.3 question set interactively and pre-populate answers from connector evidence
  • /cyber-essentials-plus:assessor-prep — generate the assessor pack (asset inventory, network diagram, firewall exports, patch report) ready for the technical verification visit
  • /cyber-essentials-plus:boundary-review — help the organisation define and justify their certification boundary, flag devices that must be included, and identify candidates for explicit exclusion
  • /cyber-essentials-plus:mfa-audit — enumerate all cloud services in scope and verify MFA is enforced on every one, given the mandatory MFA requirement under Danzell v3.3

References

Commands 3

UK NCSC Cyber Essentials Plus (CE+) Assessment

Runs a compliance gap assessment against UK NCSC Cyber Essentials Plus (CE+) v3.3 Danzell by delegating to /grc-engineer:gap-assessment with the framework's SCF identifier, then overlays CE+-specific context and evidence requirements.

Usage

/cyber-essentials-plus:assess [--scope=<scope>] [--sources=<connector-list>]

Arguments

  • --scope=<scope> (optional) — narrow the assessment to one of the five CE+ controls: firewalls, secure-configuration, user-access-control, malware-protection, patch-management.
  • --sources=<connector-list> (optional) — comma-separated connector plugins (e.g. aws-inspector,github-inspector).

What the assessment produces

  1. Compliance score — overall CE+ readiness percentage, weighted by mapped SCF controls.
  2. Applicable-requirements summary — which of the five controls apply to the defined certification boundary.
  3. Control-by-control gap — each of the 5 mapped controls, with pass/fail/inconclusive status from connector findings.
  4. Evidence gaps — controls where no evidence source is configured.
  5. Remediation roadmap — prioritized by severity and effort, with the 14-day patching window and MFA-for-cloud requirements flagged as highest priority.

Delegation

Under the hood:

/grc-engineer:gap-assessment "emea-gbr-cyber-essentials-requirements-3-3" [--sources=<connector-list>]

The SCF crosswalk expands 26 SCF controls into the 5 Cyber Essentials Plus controls.

Framework-specific assessment notes

Most commonly requested scope

Full-boundary assessments are the norm — CE+ certifies the entire defined boundary, not individual controls. Partial-scope runs are useful for pre-assessment gap analysis only.

Known interactions with sibling frameworks

  • ISO 27001: CE+ five controls map closely to ISO Annex A domains A.8 (Asset Management), A.9 (Access Control), A.12 (Operations Security), and A.13 (Communications Security). Achieving CE+ first provides a solid foundation before pursuing ISO 27001.
  • NIST CSF: CE+ maps primarily to the Protect function. Use /grc-engineer:map-controls-unified to identify overlapping controls before running parallel assessments.
  • GDPR / UK GDPR: CE+ certification is referenced in ICO guidance as a baseline technical measure for Article 32 security obligations. It does not substitute for a full GDPR assessment.

Mandatory cadence

  • Annual recertification required — CE+ lapses 12 months after the certification date.
  • Danzell v3.3 question set is effective 27 April 2026; assessments submitted on or after that date must use this version.
  • No grace period for critical patch application: patches must be applied within 14 days of release.

Common misinterpretations this assessment corrects

  • MFA is now mandatory for cloud services (Danzell v3.3): Many organisations believe MFA is optional or only required for admin accounts. Under v3.3, MFA is required for all user accounts accessing any cloud service within the boundary.
  • CE vs CE+: Cyber Essentials (self-assessed) and Cyber Essentials Plus (independently verified) are different certifications. This plugin covers CE+ only. The verification testing in CE+ may surface gaps invisible to self-assessment.
  • Unsupported software must be removed: Risk-acceptance alone is not sufficient for unsupported OS or software — it must be removed from the boundary or the boundary redrawn.

UK NCSC Cyber Essentials Plus (CE+) Evidence Checklist

Baseline evidence checklist for a CE+ assessment under the Danzell v3.3 question set (effective 27 April 2026). The SCF crosswalk maps 30 SCF controls to the 5 Cyber Essentials Plus controls; this command enumerates what evidence is expected for each control.

Usage

/cyber-essentials-plus:evidence-checklist [--control=<control-name>]

Arguments

  • --control=<control-name> (optional) — restrict to a single CE+ control. Valid values: firewalls, secure-configuration, user-access-control, malware-protection, patch-management. Defaults to all five controls.

Output

Markdown checklist grouped by CE+ control with:

  • CE+ control → mapped SCF control ID(s) (from crosswalk)
  • Evidence types typically expected (screenshots, config exports, policy documents, scan reports, audit logs)
  • Which connector plugins can collect each type automatically
  • Which items require manual upload / narrative

Evidence by Control

1. Firewalls

  • Firewall rule sets for all boundary firewalls (exported config or screenshot)
  • Host-based firewall configuration for all in-scope end-user devices and servers
  • Evidence that default-deny inbound rules are in place
  • Network diagram showing firewall placement relative to the certification boundary
  • Change management records for recent firewall rule changes
  • Requires manual upload: network diagram, rule rationale for any non-default allow rules

2. Secure Configuration

  • Asset inventory listing all in-scope devices with OS version and build
  • Evidence that default passwords have been changed on all devices and software
  • List of enabled services, ports, and protocols per device type — with justification for any non-essential ones
  • Auto-lock / screen-lock configuration evidence (≤10 minutes for CE+)
  • Requires manual upload: configuration baseline documents, password policy screenshots

3. User Access Control

  • User account inventory: all accounts, roles, and privilege levels
  • Evidence of MFA enforcement for all cloud services (mandatory under Danzell v3.3)
  • Privileged account register — evidence that admin accounts are separate from standard user accounts
  • Evidence of removal or disabling of accounts for leavers (joiners/movers/leavers process)
  • Evidence that administrative accounts are not used for email or web browsing
  • Requires manual upload: MFA policy, access review records, leaver process documentation

4. Malware Protection

  • Anti-malware product name, version, and signature date for all in-scope devices
  • Evidence that real-time scanning is enabled
  • Evidence that automatic updates are configured (signatures ≤24 hours old at time of assessment)
  • Application allowlisting configuration (where used as alternative to anti-malware)
  • Requires manual upload: screenshots of anti-malware console, policy documents

5. Patch Management

  • Patch status report showing all in-scope software and OS versions
  • Evidence that critical and high patches are applied within 14 days of release
  • Evidence that unsupported or end-of-life software has been removed, updated/replaced, or excluded from the certification boundary
  • Patch management process documentation (cadence, tooling, exception handling)
  • Requires manual upload: vulnerability scan output, patch deployment records

CE+-specific evidence (verified testing)

CE+ requires an independent technical verification by an accredited assessor — unlike self-assessed Cyber Essentials. Additional evidence the assessor will generate or verify:

  • Authenticated vulnerability scan of all in-scope external IP addresses
  • Internal network scan of a sample of in-scope devices
  • Assessor-conducted checks of firewall rule sets and host configuration
  • MFA bypass attempt results for cloud service logins

Assessor expectations

  • All evidence must reflect the state at the time of assessment, not a prior period
  • Screenshots must be timestamped or assessor-witnessed
  • Cloud tenants (Microsoft 365, Google Workspace, AWS) are commonly in scope; export admin portal settings as evidence

UK NCSC Cyber Essentials Plus (CE+) Scope

Determines whether and how UK NCSC Cyber Essentials Plus (CE+) v3.3 Danzell applies to the organization. Reference-depth scope is a decision-tree prompt; Full-depth plugins extend this with jurisdiction-aware logic.

Usage

/cyber-essentials-plus:scope

What this produces

  • Applicability verdict: In-scope / out-of-scope / partially in-scope, with the triggers that led there
  • In-scope entity types: organizations handling UK government contracts, consumer-facing services, or any entity seeking CE+ certification
  • In-scope systems: all devices that can access organisational data or services — laptops, desktops, servers, cloud tenants, mobile devices, and network devices in scope boundary
  • Jurisdiction reach: UK-based operations; mandatory for UK government supply chain contracts
  • Carve-outs: operational technology (OT/ICS), IoT devices without IP connectivity, and systems explicitly excluded from the certification boundary by the certifying body
  • Next steps: whether to proceed with /cyber-essentials-plus:assess or /cyber-essentials-plus:evidence-checklist

Framework-specific scope triggers

CE+ scope depends on (at minimum):

  • Certification boundary — the applicant defines the boundary; the assessor verifies all in-boundary devices meet all five controls. Boundary must include all devices that access organisational data or services.
  • Cloud services — any cloud service (SaaS, IaaS, PaaS) used within the boundary is in scope. MFA is mandatory for all cloud services under Danzell v3.3 (effective 27 April 2026).
  • Bring Your Own Device (BYOD) — devices used to access organisational data are in scope unless explicitly excluded and compensating controls documented.
  • Annual recertification — CE+ certification lapses after 12 months; scope must be re-confirmed at each cycle.
  • Government supply chain — UK government contracts handling personal data or sensitive information typically mandate CE+ as a minimum.
  • Entity classification — sole traders, SMEs, and large enterprises are all eligible; there is no revenue or headcount threshold.

This scope command should ask only the questions that actually matter for CE+, then output the applicability verdict without asking the user to search through the whole question set.

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/cyber-essentials-plus
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70