-
Notifications
You must be signed in to change notification settings - Fork 2
Specs Management Review Isms Change
Claude edited this page Aug 28, 2026
·
1 revision
reports.models.management_review.IsmsChange
Formalised ISMS change decided during a management review (ISO 27001:2022 clause 9.3.3 requirement on "any need for changes to the ISMS").
Clause 9.3.3 requirement : "any need for changes to the ISMS". Formalisation of the changes decided during a review.
| Field | Type | Constraints | Description |
|---|---|---|---|
id |
UUID | PK | |
reference |
string | auto (prefix ICHG), unique |
e.g. ICHG-1
|
review |
FK → ManagementReview | required, CASCADE | Originating review |
change_type |
enum | required |
scope, policy, control, organization, resource, process, other
|
title |
string | required, max 255 | Title |
description |
text | required | Description of the change |
impact_analysis |
text | optional | Impact analysis (interested parties, risks, assets) |
affected_scopes |
M2M → Scope | optional | Affected scopes |
affected_frameworks |
M2M → Framework | optional | Affected frameworks |
affected_policies |
text | optional | List of policies to revise (free text, future evolution towards a Policy model) |
status |
enum | required |
proposed, approved, in_progress, implemented, rejected
|
owner |
FK → User | required | Person responsible for implementation |
target_date |
date | optional | Target date |
implemented_at |
date | optional | Actual implementation date |
created_at, updated_at
|
datetime | auto |
History : HistoricalRecords.
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)