Contribution: Mapping NIST SP 800-53 Controls to OpenCRE
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 180
- Forks
- 137
- Avg merge
- 3d 23h
- Merged PRs (30d)
- 21
Description
Contribution: Standard Mapping to OpenCRE
I am contributing a mapping of selected controls from NIST SP 800-53 Rev.5 to existing CREs.
Scope
- Initial mapping of 7 controls
- Focused on development, configuration, cryptography, input validation, authentication, and auditing
Notes
- Mappings are based on semantic alignment between control intent and CRE definitions
- Some mappings (e.g., SI-10, IA-5) are partial where CRE scope is narrower or broader
- No new CREs were proposed in this batch
Attached
- Mapping spreadsheet (CSV format)
Looking forward to feedback and suggestions for improvement.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the attached myopencre_mapping.xlsx and the existing CRE definitions for the seven listed control areas. Check how comparable mappings are represented in OpenCRE, then confirm the expected contribution format with the project before making changes. Done means the selected NIST SP 800-53 Rev. 5 controls have accepted, well-supported mappings, including the noted partial mappings.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100