IT Compliance category

IT Governance, Risk and Quality Frameworks

How IT is directed, controlled, measured and audited, from boardroom governance to service management and quality. 12 entries, 7 with a full guide.

Governance frameworks answer a different question from security standards: is IT delivering value, managing risk and using resources well? Boards, auditors and large clients use them to judge whether an IT organisation is under control.

COBIT from ISACA sets governance and management objectives for enterprise IT. ITIL describes service management practices such as incident, change and service desk. ISO 9001 is the certifiable quality management standard many software and IT services firms hold for RFPs.

Two are legal duties in the US: Sarbanes-Oxley makes listed companies test the IT general controls behind financial reporting, and FISMA requires federal agencies and their contractors to run risk-based security programmes.

IT Governance & Risk Management standards and laws

ISO 9001

ISO 9001:2026 Quality management systems: Requirements

Certifiable standard Voluntary Global

ISO 9001 is the international standard for a quality management system (QMS). It asks you to understand customer and stakeholder requirements, plan processes and risks, control how you design and deliver products and services, measure customer satisfaction and keep improving. For software and IT services firms it formalises requirements management, design and development control, testing, change control and supplier management. The 2026 edition was published in September 2026.

Covers, who needs it and key requirements
What it covers
Context and interested parties, quality policy and objectives, risks and opportunities, competence and awareness, operational planning, requirements review, design and development, supplier control, release, nonconforming outputs, customer satisfaction, internal audit and improvement.
Who needs it
Software development companies, IT services and managed service providers, system integrators and any supplier asked for a quality certificate in RFPs or government tenders.
Why it matters
It is the most widely held management system certificate in the world and a common minimum requirement in public and enterprise procurement.
Applies in
Worldwide (international standard)
Key requirements
  • Determine context, interested parties and QMS scope
  • Quality policy, objectives and assigned responsibilities
  • Address risks and opportunities and plan changes
  • Control design and development, suppliers and service delivery
  • Monitor customer satisfaction, run internal audits and management reviews
  • Correct nonconformities and improve continually

NIST CSF 2.0

NIST Cybersecurity Framework (CSF) 2.0

Framework Voluntary US / global

The NIST Cybersecurity Framework 2.0 is a voluntary framework of cybersecurity outcomes organised into six functions: Govern, Identify, Protect, Detect, Respond and Recover. It does not prescribe specific controls; instead it gives a common language, organisational profiles (current and target) and tiers to describe how rigorous your practices are. Version 2.0, released in February 2024, added the Govern function and supply chain risk management, and is designed for organisations of any size or sector.

Covers, who needs it and key requirements
What it covers
Cybersecurity governance, risk strategy and supply chain risk (Govern), asset and risk identification (Identify), safeguards (Protect), monitoring (Detect), incident response (Respond) and recovery (Recover), with references to detailed controls such as SP 800-53, ISO 27001 and CIS Controls.
Who needs it
Any organisation that wants a structured cybersecurity programme, including IT companies reporting cyber risk to boards, clients, investors or insurers, and US federal contractors.
Why it matters
It is the most widely recognised way to describe cybersecurity maturity, maps to most other standards, and is free.
Applies in
United States origin; used worldwide
Key requirements
  • Govern (GV): context, risk strategy, roles, policy, oversight and cybersecurity supply chain risk management
  • Identify (ID): asset management, risk assessment and improvement
  • Protect (PR): identity and access, awareness and training, data security, platform security, resilience
  • Detect (DE): continuous monitoring and adverse event analysis
  • Respond (RS): incident management, analysis, reporting and mitigation
  • Recover (RC): recovery plan execution and communication

NIST SP 800-53

NIST Special Publication 800-53 Revision 5: Security and Privacy Controls for Information Systems and Organizations

Framework Mandatory if in scope US federal

NIST SP 800-53 Revision 5 is the US government's catalogue of security and privacy controls, organised into 20 families from Access Control to Supply Chain Risk Management. Federal agencies must select controls from it using the Low, Moderate or High baselines in SP 800-53B, and FedRAMP builds on it for cloud services. Private companies use it as the most detailed public control library. Release 5.2.0 in August 2025 strengthened software update and patching controls.

Covers, who needs it and key requirements
What it covers
Twenty control families: AC, AT, AU, CA, CM, CP, IA, IR, MA, MP, PE, PL, PM, PS, PT, RA, SA, SC, SI and SR, covering technical, operational, management, privacy and supply chain safeguards.
Who needs it
US federal agencies, federal contractors and cloud providers pursuing FedRAMP, plus organisations that want a detailed control catalogue for high-assurance systems.
Why it matters
It is the control foundation for FISMA, FedRAMP and many state and sector programmes, and the reference most other frameworks map to.
Applies in
United States (federal); used worldwide as a reference catalogue
Key requirements
  • Categorise the system (FIPS 199) and select a Low, Moderate or High baseline (SP 800-53B)
  • Tailor controls and document them in a System Security and Privacy Plan
  • Implement controls across the 20 families
  • Assess controls using SP 800-53A procedures
  • Obtain authorization (ATO) based on residual risk
  • Continuously monitor controls and update plans of action and milestones (POA&M)

COBIT

COBIT (Control Objectives for Information and Related Technologies) framework for the governance and management of enterprise IT

Framework Voluntary Global

COBIT is ISACA's framework for the governance and management of enterprise IT. It separates governance (evaluate, direct, monitor) from management (plan, build, run, monitor) and defines objectives such as managing risk, security, changes, suppliers and performance, with a capability scale and design factors to tailor the system. ISACA has announced COBIT 7 for launch in late October 2026; COBIT 2019, with its 40 objectives in five domains, is still the version most organisations have implemented.

Covers, who needs it and key requirements
What it covers
Governance objectives (EDM) and management objectives across Align, Plan and Organise (APO), Build, Acquire and Implement (BAI), Deliver, Service and Support (DSS) and Monitor, Evaluate and Assess (MEA), plus components such as processes, structures, information flows and skills.
Who needs it
Boards, CIOs and IT auditors in mid-sized and large organisations, banks and regulated entities, and IT service providers supporting their governance or audit.
Why it matters
It links IT to business goals and gives auditors and regulators a recognised yardstick for IT control.
Applies in
Worldwide
Key requirements
  • Understand enterprise strategy and goals and map them to IT-related goals (goals cascade)
  • Use design factors to tailor the governance system
  • Define roles and governance structures (board, IT steering committee)
  • Implement prioritised objectives such as managed risk, security, change and service requests
  • Measure process capability and performance
  • Monitor, evaluate and report on governance to the board

ITIL

ITIL (formerly IT Infrastructure Library) IT and digital service management framework

Framework Voluntary Global

ITIL is the most widely used framework for IT service management. ITIL 4 describes a service value system and 34 management practices, such as incident management, change enablement, problem management, service desk and service level management, that help IT teams deliver reliable services. PeopleCert began rolling out ITIL Version 5 in 2026, with ITIL 4 running alongside it. ITIL itself is not certifiable for organisations; ISO/IEC 20000-1 is the matching certifiable standard.

Covers, who needs it and key requirements
What it covers
Service management principles, the service value chain, governance, continual improvement and practices for incident, problem, change, service request, service desk, service level, configuration, release, deployment, monitoring and supplier management.
Who needs it
Managed service providers, IT outsourcing and support companies, internal IT departments and SaaS operations teams.
Why it matters
Clients use ITIL language in contracts and SLAs, and consistent practices reduce outages and improve customer satisfaction.
Applies in
Worldwide
Key requirements
  • Adopt the guiding principles and define value streams for your services
  • Service desk and incident management with priorities and SLAs
  • Change enablement with risk-based approvals
  • Problem management to remove root causes
  • Service level management and reporting to customers
  • Continual improvement using measurable objectives

FISMA

Federal Information Security Modernization Act of 2014 (originally the Federal Information Security Management Act of 2002)

Law Mandatory if in scope US federal

FISMA is the US federal law that requires every federal agency to run an agency-wide information security programme, including for systems operated by contractors. Agencies categorise systems, apply NIST SP 800-53 controls under the Risk Management Framework, authorize systems to operate, continuously monitor them and report annually to OMB and Congress. IT companies meet FISMA through contract clauses when they build, host or operate systems for federal agencies.

Covers, who needs it and key requirements
What it covers
Federal information and information systems, including those run by contractors: risk-based security programmes, system categorisation, security controls, authorization, continuous monitoring, incident reporting to CISA and annual reporting.
Who needs it
US federal agencies and the IT contractors, integrators and cloud providers that operate systems or process information on their behalf.
Why it matters
Federal contracts flow FISMA duties down to vendors; without an ATO a system cannot go live.
Applies in
United States (federal)
Key requirements
  • Inventory information systems and categorise them (FIPS 199)
  • Select and implement NIST SP 800-53 controls (FIPS 200 minimum requirements)
  • Write a system security plan and assess controls
  • Obtain an Authorization to Operate from the authorizing official
  • Continuously monitor and report incidents to CISA
  • Annual independent evaluation and FISMA reporting to OMB

SOX

Sarbanes-Oxley Act of 2002 (IT general controls under Sections 302 and 404)

Law Mandatory if in scope US-listed companies

The Sarbanes-Oxley Act requires US-listed companies to certify their financial reports and maintain effective internal control over financial reporting (ICFR). Section 302 makes the CEO and CFO certify each report, and Section 404 requires an annual management assessment of ICFR, with auditor attestation for larger filers. For IT, this means tested IT general controls (ITGCs) over access, change management and operations for every system that affects the financial statements.

Covers, who needs it and key requirements
What it covers
Internal control over financial reporting, including IT general controls over financial systems (ERP, billing, payroll, data warehouses), application controls, access, change management, computer operations and outsourced service providers.
Who needs it
SEC-registered public companies and companies preparing for a US IPO, plus the SaaS, ERP, payroll and managed IT providers whose systems support their financial reporting.
Why it matters
IT control failures can become material weaknesses that must be disclosed to investors, and listed clients will ask vendors for SOC 1 reports and evidence.
Applies in
United States; applies to SEC-registered companies worldwide
Key requirements
  • Scope financially significant applications and supporting infrastructure
  • Logical access controls: provisioning, periodic reviews, privileged access, segregation of duties
  • Change management: approval, testing and segregation for changes to in-scope systems
  • Computer operations: job scheduling, backups, incident management
  • Obtain and review SOC 1 reports for outsourced services, including complementary user entity controls
  • Document, test and remediate controls each year for management's assessment and the auditor

ISO 20000-1

ISO/IEC 20000-1:2018 Information technology: Service management: Part 1: Service management system requirements

Certifiable standard Voluntary Global

ISO/IEC 20000-1 is the certifiable international standard for an IT service management system. It requires a planned and governed approach to designing, delivering and improving services, including service level management, incident and request handling, problem management, change and release management, capacity, availability and continuity, supplier management and reporting. It is the organisational certificate that matches ITIL practices, and is often required in managed services and outsourcing tenders.

Covers, who needs it and key requirements
What it covers
Service management system context, leadership, planning, service portfolio, relationship and agreement management, supply and demand, service design and transition, resolution and fulfilment, assurance and improvement.
Who needs it
Managed service providers, IT outsourcing companies, data centres and internal IT departments.
Why it matters
It proves mature, repeatable service delivery to clients and is a common tender requirement for managed IT services.
Applies in
Worldwide (international standard)
Key requirements
  • Define the SMS scope and service management policy
  • Service level management and catalogue of services
  • Incident, request and problem management
  • Change, release and deployment management
  • Capacity, availability, continuity and supplier management

SOC 1

SOC 1 report on a service organisation's controls relevant to user entities' internal control over financial reporting (SSAE 18, AT-C 320)

Attestation report Voluntary US / global

A SOC 1 report is an independent CPA examination of a service organisation's controls that are relevant to its customers' financial reporting. Payroll, billing, payments, ERP hosting and fund administration providers commonly need one so that their public-company clients and their auditors can rely on the service for SOX. Like SOC 2 it comes as Type I (design) or Type II (operating effectiveness over a period), and it lists complementary controls the customer must operate.

Covers, who needs it and key requirements
What it covers
Control objectives over transaction processing and supporting IT general controls (access, change management, operations) at a service organisation.
Who needs it
SaaS and outsourcing providers whose services affect clients' financial statements, such as payroll, billing, payments and ERP hosting.
Why it matters
Listed clients and their auditors need it to rely on your service for SOX and financial audits.
Applies in
United States origin; used worldwide (ISAE 3402 is the international equivalent)
Key requirements
  • Define control objectives relevant to customers' financial reporting
  • Document the system and complementary user entity controls
  • Operate ITGCs over access, change and operations
  • Undergo a Type I or Type II examination by a CPA firm

ISO 31000

ISO 31000:2018 Risk management: Guidelines

Framework Voluntary Global

ISO 31000 provides principles, a framework and a process for managing any kind of risk. It is guidance, not a certifiable requirements standard. Many IT risk programmes use it as the overall method behind risk registers, risk appetite statements and treatment plans, while ISO 27005 applies it to information security risk.

Covers, who needs it and key requirements
What it covers
Risk management principles, framework (leadership, integration, design, implementation, evaluation, improvement) and process (identify, analyse, evaluate, treat, monitor, communicate).
Who needs it
Boards, risk and IT leaders who need a common risk method across the business.
Why it matters
It gives a consistent risk language that other standards plug into.
Applies in
Worldwide (international standard)
Key requirements
  • Integrate risk management into governance
  • Define risk criteria and appetite
  • Identify, analyse and evaluate risks
  • Treat, monitor and report risks

ISO/IEC 38500

ISO/IEC 38500:2024 Information technology: Governance of IT for the organization

Framework Voluntary Global

ISO/IEC 38500 gives boards and governing bodies principles for the effective, efficient and acceptable use of IT in their organisations. The 2024 edition sets out how governing bodies should evaluate, direct and monitor the use of IT and data. It is a short, high-level guidance standard that frameworks such as COBIT build on.

Covers, who needs it and key requirements
What it covers
Governance principles and the evaluate, direct and monitor model for IT and data use.
Who needs it
Boards, directors and executives responsible for IT governance.
Why it matters
It defines what good IT governance looks like at board level.
Applies in
Worldwide (international standard)
Key requirements
  • Assign responsibility for IT at board level
  • Evaluate current and future IT use
  • Direct strategy and policies
  • Monitor performance and conformance

SEC Cybersecurity Disclosure Rules

US SEC Cybersecurity Risk Management, Strategy, Governance, and Incident Disclosure rules (2023)

Regulation Mandatory if in scope US-listed companies

Since December 2023, US-listed companies must disclose material cybersecurity incidents on Form 8-K Item 1.05 within four business days of determining materiality, and describe their cybersecurity risk management, strategy and governance annually under Regulation S-K Item 106. Foreign private issuers make equivalent disclosures on Forms 6-K and 20-F. IT vendors are affected because incidents at third parties can trigger client disclosures.

Covers, who needs it and key requirements
What it covers
Material incident disclosure, annual description of risk management processes, board oversight and management's role in cybersecurity.
Who needs it
SEC registrants and companies preparing to list, and their critical IT and SaaS vendors.
Why it matters
Listed clients need fast, accurate incident information from vendors to meet the four-day clock.
Applies in
United States (SEC registrants, including foreign private issuers via Forms 6-K and 20-F)
Key requirements
  • Process to assess materiality of incidents without unreasonable delay
  • File Form 8-K Item 1.05 within four business days of a materiality determination
  • Annual Item 106 disclosure of risk management, strategy and governance
  • Third-party risk processes that surface vendor incidents quickly

Need help with it governance & risk management compliance?

Get a gap assessment from vetted compliance and cybersecurity firms, or ask us a question.

List your IT company for free

Create a profile in minutes, get reviewed by our editors and start receiving enquiries from clients looking for your skills.