Back to the practical resourceCONSTRUCTION FIELD GUIDE / HSEQ & COMPLIANCE

Personal phones and Cyber Essentials: which devices count?

Employee BYOD, subcontractors’ own phones and the accounts your business provides are treated differently. Here is how to work through the current scope rules with IT.

PERSONAL PHONES / SCOPE CHECK
01Employee BYODWork-data use: included
02Contractor’s own deviceDevice outside scope
03Your contractor accountsAccounts included

Check the device and the account separately.
NCSC requirements v3.3.

USE IT WITH YOUR TEAMKeep approvals, access changes and follow-up in one editable register. Set the review date and add your records; the status columns flag overdue actions and missing confirmation or evidence.
YOUR FILES

Project access evidence register

Use your work email to access the Excel evidence register, with the companion PDF guide. We’ll record which resource you request.

How we use your details: Privacy Notice

See the tools and examples
THE ANSWER IN BRIEF

An employee’s personal phone used for work is generally in Cyber Essentials scope. A third-party contractor’s own device is treated differently, but accounts your business provides to that contractor remain in scope. App protection can help control work data; it does not automatically remove an employee’s phone from scope.

Two people can reach the same project folder from phones your business does not own, yet need different Cyber Essentials scope answers. One may be your employee using a personal phone; the other a subcontractor using their employer’s equipment.

This guide separates the device and account questions so IT and the colleague coordinating certification can work through the actual arrangement together. It also explains why assessment scope does not settle every decision about protecting project information.

The current scope distinctions

The table summarises the device and account distinctions in NCSC’s April 2026 requirements, version 3.3. Confirm the scope of your own assessment with your certification body.

Personal and contractor devices under Cyber Essentials v3.3
ArrangementTreatment to checkPractical implication
Employee’s own phone used for work email or other organisational dataEmployee BYOD is included in scope.Account for the device and applicable controls. Do not assume personal ownership excludes it.
Device used only for native voice calls, SMS or MFAThe stated BYOD exception applies to these uses.Check that it really is limited to those uses. Work email or other work-data access changes the question.
Device owned by a third-party contractorThe contractor-owned device is outside the applicant’s device assessment scope.Still decide what project information it may access and how that access is controlled.
Account your business provides to a contractorYour organisation’s accounts used by third parties remain in scope.Include the account and access controls, even if you do not manage their phone.
Your organisation’s device loaned to a contractorYour organisation-owned equipment remains included.Keep it in the relevant inventory and management process.

Read the scope and third-party-device sections of the NCSC requirements.

Work through one real arrangement

Take an actual employee or external contributor and establish who owns the device, who employs the person, which accounts are used and which work information they reach.

Illustrative comparison: an employee uses Outlook on a personal phone to read work email. Separately, a subcontractor uses their employer’s phone to access a folder your business shares. Both involve mobile access. They need different device-scope answers, and the shared folder still needs appropriate permissions.

Include the client’s systems in your working notes, but distinguish what your business administers from what the client administers. Your assessment answer should describe the arrangement you have, rather than an assumed standard setup.

App protection does not change the scope rules

Intune app protection can protect organisational data in supported apps, including on devices that are not enrolled in device management. Depending on configuration, that can help keep work information separate from personal apps. Microsoft explains app protection.

That is useful for designing employee BYOD. It does not mean the phone disappears from Cyber Essentials scope, and it does not prove that every applicable control has been met.

Ask IT to test the actual experience: sign-in, permitted apps, data transfer, unsupported devices and removal of protected work data. Agree what employees will be told about privacy and management. For a contractor using another employer’s device, check the supported external-user approach separately.

Keep a short working scope note

Use a record you can maintain as people join or move project. Capture the device owner, user relationship, work uses, account provider, systems reached, the team managing the controls and any assessment question still to resolve.

A note such as “personal phone, employee, work email and Teams, company account, IT managing supported app policies” gives your assessment owner something concrete to check. “BYOD allowed” does not.

Five questions for IT and the assessment owner

  1. Which employee-owned phones access work data?
  2. Which are genuinely limited to native calls, SMS or MFA?
  3. Which devices belong to third-party contractors, and which accounts do we provide to them?
  4. Have any organisation-owned devices been loaned out?
  5. Do our scope note and customer answers reflect the current arrangement?

Record uncertainty and resolve it with the certification body. Do not substitute a supplier’s product description for the assessment requirements.

Keep the customer answer accurate

Cyber Essentials and Cyber Essentials Plus are different assessment routes. If the customer specifies Plus, confirm that requirement early; do not treat a basic certificate as interchangeable. Neither certificate is a record of every project permission or every leaver action.

It is also worth separating assessment scope from risk management. A contractor-owned phone being outside your device assessment does not remove your responsibility to decide what access to grant and when it should end.

Use the construction assurance guide when you need to bring the customer question, IT confirmation and supporting evidence together.

Turn the scope answer into a workable mobile setup

Once the relationships are clear, choose the right control arrangement: a managed company phone, protected work apps where supported, or narrower project access. The same approach does not need to fit everyone.

Compare those options. If you need help implementing the chosen approach, speak to Assured Digital about EMM and Microsoft controls.

Technical references checked 27 October 2026. NCSC requirements v3.3 · Microsoft app protection. This guide supports a discussion with IT and your certification body; it does not determine your certification outcome.
Useful to someone else on the team?Share the guide with the person who owns the next action.
Email a colleague ↗
YOUR NEXT STEP

A customer question
you’d like help with?

Start with a short outline of the customer’s requirement and what still needs confirming. We can discuss it with you and the colleague responsible for IT, then establish what would be involved.

Talk through the requirementFor certification scope, involve the relevant assessment body.
REVIEW IT WITH YOUR IT COLLEAGUE

A broader review with IT

The Mobile Access Diagnostic covers devices, remote access, messaging and connectivity. Use it with your IT colleague or provider if you want a broader starting point for the discussion.

Review mobile-access arrangementsThe diagnostic offers a broader self-review of work phones, remote access and device management. It does not assess your PQQ or certification.