The Top Ten Most Common SOC 2 Exceptions

Download the PDF version of this article here. 

What are some of the most common SOC 2 audit exceptions the our teams have encountered?

SOC 2 (Type 2) report exceptions are when a service organization fails to effectively operate its control as designed. From my experience, the top ten most common exceptions I have seen in the field are:

  1. Failure to remove/disable access to terminated user account(s) in a timely manner
  2. Failure to complete or retain evidence of policy (InfoSec, code of conduct, etc.) acknowledgment/sign off 
  3. Failure of user(s) to complete security awareness training upon hire and/or annually thereafter 
  4. Failure to retain evidence of or document a system change for approval or testing
  5. Failure to complete or retain evidence of annual performance review of employees with responsibilities related to security, availability, and confidentiality 
  6. Failure to complete a background check for new hire user(s) in a timely manner 
  7. Failure to perform an annual third party risk review of subservice organizations and/or third parties 
  8. Failure to design action plans or remediate moderate/high-risk vulnerabilities identified in scans
  9. Failure to complete or retain evidence for regular password or key rotation
  10. Failure to deploy anti-virus software or endpoint management solution on all in-scope devices

Both our Third Party Risk Management and SOC practices see these exceptions most often when service organizations are going for their first SOC report, switching audit firms, or migrating to new systems/infrastructure. 

Are these exceptions similar to your experiences, or are there others you are running into not on the list?

About Schneider Downs SOC Services

Schneider Downs employs a unique approach to SOC reports, integrating the expertise of information technology, internal audit and external audit professionals. By combining cross-disciplinary knowledge and project management expertise, we are able to effectively deliver on our clients' expectations.

If you are interested in learning how we can assist your organization, please contact us to get started and learn more about our practice at www.schneiderdowns.com/soc.

You’ve heard our thoughts… We’d like to hear yours

The Schneider Downs Our Thoughts On blog exists to create a dialogue on issues that are important to organizations and individuals. While we enjoy sharing our ideas and insights, we’re especially interested in what you may have to say. If you have a question or a comment about this article – or any article from the Our Thoughts On blog – we hope you’ll share it with us. After all, a dialogue is an exchange of ideas, and we’d like to hear from you. Email us at [email protected].

Material discussed is meant for informational purposes only, and it is not to be construed as investment, tax, or legal advice. Please note that individual situations can vary. Therefore, this information should be relied upon when coordinated with individual professional advice.

© 2024 Schneider Downs. All rights-reserved. All content on this site is property of Schneider Downs unless otherwise noted and should not be used without written permission.

our thoughts on
8 Key Considerations When Reviewing User Access
Enhancing Focus on Risk Management and Consumer Protection
The Top Risks Internal Audit Leaders Need to Know for 2024
SOC 2 Terminology: Vendor vs Subservice Organization vs Subcontractor vs Third Party vs Nth Party
Did Poor Change Management Contribute to the AT&T Wireless and McDonald’s Outages?
Register to receive our weekly newsletter with our most recent columns and insights.
Have a question? Ask us!

We’d love to hear from you. Drop us a note, and we’ll respond to you as quickly as possible.

Ask us
contact us
Pittsburgh

This site uses cookies to ensure that we give you the best user experience. Cookies assist in navigation, analyzing traffic and in our marketing efforts as described in our Privacy Policy.

×