Repository navigation
Give the OCSF allow decision its own class entry - #278
imran-siddique wants to merge 2 commits into
Conversation
The allow rule lived only in decision_class.description, under the old caption "Application Activity", and neither Trace page had a row for it. Add decision_class.allow_class with class_uid 6002, class_name "Application Lifecycle" and the fields an allow carries, add the row to events.md and extend_ocsf.md, and guard it in test_trace_mapping_defaults.py. The opt-in to Detection Finding stays. Fixes GenAI-Security-Project#198 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: Imran Siddique <45405841+imran-siddique@users.noreply.github.com>
|
This pull request's description says it closes #198, which is on the project roadmap. When it merges, GitHub closes that issue and the roadmap counts it as delivered. Please confirm the change delivers the whole issue before merging. |
|
Confirmed, this delivers all of #198. Part 1: the |
|
@rocklambros this is green and mergeable, and it delivers all of #198 as confirmed above. Could one of the code owners review it? |
What changed
decision_classinocsf-mapping.jsongainsallow_class:class_uid6002,class_name"Application Lifecycle", andrequired_fieldsnaming where the disposition goes (unmapped.acs.decision), plusseverity_id,metadata.correlation_uidand the join pair. The evaluator rides inunmapped.acs.metadata, as on a 2004. The prose rule, which still said "Application Activity" after #258, now points at it.events.mdandextend_ocsf.mdget theDecision (allow)row, andtest_trace_mapping_defaults.pychecks the caption matches the 6002 rows.The opt-in to record allows as Detection Findings stays. Dropping it is a one-line follow-up if the Spec leads want one class.
Which issue does this implement
Fixes #198
Base branch
integrationType of change
Specification changes
status:accepted)Breaking for implementers? No. Every
class_uidand existing default is unchanged;activity_idfor 6002 stays with #235.I tested this
integrationat c82310buv run pytest -v: 888 passed, 1 skipped. The 10 failures and 30 errors are Windows-only (symlinks,ghshim) and identical on unmodifiedintegrationuv run mkdocs build --strictpassesChecklist
Security
🤖 Generated with Claude Code