一键导入
oscal-catalog-provider
Fetch official NIST 800-53 and FedRAMP OSCAL catalogs from authoritative sources
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Fetch official NIST 800-53 and FedRAMP OSCAL catalogs from authoritative sources
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create and manage OSCAL component definitions for reusable security control implementations. Inspired by CivicActions components and community patterns. Use for building component libraries and shared control implementations.
Generate detailed control implementation guidance, technical steps, and implementation plans for OSCAL security controls. Use this skill to create implementation narratives, technical procedures, and deployment plans.
Create and analyze OSCAL Control Mapping documents to establish formal relationships between controls across different frameworks (NIST 800-53, ISO 27001, CIS, PCI-DSS, etc.). Use this skill to document control equivalencies, gaps, and harmonization for multi-framework compliance.
Orchestrate complex multi-step OSCAL compliance workflows by combining multiple skills. Use this skill for end-to-end compliance automation like FedRAMP package reviews, continuous monitoring, and gap assessments.
Perform comprehensive OSCAL validation using community-inspired patterns including JSON schema validation, business rule validation, cross-reference checking, and best practices from IBM Trestle, oscal-pydantic, and Lula. Use for thorough document quality assurance.
Validates OSCAL System Security Plan documents against NIST 800-18 Rev 1 requirements and FedRAMP baselines. Identifies missing elements, quality issues, and provides remediation guidance for achieving ATO compliance.
| name | oscal-catalog-provider |
| description | Fetch official NIST 800-53 and FedRAMP OSCAL catalogs from authoritative sources |
Provide access to official NIST and FedRAMP control catalogs without requiring user uploads. This skill knows where to fetch authoritative OSCAL content and how to use it.
Use this skill when:
| Resource | URL |
|---|---|
| Catalog JSON | https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/json/NIST_SP-800-53_rev5_catalog.json |
| Catalog YAML | https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/SP800-53/rev5/yaml/NIST_SP-800-53_rev5_catalog.yaml |
| Repository | https://github.com/usnistgov/oscal-content |
Stats: 1,193 controls (323 base controls + 870 enhancements) across 20 control families.
| Baseline | Controls | URL |
|---|---|---|
| HIGH | 421 | https://raw.githubusercontent.com/GSA/fedramp-automation/master/dist/content/rev5/baselines/json/FedRAMP_rev5_HIGH-baseline-resolved-profile_catalog.json |
| MODERATE | 325 | https://raw.githubusercontent.com/GSA/fedramp-automation/master/dist/content/rev5/baselines/json/FedRAMP_rev5_MODERATE-baseline-resolved-profile_catalog.json |
| LOW | 156 | https://raw.githubusercontent.com/GSA/fedramp-automation/master/dist/content/rev5/baselines/json/FedRAMP_rev5_LOW-baseline-resolved-profile_catalog.json |
| LI-SaaS | ~156 | https://raw.githubusercontent.com/GSA/fedramp-automation/master/dist/content/rev5/baselines/json/FedRAMP_rev5_LI-SaaS-baseline-resolved-profile_catalog.json |
| Repository | — | https://github.com/GSA/fedramp-automation |
| Resource | URL |
|---|---|
| CSF 2.0 Catalog | https://raw.githubusercontent.com/usnistgov/oscal-content/main/nist.gov/CSF/2.0/json/CSF_2.0_catalog.json |
| Resource | URL |
|---|---|
| CIS v8 Catalog | https://raw.githubusercontent.com/CISecurity/OCALCatalog/main/CIS_Controls_v8_catalog.json |
Based on the user's request, identify which catalog is needed:
| User Mentions | Fetch This |
|---|---|
| "NIST 800-53", "800-53", "NIST controls" | NIST 800-53 Rev 5 catalog |
| "FedRAMP High" | FedRAMP HIGH baseline |
| "FedRAMP Moderate", "FedRAMP" | FedRAMP MODERATE baseline |
| "FedRAMP Low" | FedRAMP LOW baseline |
| "FedRAMP LI-SaaS", "Low Impact SaaS" | FedRAMP LI-SaaS baseline |
| "NIST CSF", "Cybersecurity Framework" | NIST CSF 2.0 catalog |
| "CIS Controls", "CIS" | CIS Controls v8 catalog |
If you have web/fetch capabilities: Retrieve the JSON from the appropriate URL above.
If you cannot fetch (no network access): You MUST ask the user to upload the catalog manually. Use this exact message format:
I need the official OSCAL catalog to complete this task, but I can't fetch it directly.
Please download and upload one of these files:
| You Need | Download From |
|---|---|
| NIST 800-53 Rev 5 | NIST_SP-800-53_rev5_catalog.json |
| FedRAMP HIGH | FedRAMP_rev5_HIGH-baseline-resolved-profile_catalog.json |
| FedRAMP MODERATE | FedRAMP_rev5_MODERATE-baseline-resolved-profile_catalog.json |
| FedRAMP LOW | FedRAMP_rev5_LOW-baseline-resolved-profile_catalog.json |
Quick steps:
IMPORTANT: Always attempt the fetch first before asking the user to upload. Only show the upload instructions if fetching fails or is not available.
Once you have the catalog content:
oscal-parser skill)If you fetch a catalog, retain it in context for the duration of the conversation to avoid re-fetching.
NIST 800-53 Rev 5 organizes controls into 20 families:
| ID | Family | Controls |
|---|---|---|
| AC | Access Control | 25 base + enhancements |
| AT | Awareness and Training | 6 base |
| AU | Audit and Accountability | 16 base |
| CA | Assessment, Authorization, Procedures | 9 base |
| CM | Configuration Management | 14 base |
| CP | Contingency Planning | 13 base |
| IA | Identification and Authentication | 12 base |
| IR | Incident Response | 10 base |
| MA | Maintenance | 7 base |
| MP | Media Protection | 8 base |
| PE | Physical and Environmental Protection | 23 base |
| PL | Planning | 11 base |
| PM | Program Management | 32 base |
| PS | Personnel Security | 9 base |
| PT | Personally Identifiable Information Processing | 8 base |
| RA | Risk Assessment | 10 base |
| SA | System and Services Acquisition | 23 base |
| SC | System and Communications Protection | 51 base |
| SI | System and Information Integrity | 23 base |
| SR | Supply Chain Risk Management | 12 base |
FedRAMP LOW (156 controls)
FedRAMP MODERATE (325 controls)
FedRAMP HIGH (421 controls)
| Control | LOW | MODERATE | HIGH |
|---|---|---|---|
| AC-2 | ✓ | ✓ + (1)(2)(3)(4) | ✓ + (1)(2)(3)(4)(5)(11)(12)(13) |
| AU-2 | ✓ | ✓ | ✓ + additional events |
| IA-2 | ✓ + (1)(2) | ✓ + (1)(2)(8)(12) | ✓ + (1)(2)(5)(8)(12) |
| SC-8 | — | ✓ | ✓ + (1) |
| SC-28 | — | ✓ | ✓ + (1) |
"What does AC-2 require at FedRAMP Moderate?"
"Compare our SSP controls against FedRAMP Moderate"
oscal-parser)controls-extractor)| Catalog | Version | OSCAL Version | Last Updated |
|---|---|---|---|
| NIST 800-53 | Rev 5.1.1 | 1.2.0 | 2024 |
| FedRAMP Baselines | Rev 5 | 1.2.0 | 2024 |
| NIST CSF | 2.0 | 1.2.0 | 2024 |
If fetching is not possible and the user hasn't uploaded a catalog:
You MUST ask the user to upload the catalog. Use the message template in Step 2 above.
Never use training knowledge or memory to provide control definitions, parameters, or requirements for compliance tasks.
This is not a recommendation — it is a hard requirement. Using unofficial control information for compliance work is dangerous and could cause serious harm.
| Risk | Consequence |
|---|---|
| Control text may be outdated | Failed audit, security gaps |
| Parameters (ODPs) may be wrong | Non-compliant implementation |
| Enhancements may be missing | Incomplete security posture |
| Baseline assignments may differ | Wrong controls for authorization level |
Compliance decisions must be based on authoritative sources only:
⚠️ I cannot provide control definitions from memory for compliance work.
Using unofficial or potentially outdated control information could result in:
- Failed audits and authorization delays
- Security vulnerabilities from incorrect implementations
- Regulatory non-compliance and potential fines
- Legal and financial consequences for your organization
Please upload the official OSCAL catalog. I can help you download it — just let me know which baseline you need (NIST 800-53, FedRAMP Low/Moderate/High).
If you need help with something that doesn't require authoritative control text, I'm happy to assist with that instead.
User needs catalog data
│
▼
Can I fetch from URL?
│
┌───┴───┐
YES NO
│ │
▼ ▼
Fetch Has user uploaded?
it │
│ ┌───┴───┐
│ YES NO
│ │ │
│ ▼ ▼
│ Use Ask user to upload
│ upload (show download links)
│ │ │
▼ ▼ ▼
┌────────────┐ User refuses to upload?
│ Continue │ │
│ with task │ ▼
└────────────┘ ⛔ STOP
Do NOT proceed with
compliance tasks.
Offer to help with
non-compliance tasks instead.
oscal-parser — Parse fetched catalog JSONcontrols-extractor — Extract specific controls from catalogcontrol-mapper — Map between NIST and other frameworks