-
Notifications
You must be signed in to change notification settings - Fork 2
Specs M4 Risks EBIOS RM Study Framework
Claude edited this page Aug 28, 2026
·
1 revision
risks.models.ebios.study_framework.StudyFramework
Formalizes the prerequisites required by ANSSI before workshop 1: participants, frameworks, assumptions, constraints. Reference prefix: EFRA.
Formalizes the prerequisites required by ANSSI before workshop 1: participants, frameworks, assumptions, constraints.
| Field | Type | Constraints | Description |
|---|---|---|---|
id |
UUID | PK, auto | Unique identifier |
assessment_id |
relation | FK -> RiskAssessment, required, unique | Parent assessment (1 framework per assessment) |
reference |
string | required, unique, prefix EFRA | Code (e.g. EFRA-1) |
mission_statement |
text | required | Description of the mission under study |
business_perimeter |
text | required | Business perimeter (activities, processes) |
technical_perimeter |
text | required | Technical perimeter (support assets, infrastructures) |
temporal_perimeter |
text | required | Time horizon (study start / end date) |
financial_envelope |
decimal | optional | Allocated budget envelope |
participants |
M2M -> User | optional | Study participants |
participants_external |
json | optional | List of external participants (name, role, organization) |
applicable_frameworks |
M2M -> Framework | optional | Applicable frameworks (ISO 27001, NIS2, GDPR, etc.) |
assumptions |
text | optional | Assumptions retained |
constraints |
text | optional | Constraints (organizational, technical, legal) |
expected_deliverables |
text | optional | Expected deliverables |
status |
enum | required |
draft, validated
|
created_by, created_at, updated_at
|
- | auto |
BaseModel 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)