FedRAMP/StateRAMP Assessment
Assess Federal Risk and Authorization Management Program (FedRAMP) and StateRAMP readiness for "$ARGUMENTS". Determine impact level, evaluate NIST SP 800-53 control baseline, and assess ATO package readiness.
Arguments. $ARGUMENTS may contain the project name and optional flags. Take the first token as <project> and treat --skip-checks as a flag; never include flags in file paths. All paths below use <project>. If --skip-checks is present, skip the prerequisite check and, before writing any artifact, append one line to .singularskills/log.jsonl: {"ts":"<ISO timestamp>","skill":"compliance-fedramp","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}.
Prerequisites
Part of a workflow. This skill is phase 1 (Assess) of the GRC Lifecycle workflow (compliance); cross-domain workflows run it too. First check .singularskills/log.jsonl for an open run for this project: a run-started line with "project":"<project>" and no later run-finished line for the same workflow and project. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the workflow skill with the workflow the user asked for, or compliance when they named none, followed by <project>; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.
Run this skill's gate before writing: sh <this skill's folder>/scripts/gate.sh <project> <project root>, where <project root> is the folder that contains .singularskills/ (use . when you are already there). If it exits non-zero, stop and tell the user what it printed, unless --skip-checks was given (see Arguments). On a refusal, before you stop, append this line to .singularskills/log.jsonl (create the folder and file if missing): {"ts":"<ISO timestamp>","skill":"compliance-fedramp","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}. Once the gate has passed, or under --skip-checks once you have appended the skipped line, append this line before you start work: {"ts":"<ISO timestamp>","skill":"compliance-fedramp","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}.
Read .singularskills/compliance/<project>/00-scope.md. If this file does not exist, tell the user:
Phase 0 (Scope) has not been completed for "". Run /compliance-regulatory-landscape <project> first, or use --skip-checks to bypass.
Process
Read context files:
- Read
references/grc-lifecycle-guide.md for GRC methodology reference
- Read
references/assessment-template.md for output structure
- Read
.singularskills/compliance/<project>/00-scope.md for scope and control framework context
Impact level determination:
- Assess confidentiality, integrity, and availability impact levels per FIPS 199
- Determine overall impact level: Low, Moderate, or High
- Evaluate if FedRAMP Tailored (Li-SaaS) applies for low-impact SaaS
- Document impact level determination with rationale
NIST SP 800-53 control baseline assessment:
- Access Control (AC) — account management, access enforcement, separation of duties, least privilege, session controls, remote access, MFA
- Audit and Accountability (AU) — audit events, content, storage, review, analysis, reporting, reduction, generation, protection
- Security Assessment and Authorization (CA) — security assessment plan, POA&M, continuous monitoring, penetration testing
- Configuration Management (CM) — baseline configuration, change control, least functionality, software restrictions, configuration settings
- Contingency Planning (CP) — contingency plan, training, testing, alternate processing/storage, system recovery
- Identification and Authentication (IA) — user identification, authenticator management, device identification, MFA
- Incident Response (IR) — incident response plan, training, testing, handling, monitoring, reporting
- Maintenance (MA) — controlled maintenance, tools, remote maintenance, personnel
- Media Protection (MP) — media access, marking, storage, transport, sanitization
- Physical and Environmental Protection (PE) — access authorizations, monitoring, visitor control, emergency procedures
- Planning (PL) — security plan, system security plan update, rules of behavior
- Program Management (PM) — information security program plan, senior security officer, risk management strategy
- Risk Assessment (RA) — risk assessment, vulnerability scanning, risk response
- System and Communications Protection (SC) — application partitioning, boundary protection, cryptographic protection, network disconnect
- System and Information Integrity (SI) — flaw remediation, malicious code protection, security alerts, software integrity, information input validation, error handling, memory protection
- Score each control family: implemented / partially implemented / planned / not implemented
3PAO requirements:
- Identify qualified Third Party Assessment Organization (3PAO) requirements
- Assess readiness for initial assessment
- Evaluate continuous monitoring program for ongoing authorization
- Review annual assessment requirements
ATO package readiness:
- Assess System Security Plan (SSP) completeness
- Review Plan of Action and Milestones (POA&M)
- Evaluate Continuous Monitoring (ConMon) program
- Assess Incident Response Plan
- Review Security Assessment Report readiness
- Evaluate supply chain risk management documentation
StateRAMP considerations:
- Identify StateRAMP-specific requirements beyond FedRAMP
- Assess state-specific data residency requirements
- Review StateRAMP verification levels (Ready, Authorized, Authorized+)
- Evaluate reciprocity opportunities between FedRAMP and StateRAMP
Write the artifact to .singularskills/compliance/<project>/01-assess/fedramp.md following the assessment template structure with:
- Impact Level Determination — FIPS 199 analysis and overall impact level
- Control Baseline Assessment — scoring per NIST 800-53 control family
- 3PAO Readiness — assessment organization requirements and readiness
- ATO Package Status — SSP, POA&M, ConMon, and documentation readiness
- StateRAMP Considerations — additional requirements and verification level
- Evidence Inventory — existing evidence and evidence gaps
- Remediation Priorities — ranked list of gaps to address
Output
The FedRAMP/StateRAMP assessment written to .singularskills/compliance/<project>/01-assess/fedramp.md. Present a summary to the user highlighting:
- Impact level determination (Low/Moderate/High)
- Overall control baseline compliance score — score = (implemented + 0.5 × partially implemented) ÷ assessed control families, as a percentage (planned counts as not implemented)
- ATO package readiness percentage
- Top 3 gaps requiring remediation
- Estimated timeline to authorization readiness
Record the run. After you have written the artifact, append this line to .singularskills/log.jsonl (the started line of Prerequisites, with "event":"finished"): {"ts":"<ISO timestamp>","skill":"compliance-fedramp","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}.
Open the artifact with this frontmatter (agent is the agent you run in, or unknown; gate is passed when the gate ran clean and skipped under --skip-checks):
---
skill: compliance-fedramp
workflow: compliance
phase: 1
project: <project>
started: <ISO timestamp>
finished: <ISO timestamp>
agent: <the agent you run in, or "unknown">
gate: <passed|skipped>
---
End the artifact with ## Decisions and ## Open questions, in this shape:
## Decisions
- <what was chosen> — <why> — <what was rejected>
## Open questions
- <what the next phase or a reviewer must settle>
End the artifact with this paragraph, verbatim:
Not legal or audit advice. This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.
1---2name: compliance-fedramp3description: Assess FedRAMP and StateRAMP readiness — FIPS 199 impact level, NIST 800-53 control families, 3PAO requirements and the ATO package (SSP, POA&M, ConMon). Use when a cloud or SaaS company plans to sell to US federal agencies or state governments and wants to assess how far its own environment is from authorization.4metadata:5 source: https://skillmd.com/skills/bromso/compliance-fedramp6 argument-hint: "[project] [--skip-checks]"7 workflow: compliance8 phase: 19 artifact: 01-assess/10---1112# FedRAMP/StateRAMP Assessment1314Assess Federal Risk and Authorization Management Program (FedRAMP) and StateRAMP readiness for "$ARGUMENTS". Determine impact level, evaluate NIST SP 800-53 control baseline, and assess ATO package readiness.1516**Arguments.** `$ARGUMENTS` may contain the project name and optional flags. Take the first token as `<project>` and treat `--skip-checks` as a flag; never include flags in file paths. All paths below use `<project>`. If `--skip-checks` is present, skip the prerequisite check and, **before writing any artifact**, append one line to `.singularskills/log.jsonl`: `{"ts":"<ISO timestamp>","skill":"compliance-fedramp","workflow":"compliance","phase":1,"project":"<project>","event":"skipped","artifact":"01-assess/","note":"<reason or \"none given\">"}`.1718## Prerequisites1920**Part of a workflow.** This skill is phase 1 (Assess) of the GRC Lifecycle workflow (`compliance`); cross-domain workflows run it too. First check `.singularskills/log.jsonl` for an open run for this project: a `run-started` line with `"project":"<project>"` and no later `run-finished` line for the same `workflow` and `project`. If one exists, the conductor is running you: continue here. Otherwise, if the user asked to start, run, continue or resume a process or workflow rather than this one step, do not continue here: invoke the `workflow` skill with the workflow the user asked for, or `compliance` when they named none, followed by `<project>`; it runs this phase in order, asks before it writes and records the run. Otherwise continue here: a later phase runs on its own, behind its gate.2122Run this skill's gate before writing: `sh <this skill's folder>/scripts/gate.sh <project> <project root>`, where `<project root>` is the folder that contains `.singularskills/` (use `.` when you are already there). If it exits non-zero, stop and tell the user what it printed, unless `--skip-checks` was given (see Arguments). On a refusal, before you stop, append this line to `.singularskills/log.jsonl` (create the folder and file if missing): `{"ts":"<ISO timestamp>","skill":"compliance-fedramp","workflow":"compliance","phase":1,"project":"<project>","event":"refused","artifact":"01-assess/","note":"<what the gate printed>"}`. Once the gate has passed, or under `--skip-checks` once you have appended the `skipped` line, append this line before you start work: `{"ts":"<ISO timestamp>","skill":"compliance-fedramp","workflow":"compliance","phase":1,"project":"<project>","event":"started","artifact":"01-assess/","note":""}`.2324Read `.singularskills/compliance/<project>/00-scope.md`. If this file does not exist, tell the user:2526> Phase 0 (Scope) has not been completed for "<project>". Run `/compliance-regulatory-landscape <project>` first, or use `--skip-checks` to bypass.2728## Process29301. **Read context files:**31 - Read `references/grc-lifecycle-guide.md` for GRC methodology reference32 - Read `references/assessment-template.md` for output structure33 - Read `.singularskills/compliance/<project>/00-scope.md` for scope and control framework context34352. **Impact level determination:**36 - Assess confidentiality, integrity, and availability impact levels per FIPS 19937 - Determine overall impact level: Low, Moderate, or High38 - Evaluate if FedRAMP Tailored (Li-SaaS) applies for low-impact SaaS39 - Document impact level determination with rationale40413. **NIST SP 800-53 control baseline assessment:**42 - **Access Control (AC)** — account management, access enforcement, separation of duties, least privilege, session controls, remote access, MFA43 - **Audit and Accountability (AU)** — audit events, content, storage, review, analysis, reporting, reduction, generation, protection44 - **Security Assessment and Authorization (CA)** — security assessment plan, POA&M, continuous monitoring, penetration testing45 - **Configuration Management (CM)** — baseline configuration, change control, least functionality, software restrictions, configuration settings46 - **Contingency Planning (CP)** — contingency plan, training, testing, alternate processing/storage, system recovery47 - **Identification and Authentication (IA)** — user identification, authenticator management, device identification, MFA48 - **Incident Response (IR)** — incident response plan, training, testing, handling, monitoring, reporting49 - **Maintenance (MA)** — controlled maintenance, tools, remote maintenance, personnel50 - **Media Protection (MP)** — media access, marking, storage, transport, sanitization51 - **Physical and Environmental Protection (PE)** — access authorizations, monitoring, visitor control, emergency procedures52 - **Planning (PL)** — security plan, system security plan update, rules of behavior53 - **Program Management (PM)** — information security program plan, senior security officer, risk management strategy54 - **Risk Assessment (RA)** — risk assessment, vulnerability scanning, risk response55 - **System and Communications Protection (SC)** — application partitioning, boundary protection, cryptographic protection, network disconnect56 - **System and Information Integrity (SI)** — flaw remediation, malicious code protection, security alerts, software integrity, information input validation, error handling, memory protection57 - Score each control family: implemented / partially implemented / planned / not implemented58594. **3PAO requirements:**60 - Identify qualified Third Party Assessment Organization (3PAO) requirements61 - Assess readiness for initial assessment62 - Evaluate continuous monitoring program for ongoing authorization63 - Review annual assessment requirements64655. **ATO package readiness:**66 - Assess System Security Plan (SSP) completeness67 - Review Plan of Action and Milestones (POA&M)68 - Evaluate Continuous Monitoring (ConMon) program69 - Assess Incident Response Plan70 - Review Security Assessment Report readiness71 - Evaluate supply chain risk management documentation72736. **StateRAMP considerations:**74 - Identify StateRAMP-specific requirements beyond FedRAMP75 - Assess state-specific data residency requirements76 - Review StateRAMP verification levels (Ready, Authorized, Authorized+)77 - Evaluate reciprocity opportunities between FedRAMP and StateRAMP78797. **Write the artifact** to `.singularskills/compliance/<project>/01-assess/fedramp.md` following the assessment template structure with:80 - **Impact Level Determination** — FIPS 199 analysis and overall impact level81 - **Control Baseline Assessment** — scoring per NIST 800-53 control family82 - **3PAO Readiness** — assessment organization requirements and readiness83 - **ATO Package Status** — SSP, POA&M, ConMon, and documentation readiness84 - **StateRAMP Considerations** — additional requirements and verification level85 - **Evidence Inventory** — existing evidence and evidence gaps86 - **Remediation Priorities** — ranked list of gaps to address8788## Output8990The FedRAMP/StateRAMP assessment written to `.singularskills/compliance/<project>/01-assess/fedramp.md`. Present a summary to the user highlighting:91- Impact level determination (Low/Moderate/High)92- Overall control baseline compliance score — score = (implemented + 0.5 × partially implemented) ÷ assessed control families, as a percentage (planned counts as not implemented)93- ATO package readiness percentage94- Top 3 gaps requiring remediation95- Estimated timeline to authorization readiness9697**Record the run.** After you have written the artifact, append this line to `.singularskills/log.jsonl` (the `started` line of Prerequisites, with `"event":"finished"`): `{"ts":"<ISO timestamp>","skill":"compliance-fedramp","workflow":"compliance","phase":1,"project":"<project>","event":"finished","artifact":"01-assess/","note":""}`.9899Open the artifact with this frontmatter (`agent` is the agent you run in, or `unknown`; `gate` is `passed` when the gate ran clean and `skipped` under `--skip-checks`):100101```yaml102---103skill: compliance-fedramp104workflow: compliance105phase: 1106project: <project>107started: <ISO timestamp>108finished: <ISO timestamp>109agent: <the agent you run in, or "unknown">110gate: <passed|skipped>111---112```113114End the artifact with `## Decisions` and `## Open questions`, in this shape:115116```markdown117## Decisions118- <what was chosen> — <why> — <what was rejected>119120## Open questions121- <what the next phase or a reviewer must settle>122```123124End the artifact with this paragraph, verbatim:125126> **Not legal or audit advice.** This artifact supports preparation for compliance work; certification, attestation and regulatory conclusions require a qualified auditor or counsel.