Frameworks
Start with one framework. Add the rest without starting over.
Most frameworks ask for the same things in different words. Evidence collected for one carries into the next.
Supported frameworks
Each one has its own page: what it is, who needs it, and what the audit actually involves.
SOC 2
The one your buyers ask for
ISO 27001
Recognised worldwide
HIPAA
Protect health information
GDPR
Handle EU personal data
PCI DSS
Take card payments safely
ISO 42001
Govern how you use AI
NIST CSF
A common security language
CMMC
Work with the DoD
Custom
Your own control set
ISO 27701
Privacy extension to ISO 27001
DORA
EU financial operational resilience
NIS 2
EU critical infrastructure cybersecurity
CCPA / CPRA
California comprehensive privacy
FERPA
Student education privacy standard
FDA 21 CFR Part 11
FDA electronic records & signatures
HDS Certification
French health data hosting certification
SOX ITGC
IT controls for public companies
HITRUST CSF
Assurance healthcare buyers ask for
FedRAMP
Sell cloud services to US agencies
NIST SP 800-53
The federal security control catalog
NIST SP 800-171
Protect CUI on federal contracts
Why the second framework costs less than the first
A control is a thing you do: review access quarterly, encrypt data at rest, test your backups. A framework is a list of things it wants done, written in its own vocabulary.
Map the control once, to every requirement that asks for it, and adding a framework becomes a question of what is genuinely new rather than a second collection exercise.
Find out what your compliance program actually looks like
Thirty minutes, your real systems, no slideware. We'll show you what we'd automate first, and what you don't need us for.