REVIEW DRAFTOverviewV1 · one pageV2 · part 1V2 · part 2V2 · part 3
THE BAY PLAYBOOK
DRAFT · COMPANY SECTION / PART 2 OF 3PARTNER GUIDE · FROM SPRINTO

Which framework, and what to build first

The starter kit most startups put in place first, then SOC 2 and the frameworks that sit around it, and a way to choose. (About 14 minutes)

PARTNER GUIDEWritten by Sprinto, our compliance partner, and shared with The Founder Folks. The words below are Sprinto’s.

Earlier: Do you need it yet?. This part stands on its own if you’d rather start here.

Your Compliance Starter Kit

Here is a list of measures most startups put in place first, regardless of which framework they’re going after. Use it as a simple starting point. This is not an exhaustive list—your auditor may expect more, depending on your industry, product, team size, and infrastructure.

THE STARTER KIT21 ITEMS · TICK AS YOU GO
POLICIES AND RISK MANAGEMENT
Core security policies
Written policies cover Information Security, Access, Incident Response, Data Classification and Retention, Change Management, Business Continuity, Disaster Recovery, Vendor Management, and Risk Management, and must be approved by leadership.
Risk assessment
A risk assessment exercise is conducted annually. It lists potential risks, estimates their likelihood of occurrence, and assesses the potential impact.
Risk ownership
Every listed risk has a named owner who tracks and mitigates its impact. Leadership reviews this list regularly.
Control monitoring
The status of controls is checked periodically by a team member. They also track fixes to closure.
PEOPLE
Policy acknowledgment and sign-offs
Every employee reads and accepts your security policies when they join, and again each year.
Background checks
New hires are screened before they are allowed access to sensitive systems (where local laws permit).
Security training
Every employee completes a security training module at onboarding and once every year.
DEVICES AND DATA
Secured devices
Company devices are encrypted, auto-lock after 10 minutes of inactivity, and are tracked through a device management tool.
Customer data handling
Customer data is encrypted in transit and at rest.
ACCESS
Multi-factor authentication
MFA is enabled across key systems—email, code, cloud, etc.
Unique accounts
All employees operate with separate accounts—no shared accounts or passwords.
Role-based access
People gain access to systems based on their roles, and access is approved by management.
Access reviews
Access to production and customer data is reviewed quarterly, and anyone who should not have access must be removed.
Offboarding
Once an employee leaves, their access is removed promptly, ideally on the same day.
OPERATIONS
Logging and alerts
Production systems log activity and alert teams for unusual activity.
Vulnerability scanning and penetration testing
Automated vulnerability scans are conducted regularly. An independent penetration test is conducted at least once a year.
Data backup and recovery
Data is backed up automatically, and restoration is tested to confirm that data can be recovered after an incident.
Incident response
A plan for how security incidents are identified, escalated, contained, and communicated with clear roles must be documented. This plan is tested once a year.
Disaster recovery
A written plan explains how critical systems and data are restored after major outages with target recovery times. This plan is tested once a year.
CHANGE AND VENDOR MANAGEMENT
Code review
Every code change is documented, reviewed, and approved before deployment to production systems.
Vendor reviews
Vendors that handle company or customer data are vetted before onboarding and reviewed annually.
0 of 21 in place

Your ticks stay in this browser only. They’re there to help you see where you stand today.

Frameworks you’ll most likely encounter

If you’re a tech company selling in the US, SOC 2 is almost certainly the first framework you’ll encounter. There’s a reason we’ve mentioned it so many times—SOC 2 is the default trust signal customers expect to see when they ask whether you’re secure. So let’s start there.

The essentials of SOC 2

What it is: SOC 2 is a framework created by the American Institute of Certified Public Accountants (AICPA), the US accounting body.

The framework is interpretive rather than prescriptive, which means it lists what you need to achieve, not what controls you implement. So you can design controls that you think best fit your business. A Certified Public Accountant (CPA) or a CPA firm then reviews these measures and compiles a report of their opinion and findings.

Who it applies to: SOC 2 is an attestation and applies to service organizations—any company that stores, processes, or handles customer data as a part of what it sells. This could include:

What it covers: SOC 2 evaluates an organization’s controls based on five operational areas, known as ‘Trust Services Criteria’. These are:

THE FIVE TRUST SERVICES CRITERIATAP ONE
MANDATORY
Security
Evaluates controls designed to protect systems and data from unauthorized access.
INCLUDED BASED ON THE SERVICES YOU OFFER
Availability
Evaluates measures designed to keep systems up and operational.
INCLUDED BASED ON THE SERVICES YOU OFFER
Confidentiality
Evaluates how organizations safeguard sensitive information.
INCLUDED BASED ON THE SERVICES YOU OFFER
Processing Integrity
Evaluates if systems process data accurately.
INCLUDED BASED ON THE SERVICES YOU OFFER
Privacy
Evaluates how organizations collect, process, store, and dispose of personal data and keep to privacy commitments.

Of these, Security is mandatory, while the others are included based on the nature of services offered.

Types of reports: There are two types of SOC 2 reports—Type 1 and Type 2.

A SOC 2 Type 1 report covers control design at a point in time.

A SOC 2 Type 2 report evaluates if your controls worked as intended over a period of time, typically 3 to 12 months.

QUICK TIP
If you find a deal being blocked by compliance, aim for a SOC 2 Type 1 report immediately. This can help unblock the deal. Then start the SOC 2 Type 2 observation period. Your first Type 2 report can span a shorter timeframe, say, 3 months. You can later expand your observation window to cover a year.

Other frameworks and regulations you’ll likely encounter

Think of SOC 2 as your home planet. Everything else in the galaxy is a short trip from here.

It’s a common starting point for most early-stage companies, but it isn’t the only way in. It does, however, become your foundation while the ones listed below apply to you depending on which regions you sell to and what data you handle. You can pursue them alongside SOC 2 or even earlier if your market calls for it.

WHAT IT IS

Unlike SOC 2, ISO 27001 is a certification from an accredited body. It sets out guidelines on building and maintaining what the International Organization for Standardization (ISO) calls an Information Security Management System (ISMS).

An ISMS is a structured set of policies, procedures, and technical controls designed to identify information security risks, evaluate them, and implement measures to minimize impact.

WHO IT APPLIES TO

While US buyers prefer SOC 2, customers from Europe, the UK, the Middle East, and most of Asia prefer ISO 27001. Many founders who relocate to the US end up selling across two or more of these regions. So a combination of both frameworks is very common.

THE OVERLAP

A significant number of ISO 27001 controls overlap with SOC 2. So if you’ve got the groundwork done for SOC 2, ISO 27001 becomes an extension of these efforts rather than a new project altogether.

WHAT IT IS

The Health Insurance Portability and Accountability Act, HIPAA for short, is a US federal law and comes into effect if you handle Protected Health Information (PHI) for hospitals, clinics, insurers, or other healthcare organizations, including as their software provider. HIPAA is overseen by the US Department of Health and Human Services (HHS), which issues its rules, and enforced by the HHS Office for Civil Rights (OCR).

HIPAA has three key rules:

  • Privacy rule (provides patients with certain rights, affording them better control over their PHI, and limiting how this data is used)
  • Security rule (ensures the security of PHI that is collected, stored, processed, transmitted, and maintained by Covered Entities)
  • Breach notification rule (requires Covered Entities and Business Associates to notify impacted parties and regulators about breaches within a stipulated timeframe)

It’s important to note that HIPAA does not have an official certification. Failing to comply with HIPAA carries hefty penalties, including fines, terminations, sanctions, and criminal charges.

WHO IT APPLIES TO

HIPAA rules apply to two types of organizations—Covered Entities (healthcare providers, health plans, and healthcare clearinghouses), and Business Associates (organizations that handle PHI on behalf of Covered Entities or provide them with services).

If you’re a startup with healthcare organizations as customers, HIPAA applies to you. Customers will expect you to sign a BAA (Business Associate Agreement), a binding contract that guarantees you will keep their information safe.

THE OVERLAP

SOC 2 covers a lot of the groundwork for HIPAA. HIPAA’s Security Rule specifically evaluates administrative, physical, and technical safeguards, and many of these overlap with SOC 2.

Having said that, HIPAA includes unique measures, such as the Breach Notification Rule, which sets deadlines for notifying affected parties and regulators.

WHAT IT IS

The Payment Card Industry Data Security Standard, PCI DSS, for short, is a global security standard for the protection of cardholder data. First released in 2004, PCI DSS has been managed by the PCI Security Standards Council, founded by American Express, JCB, Discover, Visa, and Mastercard.

PCI DSS essentially covers security measures designed to ensure the safe and secure handling of cardholder data. The framework groups 12 core requirements under 6 vital goals:

  • Build and maintain a secure network and systems
  • Protect account data
  • Maintain a vulnerability management program
  • Implement strong access control measures
  • Regularly monitor and test networks
  • Maintain an Information Security Policy

Unlike SOC 2 and ISO 27001, non-compliance incurs fines ranging from $5k to $100k per month, depending on the duration. A breach can add to these costs, and companies can even lose the ability to accept card payments.

WHO IT APPLIES TO

PCI DSS applies to any organization that collects, processes, transmits, and stores cardholder information. PCI DSS groups organizations into various levels based on the number of transactions processed per year.

PCI DSS is validated through a Self-Assessment Questionnaire or by a Qualified Security Assessor, depending on the organization's level.

THE OVERLAP

Many controls from SOC 2 count towards both frameworks—MFA, unique accounts, encryption, written policies, and vendor reviews, to name a few. And while SOC 2 provides a strong foundation, PCI DSS requires its own scoping and validation.

WHAT IT IS

ISO 42001 is the first international standard for AI management. Launched in 2023, it provides organizations with a structured approach to governing the development and use of AI. At its core, ISO 42001 provides guidelines for building and maintaining an AI Management System (AIMS).

Like ISO 27001, it’s a certification issued by an accredited body.

WHO IT APPLIES TO

ISO 42001 applies to any organization that builds, uses, or sells AI systems. Startups fine-tuning their models or building features on a third-party model API can pursue the framework. While the certification is voluntary, it’s become a real differentiator for any company with AI at its center, especially for highly regulated industries like healthtech or finance.

THE OVERLAP

ISO 42001 and SOC 2 overlap significantly in the foundational security layer. Risk assessment, policies, defined roles, and access controls are some ways they overlap. What SOC 2 doesn’t cover is the AI-specific layer, which includes measures such as human oversight, transparency, lifecycle controls, and impact assessments.

WHAT IT IS

NIST, or the National Institute of Standards and Technology, is the institute that formalized its AI Risk Management Framework in 2023. It serves as a voluntary standard governing the management of risks arising from the development and use of AI.

The framework is built around four key functions:

  • Govern: Setting up policies, roles, and culture for managing AI risk across the AI lifecycle
  • Map: Understanding the context of AI—what it does, who it impacts, and what could go wrong
  • Measure: Assessing and tracking risks through testing and monitoring
  • Manage: Prioritizing risks, determining response, and keeping watch when things change
WHO IT APPLIES TO

NIST AI RMF is designed for any organization that builds, deploys, or uses AI, regardless of size and industry. This includes startups building AI features on a third-party model API, not just large companies looking to build their own models.

The framework is voluntary, but matters most for AI-first companies looking to sell to US enterprises or working in regulated industries. Some state AI laws also designate it as a recognized framework.

THE OVERLAP

Similar to ISO 42001, SOC 2 and NIST AI RMF have significant operational overlaps. The Govern step leans on the same written policies and defined roles under SOC 2. The Map and Measure steps build on SOC 2’s risk assessment and control monitoring, while the Manage step mirrors risk management and mitigation.

SOC 2 does not include the AI-specific layer addressing bias, fairness, explainability, and impact assessment.

NIST AI RMF is not a certification and does not involve an audit. That’s why many startups in the US align with the framework before moving on to ISO 42001 when customers request AI certification.

To sum up

IF YOU…PICK THE ONE THAT’S CLOSEST
START WITH
SOC 2
FRAMEWORK TO CONSIDER NEXT
Nothing yet
START WITH
SOC 2
FRAMEWORK TO CONSIDER NEXT
ISO 27001
START WITH
SOC 2 + HIPAA
FRAMEWORK TO CONSIDER NEXT
ISO 27001 if selling globally
START WITH
SOC 2 + PCI DSS
FRAMEWORK TO CONSIDER NEXT
Depends on your buyer
START WITH
SOC 2
FRAMEWORK TO CONSIDER NEXT
NIST AI RMF + ISO 42001
See the whole table
IF YOUSTART WITHFRAMEWORK TO CONSIDER NEXT
Sell primarily in the USSOC 2Nothing yet
Sell in the US and look to expand to EU, Asia, the UK, or the Middle EastSOC 2ISO 27001
Serve the healthcare industrySOC 2 + HIPAAISO 27001 if selling globally
Process payment card informationSOC 2 + PCI DSSDepends on your buyer
Build an AI-first productSOC 2NIST AI RMF + ISO 42001

You don’t need everything at once

Once you start reading about compliance, it sounds like an unending list of frameworks you need all at once. So here’s an important myth worth killing. Trying to do everything at once is how small teams burn out. Focus on one framework at a time, and add the next when customers ask.

THE ORDERONE AT A TIME
01Start with security: This is your base. SOC 2’s Security TSC is your foundation and unlocks most US deals.
02Add AI next, if it applies: Once you have security in place, layer on AI governance. Align with NIST AI RMF first. Consider ISO 42001 only if customers ask for it.
03Tackle federal frameworks last: Government frameworks like FedRAMP require heavy lifting. Work on them only if the revenue justifies it.