Cyber Resilience Control Mapper.

Required input fields.

• Critical process (required)
• Scenario (required): Ransomware, Cloud or identity outage, Data corruption, Critical supplier disruption, ...
• RTO pressure (required): Days, Hours, Minutes
• RPO pressure (required): Day-level, Hours, Near-zero
• Backup/recovery state (required): Weak or unknown, Partial, Strong and evidenced
• Telemetry coverage (required): Weak or unknown, Partial, Strong and evidenced
• Tabletop/test state (required): Weak or unknown, Partial, Strong and evidenced

Data handling: this interface uses the L2ET protected same-origin instrument engine. Do not enter confidential, regulated, privileged, incident, medical or sensitive operational data.

Evidence Matrix logic.

Combines service criticality, recovery objectives, backup maturity, telemetry and testing state into a resilience gap map.

Source families

Assumptions

• Recovery feasibility depends on real exercises.
• RTO/RPO must be validated with business owners.
• Dependencies may be incomplete.

Cyber resilience control map.

The generated artifact includes findings, assumptions, limitations, recommended next actions and exportable structured output.

Export options

Example input and output.

Example input

Critical identity service with hour-level RTO/RPO, partial backup evidence and weak tabletop history.

Example output

Outputs missing telemetry, recovery validation plan, test cadence and residual-risk summary.