# NIST SP 800-53 Rev. 5 CA-8(2) — Red Team Exercises

- Source: https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ca-8-2-red-team-exercises
- Section: [Compliance](https://support.icompaas.com/compliance) › [NIST SP 800-53 Rev. 5 Controls](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5) › CA — Assessment, Authorization, and Monitoring
- Last updated: 2026-06-05
- Publisher: iCompaas, Inc. (https://www.icompaas.com)

**NIST SP 800-53 Rev. 5**·Control `CA-8(2)`·high·Component: **Assessment, Authorization, and Monitoring**

## What this control requires

> Conducts red team exercises to simulate adversary attempts to compromise systems, assessing security and privacy posture with defined rules of engagement. This control supports the Red Team Exercise System capability within the Assessment, Authorization, and Monitoring family.
> 
> — NIST SP 800-53 Rev. 5, Control CA-8(2)

### In plain English

Conducts red team exercises to simulate adversary attempts to compromise systems, assessing security and privacy posture with defined rules of engagement. In practice, this means you can prove you security management-level controls on a defined cadence.

## Why it matters

SP 800-53 is the catalogue every U.S. federal authorisation (FedRAMP, FISMA, CMMC) and most regulated industries point at. A missing control surfaces as a Plan of Action & Milestones (POA&M) item that an Authorizing Official must approve before the Authority To Operate is granted or renewed.

This control is rated **high**. Auditors expect a named owner, a remediation SLA, and a tooling artefact that evidences continuous operation.

## What an auditor looks for

A 3PAO (FedRAMP) or Independent Assessor (NIST RMF) tests against NIST SP 800-53A assessment procedures. For each control they expect a documented implementation that addresses every assessment objective (Examine, Interview, Test) and an implementation summary in the System Security Plan.

Within **Assessment, Authorization, and Monitoring**, the assessor will trace your implementation back to the catalogue reference (Control CA-8(2)) and look for objective evidence on the latest two assessment cycles.

## How to implement

#### Vulnerability Management

**Scanners.** Pair an unauthenticated scanner (Nessus / Qualys / Tenable.io) for external surface with an authenticated agent for OS/library CVEs on every host.

**SLA.** Document remediation SLAs by CVSS / EPSS: critical 7 days, high 30 days, medium 90 days; report monthly trend to leadership.

**Containers.** Scan images in CI (Trivy / Grype / Snyk Container) AND at runtime; block deploys on critical findings without exception.

#### Cloud Posture

**CSPM.** Run Wiz / Prisma / Defender for Cloud / Security Command Center over every account; auto-ticket findings above your accepted-risk threshold.

#### Code Review Testing

**Pipeline.** Require at least one human reviewer plus passing CI (lint, type, unit, security scan) before merge — protected branches enforce this.

### Operational checklist

-   **Security.** Document the trigger, the owner and the cadence.
-   **Review.** Document the trigger, the owner and the cadence.
-   **System.** Document the trigger, the owner and the cadence.
-   **Control.** Document the trigger, the owner and the cadence.
-   **Authorization.** Document the trigger, the owner and the cadence.
-   **Scope:** management, authorization, privacy, system, exercises, assessment, team exercises, review.

## Evidence to collect

-   **Vapt Scan.** `vapt_scan` evidence

Pen-test and vulnerability scan reports substantiate attack-surface coverage. Focus: Red Team Exercises.

## Common pitfalls

-   Scans that hit only the perimeter; missing authenticated scans of OS, runtime libs and base images so most CVEs are invisible.
-   Treating CSPM findings as a backlog instead of a hot queue: findings older than the policy SLA accumulate until the auditor asks why.

## How it maps to other frameworks

Computed from shared tags, control component and key-operation subjects — handy when you are reconciling controls across an audit.

-   [**NIST SP 800-171 Rev. 3 3.11.2** — Vulnerability Monitoring and Scanning](https://support.icompaas.com/compliance/nist-sp-800-171-rev-3/3-11-2-vulnerability-monitoring-and-scanning)

## Related controls in NIST SP 800-53 Rev. 5

-   [**Control CA-8(1)** — Independent Penetration Testing Agent Or Team](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ca-8-1-independent-penetration-testing-agent-or-team)
-   [**Control CA-8** — Penetration Testing](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ca-8-penetration-testing)
-   [**Control CA-9(1)** — Compliance Checks](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ca-9-1-compliance-checks)
-   [**Control RA-5(9)** — Penetration Testing And Analyses](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ra-5-9-penetration-testing-and-analyses)
-   [**Control CA-8(3)** — Facility Penetration Testing](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ca-8-3-facility-penetration-testing)
-   [**Control RA-5(3)** — Breadth And Depth Of Coverage](https://support.icompaas.com/compliance/nist-sp-800-53-rev-5/ra-5-3-breadth-and-depth-of-coverage)

## References

-   [NIST Computer Security Resource Center — NIST SP 800-53 Rev. 5](https://csrc.nist.gov/Projects/risk-management/sp800-53-controls)
-   Catalogue identifier: `Control CA-8(2)`

Topics: governance riskvulnerability managementcloud posturecode review testingprivacy management

## 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): Start with the full NIST SP 800-53 implementation guide — scope, roadmap, evidence and how the assessment runs.
- [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 your obligation is protecting CUI in your own systems for a federal or defence contract, this derived subset — not the full catalogue — is the requirement.
- [SOC 2 compliance: a practical implementation guide for cloud-native SaaS teams](https://support.icompaas.com/compliance/soc-2-trust-services-criteria): Most commercial SaaS already hold a SOC 2 Type 2, and FedRAMP 20x Class A is designed for providers that have one.