
from devops-security-agent-skills18
Guidance and templates to implement FedRAMP/NIST 800-53 controls, continuous monitoring, and authorization artifacts for cloud services pursuing federal complia
Provides a detailed, prescriptive playbook for implementing FedRAMP and NIST 800-53 controls for cloud service offerings. The skill covers impact-level guidance (Low/Moderate/High), control family summaries, System Security Plan (SSP) structure, POA&M templates, continuous monitoring procedures, and operational checklists that map technical controls to cloud tooling (audit logs, vulnerability scanning, configuration management). It also includes example YAML snippets and runnable audit/check templates in the repository.
Use this skill when preparing a cloud service for FedRAMP authorization, establishing continuous monitoring (ConMon), building an SSP, preparing evidence for a 3PAO assessment, or tracking remediation through a POA&M. It is appropriate for security engineers, compliance owners, and platform teams responsible for federal workloads.
Best used by agents supporting DevOps/security workflows (Copilot/Code-style agents, CLI-capable agents) and human operators familiar with cloud IAM, logging, and compliance evidence collection.
FedRAMP compliance guidance skill providing detailed NIST 800-53 control family references, SSP outline, POA&M templates, and continuous monitoring procedures. No scripts included — purely reference/knowledge content. Well-structured YAML documentation with practical checklists and implementation notes, but lacks actionable automation or tooling. Niche audience limited to US federal cloud service providers pursuing FedRAMP authorization.
Reference-only skill with no scripts. Clean from a security perspective — no shell injection risks, no credentials, no destructive commands, no network calls. Architecture is basic: monolithic SKILL.md with no scripts/ or references/ directories. Content is comprehensive and well-organized but the skill only provides guidance rather than automation. Usefulness is limited by niche audience (US federal cloud compliance).