SOC 2 Endpoint Security: Do You Need MDM?
Does SOC 2 require MDM or antivirus? Read what the criteria say about laptops, set a device baseline, handle personal devices, and keep evidence for the full period.

SOC 2 does not require MDM or any other product. Points of focus under CC6.7 and CC6.8 mention protecting endpoint devices and using antivirus, and CC6.6 lists EDR as an example, but points of focus are not requirements. You design a control that protects the data on your devices, and the CPA firm tests it. For most SaaS teams that control is a short device baseline: encryption, screen lock, supported and updated software, and malware protection on every laptop that can reach production, source code, or customer data. MDM is the easiest way to enforce that baseline and prove it held. A very small team can sometimes do it without one, but the proof gets harder as the team grows.
TL;DR
- No rule in the Trust Services Criteria says “use MDM” or “install antivirus.” Your approved control sets the rule.
- Scope the control by access. Any device that can reach in-scope systems or customer data belongs in it, including contractor and personal devices.
- A typical baseline covers disk encryption, screen lock, OS updates, malware protection, and lock or wipe for lost company devices.
- With a handful of company laptops on one platform, manual checks can work if they are dated and complete. Past that, a device management service usually costs less than the manual proof.
- For a Type 2 report, show the device list was complete and each device met the baseline across the period, not only on the day you checked.
What do the SOC 2 criteria say about endpoints?
The AICPA Trust Services Criteria touch laptops and phones in several places. None of them requires a specific product.
| Criterion | What it asks for | Endpoint point of focus |
|---|---|---|
| CC6.7 | Restrict and protect the transmission, movement, and removal of information | “Protects Endpoint Devices”: processes and controls protect endpoint devices such as mobile devices, laptops, desktops, and sensors |
| CC6.8 | Prevent or detect and act on unauthorized or malicious software | Restrict who can install software, detect unauthorized changes, and use antivirus and anti-malware on servers and endpoint devices |
| CC6.4 | Restrict physical access to facilities and protected information assets | “Recovers Physical Devices”: recover laptops and mobile devices when someone no longer needs access |
| CC6.6 | Protect against threats from sources outside the system boundary | “Implements Boundary Protection Systems”: lists firewalls and endpoint detection and response systems as examples |
| CC6.5 | Remove protections from physical assets only after the ability to read or recover data on them is no longer required | Covers removing data and software before disposal |
| CC7.1 | Detect configuration changes and new vulnerabilities | Defined configuration standards, monitoring for noncompliance, and detecting unknown or unauthorized components |
Points of focus explain the criteria. The same AICPA document says using the criteria “does not require an assessment of whether each point of focus is addressed.” Some may not fit your company at all. So the antivirus point of focus under CC6.8 is a strong hint about what a CPA firm will ask, not a requirement to buy an antivirus product for every Mac.
What the criteria do require is that your controls meet the criterion. If engineers clone the production repository onto laptops, or open customer records in a browser, a stolen unencrypted laptop is a real path to that data. Your CPA firm will want to see how you closed it.
Do you need MDM for SOC 2?
You need a way to enforce your device rule and prove it held. MDM does both: it pushes settings to enrolled devices and reports which ones comply. That is why many teams pick one. But the decision depends on your team, not on the criteria.
| Situation | Reasonable approach |
|---|---|
| 2 to 5 people, all on company laptops of one platform | Manual checks can work: a dated screenshot or command output per device for each setting, on a set schedule, kept with the device list |
| 6 to 20 people, or mixed platforms | A device management service usually saves time, because one report replaces a pile of screenshots and catches drift between checks |
| Contractors or personal devices reach production, source code, or customer data | Enroll the device, require proof of the same settings, or limit access to a managed environment such as a virtual desktop or a managed browser profile with downloads and sync blocked |
| A customer contract requires managed devices | Use MDM. SOC 2 does not name MDM, but once you commit to managed devices, your controls must meet that commitment and the CPA firm may test it |
| No laptop can reach production, source code, or customer data | Document how that boundary is enforced. The endpoint control may be narrow, but it still needs evidence |
The headcount ranges are my rough guide to how much manual proof a Type 2 period takes, not a rule. Manual checks break down for a simple reason: they show a setting on the day you looked. If a developer turns off disk encryption the next week, nothing tells you until the next check. A device management service flags that drift between checks, if someone watches its alerts or reports. You still need dated exports and follow-up records, because a Type 2 report tests whether the control operated across the whole period.
If you go manual, keep each check complete. Every device on the list, every setting in the baseline, the date, who checked, and what happened to devices that failed. A missing device is harder to explain than a failed one.
What should a SOC 2 laptop baseline include?
Write the baseline as a short standard that your control points to. Each line should be something you can check and prove. Here is a common starting point for a small SaaS team.
| Setting | Why it matters | How teams usually prove it |
|---|---|---|
| Full-disk encryption on | A lost or stolen laptop does not expose source code or data | Device management compliance report, or OS encryption status output |
| Screen lock after a short idle time | An unattended laptop does not stay open | Configuration profile or device report |
| Supported OS with security updates | Known vulnerabilities get patched | OS version report against the vendor’s supported versions |
| Malware protection on and current | Covers the CC6.8 point of focus on endpoint malware | Built-in protection status or security tool report |
| Firewall on where the platform has one | Limits inbound connections on untrusted networks | Configuration profile or device report |
| Lock or wipe for lost company devices | Supports the CC6.7 point of focus on protecting endpoint devices | Device management enrollment, or the OS vendor’s remote lock and erase under a company-controlled account, plus a tested record |
| Restricted local admin rights, if used | Supports the CC6.8 point of focus on who can install software | Device configuration or role list |
Do not add a setting you cannot prove. A baseline that says “EDR on every device” fails the first sample if two Linux laptops never got the agent. Write the rule you can operate, and record the gaps as exceptions with an owner and an end date.
Built-in protection can satisfy your control if you name it and verify it. macOS and Windows both include malware protection that runs without a user-triggered scan. Your CPA firm decides whether your design is enough, so say which protection each platform uses, and how you check that it is on and current. Linux laptops often have the least built-in coverage, so decide whether they need a separate tool, tighter access limits, or an exception.
Encryption details for data at rest and in transit live in the SOC 2 encryption requirements guide. Vulnerability scanning and patch timelines for servers belong with SOC 2 vulnerability management.
How should you handle personal and contractor devices?
Decide by access. A device belongs in the control when it can reach in-scope systems, source code, or customer data, whoever pays for it. NIST SP 800-46 Rev. 2, the NIST guide to telework and bring-your-own-device security, recommends planning on the assumption that external environments contain hostile threats, so treat a device you do not manage as one you cannot fully trust.
You have three workable options:
- Bring it under the same rule. Enroll the personal or contractor device in your device management service, or collect the same proof you collect for company laptops. Approve the device before access and record what happens at exit.
- Accept equivalent proof. For a contractor firm that runs its own device program, get a statement or report that covers the same settings, and record who reviewed it and when.
- Keep company data off the device. Give access through a managed virtual desktop, a managed browser profile, or a separate managed environment, with downloads, clipboard, and local sync blocked. A plain browser session can still download files and cache pages, so it does not count by itself. Then the control covers that environment, and you document how those restrictions keep company data off the personal device.
Whichever you choose, write it into the policy and the control, and keep the approval record. Phones need the same thought: if staff read customer support email or approve production deploys on a phone, the phone is in scope for that access. The contractor guide and the remote team guide cover the access side in more detail.
What evidence do you need for a Type 2 period?
A Type 1 report looks at design on one date. A Type 2 report tests whether the control operated through the whole period, so your evidence has to cover time, not just a snapshot. Plan for these items:
- The approved control and device standard: the baseline, who owns it, and the effective date.
- A complete device list. Reconcile it to your identity provider and HR records so every person with access has a device on the list, and every device has an owner. The asset inventory guide shows how.
- Dated compliance reports. Export from your device source near the start and end of the period, plus each scheduled check in between. Device tools often keep limited history, so export on schedule rather than at the end.
- Follow-up for failures. When a device falls out of compliance, show the date you noticed, what you did, and when it came back.
- Joiners and leavers. Keep device setup records for people who started during the period and device return or wipe records for people who left. The onboarding and offboarding checklist covers both.
- Approved exceptions, each one with scope, owner, compensating safeguards, approval, and end date.
- Disposal records. For devices retired during the period, proof that data was removed before reuse, resale, or recycling. NIST SP 800-88 Rev. 2 is the common reference for media sanitization.
Your CPA firm decides the sample size and the evidence it accepts. Ask early which report format it wants, because a device tool export with a clear date and device count saves a lot of back and forth.
Common gaps auditors find
- The device list misses people. A new contractor got repository access but never got a device record.
- The baseline promises more than the tools enforce, such as EDR on every device when the agent only supports one platform.
- Proof exists only for the last week of the period.
- A departed employee’s laptop has no return or wipe record.
- Personal devices reach email or source code with no approval on file.
- An exception has no end date, so it quietly became the rule.
If one of these turns into an audit exception, the audit exceptions guide explains what it means for your report.
Track the endpoint control in FileGRC
FileGRC is a Git-native GRC workspace for SOC 2 work. JSON holds
structured records, Markdown holds long-form work, and Git supplies the change
history. A new workspace includes a proposed endpoint protection control
(OPS-02) mapped to CC6.6, CC6.8, and CC7.1, a proposed monthly endpoint
protection check, and proposed event-driven work to approve and register a
personal device before use. Separate asset work covers registering issued
devices at worker start, recovering company property when someone leaves,
disposal proof, and an annual inventory review. The starter program maps CC6.7 to the encryption control (DATA-02), which
covers device encryption. Add CC6.7 to OPS-02 too if you want endpoint
protection itself traced to that criterion. Starter records are proposals, not compliance claims, so edit the
control statement and the schedules until they match how you run devices.
Check what the control still needs:
npx filegrc get control control-endpoint-protection
npx filegrc program-readiness --control control-endpoint-protection
On a new workspace, the readiness output asks you to review which devices may reach company Systems, link the in-scope Systems, and cover the missing Endpoint Management evidence family with an active Component that can produce the proof.
Record your device management service as that Component. Each scaffold
command prints a template, so write it to a private temporary folder outside
the repository:
tmp="$(umask 077; mktemp -d)"
npx filegrc scaffold component --title "Device management service" > "$tmp/component.json"
Fill in the kind, description, and owners, set evidenceSourceKinds to
["endpoint-asset"], and name the people who can pull reports in
evidenceOwnerIds. Then preview and create it. The preview rejects a record with missing
fields or unknown IDs:
npx filegrc preview-mutation "$tmp/component.json" --json
npx filegrc create "$tmp/component.json" --json && rm -rf "$tmp"
npm run validate
The Component starts as planned. Mark it active once you add its System
uses, which means the System records for the service you are examining must exist first, and write the steps to pull a compliance report in its Markdown so the
next person can repeat them.
Then link the Component to the control. Readiness only counts evidence sources
listed in the control’s evidenceSourceComponentIds:
tmp="$(umask 077; mktemp -d)"
npx filegrc get control control-endpoint-protection --mutation > "$tmp/control.json"
The file may not have an evidenceSourceComponentIds key yet. Add one to
record as an array holding the Component ID, then apply the change:
npx filegrc update control control-endpoint-protection "$tmp/control.json" --json && rm -rf "$tmp"
FileGRC writes the files but does not commit them, so review the diff before you commit.
The monthly check creates no work until its rule is active. Activating the rule
is one of several gates: the program and the governing Policy must also be
active, and the control implemented, before you can record a completed check.
To activate the rule, scaffold the
activation, review the cadence, fill in the approvers, and copy the scaffold’s
review.revision value into payload.confirmedRevision to confirm the rule
you reviewed. Then run the command again with the file:
tmp="$(umask 077; mktemp -d)"
rule=obligation-rule-monthly-endpoint-protection-verification-v1
npx filegrc activate-obligation-rule "$rule" --scaffold > "$tmp/activation.json"
After you set payload.approvedByIds and payload.confirmedRevision in that
file, activate the rule from the same terminal session, since it reuses
$rule and $tmp:
npx filegrc activate-obligation-rule "$rule" "$tmp/activation.json" && rm -rf "$tmp"
Once those gates pass, each monthly check becomes a Work Queue item. The recurring SOC 2 tasks guide walks through recording and reconciling each occurrence with the exported report as evidence. Devices that need custody tracking can go in Asset records with an owner, custodian, and status, and gaps such as an unsupported Linux laptop can go in an exception record with an approval and end date.
An agent with access to the repository can read the control, its obligations, and linked evidence, then flag a missed monthly check, an expired exception, or a control with no device evidence source.
Your device management service and operating systems enforce the settings. FileGRC does not enroll devices, pull compliance reports, or decide whether your evidence is enough. Your team runs the checks, exports the reports, and approves exceptions. An independent CPA firm performs the SOC 2 examination and judges whether the control was designed and operated well.
Run your SOC 2 program as files in Git.
Keep policies, controls, work, and evidence indexes in a repository your team and agents can inspect. Add optional FileGRC Autopilot email and Slack reminders to keep work moving.
Frequently asked questions
Does SOC 2 require MDM?
No. The AICPA Trust Services Criteria do not mention mobile device management or require any product. A CC6.7 point of focus says processes and controls are in place to protect endpoint devices such as laptops and mobile devices, and CC6.8 covers preventing or detecting malicious software. MDM is a common way to enforce and report device settings, but a small team can meet its own approved control another way if it can show the settings held for every covered device. Confirm the design with your CPA firm.
Does SOC 2 require antivirus on every laptop?
No single rule requires it. A CC6.8 point of focus describes antivirus and anti-malware software on servers and endpoint devices, and points of focus are characteristics to consider, not a checklist. Many teams rely on the protection built into the operating system and verify that it is on and current. Write down which protection each platform uses and how you check it.
What laptop settings do SOC 2 auditors usually test?
Auditors test the settings your approved control names. For a small SaaS team that often means full-disk encryption, automatic screen lock, a supported operating system with security updates, malware protection, a firewall where relevant, and the ability to lock or wipe a lost company device. The CPA firm picks samples from your device population and asks for proof for each one.
Can employees use personal devices under SOC 2?
Yes, if your policy allows it and you control the risk. Common designs approve personal-device use before access, register the device, verify its safeguards, limit which data and systems it can reach, and define what happens when the person leaves. Some teams block personal devices from production and customer data entirely. Record whichever rule you choose and keep proof that it held.
Do we need EDR on every laptop for SOC 2?
No. A CC6.6 point of focus lists endpoint detection and response systems as one example of boundary protection, and a CC6.8 point of focus describes antivirus and anti-malware software, but neither requires a product. Use EDR where your risk calls for it, and only write it into your control for the devices where you can actually deploy and prove it.
What evidence shows an endpoint control operated during a SOC 2 Type 2 period?
Keep the approved control and device standard, a complete device list reconciled to the people with access, dated compliance reports from your device source near the start and end of the period, periodic check results, follow-up for devices that fell out of compliance, approved exceptions, and onboarding and offboarding records for devices that joined or left during the period.
Does FileGRC manage laptops or enforce device settings?
No. Your device management service, operating system, and security tools enforce settings and produce reports. FileGRC is a Git-native GRC workspace for SOC 2 work. It records the endpoint control, the device source, recurring checks, exceptions, and fixed evidence your team exports, with JSON for structured records, Markdown for long-form work, and Git for change history.