-
Notifications
You must be signed in to change notification settings - Fork 2
Specs M4 Risks EBIOS RM Mitre Attack Technique
Claude edited this page Aug 28, 2026
·
1 revision
risks.models.ebios.mitre_attack.MitreAttackTechnique
Reference catalog for the MITRE ATT&CK Enterprise Matrix. Seeded via the risks/fixtures/mitre_attack_v15.json fixture at installation, updated by the python manage.py refresh_mitre_attack command. No internal prefix: the natural key is mitre_id.
Reference catalog for the MITRE ATT&CK Enterprise Matrix. Seeded via the risks/fixtures/mitre_attack_v15.json fixture at installation, updated by the python manage.py refresh_mitre_attack command.
| Field | Type | Constraints | Description |
|---|---|---|---|
id |
UUID | PK, auto | Unique identifier |
mitre_id |
string | required, unique | MITRE identifier (e.g. T1566, T1566.001) |
name |
string | required, max 255 | Name |
description |
text | required | Description |
tactic |
enum | required |
reconnaissance, resource_development, initial_access, execution, persistence, privilege_escalation, defense_evasion, credential_access, discovery, lateral_movement, collection, command_and_control, exfiltration, impact
|
parent_technique_id |
relation | FK -> self, optional | Parent technique (sub-techniques) |
version |
string | required, max 16 | MITRE version (e.g. 15.1) |
url |
string | optional, max 500 | Link to the MITRE entry |
is_active |
boolean | required, default true | Can be deactivated if removed from MITRE |
created_at, updated_at
|
- | auto | Standard |
Built from docs/ at v0.36.0. Edits made here are overwritten by the next release : open a pull request against the source instead.
- Administration
- Ask Cairn
- Assets and suppliers
- Compliance
- The dashboard
- Finding your way
- Getting started
- Incidents
- How records move
- Organisational context
- Reports and management review
- Risks
- Trust Center
- Architecture
- Configuration
- Contributing
- The documentation system
- Installation
- Internationalisation
- Operations
- Release process
- Security
- Testing
- Adding an assistant provider
- Adding a dashboard widget
- Adding a domain entity
- Declaring a lifecycle
- Adding an MCP tool
- Adding a REST endpoint
- Adding a report
- Interface conventions
- Dashboard widgets
- Lifecycles
- MCP tools
- MCP tool parameters : Assets
- MCP tool parameters : Compliance
- MCP tool parameters : Governance and context
- MCP tool parameters : General
- MCP tool parameters : Incidents
- MCP tool parameters : Reports and management review
- MCP tool parameters : Risks
- MCP tool parameters : System and administration
- MCP tool parameters : Trust Center
- Management commands
- Models
- Permissions
- REST endpoints
- Environment variables
- MCP server
- REST API
- Assistant module (Ask Cairn)
- Module 0: User Management and Access Control
- Module 1: Context and Organization
- Module 2: Asset Management
- Module 3: Compliance
- Module 4: Risk Management
- Module 4 bis - EBIOS Risk Manager
- Module 5 : Trust Center
- Module 6 : Security Incident Management
- Management review : ISO 27001:2022 compliance (clause 9.3)