BYOD & Mobile Device Policy Template for SOC 2
A SOC 2 BYOD (Bring Your Own Device) and Mobile Device Policy defines whether employees and contractors may access company systems from personal laptops or phones, and the minimum security controls required on those devices. Auditors test this under CC6.1, CC6.6, and CC6.7 by verifying MDM enrollment, disk encryption, OS patching, and remote wipe on offboarding.
Free Markdown Template
Copy or download the byod & mobile device policy
Replace bracketed [PLACEHOLDERS] with your actual stack
# Bring Your Own Device (BYOD) and Mobile Device Policy
**Document Owner:** [IT / Security Lead]
**Approved By:** [CEO / CTO]
**Effective Date:** [YYYY-MM-DD]
**Review Cadence:** Annual
**Applies To:** All employees, contractors, and advisors accessing [Company Name] systems or data
---
## 1. Purpose
This policy establishes security requirements for personally owned laptops, smartphones, and tablets (BYOD) used to access [Company Name] email, chat, source code, or production systems.
## 2. Eligibility and Approved Use
- **Workstations (Laptops/Desktops):** [Company Name] issues company-managed workstations for accessing production infrastructure and source code. Personal laptops are [prohibited from accessing production systems / permitted only if enrolled in [MDM Provider] with full compliance checks passing].
- **Mobile Devices (Phones/Tablets):** Employees may use personal iOS or Android devices to access [Google Workspace / Microsoft 365 / Slack] only after meeting every baseline requirement in Section 3.
- **Customer Data Restriction:** Downloading or storing raw customer production data, database dumps, or private keys on unmanaged personal devices is strictly prohibited.
## 3. Baseline Security Requirements for BYOD Devices
Every personal device permitted to access company resources must enforce:
1. **Authentication:** Biometric unlock or strong passcode (minimum [6]-digit PIN on mobile; [12]-character password on laptops) with automatic screen lock after no more than [5] minutes on mobile and [15] minutes on laptops.
2. **Full-Disk Encryption:** Native device encryption enabled (FileVault for macOS, BitLocker for Windows, native hardware encryption on iOS/Android).
3. **Supported Operating System:** Running a vendor-supported OS version with security updates installed within [14 / 30] days of release. Jailbroken or rooted devices are prohibited.
4. **Endpoint Protection / Management:** [MDM enrollment via Kandji / Jamf / Intune / Google Endpoint Management] enforcing posture verification and remote wipe of corporate accounts.
5. **Multi-Factor Authentication (MFA):** All access to company SaaS, SSO, and identity tools must pass through [Okta / Google Workspace / Entra ID] with phishing-resistant or TOTP MFA enabled.
## 4. Lost, Stolen, or Compromised Devices
1. Users must report any lost, stolen, or suspected compromised BYOD device to [security@company.com / #security-incidents] within [4 / 24] hours of discovery.
2. [IT / Security] will immediately revoke active SSO/OAuth sessions, disable email/Slack sync, and execute a corporate container wipe (or full remote wipe on enrolled workstations).
## 5. Offboarding and Revocation
Upon termination of employment or contract, [IT / Security] revokes all identity sessions and removes company email, Slack, and managed workspace profiles from the user's personal devices within [24] hours. Users agree to delete any residual local copies of company documents.
## 6. Privacy Boundaries
On personal mobile devices configured with corporate profile separation (e.g., Google Endpoint Management or MDM work profiles), [Company Name] limits management actions to enforcing baseline security checks and wiping corporate apps/data without inspecting personal photos, messages, or non-work apps.
## 7. Exceptions and Review
Exceptions require documented approval from [CTO / Security Lead] with compensating controls and an expiration date. This policy is reviewed annually.
Evidence Mapping
What auditors test beyond this policy
A signed policy document only satisfies design intent. During SOC 2 fieldwork, your CPA auditor samples operating evidence against each clause below:
| Policy Requirement | Control | Evidence Your Auditor Requests |
|---|---|---|
| Disk encryption, screen lock & OS posture on laptops | CC6.1 / CC6.6 | MDM device inventory export (Kandji, Jamf, Intune, Fleet) showing 100% of in-scope workstations encrypted, screen-locked, and on supported OS versions. |
| Mobile device conditional access / workspace policies | CC6.1 / CC6.7 | Google Workspace Endpoint Management or Microsoft Intune app-protection policy screenshot showing passcode enforcement and session wipe capability. |
| Session revocation on termination | CC6.3 | Sample of terminated employees showing IdP account suspension, OAuth token revocation, and MDM wipe within your 24-hour SLA. |
| Employee policy acknowledgment | CC1.4 | Signed/timestamped acknowledgment records confirming every in-scope employee accepted the BYOD policy. |
- Writing 'personal devices are strictly prohibited' when founders and engineers read Slack and company email on their personal iPhones. Auditors will spot the contradiction immediately.
- Allowing contractors to use personal laptops with production GitHub/AWS access without either enrolling them in MDM or restricting them to an isolated VDI/cloud dev box.
- Skipping mobile endpoint policies in Google Workspace or Microsoft 365 even when basic mobile device management is already included in your license.
Related guide: What SOC 2 auditors actually want to see for control evidence
Frequently Asked Questions
BYOD & Mobile Device Policy FAQ
- Can a startup pass SOC 2 with BYOD laptops?
- Yes, provided every laptop accessing in-scope production systems or source code meets your security baseline (full-disk encryption, screen lock, OS patching, endpoint protection) and you can prove compliance to your auditor, typically through MDM or a lightweight agent like Fleet, Kandji, Jamf, or Intune.
- Do personal phones need full MDM for SOC 2?
- Usually no. If personal phones only access email and Slack, most SOC 2 auditors accept mobile application management (such as Google Workspace Basic/Advanced Endpoint Management or Intune App Protection) that enforces device PINs and allows remote wipe of corporate accounts.
- What if our company issues laptops to everyone?
- Keep a short BYOD section that clearly states company-issued laptops are required for production access while defining the rules for personal phones accessing Slack or email. That closes the gap without banning normal phone use.
Skip manual fill-in-the-blank edits
Draft this policy directly from your real infrastructure.
Screenata scans your AWS, GCP, GitHub, and identity provider read-only, writes auditor-ready policies tied to real controls, and collects signed evidence automatically.