Cybersecurity (cross-sector)
Cybersecurity obligations that extend across every industry.
Overview
Cybersecurity compliance is driven by sector regulation, frameworks and contracts. Primary concerns include data protection, incident response, business continuity, vendor risk management and secure development.
Typical authorities and frameworks: NIST CSF, NIST 800 series, CIS Controls, ISO 27001, PCI DSS, SOC 2.
Authorities in this glossary active in it include NIST and CIS.
Check the official sources below for legal scope, applicable dates and exceptions. This entry is an explanatory reference, not legal advice.
Why it matters
Regulators increasingly look at activities and outcomes in this space, so obligations follow the business model rather than the label.
Who it affects
Organisations operating in cybersecurity (cross-sector), and the vendors who serve them.
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 Cybersecurity (cross-sector). Select one to open it.
What to do about it
- 1List the activities you actually perform.
- 2Identify the authorities and licences those activities trigger.
- 3Scope your obligation library to the sector and its activities.
- 4Set up controls and evidence for the highest-risk obligations first.
From requirement to evidence.
Tag your organisation with this industry and Regulation Layer scopes the obligation library to it.
Request early access →