-
Notifications
You must be signed in to change notification settings - Fork 2
Specs M4 Risks EBIOS RM Risk Source
Claude edited this page Aug 28, 2026
·
1 revision
risks.models.ebios.risk_source.RiskSource
Risk source (SR): an element (individual, group, organization, State, phenomenon) at the origin of the risk. Reference prefix: ERSC.
| Field | Type | Constraints | Description |
|---|---|---|---|
id |
UUID | PK, auto | Unique identifier |
assessment_id |
relation | FK -> RiskAssessment, required | Parent assessment |
reference |
string | required, unique, prefix ERSC | Code (e.g. ERSC-1) |
name |
string | required, max 255 | Name of the SR |
description |
text | optional | Description |
category |
enum | required |
state, organized_crime, terrorist, activist, competitor, employee, service_provider, amateur, natural, other
|
motivation_level |
integer | required, 1 to 4 | Motivation level (1 low, 4 very high) |
motivation_description |
text | optional | Qualitative description |
resources_level |
integer | required, 1 to 4 | Resources level (1 limited, 4 unlimited) |
activity_level |
integer | required, 1 to 4 | Observed activity level |
threat_level |
integer | computed, 1 to 4 (V1-V4) | ANSSI threat level (grid A, see README §2.8) |
is_retained |
boolean | required, default true | SR retained for the analysis |
retention_justification |
text | optional | Justification |
is_from_catalog |
boolean | required, default false | Sourced from the predefined ANSSI catalog |
criteria_snapshot |
json | computed | Snapshot of the scoring grid |
created_by, created_at, updated_at
|
- | auto | Standard |
threat_levelis computed insave()according to grid A (see README §2.8). The result is stored for use in filtering/indexing. The grid is configurable via a JSON field onRiskCriteria(keyebios_threat_grid).
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)