[Feature Request] Ability to add specific NIST mappings
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 139
- Forks
- 52
- Avg merge
- 1h 16m
- Merged PRs (30d)
- 3
Description
Source: https://splunk-usergroups.slack.com/archives/CDNHXVBGS/p1730893006095839
Customers would like to add specific NIST annotations.
In addition to overriding the built in NIST & CIS mappings, in order to take advantage of any unmanaged annotation frameworks customers would want to use, we should likely consider some sort of basic KV pair object under tags to accommodate future requests regarding customizing this.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by locating the schema and mapping code for tags, NIST, and CIS annotations, then trace how content metadata is validated and emitted. Done means users can provide specific NIST mappings, override built-in NIST and CIS mappings, and represent other annotation frameworks through the proposed key-value tags without breaking existing content.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100