Skip to content

RC.RP - Incident Recovery Plan Execution: Contribute case study test steps and artifacts #49

@CPAtoCybersecurity

Description

@CPAtoCybersecurity

Description:

Help us develop assessment materials for RC.RP - Incident Recovery Plan Execution, a RECOVER category.

About This Category

Incident Recovery Plan Execution covers:

  • Executing recovery plans post-incident
  • System restoration procedures
  • Data restoration and validation
  • Backup and disaster recovery testing
  • Recovery time objective (RTO) achievement
  • Post-recovery validation and verification

Alma Security Context: Alma Security operates a critical SaaS authentication platform serving customers. Recovery capabilities are essential to maintain customer trust and meet service level agreements. Business continuity and disaster recovery planning are integral to resilience.

What We Need

  1. Test Procedures - How to audit incident recovery:

    • Recovery plan completeness review
    • System restoration procedures
    • Backup restoration procedures and testing
    • RTO and RPO achievement verification
    • Recovery procedure documentation
    • Recovery team training and readiness
    • Post-recovery validation procedures
    • Recovery testing and tabletop exercises
  2. Assessment Artifacts - Supporting documentation:

    • Incident Recovery Plans
    • System Restoration Procedures and Runbooks
    • Backup Restoration Procedures
    • RTO/RPO Documentation and Achievement Tracking
    • Recovery Procedure Testing Results
    • Tabletop Exercise Records
    • Recovery Readiness Assessment Results
    • Interview notes with recovery/infrastructure teams
  3. Implementation Description - Alma's incident recovery program

Submission Guidelines

  • Reference CSF subcategories RC.RP-01 and RC.RP-02
  • Address SaaS platform recovery requirements
  • Include backup and system restoration procedures
  • Show RTO/RPO definitions and testing
  • Include recovery procedure testing results
  • Format as Markdown

Related Resources

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions