🚨 CMMC Phase One started November 10! Here's everything you need to know →

How to Meet Essential Cybersecurity Controls (ECC – 2 : 2024) - Control - 2-6-3

Practical guide for SMBs to implement Essential Cybersecurity Controls (ECC – 2 : 2024) - Control - 2-6-3

January 17, 2026
3 min read

Share:

Schedule Your Free Compliance Consultation

Feeling overwhelmed by compliance requirements? Not sure where to start? Get expert guidance tailored to your specific needs in just 15 minutes.

Personalized Compliance Roadmap
Expert Answers to Your Questions
No Obligation, 100% Free

Limited spots available!

Requirement

Essential Cybersecurity Controls (ECC – 2 : 2024) - Control - 2-6-3 – The cybersecurity requirements for mobile devices security and BYOD must include at least the following:

Understanding the Requirement

This control requires SMBs to define and enforce minimum security requirements for mobile devices and bring-your-own-device (BYOD) use. In practical terms, the organisation must satisfy the sub-objectives listed as 2-6-3-1, 2-6-3-2, 2-6-3-3 and 2-6-3-4 by creating policy, operational and technical measures that cover device inventory and ownership, secure configuration and patching, access controls and authentication, and data protection including remote wipe and loss prevention. This control comes from the Essential Cybersecurity Controls (ECC – 2 : 2024) framework and is intended to reduce risk from unmanaged or poorly configured mobile devices connecting to corporate resources.

Technical Implementation

  • Write a clear BYOD and mobile device policy. Specify who may enroll devices, acceptable device types and OS versions, minimum security settings (screen lock, automatic updates, encryption), and what corporate data is allowed on personal devices. Require agreement to the policy during onboarding.
  • Maintain a device inventory and enrollment process. Use an automated Mobile Device Management (MDM) or Unified Endpoint Management (UEM) solution to register every device that accesses corporate email or apps. Track device ownership (company-owned vs personal), OS, last-seen time and compliance status; remove access for devices not registered.
  • Enforce secure baseline configuration and patching. Configure MDM profiles to require device encryption, a strong passcode/PIN or biometric unlock, disable developer/side-loading on Android, and block jailbroken/rooted devices. Push OS and app updates or deny access until devices meet minimum patch levels.
  • Implement strong access controls and multi-factor authentication (MFA). Require MFA to access corporate email, VPN and cloud services from mobile devices. Combine device checks (compliance posture) with conditional access rules that restrict resources when a device is non-compliant or connects from risky networks.
  • Protect corporate data with containerization and remote wipe. Use app-level containerization or Mobile Application Management (MAM) to separate corporate data from personal data; enforce data loss prevention (DLP) policies like copy/paste restrictions and blocking unapproved cloud backups. Ensure the capability for selective or full remote wipe when a device is lost, stolen or an employee leaves.
  • Monitor, audit and train. Enable logging for device enrollment, access attempts and policy violations. Schedule quarterly audits of device compliance and provide short, role-based training for employees on secure BYOD practices and incident reporting procedures.

Example in a Small or Medium Business

Harbor Marketing, a 45-person digital agency, allowed designers to use personal tablets and phones for email and file access but needed better controls. The leadership approved a BYOD policy that required employees to enroll devices in a cloud MDM during onboarding. The IT lead configured a baseline profile enforcing device encryption, automatic OS updates, screen-lock timeout, and blocking of rooted or jailbroken devices. Conditional access rules were applied so only compliant devices could access cloud storage and email, and MFA was enforced for all remote logins. For designers who needed corporate files on personal devices, IT issued a containerized file app with DLP rules that prevented saving to personal cloud accounts and allowed selective remote wipe. When an employee resigned, IT used the MDM to deprovision the device and confirm the corporate container was wiped without affecting personal data. Quarterly checks and a short training session for staff on secure device practices reduced both incidents and support calls, and the agency documented the controls as part of their security checklist.

Summary

Combining a concise BYOD policy with technical controls—MDM/UEM enrollment, enforced secure baselines, MFA/conditional access, containerization and remote wipe—lets SMBs meet the requirements of Control 2-6-3. These measures provide inventory, configuration hygiene, access control and data protection while preserving employee flexibility. Regular monitoring, audits and user training complete the program, ensuring devices that access corporate resources remain accountable and secure.

 

Quick & Simple

Discover Our Cybersecurity Compliance Solutions:

Whether you need to meet and maintain your compliance requirements, help your clients meet them, or verify supplier compliance we have the expertise and solution for you

 CMMC Level 1 Compliance App

CMMC Level 1 Compliance

Become compliant, provide compliance services, or verify partner compliance with CMMC Level 1 Basic Safeguarding of Covered Contractor Information Systems requirements.
 NIST SP 800-171 & CMMC Level 2 Compliance App

NIST SP 800-171 & CMMC Level 2 Compliance

Become compliant, provide compliance services, or verify partner compliance with NIST SP 800-171 and CMMC Level 2 requirements.
 HIPAA Compliance App

HIPAA Compliance

Become compliant, provide compliance services, or verify partner compliance with HIPAA security rule requirements.
 ISO 27001 Compliance App

ISO 27001 Compliance

Become compliant, provide compliance services, or verify partner compliance with ISO 27001 requirements.
 FAR 52.204-21 Compliance App

FAR 52.204-21 Compliance

Become compliant, provide compliance services, or verify partner compliance with FAR 52.204-21 Basic Safeguarding of Covered Contractor Information Systems requirements.
 
Hello! How can we help today? 😃

Chat with Lakeridge

We typically reply within minutes