[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EM9SS2NNGY3145PC93AQJV":3,"skill-same:01M7EM9SS2NNGY3145PC93AQJV":48},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M7EM9SS2NNGY3145PC93AQJV","fedramp-moderate-baseline",null,"Implements FedRAMP Moderate baseline assessments using NIST SP 800-53 Revision 5 controls—authorization boundary definition, System Security Plan (SSP), Plan of Action and Milestones (POA&M), and continuous monitoring (ConMon)—with Cloud Service Provider (CSP) and agency customer responsibility matrices. Trigger when preparing FedRAMP authorization packages, assessing cloud offerings for federal customers, mapping 800-53 Rev 5 controls to CSF outcomes, or auditing ConMon deliverables (monthly POA&M, annual assessments). Do not use for CMMC\u002FCUI defense contractor assessments (use cmmc-nist-800-171), SOX ITGC financial reporting controls (use sox-itgc-audit), or generic CSF gap analysis without FedRAMP artifacts (use nist-csf-2-assessment).","Mr-Nobody-Anonymous\u002FAll-skills","Mr-Nobody-Anonymous","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F184253119?v=4","01M7AEXFJHKTYQW5R0ZCQQTWFV","anonymous","01M7C00M3GQR4QKP9GZA42GFAK",0,"MIT","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcompliance\u002Ffedramp-moderate-baseline\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: fedramp-moderate-baseline\ndescription: Implements FedRAMP Moderate baseline assessments using NIST SP 800-53 Revision 5 controls—authorization boundary definition, System Security Plan (SSP), Plan of Action and Milestones (POA&M), and continuous monitoring (ConMon)—with Cloud Service Provider (CSP) and agency customer responsibility matrices. Trigger when preparing FedRAMP authorization packages, assessing cloud offerings for federal customers, mapping 800-53 Rev 5 controls to CSF outcomes, or auditing ConMon deliverables (monthly POA&M, annual assessments). Do not use for CMMC\u002FCUI defense contractor assessments (use cmmc-nist-800-171), SOX ITGC financial reporting controls (use sox-itgc-audit), or generic CSF gap analysis without FedRAMP artifacts (use nist-csf-2-assessment).\nsource: \"https:\u002F\u002Fgithub.com\u002Fvaquarkhan\u002Fcompliance-agent-skills\"\nsource_repository: \"vaquarkhan\u002Fcompliance-agent-skills\"\nsource_path: \"skills\u002Ffedramp-moderate-baseline\u002FSKILL.md\"\nlicense: \"MIT\"\nimported_at: \"2026-09-20\"\n---\n\n# FedRAMP Moderate Baseline\n\n## Overview\n\nThis skill implements **FedRAMP Moderate** authorization readiness and assessment workflows aligned to **NIST SP 800-53 Revision 5** (September 2020, updated per FedRAMP baselines). FedRAMP Moderate applies to cloud systems where loss of confidentiality, integrity, or availability would have **serious adverse effect** on agency operations.\n\n| Artifact | Purpose | Primary reference |\n| --- | --- | --- |\n| **Authorization boundary** | Defines system components, data flows, and trust zones | FedRAMP SSP Section 9; NIST SP 800-37 Rev 2 |\n| **System Security Plan (SSP)** | Documents control implementation per 800-53 Rev 5 | FedRAMP SSP template (Moderate baseline) |\n| **Security Assessment Plan (SAP)** | Defines assessor test procedures | FedRAMP SAP template |\n| **Security Assessment Report (SAR)** | Documents findings and risk | FedRAMP SAR template |\n| **POA&M** | Tracks deficiencies, milestones, risk ratings | FedRAMP POA&M template |\n| **ConMon** | Ongoing vulnerability scanning, POA&M updates, annual assessment | FedRAMP ConMon Strategy Guide |\n\n**Moderate baseline** includes approximately **323 controls** from NIST SP 800-53 Rev 5 (including enhancements where applicable). Control families span AC, AU, AT, CM, CP, IA, IR, MA, MP, PE, PL, PS, RA, CA, SC, SI, SR, and others per FedRAMP baseline documentation.\n\n**Responsibility split**:\n\n| Party | Typical responsibilities |\n| --- | --- |\n| **CSP (Cloud Service Provider)** | Physical\u002Fdata center security, hypervisor, platform controls, FedRAMP package maintenance, customer responsibility matrix |\n| **Agency customer** | Identity federation configuration, data classification, endpoint protection for agency users, configuration within customer-managed layers (IaaS\u002FPaaS\u002FSaaS dependent) |\n| **Leveraged authorizations** | Agency inherits CSP controls via FedRAMP ATO; must document **customer responsibility matrix (CRM)** gaps |\n\nCross-walk: FedRAMP controls map to **NIST CSF 2.0** outcomes—use `nist-csf-2-assessment` for executive profiles; this skill produces **FedRAMP-specific authorization artifacts**.\n\nReference documents: [FedRAMP.gov](https:\u002F\u002Fwww.fedramp.gov\u002F), [NIST SP 800-53 Rev 5](https:\u002F\u002Fcsrc.nist.gov\u002Fpublications\u002Fdetail\u002Fsp\u002F800-53\u002Frev-5\u002Ffinal), [NIST SP 800-37 Rev 2](https:\u002F\u002Fcsrc.nist.gov\u002Fpublications\u002Fdetail\u002Fsp\u002F800-37\u002Frev-2\u002Ffinal).\n\n## When to Use\n\nUse this skill when:\n\n- **Preparing or reviewing** a FedRAMP Moderate authorization package (SSP, SAP, SAR, POA&M)\n- Defining or validating the **authorization boundary** for a cloud offering (SaaS, PaaS, IaaS)\n- Assessing **CSP vs agency customer** control inheritance and CRM completeness\n- Auditing **continuous monitoring** deliverables (monthly ConMon, annual assessment, significant change requests)\n- Mapping **800-53 Rev 5** control implementations for federal sales or ATO inheritance\n- Harmonizing FedRAMP controls with existing **IAM** and **logging** programs\n\nDo **not** use this skill when:\n\n- CMMC Level 2 \u002F NIST SP 800-171 for CUI in defense supply chain (use `cmmc-nist-800-171`)\n- SOX IT general controls for financial reporting (use `sox-itgc-audit`)\n- PCI CDE or cardholder data environments (use `pci-dss-network-segmentation`)\n- HIPAA BAA vendor legal review without FedRAMP scope (use `hipaa-baa-vendor-assessment`)\n\n## Core Process\n\nExecute steps **in order**.\n\n### Step 1: Authorization boundary and system categorization\n\n1. Document **FIPS 199** security categorization (confidentiality, integrity, availability impact levels)—Moderate typically **Moderate\u002FModerate\u002FModerate** or equivalent.\n2. Draw authorization boundary diagram:\n   - CSP-managed infrastructure, tenant isolation, managed services\n   - Customer-managed components (IdP federation, endpoints, custom configs)\n   - External interfaces: API gateways, FedRAMP-approved interconnections\n3. Identify **leveraged services** (e.g., AWS GovCloud, Azure Government) with existing FedRAMP authorizations.\n4. Artifact: `fedramp-boundary-{id}.json` with component inventory and data flow descriptions.\n\n### Step 2: Control baseline selection and CRM\n\n1. Load **FedRAMP Moderate baseline** control list (800-53 Rev 5).\n2. For each control, assign implementation status per CRM:\n   - **CSP inherited**, **CSP fully responsible**, **Customer responsible**, **Shared**, **Not applicable** (with justification)\n3. Priority families for cloud audits:\n   - **AC** (Access Control) → `access-control-identity-audit`\n   - **AU** (Audit and Accountability) → `audit-logging-integrity`\n   - **IA** (Identification and Authentication)\n   - **SC** (System and Communications Protection)\n   - **SI** (System and Information Integrity)\n   - **CA** (Assessment, Authorization, and Monitoring)\n4. Artifact: `crm-matrix-{id}.csv` linked to SSP Part C.\n\n### Step 3: SSP development or gap review\n\n1. For each in-scope control, document per FedRAMP SSP format:\n   - Control description and responsible role\n   - Implementation narrative (how, not just policy reference)\n   - **Implementation status**: Implemented, Partially Implemented, Planned, Alternative Implementation, Not Applicable\n2. Cross-reference **NIST SP 800-53A Rev 5** assessment procedures for testability of narratives.\n3. Validate **AI\u002Fagent components** if in boundary:\n   - LLM API data handling, MCP tool scopes, logging of automated decisions\n   - Map to AC-3, AU-2, AU-12, SI-4, SR controls\n4. Use **Terraform MCP** (`mcp\u002Fterraform.mcp.json`) for IaC evidence supporting SC and CM families.\n\n### Step 4: Access control and identity (AC, IA families)\n\n1. Execute `access-control-identity-audit` Steps 1–5 against FedRAMP AC\u002FIA control mapping:\n   - AC-2 (Account Management), AC-3 (Access Enforcement), AC-6 (Least Privilege)\n   - IA-2 (Identification and Authentication), IA-5 (Authenticator Management)\n2. Verify **PIV\u002FCAC federation** or approved alternative for agency users where CRM assigns customer responsibility.\n3. Verify **privileged access** (PAM), MFA, and service account governance for CSP operations staff.\n4. Document findings with 800-53 control IDs (e.g., `AC-6(10)` for privileged function restrictions).\n\n### Step 5: Audit logging and accountability (AU family)\n\n1. Execute `audit-logging-integrity` against AU controls:\n   - AU-2 (Event Logging), AU-3 (Content of Audit Records), AU-6 (Audit Review)\n   - AU-9 (Protection of Audit Information), AU-11 (Audit Record Retention)\n2. Verify logs cover authorization boundary components; **centralized SIEM** with tamper protection.\n3. Use **Postgres MCP** read-only queries for log retention configuration evidence where applicable.\n4. Confirm **agency access** to audit records per CRM and AU-6 requirements.\n\n### Step 6: Security assessment planning and testing\n\n1. Build or review **SAP** with test cases mapped to 800-53A procedures.\n2. Sampling methodology for Moderate: document population, sample size, pass\u002Ffail criteria.\n3. Test categories:\n   - **Technical**: vulnerability scans (authenticated), penetration testing per FedRAMP requirements\n   - **Operational**: incident response tabletop, backup restoration\n   - **Administrative**: policy review, training records, PS-3 personnel screening\n4. Record results in SAR format with **risk ratings** (Low, Moderate, High per FedRAMP guidance).\n\n### Step 7: POA&M management\n\n1. For each deficiency, create POA&M entry:\n   - Weakness description, risk level, milestones, scheduled completion date, responsible official\n2. **Operational requirements**: update POA&M **at least monthly**; close items only with evidence of remediation.\n3. Flag **high-risk open items** approaching milestone breach—escalate to authorizing official.\n4. Artifact: `poam-{id}.yaml` aligned to FedRAMP POA&M template fields.\n\n### Step 8: Continuous monitoring (ConMon)\n\n1. Verify ConMon strategy implementation:\n   - **Monthly**: OS\u002Finfrastructure\u002Fdatabase vulnerability scanning; POA&M updates\n   - **Annual**: full security assessment or continuous assessment approach per FedRAMP guidance\n   - **Significant change requests (SCR)** for material architecture or control changes\n2. Cross-ref `soc2-ccm-continuous-monitoring` for shared monitoring patterns (adapt to FedRAMP ConMon deliverables).\n3. Integrate **threat intelligence** (SI-5), **configuration drift** detection (CM family)—`compliance-as-code-governance` for IaC drift scans.\n\n### Step 9: Authorization decision support and evidence packaging\n\n1. Prepare **authorization package** summary for AO\u002FAuthorizing Official Designated Representative (AODR):\n   - Boundary, categorization, CRM, open POA&M risk summary, ConMon status\n2. Map residual gaps to **NIST CSF 2.0** for executive reporting via `nist-csf-2-assessment` cross-walk table.\n3. Package evidence with SHA-256 hashes per `templates\u002Faudit-evidence-manifest.yaml`.\n4. Emit findings:\n\n```yaml\nid: FIND-FEDRAMP-001\nseverity: HIGH\ncontrol_id: AU-6\nobservation: \"No documented procedure for monthly review of privileged user audit logs\"\nrecommendation: \"Implement AU-6 review SOP with SIEM dashboard and sign-off records\"\nowner: \"\"\ndue_date: null\nstatus: open\n```\n\n## Common Rationalizations\n\n| Excuse the agent might generate | Required rebuttal |\n| --- | --- |\n| \"We inherit FedRAMP from AWS\u002FAzure, so no SSP needed.\" | **Leveraged authorization requires CRM**—customer must document inherited vs customer-implemented controls; inheritance is not blanket exemption. |\n| \"800-53 Rev 4 narratives still apply.\" | FedRAMP baseline is **800-53 Rev 5**—control IDs, enhancements, and assessment procedures changed; remap all references. |\n| \"POA&M items can stay open indefinitely with accepted risk.\" | FedRAMP requires **milestones and AO tracking**—permanent open POA&M without AO acceptance is authorization deficiency. |\n| \"ConMon is just vulnerability scanning.\" | ConMon includes **POA&M updates, inventory maintenance, incident reporting, significant change management**—not scans alone. |\n| \"Moderate baseline is the same as SOC 2 Type II.\" | Overlap exists but **FedRAMP artifacts, 800-53 Rev 5 baseline, CRM, and ConMon** are distinct—SOC 2 report does not substitute for SSP\u002FSAR. |\n| \"Agency customer owns all access controls.\" | CRM defines split—**CSP must implement AC\u002FIA for platform layers**; vague CRM is a common SAR finding. |\n\n## Red Flags\n\n- Authorization boundary excludes multi-tenant isolation components or LLM\u002FMCP data processors\n- CRM marks all controls \"CSP inherited\" without customer responsibility documentation\n- SSP narratives cite policy titles without implementation evidence (AU, AC families)\n- POA&M not updated within 30 days; high-risk items past milestone without AO approval\n- Vulnerability scans missing authenticated credentials or scope gaps vs boundary\n- No SCR process for major releases affecting security posture\n- AU-9 audit log protection inadequate (customer or operator can alter own logs)\n- 800-53 Rev 4 control references in current authorization package\n- ConMon deliverables missing monthly cadence evidence\n\n## Verification\n\n- [ ] FIPS 199 categorization documented; authorization boundary diagram current\n- [ ] FedRAMP Moderate baseline (800-53 Rev 5) control list loaded and scoped\n- [ ] Customer Responsibility Matrix complete with inherited\u002Fshared\u002Fcustomer assignments\n- [ ] SSP control narratives assessed for implementation status and testability\n- [ ] AC\u002FIA and AU families audited via access-control and audit-logging skills\n- [ ] SAP\u002FSAR test procedures executed with risk-rated findings documented\n- [ ] POA&M current within 30 days with milestones and responsible officials\n- [ ] ConMon strategy evidence: monthly scans, annual assessment, SCR process\n- [ ] Cross-walk to nist-csf-2-assessment completed for executive gap reporting\n- [ ] Evidence manifest complete with SHA-256 hashes and engagement ID\n","# FedRAMP Moderate Baseline\n\n## Overview\n\nThis skill implements **FedRAMP Moderate** authorization readiness and assessment workflows aligned to **NIST SP 800-53 Revision 5** (September 2020, updated per FedRAMP baselines). FedRAMP Moderate applies to cloud systems where loss of confidentiality, integrity, or availability would have **serious adverse effect** on agency operations.\n\n| Artifact | Purpose | Primary reference |\n| --- | --- | --- |\n| **Authorization boundary** | Defines system components, data flows, and trust zones | FedRAMP SSP Section 9; NIST SP 800-37 Rev 2 |\n| **System Security Plan (SSP)** | Documents control implementation per 800-53 Rev 5 | FedRAMP SSP template (Moderate baseline) |\n| **Security Assessment Plan (SAP)** | Defines assessor test procedures | FedRAMP SAP template |\n| **Security Assessment Report (SAR)** | Documents findings and risk | FedRAMP SAR template |\n| **POA&M** | Tracks deficiencies, milestones, risk ratings | FedRAMP POA&M template |\n| **ConMon** | Ongoing vulnerability scanning, POA&M updates, annual assessment | FedRAMP ConMon Strategy Guide |\n\n**Moderate baseline** includes approximately **323 controls** from NIST SP 800-53 Rev 5 (including enhancements where applicable). Control families span AC, AU, AT, CM, CP, IA, IR, MA, MP, PE, PL, PS, RA, CA, SC, SI, SR, and others per FedRAMP baseline documentation.\n\n**Responsibility split**:\n\n| Party | Typical responsibilities |\n| --- | --- |\n| **CSP (Cloud Service Provider)** | Physical\u002Fdata center security, hypervisor, platform controls, FedRAMP package maintenance, customer responsibility matrix |\n| **Agency customer** | Identity federation configuration, data classification, endpoint protection for agency users, configuration within customer-managed layers (IaaS\u002FPaaS\u002FSaaS dependent) |\n| **Leveraged authorizations** | Agency inherits CSP controls via FedRAMP ATO; must document **customer responsibility matrix (CRM)** gaps |\n\nCross-walk: FedRAMP controls map to **NIST CSF 2.0** outcomes—use `nist-csf-2-assessment` for executive profiles; this skill produces **FedRAMP-specific authorization artifacts**.\n\nReference documents: [FedRAMP.gov](https:\u002F\u002Fwww.fedramp.gov\u002F), [NIST SP 800-53 Rev 5](https:\u002F\u002Fcsrc.nist.gov\u002Fpublications\u002Fdetail\u002Fsp\u002F800-53\u002Frev-5\u002Ffinal), [NIST SP 800-37 Rev 2](https:\u002F\u002Fcsrc.nist.gov\u002Fpublications\u002Fdetail\u002Fsp\u002F800-37\u002Frev-2\u002Ffinal).\n\n## When to Use\n\nUse this skill when:\n\n- **Preparing or reviewing** a FedRAMP Moderate authorization package (SSP, SAP, SAR, POA&M)\n- Defining or validating the **authorization boundary** for a cloud offering (SaaS, PaaS, IaaS)\n- Assessing **CSP vs agency customer** control inheritance and CRM completeness\n- Auditing **continuous monitoring** deliverables (monthly ConMon, annual assessment, significant change requests)\n- Mapping **800-53 Rev 5** control implementations for federal sales or ATO inheritance\n- Harmonizing FedRAMP controls with existing **IAM** and **logging** programs\n\nDo **not** use this skill when:\n\n- CMMC Level 2 \u002F NIST SP 800-171 for CUI in defense supply chain (use `cmmc-nist-800-171`)\n- SOX IT general controls for financial reporting (use `sox-itgc-audit`)\n- PCI CDE or cardholder data environments (use `pci-dss-network-segmentation`)\n- HIPAA BAA vendor legal review without FedRAMP scope (use `hipaa-baa-vendor-assessment`)\n\n## Core Process\n\nExecute steps **in order**.\n\n### Step 1: Authorization boundary and system categorization\n\n1. Document **FIPS 199** security categorization (confidentiality, integrity, availability impact levels)—Moderate typically **Moderate\u002FModerate\u002FModerate** or equivalent.\n2. Draw authorization boundary diagram:\n   - CSP-managed infrastructure, tenant isolation, managed services\n   - Customer-managed components (IdP federation, endpoints, custom configs)\n   - External interfaces: API gateways, FedRAMP-approved interconnections\n3. Identify **leveraged services** (e.g., AWS GovCloud, Azure Government) with existing FedRAMP authorizations.\n4. Artifact: `fedramp-boundary-{id}.json` with component inventory and data flow descriptions.\n\n### Step 2: Control baseline selection and CRM\n\n1. Load **FedRAMP Moderate baseline** control list (800-53 Rev 5).\n2. For each control, assign implementation status per CRM:\n   - **CSP inherited**, **CSP fully responsible**, **Customer responsible**, **Shared**, **Not applicable** (with justification)\n3. Priority families for cloud audits:\n   - **AC** (Access Control) → `access-control-identity-audit`\n   - **AU** (Audit and Accountability) → `audit-logging-integrity`\n   - **IA** (Identification and Authentication)\n   - **SC** (System and Communications Protection)\n   - **SI** (System and Information Integrity)\n   - **CA** (Assessment, Authorization, and Monitoring)\n4. Artifact: `crm-matrix-{id}.csv` linked to SSP Part C.\n\n### Step 3: SSP development or gap review\n\n1. For each in-scope control, document per FedRAMP SSP format:\n   - Control description and responsible role\n   - Implementation narrative (how, not just policy reference)\n   - **Implementation status**: Implemented, Partially Implemented, Planned, Alternative Implementation, Not Applicable\n2. Cross-reference **NIST SP 800-53A Rev 5** assessment procedures for testability of narratives.\n3. Validate **AI\u002Fagent components** if in boundary:\n   - LLM API data handling, MCP tool scopes, logging of automated decisions\n   - Map to AC-3, AU-2, AU-12, SI-4, SR controls\n4. Use **Terraform MCP** (`mcp\u002Fterraform.mcp.json`) for IaC evidence supporting SC and CM families.\n\n### Step 4: Access control and identity (AC, IA families)\n\n1. Execute `access-control-identity-audit` Steps 1–5 against FedRAMP AC\u002FIA control mapping:\n   - AC-2 (Account Management), AC-3 (Access Enforcement), AC-6 (Least Privilege)\n   - IA-2 (Identification and Authentication), IA-5 (Authenticator Management)\n2. Verify **PIV\u002FCAC federation** or approved alternative for agency users where CRM assigns customer responsibility.\n3. Verify **privileged access** (PAM), MFA, and service account governance for CSP operations staff.\n4. Document findings with 800-53 control IDs (e.g., `AC-6(10)` for privileged function restrictions).\n\n### Step 5: Audit logging and accountability (AU family)\n\n1. Execute `audit-logging-integrity` against AU controls:\n   - AU-2 (Event Logging), AU-3 (Content of Audit Records), AU-6 (Audit Review)\n   - AU-9 (Protection of Audit Information), AU-11 (Audit Record Retention)\n2. Verify logs cover authorization boundary components; **centralized SIEM** with tamper protection.\n3. Use **Postgres MCP** read-only queries for log retention configuration evidence where applicable.\n4. Confirm **agency access** to audit records per CRM and AU-6 requirements.\n\n### Step 6: Security assessment planning and testing\n\n1. Build or review **SAP** with test cases mapped to 800-53A procedures.\n2. Sampling methodology for Moderate: document population, sample size, pass\u002Ffail criteria.\n3. Test categories:\n   - **Technical**: vulnerability scans (authenticated), penetration testing per FedRAMP requirements\n   - **Operational**: incident response tabletop, backup restoration\n   - **Administrative**: policy review, training records, PS-3 personnel screening\n4. Record results in SAR format with **risk ratings** (Low, Moderate, High per FedRAMP guidance).\n\n### Step 7: POA&M management\n\n1. For each deficiency, create POA&M entry:\n   - Weakness description, risk level, milestones, scheduled completion date, responsible official\n2. **Operational requirements**: update POA&M **at least monthly**; close items only with evidence of remediation.\n3. Flag **high-risk open items** approaching milestone breach—escalate to authorizing official.\n4. Artifact: `poam-{id}.yaml` aligned to FedRAMP POA&M template fields.\n\n### Step 8: Continuous monitoring (ConMon)\n\n1. Verify ConMon strategy implementation:\n   - **Monthly**: OS\u002Finfrastructure\u002Fdatabase vulnerability scanning; POA&M updates\n   - **Annual**: full security assessment or continuous assessment approach per FedRAMP guidance\n   - **Significant change requests (SCR)** for material architecture or control changes\n2. Cross-ref `soc2-ccm-continuous-monitoring` for shared monitoring patterns (adapt to FedRAMP ConMon deliverables).\n3. Integrate **threat intelligence** (SI-5), **configuration drift** detection (CM family)—`compliance-as-code-governance` for IaC drift scans.\n\n### Step 9: Authorization decision support and evidence packaging\n\n1. Prepare **authorization package** summary for AO\u002FAuthorizing Official Designated Representative (AODR):\n   - Boundary, categorization, CRM, open POA&M risk summary, ConMon status\n2. Map residual gaps to **NIST CSF 2.0** for executive reporting via `nist-csf-2-assessment` cross-walk table.\n3. Package evidence with SHA-256 hashes per `templates\u002Faudit-evidence-manifest.yaml`.\n4. Emit findings:\n\n```yaml\nid: FIND-FEDRAMP-001\nseverity: HIGH\ncontrol_id: AU-6\nobservation: \"No documented procedure for monthly review of privileged user audit logs\"\nrecommendation: \"Implement AU-6 review SOP with SIEM dashboard and sign-off records\"\nowner: \"\"\ndue_date: null\nstatus: open\n```\n\n## Common Rationalizations\n\n| Excuse the agent might generate | Required rebuttal |\n| --- | --- |\n| \"We inherit FedRAMP from AWS\u002FAzure, so no SSP needed.\" | **Leveraged authorization requires CRM**—customer must document inherited vs customer-implemented controls; inheritance is not blanket exemption. |\n| \"800-53 Rev 4 narratives still apply.\" | FedRAMP baseline is **800-53 Rev 5**—control IDs, enhancements, and assessment procedures changed; remap all references. |\n| \"POA&M items can stay open indefinitely with accepted risk.\" | FedRAMP requires **milestones and AO tracking**—permanent open POA&M without AO acceptance is authorization deficiency. |\n| \"ConMon is just vulnerability scanning.\" | ConMon includes **POA&M updates, inventory maintenance, incident reporting, significant change management**—not scans alone. |\n| \"Moderate baseline is the same as SOC 2 Type II.\" | Overlap exists but **FedRAMP artifacts, 800-53 Rev 5 baseline, CRM, and ConMon** are distinct—SOC 2 report does not substitute for SSP\u002FSAR. |\n| \"Agency customer owns all access controls.\" | CRM defines split—**CSP must implement AC\u002FIA for platform layers**; vague CRM is a common SAR finding. |\n\n## Red Flags\n\n- Authorization boundary excludes multi-tenant isolation components or LLM\u002FMCP data processors\n- CRM marks all controls \"CSP inherited\" without customer responsibility documentation\n- SSP narratives cite policy titles without implementation evidence (AU, AC families)\n- POA&M not updated within 30 days; high-risk items past milestone without AO approval\n- Vulnerability scans missing authenticated credentials or scope gaps vs boundary\n- No SCR process for major releases affecting security posture\n- AU-9 audit log protection inadequate (customer or operator can alter own logs)\n- 800-53 Rev 4 control references in current authorization package\n- ConMon deliverables missing monthly cadence evidence\n\n## Verification\n\n- [ ] FIPS 199 categorization documented; authorization boundary diagram current\n- [ ] FedRAMP Moderate baseline (800-53 Rev 5) control list loaded and scoped\n- [ ] Customer Responsibility Matrix complete with inherited\u002Fshared\u002Fcustomer assignments\n- [ ] SSP control narratives assessed for implementation status and testability\n- [ ] AC\u002FIA and AU families audited via access-control and audit-logging skills\n- [ ] SAP\u002FSAR test procedures executed with risk-rated findings documented\n- [ ] POA&M current within 30 days with milestones and responsible officials\n- [ ] ConMon strategy evidence: monthly scans, annual assessment, SCR process\n- [ ] Cross-walk to nist-csf-2-assessment completed for executive gap reporting\n- [ ] Evidence manifest complete with SHA-256 hashes and engagement ID\n",{"name":5,"source":24,"license":15,"description":7,"imported_at":25,"source_path":26,"source_repository":27},"https:\u002F\u002Fgithub.com\u002Fvaquarkhan\u002Fcompliance-agent-skills","2026-09-20","skills\u002Ffedramp-moderate-baseline\u002FSKILL.md","vaquarkhan\u002Fcompliance-agent-skills","main","2d1750717747097b602acf30bd09a7cbd4b4c6ea","awesome_skills\u002Fcompliance\u002Ffedramp-moderate-baseline","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous","2026-11-09 11:45:36",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill fedramp-moderate-baseline",{"tool":40,"command":41},"bunx","bunx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill fedramp-moderate-baseline",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Mr-Nobody-Anonymous\u002FAll-skills --skill fedramp-moderate-baseline","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fcompliance\u002Ffedramp-moderate-baseline\u002FSKILL.md",true,[],[49,57,64,71,78,85],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":56},"01M7FFFZPC2025JQQHPHDX154J","dei-assessment","Assess diversity, equity, and inclusion with metrics. TRIGGERS - Use when user needs help with dei-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-assessment\u002FSKILL.md",[],[],"2026-11-16 10:05:34",{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":56},"01M7FFFWN8H4WA7A6Y398QKB6J","dei-action-plan","Create DEI action plans with goals and initiatives. TRIGGERS - Use when user needs help with dei-action-plan related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fdei-action-plan\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":56},"01M7FFFSHTM0QZRVZ2NRJTJ0PY","culture-fit-assessment","Design culture add assessment processes. TRIGGERS - Use when user needs help with culture-fit-assessment related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fculture-fit-assessment\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":56},"01M7FFFMA12RKEQA38KHJSXXPS","cowork-to-code-bridge","Use an already-installed, independently verified cowork-to-code bridge to run narrowly approved actions on the user's own macOS, Linux, or WSL2 machine through a local file queue.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcowork-to-code-bridge\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":56},"01M7FFFH1F6M8YRGW5V487GH1K","counter-offer-response","Draft counter-offer responses for retention. TRIGGERS - Use when user needs help with counter-offer-response related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcounter-offer-response\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":56},"01M7FFFDGEHV8Y7J9N40HZXW52","continuous-feedback-system","Design continuous feedback systems. TRIGGERS - Use when user needs help with continuous-feedback-system related tasks.","https:\u002F\u002Fgithub.com\u002FMr-Nobody-Anonymous\u002FAll-skills\u002Fblob\u002Fmain\u002Fawesome_skills\u002Fhr-people\u002Fcontinuous-feedback-system\u002FSKILL.md",[],[]]