feat: add OWASP Attack as first-class resource (Phase 1) #718
+110
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Feature: Support for OWASP Attack resources (Phase 1)
Partially Fixes #471
Description
This PR implements Phase 1 (Foundation) of mapping OWASP resources into OpenCRE.
It introduces OWASP Attack pages as first-class entities in the graph, distinct from Standards and Tools.
This PR focuses on establishing the data model and backend support only. No automated parsers or external syncing are introduced yet.
Changes
1. Data Model
application/defs/cre_defs.py
Attackto theCredoctypesenum.Attack(Node)dataclass.This keeps OWASP Attacks semantically distinct from other resource types and enables clean graph modeling in later phases.
2. Backend Support
application/database/db.py
dbNodeFromAttackand updatednodeFromDBto support the newAttacktype.add_nodeto safely handle nodes without asectionattribute (required for non-Standard node types such as Attacks), preventing anAttributeError.application/cmd/cre_main.py
register_nodeand parsing logic to accept and registerdefs.Attack.3. Verification Script
application/manual_seed_attacks.py
doctype = "Attack".Verification
Ran the manual seed script locally: