Critical or important functions
Register critical functions with MTPD, RTO, RPO and an owner, linked to systems, assets, suppliers and controls.
Framework-specific surfaces
Critical functions, ICT incidents, resilience tests and ICT suppliers stay connected to the same controls and evidence used across the rest of your compliance scope.
Register critical functions with MTPD, RTO, RPO and an owner, linked to systems, assets, suppliers and controls.
Record operational incidents with a DORA profile, status and notification stage: initial, intermediate, final.
Plan and run vulnerability tests, disaster recovery, backup/restore, penetration tests and tabletop scenarios.
Track whether a supplier provides ICT services, supports a critical function, holds audit rights, has a documented exit plan and where data is located.
Define scope, owner and links to systems, assets and suppliers.
Check critical services, audit rights, exit plan and data location.
From vulnerability testing to tabletop scenarios.
Track status, cause and notification stage, linked to the available evidence.
Modules: Resilience and ICT incidents, Risk register, Compliance inventory
Frameworks: DORA
AuditReady supports compliance work; it does not replace the customer’s assessments, obligations, or decisions.
AuditReady separates exercises from operational incidents: both generate learning, findings and evidence, but they remain two separate registers.
ExploreAssess likelihood and impact before and after controls, assign a treatment and bring the rationale and available evidence into review.
ExploreFrom entity profiling to board attestations, from policies to assets: AuditReady connects the elements that define the scope you need to govern.
ExploreNot yet: today AuditReady covers critical functions, ICT incidents, resilience tests and ICT suppliers; export in the RoI format is not available.
Yes, they remain two separate registers: real incidents and tabletop exercises.
Yes, you can link ICT suppliers to the critical or important functions they support.