# NIST800 53 IR-4(3) — Continuity Of Operations

- Source: https://support.icompaas.com/support/solutions/articles/a_gen_nist80053_ir43_00bdf5abba-nist800-53-ir-43-continuity-of-operations
- Section: [Solutions](https://support.icompaas.com/support/solutions) › [NIST](https://support.icompaas.com/support/solutions/62000112528) › [Incident Response](https://support.icompaas.com/support/solutions/folders/f_gen_62000112528_incidentresponse)
- Last updated: 2026-05-30
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

NIST800 53 · Control IR-4(3) · Priority: critical · Component: Incident Response

### What this control covers

Organization-defined classes of incidents and taking specified actions to ensure continuity of mission and business functions. Actions include system degradation, shutdown, or alternative operations, using tools like incident management systems to maintain operations, aligning with IR-3, CP-2, and CP-4. This control supports the Incident Response Management System capability within the Incident Response family.

### Why it matters

How quickly and methodically you contain an incident determines the regulatory consequence — most fines are not for the breach itself but for the slow or absent response.

### How to implement

#### AWS

Wire **GuardDuty**, **Security Hub** and **Macie** findings into your ticketing/SIEM via EventBridge. Maintain documented playbooks for IAM-key compromise, EC2 instance compromise, S3 data exposure, and run **quarterly tabletop exercises**.

#### Azure

Use **Defender for Cloud** + **Microsoft Sentinel** with playbooks (Logic Apps) for automated containment — disable user, isolate VM (NSG), revoke session tokens. Keep an on-call rotation in Teams with PagerDuty.

#### GCP

**Org Policy Service** for guardrails and **Config Validator** in CI to pre-check Terraform plans against policy as code (Rego).

#### GitHub

Subscribe to **secret-scanning** alerts and **Dependabot** security advisories; require triage SLAs by severity. For exposed secrets, rotate at the cloud provider FIRST then revoke at GitHub — order matters.

### Evidence to collect

-   `ticketing_workflow` — See the iCompaas Evidence library for the canonical source for this evidence type.

Workflow metrics (ServiceNow, Jira) show approvals and remediation. Focus: Continuity Of Operations.

### Quick checklist

-   Response — Management / Actions
-   Shutdown — Management / Actions
-   System — Management / Actions
-   Control — Management / Actions
-   Alternative — Management / Actions
-   Change — Management / Actions

### Related articles on this site

-   [Ensure Lambda functions invoke API operations are being recorded by CloudTrail](https://support.icompaas.com/support/solutions/articles/62000127055-ensure-lambda-functions-invoke-api-operations-are-being-recorded-by-cloudtrail)
-   [Ensure Lambda functions invoke API operations are being recorded by CloudTrail](https://support.icompaas.com/support/solutions/articles/62000129489-ensure-lambda-functions-invoke-api-operations-are-being-recorded-by-cloudtrail)
-   [NIST 800-171 3.3.2 Ensure that the actions of individual system users can be uniquely traced to those users, so they can be held accountable for their actions.](https://support.icompaas.com/support/solutions/articles/62000229272-nist-800-171-3-3-2-ensure-that-the-actions-of-individual-system-users-can-be-uniquely-traced-to-those)
-   [NIST 800-171 3.11.1 Periodically assess the risk to organizational operations (including mission, functions, image, or reputation), organizational assets, and individuals, resulting from the operation of organizational systems and the assoc](https://support.icompaas.com/support/solutions/articles/62000229327-nist-800-171-3-11-1-periodically-assess-the-risk-to-organizational-operations-including-mission-fun)

## Related compliance guidance

- [NIST SP 800-53 Rev. 5: a practical implementation guide for cloud teams](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5): How the 800-53 catalogue, baselines and the Risk Management Framework fit together, and which controls take the most work in the cloud.
- [NIST SP 800-171 and CMMC: a practical guide to protecting CUI in the cloud](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3): If the driver is a DoD or federal contract handling CUI, 800-171 (and CMMC) is the scope you actually need.