Here is a detailed Incident Response Policy, aligned with ISO/IEC 27001:2022 (Controls A.5.25–A.5.27) and SOC 2 (CC7.3, CC7.4):

1. Document Control

• Document Title: Incident Response Policy

• Document Identifier: POL-ALL-009

• Version Number: v1.0

• Approval Date: <23 June 2025>

• Effective Date: <23 June 2025>

• Review Date: <23 June 2026>

• Document Owner: <Chief Information Security Officer>

• Approved By: <Information Security Governance Committee>

2. Purpose

The purpose of this Incident Response Policy is to establish a structured and consistent approach for identifying, managing, and recovering from information security incidents affecting . The policy ensures that incidents are responded to efficiently, contain minimal damage, and are appropriately escalated, communicated, and documented to meet legal, operational, and contractual obligations.

This policy supports the requirements outlined in ISO/IEC 27001:2022 controls A.5.25 through A.5.27 and SOC 2 Trust Services Criteria CC7.3 and CC7.4. By implementing a repeatable incident response process, can reduce response times, minimize business disruption, preserve evidence, and learn from past incidents to strengthen its overall security posture.

3. Scope

This policy applies to all personnel, systems, networks, cloud platforms, applications, and third parties that support or handle 's data or services. It governs the full lifecycle of an incident, from detection to resolution and post-incident review.

Types of incidents covered include but are not limited to:

• Unauthorized access or system compromise

• Malware infections or ransomware attacks

• Data breaches or information leaks

• Denial-of-service (DoS) attacks

• Insider threats or sabotage

• Physical security breaches

• Policy violations or misconfigurations

4. Policy Statement

shall maintain a documented and tested incident response capability to:

1. Detect security events and analyze them to determine if they qualify as incidents.

2. Contain and mitigate the impact of confirmed incidents.

3. Eradicate the root cause and restore affected systems to a secure state.

4. Notify relevant internal stakeholders and, where required, external parties such as regulators, customers, or law enforcement.

5. Document all actions taken during incident handling.

6. Review and improve controls and procedures after each significant incident.

Incident response must be initiated promptly upon detection or suspicion of a security incident. Escalation paths and responsibilities must be clearly defined and tested.

5. Safeguards

implements the following controls to enable effective incident response: