How alfa-group/bron works
Main Components
a. Data Sources Layer:
• External data sources (MITRE ATT&CK, CAPEC, CWE, CVE, MITRE Engage, MITRE D3FEND, MITRE CAR, exploitdb)
• As external system components
b. Data Processing Layer:
• Download Component (download_threat_information/)
• Parsing Component (parsing_scripts/)
• Processing Components:
• Offense processing (offense/)
• Mitigations processing (mitigations/)
• Corpus building (bron_corpus/)
c. Storage Layer:
• ArangoDB Graph Database (graph_db/)
• Schema definitions (graph_db/schemas/)
• Collections (both vertex and edge collections)
d. API/Interface Layer:
• Query interface (graph_db/query_graph_db.py)
• Utility functions (utils/)
• Tutorial interfaces (tutorials/)
Relationships to Highlight
• Data flow from external sources through the processing pipeline
• Bidirectional relationships between different node types
• Demonstrate the connection between schemas and database collections
• How the API layer interfaces with the graph database
Specific Implementation Details
[External Data Sources]
• ↓
[Data Processing Pipeline]
• ↓
[Graph Database Layer]
• ↓
[API/Interface Layer]
Key elements to emphasize:
• Docker deployment option (show containerization boundary)
• ArangoDB as the central storage system
• Schema validation flow
• Bidirectional relationships in the graph structure
Additional Elements
Annotations for:
• Environment variables (BRON_PWD, BRON_SERVER_IP)
• Port configurations (8529 for ArangoDB)
• Data validation points
• Testing interfaces
• Connection types
• Container boundaries
• External system interfaces
This system design should emphasize BRON's role as a cybersecurity knowledge graph system, highlighting how it integrates various threat and mitigation data sources into a unified, queryable graph database.