Skip to content

SSZcreate/Pentab_server / .agents/skills/cybersecurity/skills/executing-nist-rmf-authorization-to-operate

executing-nist-rmf-authorization-to-operate

Verified

Drive a federal system through the NIST Risk Management Framework (SP 800-37 Rev 2) to an Authorization to Operate (ATO): Prepare, Categorize (FIPS 199), Select a control baseline (FIPS 200 / SP 800-53 Rev 5), Implement, Assess (SP 800-53A), Authorize, and Monitor continuously. Use when a system needs an ATO or a renewal, when working a FISMA/FedRAMP authorization package, when building or reviewing an SSP, SAR, or POA&M, when categorizing a system as Low/Moderate/High impact, when selecting or tailoring a control baseline, or when standing up continuous monitoring (ConMon) after authorization. Covers ATO, conditional ATO (cATO), and the artifacts assessors expect. Keywords: NIST RMF, 800-37, ATO, authorization to operate, FISMA, FedRAMP, SSP, SAR, POA&M, FIPS 199, FIPS 200, 800-53, 800-53A, control baseline, security categorization, continuous monitoring, authorizing official, system boundary, ongoing authorization.

FileKindSize
LICENSEother11.0 KB
SKILL.mdskill md8.6 KB
assets/template.mdmarkdown4.2 KB
references/standards.mdmarkdown4.6 KB
scripts/process.pyscript7.7 KB

assets/template.md

View on GitHub
# Authorization Package Summary (NIST RMF / SP 800-37 Rev 2) — Worked Example

> Filled example for a Moderate-impact federal web application seeking an initial ATO.
> Replace bracketed content for your own system.

## 1. System & Authorization Boundary
- **System name:** Citizen Services Portal (CSP)
- **System owner / ISSO / AO:** [SO name] / [ISSO name] / [AO name]
- **Description:** Public-facing web portal for benefit applications; React frontend, containerized API, managed Postgres, all in an authorized cloud (FedRAMP Moderate) tenant.
- **Boundary:** The application containers, API gateway, database, and CI/CD pipeline within the project's cloud account. **Inherited:** physical, environmental, and hypervisor controls from the FedRAMP-authorized platform (documented in the CRM).
- **Leveraged authorization:** Platform IaaS at FedRAMP Moderate.

## 2. FIPS 199 Categorization
*(generated by `scripts/process.py` from the information-type table; overall = high-water mark)*

| Objective | High-water mark |
|---|---|
| Confidentiality | Moderate |
| Integrity | Moderate |
| Availability | Moderate |
| **Overall system impact** | **Moderate** |

**Information types:** PII (C:Mod / I:Mod / A:Low), Eligibility records (C:Mod / I:Mod / A:Mod), Public content (C:Low / I:Mod / A:Mod).
**Selected SP 800-53B baseline:** Moderate. Privacy overlay applied (PII present).

## 3. Control Baseline & Tailoring
- **Baseline:** SP 800-53B Moderate + privacy controls (PT family).
- **Tailoring decisions:** PE family largely **inherited** from the platform (common controls). Organization-defined parameters set for AC-7 (lockout threshold = 5), AU-11 (log retention = 1 year), IA-5 (password/authenticator policy).
- **Allocation:** Common (inherited) — PE, parts of SC/CP; System-specific — AC, AU, SI, application-layer SC; Hybrid — IR, CM (platform + app split per CRM).

## 4. Control Implementation Status (from the SSP)
| Family | Implemented | Total | % |
|---|---|---|---|
| AC | 22 | 25 | 88% |
| AU | 14 | 16 | 88% |
| SC | 28 | 30 | 93% |
| SI | 12 | 14 | 86% |
| **Total** | **76** | **85** | **89%** |

*(Each implemented control carries an implementation statement in the SSP — not a bare "yes." Open items map to the POA&M below.)*

## 5. Assessment Results (SAR)
Independent assessment per SP 800-53A Rev 5 (examine / interview / test). Result: **3 controls "Other Than Satisfied"**, all with remediation plans. No Critical findings. Detailed evidence in the full SAR.

## 6. Plan of Action & Milestones (POA&M)
*(generated by `scripts/process.py`, sorted by severity)*

| ID | Control | Weakness | Severity | Status | Remediation | Owner | Milestone |
|---|---|---|---|---|---|---|---|
| F-001 | AC-7 | No account lockout on the portal login | High | Other Than Satisfied | Configure lockout after 5 failed attempts | App team | 2026-07-15 |
| F-002 | AU-6 | Audit logs not reviewed on a defined cadence | Moderate | Other Than Satisfied | Stand up weekly SIEM review + alerting | SOC | 2026-08-01 |
| F-003 | SI-2 | Two medium CVEs unpatched in a dependency | Moderate | Other Than Satisfied | Patch in next sprint; add Dependabot gate | App team | 2026-07-30 |

_Open High/Critical findings: 1 (F-001) — track to closure before/within ATO conditions._

## 7. Authorization Decision
- **Decision:** **ATO with conditions** (effectively a cATO posture).
- **Term:** 3 years, contingent on continuous monitoring and POA&M adherence.
- **Conditions:** Close F-001 (High) within 30 days of authorization; F-002 and F-003 per their milestones.
- **Residual-risk statement:** Residual risk is **Moderate and acceptable** given the compensating monitoring and the committed remediation timeline.
- **Authorizing Official:** [AO name], [date].

## 8. Continuous Monitoring (ConMon) Plan
- **Monitored continuously:** vulnerability scans (weekly), configuration drift (CM), POA&M status (monthly to the AO), control effectiveness sampling (quarterly).
- **Reporting cadence:** Monthly ConMon report; immediate notification of any High/Critical finding or significant change.
- **Reassessment triggers:** new external interface, change of categorization, major architecture change, or a significant incident.
- **Maturity goal:** Move from periodic re-ATO toward ongoing authorization as ConMon evidence stabilizes.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall