Standards body
An organisation that publishes technical or professional standards but generally has no direct power to enforce them.
Overview
Standards bodies such as NIST, ISO, the Center for Internet Security, CSA Group, the Basel Committee, the PCI Security Standards Council, FASB and the IASB write frameworks that define good practice.
Their standards frequently become de facto requirements through regulation that references them, contracts that require them, audits that test against them, or supervisory expectations that assume them.
It connects most directly to Industry standard, National Institute of Standards and Technology, International Organization for Standardization, Basel Committee on Banking Supervision and PCI Security Standards Council.
Check the official sources below for legal scope, applicable dates and exceptions. This entry is an explanatory reference, not legal advice.
Why it matters
A standard you never agreed to can still bind you once a regulator cites it or a customer contract requires it.
Who it affects
Technology, financial services, payments and any organisation that is audited or certified.
Where it sits
Ten linked steps connect where you operate to the proof that you complied.
- 01Jurisdiction
- 02Industry
- 03Activity
- 04Authority
- 05Regulation
- 06Requirement
- 07Guidance
- 08Control
- 09Evidence
- 10Enforcement
Connections
The terms most closely tied to Standards body. Select one to open it.
What to do about it
- 1List every body of this type with a say over you.
- 2Record the powers each one holds.
- 3Prioritise obligations by the consequences behind them.
From requirement to evidence.
Regulation Layer’s standards crosswalk links each standard to the regulations and contracts that reference it, so one tested control can satisfy both.
Request early access →