Skip to content

RS.CO - Incident Response Reporting and Communication: Contribute case study test steps and artifacts #48

@CPAtoCybersecurity

Description

@CPAtoCybersecurity

Description:

Help us develop assessment materials for RS.CO - Incident Response Reporting and Communication, a RESPOND category.

About This Category

Incident Response Reporting and Communication covers:

  • Internal incident reporting and escalation
  • External stakeholder notification (customers, regulators, law enforcement)
  • Communication during incidents
  • Status updates and progress reporting
  • Regulatory and legal coordination
  • Post-incident communications

Alma Security Context: Alma Security experienced a 2024 security incident that damaged customer trust. The organization's strategy includes "Leverage PR to share as much of our progress as possible with the public to rebuild trust." Customer trust score is a key KPI (target 90%+ by Jan 2027).

What We Need

  1. Test Procedures - Assessment steps for incident communication:

    • Internal notification procedures
    • External notification procedures
    • Customer communication plans
    • Regulatory notification requirements
    • Legal and compliance coordination
    • Status reporting processes
    • Communication templates and procedures
    • Post-incident transparency reporting
  2. Assessment Artifacts - Supporting documentation:

    • Incident Communication Plan
    • Notification Procedures and Contact Lists
    • Customer Notification Templates
    • Regulatory Notification Procedures
    • Executive Status Report Examples
    • Public Communication Examples
    • Transparency Reporting Examples
    • Interview notes with communications/legal teams
  3. Implementation Description - Alma's incident communication program

Submission Guidelines

  • Reference CSF subcategories RS.CO-01 through RS.CO-03
  • Address 2024 incident and customer trust recovery
  • Include internal and external communication procedures
  • Show transparency and customer communication
  • Address regulatory notification requirements
  • 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