Cybersecurity Frameworks & Compliance Standards We Work To
Eleven UK, US, and international certification and compliance frameworks, four testing methodologies — the standards that actually govern how Mutex Systems designs, tests, and certifies security programmes, broken down individually so you know exactly what each one requires before you commit to it, and exactly how grComply automates the ongoing evidence work behind it.
Governance, Certification & Attestation
What each framework requires, who asks for it, and how long it typically takes.
United Kingdom
UK GDPR & Data Protection Act 2018
Data protection law enforced by the ICO for any UK-facing business
Read the guideCyber Essentials & Cyber Essentials Plus
NCSC-backed UK certification, often mandatory for government contracts
Read the guideNHS DSPT
Annual Data Security and Protection Toolkit for anyone handling NHS data
Read the guideNCSC Cyber Assessment Framework (CAF)
Outcome-based assessment used for NIS, the NHS and UK government
Read the guideUK NIS Regulations & Cyber Security and Resilience Bill
UK rules for essential services and digital providers — being expanded
Read the guideTelecommunications Security Act
Ofcom-enforced security duties and Code of Practice for UK telecoms providers
Read the guideDef Stan 05-138 & DCPP
MOD Cyber Risk Profile controls for the UK defence supply chain
Read the guideFCA & PRA Operational Resilience
Important business services, impact tolerances and scenario testing (PS21/3, SS1/21)
Read the guideEuropean Union
NIS2 Directive
EU cybersecurity law for essential and important entities across 18 sectors
Read the guideDORA
Digital Operational Resilience Act for EU financial entities and their ICT providers
Read the guideEU AI Act
Risk-based EU regulation for AI systems, with obligations phasing in from 2025
Read the guideInternational standards
ISO/IEC 27001:2022
Information security management system (ISMS) certification
Read the guidePCI DSS v4.0
Mandatory standard for anyone storing, processing, or transmitting card data
Read the guideISO/IEC 42001:2023
The first certifiable AI management system (AIMS) standard
Read the guideISO/IEC 27701
Privacy Information Management System (PIMS) certification
Read the guideISO 22301
Business continuity management system certification
Read the guideCIS Critical Security Controls v8.1
Prioritised safeguards organised into Implementation Groups 1–3
Read the guideISA/IEC 62443
Security standards for industrial automation, SCADA and OT
Read the guideTISAX
Automotive-industry information security assessment (VDA ISA)
Read the guideISO/IEC 27017 & 27018
Cloud security and cloud privacy codes of practice
Read the guideSANS Incident Response Framework
Six-step PICERL incident-handling model, with NIST SP 800-61
Read the guideISO/IEC 27002:2022
Implementation guidance for the 93 information security controls
Read the guideISO/IEC 27005:2022
Information security risk management guidance for an ISMS
Read the guideCOBIT 2019
ISACA framework for governance and management of enterprise IT and security
Read the guideCSA Cloud Controls Matrix & STAR
Cloud security control framework and the STAR assurance registry
Read the guideISO/IEC 23894:2023
Guidance on risk management for artificial intelligence
Read the guideUnited States
SOC 2 Type I & Type II
AICPA Trust Services Criteria attestation for SaaS and service providers
Read the guideSOC 3
The public-facing, general-use version of a SOC 2 report
Read the guideNIST Cybersecurity Framework
Govern, Identify, Protect, Detect, Respond, Recover — risk-based baseline
Read the guideHIPAA
US federal law protecting the privacy and security of patient health data
Read the guideCMMC 2.0
Mandatory cybersecurity certification for the US Defense Industrial Base
Read the guideFedRAMP
Authorization standard for cloud services selling to US federal agencies
Read the guideNIST SP 800-53 Rev. 5
Comprehensive security and privacy control catalogue
Read the guideNIST AI Risk Management Framework
Govern, Map, Measure, Manage — trustworthy and secure AI
Read the guideHow Security Testing Actually Gets Structured
The methodologies behind every penetration test, red team engagement, and AI application assessment we run.
OWASP Testing Framework
Top 10, ASVS, MASVS, and API Security Top 10 for application testing
Read the guidePTES
The Penetration Testing Execution Standard — 7-phase engagement methodology
Read the guideMITRE ATT&CK
Adversary tactics and techniques knowledge base for red teaming
Read the guideLLM Penetration Testing
OWASP LLM Top 10 and NIST AI RMF-aligned testing for AI applications
Read the guideOWASP Top 10 (2025)
The ten most critical web application security risks
Read the guideOWASP ASVS
Application Security Verification Standard — testable requirements in three levels
Read the guideOWASP MASVS & MASTG
Mobile app security standard and testing guide for iOS and Android
Read the guideOWASP API Security Top 10
The ten most critical API security risks (2023 edition)
Read the guideNIST SP 800-115
NIST technical guide to information security testing and assessment
Read the guideOSSTMM
Open Source Security Testing Methodology Manual (ISECOM)
Read the guideMITRE ATLAS
Adversary tactics and techniques against AI and machine-learning systems
Read the guideOWASP Top 10 for LLM Applications
The most critical risks in applications built on large language models
Read the guideOWASP Top 10 for Agentic Applications
Risks unique to AI agents that plan, use tools and act autonomously
Read the guideCommon Questions About Choosing a Framework
What is the difference between a compliance framework and a testing methodology?
A compliance framework — ISO 27001, SOC 2, NIST CSF, GDPR, PCI DSS, Cyber Essentials, ISO 42001 — defines the governance, controls, and evidence an organisation must maintain, often verified through certification or an attestation report. A testing methodology — OWASP's standards, PTES, MITRE ATT&CK, LLM penetration testing — defines how security testing is actually structured and executed to prove those controls hold up in practice. Most serious security programmes need both: a framework to govern against, and a methodology to test whether the governance actually works.
Which framework should we start with?
It depends on who is asking. If enterprise or US-facing SaaS buyers are asking, SOC 2 is usually the fastest path to a shareable report. If UK or EU procurement or regulators are asking, ISO 27001 carries more weight. If you are bidding for UK government contracts, Cyber Essentials may be a mandatory minimum. If you handle card payments, PCI DSS is not optional. Most organisations end up holding two or three of these frameworks over time as different buyers and markets ask for different proof.
Do these pages cover Pakistan-specific regulation as well?
No — this page covers international and UK standards. Pakistan-specific regulatory frameworks such as PTA CTDISR, the State Bank of Pakistan's cybersecurity guidelines, NEPRA's IT/OT regulations, and the Pakistan Information Security Framework are covered separately on our Pakistan regulatory compliance hub.
Can Mutex Systems help with more than one framework at once?
Yes, and it is usually more efficient to. Control evidence overlaps heavily between frameworks — the same access-control policy, encryption standard, or incident-response plan can satisfy requirements across ISO 27001, SOC 2, and NIST CSF simultaneously. Programmes are scoped to build the underlying control set once and map it to whichever frameworks actually apply to your business.
Not Sure Which Framework You Actually Need?
Tell us who is asking — a customer, a regulator, an insurer, a tender — and we'll tell you honestly which framework actually matters first.