Skip to main content
Frameworks & Standards

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.

Frameworks & standardsFramework library
Compliance Frameworks

Governance, Certification & Attestation

What each framework requires, who asks for it, and how long it typically takes.

International standards

International

ISO/IEC 27001:2022

Information security management system (ISMS) certification

Read the guide
International

PCI DSS v4.0

Mandatory standard for anyone storing, processing, or transmitting card data

Read the guide
International

ISO/IEC 42001:2023

The first certifiable AI management system (AIMS) standard

Read the guide
International

ISO/IEC 27701

Privacy Information Management System (PIMS) certification

Read the guide
International

ISO 22301

Business continuity management system certification

Read the guide
International

CIS Critical Security Controls v8.1

Prioritised safeguards organised into Implementation Groups 1–3

Read the guide
International

ISA/IEC 62443

Security standards for industrial automation, SCADA and OT

Read the guide
International

TISAX

Automotive-industry information security assessment (VDA ISA)

Read the guide
International

ISO/IEC 27017 & 27018

Cloud security and cloud privacy codes of practice

Read the guide
International

SANS Incident Response Framework

Six-step PICERL incident-handling model, with NIST SP 800-61

Read the guide
International

ISO/IEC 27002:2022

Implementation guidance for the 93 information security controls

Read the guide
International

ISO/IEC 27005:2022

Information security risk management guidance for an ISMS

Read the guide
International

COBIT 2019

ISACA framework for governance and management of enterprise IT and security

Read the guide
International

CSA Cloud Controls Matrix & STAR

Cloud security control framework and the STAR assurance registry

Read the guide
International

ISO/IEC 23894:2023

Guidance on risk management for artificial intelligence

Read the guide
Testing Methodologies

How Security Testing Actually Gets Structured

The methodologies behind every penetration test, red team engagement, and AI application assessment we run.

FAQs

Common 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.

Let's Talk

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.

No commitment requiredResponse within 2 working daysConfidential brief handling