DORA
Digital Operational Resilience Act
Live structured obligations, operational impact and attributable review for EU financial entities.
European regulatory libraryOne operating model.
One operating model.
A growing regulatory library.
Start with the regulation that matters today. Every new structure inherits the same source traceability, human review and connected GRC model.
- Live
- 2
- In development
- 0
- Coming soon
- 4
6 regulations shown
Live means available in the product today. In development identifies actively structured coverage. Coming soon is directional and is not presented as available functionality.
GDPR
General Data Protection Regulation
A privacy operating model connecting processing, controls, incidents, evidence and accountable decisions.
NIS2
Network and Information Security Directive
Planned regulatory-library coverage for cyber-risk governance and incident readiness.
EU AI Act
European Union Artificial Intelligence Act
Planned coverage for system classification, governance, oversight and evidence.
MiCA
Markets in Crypto-Assets Regulation
Planned coverage for crypto-asset governance and operational obligations.
CSRD/CSDDD
Sustainability reporting and due diligence
Planned library coverage for sustainability and supply-chain due diligence.
Shared regulatory operating model
Different laws. The same accountable chain.
1Official source2Structured provision3Obligation4Applicability5Impact6Human decision7Evidence
Choose coverage with confidence
Know what is live before you plan around it.
The library separates released, in-development and planned coverage. Buyers can evaluate the operating depth available now without treating a roadmap label as implemented functionality.
Authoritative source
Each structure begins with an identifiable official text and version.
Clear status
Live, in-development and coming-soon labels set an explicit expectation.
Operational depth
Published coverage connects requirements to ownership, controls and evidence.
Human accountability
Applicability and compliance conclusions remain attributable decisions.
A focused working session
Start with the regulation that creates the most work.
Bring one regulatory requirement and the register, evidence request or review process used to manage it. We will show the operating path and identify where NeoGRC would need to fit your governance model.
Discuss your regulatory operating model- 01Confirm the scope
Regulations, entities, teams and current source material.
- 02Trace one requirement
Applicability, ownership, controls, evidence and decisions.
- 03Test an exception
A missing record, overdue action or disputed conclusion.
- 04Define the next step
A realistic starting scope and evaluation criteria.
Questions buyers ask
The regulatory library, in practical terms.
Answers for teams deciding whether the available regulatory coverage fits their operating needs.
What is the NeoGRC regulatory library?
It is a collection of structured regulatory content designed to connect source requirements with applicability, ownership, controls, evidence and accountable decisions. The catalogue clearly identifies which regulation structures are live and which remain in development or planned.
Does a live label mean the regulation is operationally available?
Yes. Live identifies a published regulatory structure that can be explored in the product experience. In-development and coming-soon entries are labelled separately so buyers can distinguish current capability from roadmap intent.
Does NeoGRC determine whether a regulation applies to us?
No. NeoGRC can structure the applicability process, supporting rationale and approval history, but the legal and regulatory conclusion remains with your authorised advisers and accountable personnel.
Can one control support requirements from different regulations?
Yes. A shared control can be connected to multiple relevant requirements while each regulation retains its own source, applicability, assessment and decision context.
How is regulatory source traceability handled?
The operating model retains the source reference and version beside the structured provision and resulting obligation, allowing reviewers to move from an internal record back to the authoritative text.
What should we bring to a regulatory demo?
Bring one high-priority requirement, your current obligation or control register, and an example of evidence or remediation that is difficult to follow. The session can then test the model against your real process.
DORA proves the engine. It does not define its limit.
Discuss the regulations and operating model relevant to your organisation.