cyber-resilience-engineer

Design RTO/RPO architectures and immutable backup patterns for critical services.

7|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/daemon-blockint-tech/Agentic-Enteprises-Skill --skill cyber-resilience-engineer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cyber-resilience-engineer
Source: https://github.com/daemon-blockint-tech/Agentic-Enteprises-Skill/tree/main/cyber-resilience-engineer
Command: npx skills add https://github.com/daemon-blockint-tech/Agentic-Enteprises-Skill --skill cyber-resilience-engineer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Designs and operates cyber resilience capabilities—RTO/RPO architecture, backup/restore and immutable backup patterns, dependency mapping for critical services, crisis playbooks for ransomware, destructive malware, and cloud control-plane loss, chaos and failure injection for security-relevant failures, resilience testing with evidence, and alignment with NIST CSF Recover and business continuity. Use when engineering recovery objectives and tiers, designing backup immutability and restore validation, running resilience or chaos tests, mapping attack-scenario playbooks, reporting resilience metrics, or sustaining continuity during active attacks—not enterprise BCM program ownership alone (bcm-disaster-recovery-specialist), live incident command (incident-responder), SRE performance and toil only (site-reliability-engineer), backup operator runbooks without architecture (cloud-system-administrator), GRC audit prep only (compliance-specialist), or CISO board strategy (chief-information-security-officer).

Core Features & Use Cases

  • Define RTO/RPO architecture and tiering for critical services
  • Design backup, restore, and immutability patterns with validation
  • Create attack-scenario playbooks and resilience tests (game days, drills)
  • Generate resilience metrics and governance artifacts
  • Use Case: Map dependencies and document MVC targets to support audits and charters

Quick Start

Describe your critical services and current RTO/RPO targets, and I will draft a resilience plan and actionable playbooks.

Frequently Asked Questions about cyber-resilience-engineer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design RTO and RPO architecture for critical services?

Design RTO and RPO architecture by mapping critical service dependencies, tiering recovery objectives, and defining validation criteria for restore targets to ensure rapid recovery during active attacks.

What is backup immutability and how does it prevent ransomware recovery failure?

Backup immutability prevents ransomware recovery failure by locking backup data from unauthorized modification or deletion, ensuring clean restore points exist for recovery playbooks during destructive malware incidents.

How do I create a recovery playbook for cloud control-plane loss?

Create a recovery playbook for cloud control-plane loss by mapping attack scenarios, defining crisis response steps, and integrating chaos testing to validate failover and restoration procedures for critical services.

Can I use chaos testing to validate cyber resilience for security-relevant failures?

Use chaos testing to validate cyber resilience by injecting security-relevant failures, running game day drills, and generating test plans with evidence to satisfy NIST CSF Recover and business continuity requirements.

What is the best way to generate resilience metrics and governance artifacts for audits?

Generate resilience metrics and governance artifacts for audits by documenting MVC targets, mapping dependencies, and producing evidence from resilience tests to satisfy compliance and business continuity reporting requirements.

Does this approach handle ransomware playbooks differently than general disaster recovery?

Ransomware playbooks differ from general disaster recovery by focusing on backup immutability, attack-scenario mapping, and destructive malware response, rather than enterprise BCM program ownership or live incident command operations.