FedRAMP Rev 5 traditional authorization with SSP/SAP/SAR/POA&M and NIST 800-53 controls

version
0.1.0
GitHub stars
436

Install

/plugin install fedramp-rev5@grc-engineering-suite

Run it inside Claude Code after adding the marketplace with /plugin marketplace add GRCEngClub/claude-grc-engineering.

Contents

Discovered from source

Skills 1

FedRAMP Rev 5 Expert

Deep expertise in traditional FedRAMP authorization under Rev 5.

Expertise Areas

Authorization Paths

  • Agency Authorization: Single agency sponsor
  • JAB Authorization: Joint Authorization Board (GSA, DOD, DHS)
  • FedRAMP Connect: Prioritization for JAB review

Impact Levels

  • Low: ~125 controls, public data
  • Moderate: ~325 controls, CUI/PII (most common)
  • High: ~425 controls, sensitive/law enforcement

Required Documentation

DocumentPurpose
SSPSystem Security Plan - control implementation
SAPSecurity Assessment Plan - test procedures
SARSecurity Assessment Report - findings
POA&MPlan of Action & Milestones - remediation

Authorization Process

  1. Preparation (document development)
  2. Authorization (3PAO assessment)
  3. Continuous Monitoring (ongoing)

Control Families (NIST 800-53 Rev 5)

All 20 control families apply based on baseline:

  • AC, AT, AU, CA, CM, CP, IA, IR, MA, MP
  • PE, PL, PM, PS, PT, RA, SA, SC, SI, SR

Capabilities

  • SSP section development guidance
  • Control implementation recommendations
  • POA&M management and prioritization
  • 3PAO readiness assessment
  • Continuous monitoring setup
  • Agency liaison communication templates

Commands 4

FedRAMP Rev 5 Assessment

Evaluates readiness for traditional FedRAMP authorization under Rev 5.

Arguments

  • $1 - Impact level (required: low, moderate, high)
  • $2 - Authorization path (optional: agency, jab)

Impact Levels

FedRAMP Low (~125 controls)

  • Low-impact data (public information)
  • Minimal security requirements

FedRAMP Moderate (~325 controls)

  • Controlled unclassified information (CUI)
  • Most common authorization level

FedRAMP High (~425 controls)

  • Highly sensitive data
  • Law enforcement, emergency services

Authorization Paths

  • Agency: Sponsored by single federal agency
  • JAB: Joint Authorization Board (provisional ATO from GSA, DOD, DHS)

Assessment Output

  • Authorization readiness score
  • Control implementation gaps
  • Documentation requirements (SSP, SAP, SAR, POA&M)
  • 3PAO assessment preparation checklist

Example

/fedramp-rev5:assess moderate agency

Baseline Selection

Helps select and tailor the appropriate FedRAMP Rev 5 control baseline.

Arguments

  • $1 - Impact level (required: low, moderate, high)
  • $2 - System type (optional: saas, paas, iaas)

Baselines Overview

BaselineControlsTypical Use
Low~125Public data, low risk
Moderate~325CUI, PII, most common
High~425Sensitive, law enforcement

Tailoring Guidance

Scoping

  • Identify non-applicable controls
  • Document justification for exclusions

Compensating Controls

  • When standard control cannot be implemented
  • Must provide equivalent protection
  • Requires documented justification

Organization-Defined Parameters

  • Fill in [Assignment] and [Selection] values
  • Must meet minimum FedRAMP requirements

Example

/fedramp-rev5:baseline-select moderate saas

POA&M Review

Analyzes and provides guidance on FedRAMP Plan of Action & Milestones.

Arguments

  • $1 - POA&M file or action (required)
  • $2 - Analysis type (optional: gaps, priorities, aging)

POA&M Requirements

Each POA&M item must include:

  • Weakness description
  • Point of contact
  • Resources required
  • Scheduled completion date
  • Milestones with dates
  • Status updates
  • Risk level (High/Moderate/Low)

Analysis Types

  • gaps - Identify missing required fields
  • priorities - Rank items by risk and due date
  • aging - Flag overdue items and extensions needed

FedRAMP POA&M Rules

  • High vulnerabilities: 30 days to remediate
  • Moderate vulnerabilities: 90 days to remediate
  • Low vulnerabilities: 180 days to remediate
  • Operational requirements may extend timelines

Example

/fedramp-rev5:poam-review ./poam.xlsx priorities

SSP Guidance

Provides guidance for developing FedRAMP System Security Plan documentation.

Arguments

  • $1 - SSP section or topic (optional)
  • $2 - Impact level (optional: low, moderate, high)

SSP Sections

  1. System Information - Name, description, boundaries
  2. System Environment - Architecture, data flow
  3. System Interconnections - External connections
  4. Control Implementation - How each control is satisfied
  5. Continuous Monitoring - Ongoing assessment plan

Key Requirements

  • Describe all system components within authorization boundary
  • Document all data types processed/stored/transmitted
  • Map controls to implementation details
  • Include diagrams (architecture, network, data flow)
  • Reference policies and procedures

Output

  • SSP section templates
  • Control implementation guidance
  • Common gaps and how to address
  • FedRAMP template references

Example

/fedramp-rev5:ssp-guidance "control implementation" moderate

Sponsors

Details

Marketplace
GRCEngClub/claude-grc-engineering
Source
plugins/frameworks/fedramp-rev5
Category
Community

More from GRCEngClub/claude-grc-engineering

All 70