You got the email. An enterprise prospect wants to move forward, and their security team has one request before they'll sign: proof that you take security seriously, usually a SOC 2 report or an ISO 27001 certificate. If you don't have a security or compliance person, your next question is: which one do I even need? And do I have to do both?
The short version: get the one your customers are actually asking for. Build your controls once, and set things up so the same work counts toward the other later. Both frameworks are mostly the same security practices wearing different paperwork.
What SOC 2 actually is
SOC 2 is an attestation report produced by a licensed CPA firm in the US, built around the AICPA's Trust Services Criteria (Security, Availability, Processing Integrity, Confidentiality, Privacy). Only Security is required. There is no "SOC 2 certificate" (you get a report you hand to prospects under NDA). Type I means designed correctly at a point in time; Type II means operated over a period, commonly 3-12 months. SOC 2 is the dominant ask in the US market.
What ISO 27001 actually is
ISO/IEC 27001 is an international standard. You earn a certificate from an accredited certification body, recognized globally. It centers on an Information Security Management System: a documented, repeating cycle of assessing risk, choosing controls, and improving. The 2022 revision lists 93 Annex A controls, certified over two audit stages on a three-year cycle with annual surveillance. It's the expectation when selling into Europe, the UK, the Middle East, APAC, or to large global enterprises.
Who asks for which
Mostly US customers, SaaS, mid-market and enterprise will ask for SOC 2. European, UK, or global customers, or large multinationals, will ask for ISO 27001. As you move upmarket, increasingly both. Don't guess. Go back through your sales conversations and security questionnaires. The framework your pipeline keeps naming is the one that unblocks revenue first. Get that one first.
The overlap nobody tells you about
SOC 2 and ISO 27001 are built on the same practices: access control, encryption, change management, vendor oversight, incident response, logging, risk assessment. Practitioners who map them commonly report roughly 80%+ overlap (some claim higher); treat any single percentage as approximate. When you implement MFA, you satisfy both. The real waste isn't picking the "wrong" framework first; it's doing all the work for one and starting from scratch for the second.
Cost and time, honestly
Ballpark ranges, not quotes: a SOC 2 Type II commonly lands in the low tens of thousands (plus tooling and internal time); ISO 27001 is often similar or somewhat higher (an accredited body across two stages plus annual surveillance); timelines for both span a few months to the better part of a year. The biggest hidden cost for a small team is the weeks of founder and engineer time spent gathering evidence.
A simple decision framework
- Which framework is in the deals you're trying to close now? Get that one first.
- Where are your customers? US leans SOC 2; global and EU lean ISO 27001.
- Need speed to unblock one deal? A SOC 2 Type I can often be produced faster.
- Plan for both from day one by implementing controls once and mapping to both.
Doing it without a hire
This is what Argyx removes for teams with no security hire. Implement one set of controls, and it crosswalks them across SOC 2 and ISO 27001 (and HIPAA and PCI), testing against your live systems and auto-collecting time-stamped evidence. At audit time, your auditor gets a read-only login.
Want to see which controls you'd already pass? Run a free scan of your live systems (no login required), or start the 14-day free trial. Whichever framework you get first, you won't redo it for the second.
