sushegaad/claude-skills-governance-risk-and-compliance/fedramp

Claude Code and agent skill by sushegaad/claude-skills-governance-risk-and-compliance

Trust tier 2
  • community
LLM review pending
Source check pending

Checking that the SKILL.md file is still in the repository.

Expert guidance for FedRAMP certification and compliance under CR26 (FedRAMP Consolidated Rules for 2026). Use this skill whenever a user asks about FedRAMP authorization, ATO (Authority to Operate), cloud security for federal government, NIST SP 800-53 controls, CSP compliance, or any of the core FedRAMP document types: SSP, SAP, SAR, POA&M, CIS/CRM workbooks. Also trigger for questions about FedRAMP Certification Classes (A, B, C, D — new baseline labels: A = pilot/transitional, B = LI-SaaS/L…

Install

npx vskill@latest install sushegaad/claude-skills-governance-risk-and-compliance/fedramp

SKILL.md

The same SKILL.md was published earlier as sushegaad/claude-skills-governance-risk-and-compliance/fedramp.

FedRAMP Certification Skill

Last verified: 2026-11-15

A comprehensive guide for helping users navigate FedRAMP authorization - from initial readiness through ATO and ongoing continuous monitoring.

Quick Reference: What Does the User Need?

Identify the user's goal and jump to the appropriate section:

User GoalGo To
"Are we ready for FedRAMP?" / gap assessment→ Readiness & Gap Assessment
Writing SSP, POA&M, SAR, SAP, or other docs→ ATO Documentation
"Which controls apply to us?" / control mapping→ NIST 800-53 Control Mapping
Cloud architecture / AWS/Azure/GCP config→ Architecture Guidance
Already authorized, ongoing compliance→ Continuous Monitoring

Current FedRAMP State (as of August 2026 - CR26)

⚠️ CR26 (FedRAMP Consolidated Rules for 2026): FedRAMP has restructured its authorization framework. FIPS 199-based baseline labels (Low/Moderate/High/LI-SaaS) are replaced with Certification Classes A–D (per notice NTC-0004; CR26 rules valid through December 31, 2028). Class labels change the names of the baselines, not their requirements. CSPs already authorized under the old labels retain their authorization through a transition period in which old and new labels are linked.
  • Baseline: NIST SP 800-53 Rev 5 (fully in effect)
  • Control counts (Rev 5): Low = 156, Moderate = 323, High = 410 (CR26 class-based counts being published by PMO)
  • CR26 Certification Classes (official mapping, NTC-0004): A = new pilot/transitional baseline (entry via external frameworks such as SOC 2 Type II through Program Certification; once a federal customer uses the service, holders have 12 months to begin transition to Class B or higher), B = current LI-SaaS + Low baselines, C = current Moderate baseline (majority of federal deployments, incl. CUI), D = current High baseline.
  • FedRAMP 20x: Now the primary authorization pathway - continuous authorization built on Key Security Indicators (KSIs), machine-readable evidence, modular API-driven submissions, and automated validation. Traditional SSP/SAP/SAR templates remain for legacy paths.
  • CR26 status: finalized June 25, 2026; optional early adoption since July 4, 2026; mandatory January 1, 2027.
  • Legacy FedRAMP Ready: the Ready designation was retired/relabeled Legacy FedRAMP Ready on July 28, 2026 - no new submissions. A Ready Conversion pathway opened August 10, 2026 (NTC-0008); confirm current conversion deadlines with the PMO, as exact cutoff dates have not been published on fedramp.gov.
  • Certification Class pipelines: Class A open since August 3, 2026; Classes B/C open August 31, 2026; Class D pilot expected late 2026 with a formal option in early 2027.
  • Rev5 wind-down: new Rev5 applications are not accepted after June 11, 2027; the CR26 ruleset is valid through December 31, 2028, with Rev5-to-20x transition paths due by end of FY27.
  • JAB P-ATO: Fully suspended; FedRAMP PMO is the sole authorization body.
  • Machine-readable packages (RFC-0024, finalized by NTC-0009), Rev5 process only, not FedRAMP 20x: comprehensive machine-readable certification data is required only for Rev5 Class D (High): new submissions from May 1, 2027, existing Class D services at their next annual assessment after November 1, 2027. Classes A/B/C need semi-structured text conforming to published JSON schemas: new submissions from January 1, 2027, with a grace period for services already In Process before October 1, 2026. Legacy DOCX/XLSX templates are retired. Enforcement is progressive corrective action applied quarterly, not immediate revocation. FedRAMP partners with the OSCAL Foundation, but there is no blanket "OSCAL mandate"; use the published CR26 schemas and validator.
  • Security Inbox: All authorized CSPs must maintain a dedicated Security Inbox (no CAPTCHAs or barriers) for urgent vulnerability directives - effective January 5, 2026.
  • Templates: CR26 retires the traditional DOCX/XLSX document set for Rev5; the SSP is replaced by the Certification Package Overview and Security Decision Record, with published JSON schemas and a validator.

1. Readiness & Gap Assessment

Approach
  1. Clarify scope - Ask the user: What is the CSO (Cloud Service Offering)? IaaS/PaaS/SaaS? Target Certification Class under CR26?
  2. Identify authorization path - FedRAMP 20x (primary, preferred) vs. legacy Agency Authorization package (still available for complex systems during CR26 transition)
  3. Run through the readiness checklist - See references/readiness-checklist.md
  4. Surface gaps - Map current state to required controls; flag missing documentation, unimplemented controls, and architectural deficiencies
  5. Prioritize - Group gaps by: (a) blockers for readiness review, (b) items addressable before 3PAO assessment, (c) POA&M candidates
FedRAMP Ready retired July 28, 2026 (now "Legacy FedRAMP Ready"). Advise CSPs by pipeline instead: Class A (open since August 3, 2026) for external-framework entry, Classes B/C from August 31, 2026 for full certification; legacy Rev5 Ready holders must convert by the later of annual-assessment expiration or November 17, 2026.
Key Readiness Questions to Ask the User
  • Are you targeting FedRAMP 20x (preferred) or a legacy authorization package?
  • What cloud platform (AWS GovCloud, Azure Government, GCP, on-prem hybrid)?
  • Are you leveraging any existing FedRAMP-authorized IaaS/PaaS (e.g., AWS GovCloud FedRAMP High)?
  • Do you have FIPS 140-2/3 validated encryption in place?
  • Is your authorization boundary defined and documented?
  • Do you have a vulnerability scanning program (OS, DB, web app, container)?
  • Are security policies and procedures documented?
  • Do you have an Incident Response Plan (IRP) and Contingency Plan (CP) that have been tested?
  • Are your Rev5 package artifacts aligned to the CR26 data requirements? Semi-structured data (Classes A/B/C) is required for new submissions from January 1, 2027; comprehensive machine-readable packages (Class D) from May 1, 2027, existing Class D at the next annual assessment after November 1, 2027. (20x has its own machine-readable model.)
Output Format
  • Produce a gap table: Control Family | Current State | Gap | Priority | Owner
  • Summarize top 5–10 high-priority gaps as prose
  • Note the target Certification Class and whether FedRAMP 20x is feasible

2. ATO Documentation

The core FedRAMP authorization package consists of:

Authorization Package
├── System Security Plan (SSP) + Appendices A–Q
├── Security Assessment Plan (SAP) + Appendices A–D [3PAO-prepared]
├── Security Assessment Report (SAR) + Appendices A–F [3PAO-prepared]
└── Plan of Action & Milestones (POA&M) [SSP Appendix O]
Important: Word/Excel templates are retired for Rev5 under CR26; the SSP is replaced by the Certification Package Overview plus Security Decision Record. New Class A/B/C submissions need semi-structured data from January 1, 2027; Class D needs comprehensive machine-readable packages from May 1, 2027.
Templates: https://www.fedramp.gov/documents-templates/
Document Guidance

For detailed guidance on each document type, read the appropriate reference file:

  • SSP → references/ssp-guide.md
  • POA&M → references/poam-guide.md
  • SAP / SAR → references/sap-sar-guide.md
  • Supporting appendices → references/appendices-guide.md
General Writing Principles for All ATO Docs
  1. Describe only what is implemented - Do not document planned or aspirational controls; these trigger findings and must go in POA&M instead
  2. Be specific - Reference exact tools, filenames, section numbers, policy names; vague language causes findings
  3. Mind the verbs - Each control requirement uses specific verbs (track, document, enforce, test). Address each verb explicitly
  4. Shared responsibility - For any customer-configurable or shared control, create a clear "Customer Responsibility" section
  5. Keep it consistent - Architecture diagrams, data flows, inventory, and control statements must all be internally consistent

3. NIST 800-53 Control Mapping

Control Families (Rev 5)
IDFamilyNotes
ACAccess ControlIAM, RBAC, least privilege, remote access
ATAwareness & TrainingSecurity + privacy training (new in Rev 5)
AUAudit & AccountabilityLog retention, SIEM, audit review
CAAssessment, Authorization & MonitoringConMon, 3PAO, ATO
CMConfiguration ManagementBaselines, change control, CMDB
CPContingency PlanningBCP/DR, tested annually
IAIdentification & AuthenticationMFA, PIV, FIPS 140-2/3 crypto
IRIncident ResponseIRP, tested annually, reporting SLAs
MAMaintenanceRemote maintenance controls
MPMedia ProtectionData at rest, media sanitization
PEPhysical & EnvironmentalDatacenters; often inherited from IaaS
PLPlanningSSP, rules of behavior
PMProgram ManagementEnterprise-level security program
PSPersonnel SecurityScreening, termination procedures
PTPII Processing & TransparencyNew family in Rev 5 - privacy controls
RARisk AssessmentVulnerability scanning, MITRE ATT&CK scoring
SASystem & Services AcquisitionSDLC, supply chain
SCSystem & Communications ProtectionEncryption in transit, network segmentation
SISystem & Information IntegrityPatching, malware, integrity monitoring
SRSupply Chain Risk ManagementNew family in Rev 5 - SCRM
CR26 Certification Class Mapping

Under CR26, the FedRAMP PMO is aligning control baselines to Certification Classes. When users describe their system, map to a class:

  • Class A (Pilot/Transitional): New baseline introduced under 20x - entry into the federal market via external frameworks (initially SOC 2 Type II) through Program Certification; once a federal customer uses the service, Class A holders have 12 months to begin transition to a Class B, C, or D certification through full assessment
  • Class B (replaces LI-SaaS + Low): Systems handling non-sensitive federal information where a breach would cause limited harm
  • Class C (replaces Moderate): Most common - the majority of federal cloud deployments, including systems handling CUI
  • Class D (replaces High): Federal information where compromise has severe or catastrophic effect (e.g., law enforcement, financial, health data)
Legacy references: Many existing FedRAMP documents still reference Low/Moderate/High/LI-SaaS. These map to LI-SaaS/Low → Class B, Moderate → Class C, High → Class D (Class A is new - it has no legacy equivalent). During the CR26 transition, old and new labels are linked. Advise CSPs to check fedramp.gov for the latest.
Mapping Workflow
  1. Ask: What types of federal data will the system process/store/transmit?
  2. Determine target Certification Class (A, B, C, or D) under CR26
  3. Select NIST 800-53 Rev 5 baseline using the class mapping (B ↔ Low, C ↔ Moderate, D ↔ High)
  4. Cross-reference with FedRAMP parameter requirements (FedRAMP often sets stricter parameters than base NIST)
  5. For inherited controls, identify which are fully/partially inherited from leveraged FedRAMP IaaS/PaaS and document in CIS/CRM workbook

This is the start of the file. Read the full SKILL.md on GitHub.

Security

  • Security scanPassed, 100 of 100Pattern checks on the skill's files.
  • Model reviewNot runA model review is scheduled for the next rescan.

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
1,020
Repository forks
192
7-day trend score
34

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/sushegaad/claude-skills-governance-risk-and-compliance/fedramp/badge)](https://verified-skill.com/skills/sushegaad/claude-skills-governance-risk-and-compliance/fedramp)

Something wrong with this skill or its page? Tell us.