Block Legacy Authentication for SOC 2 Compliance
Learn how ID-02 helps you meet SOC 2 requirements for Microsoft 365 and Entra ID security.
Organizations pursuing SOC 2 compliance need to address block legacy authentication as part of their security program. The ID-02 control maps directly to SOC 2 requirements, helping demonstrate compliance while strengthening your security posture.
How ID-02 Addresses SOC 2 Requirements
SOC 2 requires organizations to implement controls around block legacy authentication. The ID-02 control provides:
- A Conditional Access policy blocks legacy authentication protocols (IMAP, POP3, SMTP, older Office clients)
- No exceptions for legacy protocols except documented service accounts
These measures directly support SOC 2 compliance by ensuring proper identity security in your Microsoft 365 environment.
Implementation for Compliance
To satisfy SOC 2 requirements with this control:
- **Enable the control** - Use TrueConfig's one-click remediation
- **Document your implementation** - Record how the control was configured
- **Maintain evidence** - TrueConfig automatically logs compliance status
- **Monitor continuously** - Track any deviations from the expected state
Evidence Collection
For SOC 2 audits, you'll need to demonstrate:
- Current configuration state
- Historical compliance data
- Remediation actions taken
- Continuous monitoring in place
TrueConfig provides all of this evidence through its audit trail and reporting features.
Why This Control Matters for SOC 2
Legacy protocols like IMAP and POP3 cannot enforce MFA. Attackers specifically target these protocols to bypass your MFA policies. Blocking them closes a major attack vector.
Implementing ID-02 is an important step toward SOC 2 compliance. Combined with TrueConfig's continuous monitoring, you can demonstrate ongoing adherence to SOC 2 requirements.
Ready to achieve SOC 2 compliance?
TrueConfig continuously monitors your Microsoft 365 tenant for compliance with SOC 2 requirements, including this control.