Risk, control and execution assessment
Risk in context, assessment, mitigation measure, control and execution. Requirement, policy and evidence are imported by reference.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 4 findings · 10 questions
Risk and assessment A risk in its context and how it was assessed.
Risk statement
A risk with its context, cause and affected objective.
Risk in context
The risk tied to the activity or asset it threatens and its cause.
- Which objective, asset or activity does the risk threaten?
- Does the risk share a common cause with other recorded risks?
Assessment
An assessment with its scale, horizon, method and date.
- Which scale and time horizon does this assessment use?
- Can assessments on different scales be compared, and by which mapping?
- On which grounds is the residual risk set?
Treatment and control Measures chosen against a risk and evidence that controls work.
Control design
A control as designed and the risks it is linked to.
Control link
Each link between a control and a risk with its justification.
- Which risks does this control address, and why for each?
- Is a policy or requirement imported by reference rather than copied?
Control execution
Each execution of a control with its outcome and evidence.
Execution evidence
Proof that a control ran and whether it was effective.
- When was the control last executed, and with what result?
- Which assessments should change after an execution failure?
- Is the control's existence being taken as proof of its effectiveness?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseRSK
- Industry
- Cross-industry
- Tags
- EM-RSK-01W1subjectRiskRiskAssessmentRiskTreatmentControlControlExecution
What it is Filled
Risk in context, assessment, mitigation measure, control and execution. Requirement, policy and evidence are imported by reference.
Why it exists Filled
Risk in context, assessment, mitigation measure, control and execution. Requirement, policy and evidence are imported by reference.
Distinguishing features Filled
- Control design and control execution are separate records; a designed control proves nothing on its own.
- Every assessment carries its scale and horizon, so numbers from different methods are not mixed.
- Residual risk is stated with grounds rather than inferred from the presence of controls.
- Distinct from audit findings and compliance requirements, which it references but does not own.
What robots and AI may and may not do Filled
Must not
- Close related risks automatically because a policy status is green.
- Treat the existence of a control as proof that it is effective.
- Compare or aggregate scores from different scales without a stated mapping.
- Change the residual risk rating without recorded grounds.
- Propagate a control failure to risks that are not justifiably linked to it.
Only with a human decision
- Accepting a risk above the stated appetite.
- Approving a risk treatment plan or its exception.
- Changing the risk scale or methodology.
May
- Show which risks are linked to a control and on what justification.
- Flag assessments whose control evidence is missing or outdated.
- Propose re-assessment of linked risks after a control execution fails.
- Group risks that share a recorded common cause.
Moral aspects Filled
- Understated risks can expose people, customers and the organisation to harm.
- Accountability needs a named owner for every accepted risk.
- Over-reporting of controls can create false confidence for regulators and boards.
Who is affected
- Risk owners and management
- Customers and staff exposed to the risk
- Regulators and auditors
Owners Filled
Steward
The risk owner, the information security lead or internal audit, depending on the record.
Master systems
- GRC platform
- Identity and access management system
- SIEM
- Service desk
Links to other meta-models Filled
neighbor
- EM-LEG-02
- EM-OPS-01
- EM-PRD-01
- EM-RSK-02
- EM-STR-02
- EM-TEC-04
references
- WM-KNW-015 - conceptual-candidate
- WM-XCT-027 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by a risk register identifier; assessments, treatments and control executions have their own identifiers and dates.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A record names a risk, an owner, a scale and an assessment date.
- Often confused with an issue, an incident or an audit finding.
Capabilities and actions required Filled
- Control failures can be traced to the risks they actually affect.
- Assessment history shows how a risk changed over time.
Hazards and failure modes required Filled
- False assurance when controls are counted rather than tested.
- Double counting when one cause is recorded as many unrelated risks.
- Stale assessments that are never revisited after change.
Standards and interfaces required Filled
- ISO 31000 for risk management principles and process.
- ISO/IEC 27001 for information security controls.
- NIST Cybersecurity Framework for governance and risk functions.
Context of use required Filled
- Used in governance, risk and compliance functions across the enterprise.
- Applies to security, operational, financial and AI risks alike.
Sources Filled
- NIST CSF/AI RMF: governance and risk functions
- ODRL/PROV: authority, grounds and evidence
- GRC/IAM/BCM practice and NIST SP 800-34 for recovery
- NIST Cybersecurity Framework - Checked live (HTTP 200) on 2026-10-07.
- NIST AI Risk Management Framework - Checked live (HTTP 200) on 2026-10-07.
- NIST SP 800-34 Rev. 1: Contingency Planning Guide for Federal Information Systems - Checked live (HTTP 200) on 2026-10-07.
- W3C PROV-O: Provenance Ontology - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to compare assessments on different scales?
- How to separate control design from its execution?
- When do several risks share a common cause?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-rsk-01/brief.json, ver-cy/world-models/card-supplements/em-rsk-01.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.