Vulnerability, affectedness and remediation
Vulnerability description, affectedness assessment, priority and remediation confirmation. A discovered weakness is not identical to its exploitation.
Bundle → Layer → Finding → Questions Filled
2 bundles · 3 layers · 4 findings · 9 questions
Vulnerability and affectedness This bundle describes a vulnerability and assesses affectedness in a specific context.
Vulnerability record
This layer records the vulnerability scope and the conditions governing affectedness.
Identifiers
This finding identifies the vulnerability and its component scope.
- Which identifiers refer to this vulnerability?
- Which component and version ranges does this vulnerability concern?
Affectedness
This finding assesses whether the specified component version is affected in the recorded context.
- Is the component version in this assessment actually affected in its recorded context?
- Which configuration or code reachability conditions support the affectedness conclusion in this assessment?
Priority and remediation This bundle records contextual priority and evidence that remediation addresses the vulnerable condition.
Priority
This layer distinguishes generic severity from contextual risk and exploitation evidence.
Contextual risk
This finding records the basis for prioritising the assessed vulnerability.
- What generic severity score and contextual risk are recorded in this assessment?
- What evidence of exploitation in the wild or in the assessed environment supports this assessment?
Remediation proof
This layer verifies remediation through a fixed version, component removal or correction of a vulnerable configuration.
Remediation in production
This finding establishes whether the corrective action eliminated the vulnerable condition within the assessed production scope.
- Which corrective action in this remediation record addresses the vulnerable condition through a fixed version, component removal or configuration correction?
- Which instances within this remediation record's scope still retain the vulnerable condition?
- Does this remediation record establish that the vulnerable condition was eliminated, or does it rely only on a closed ticket?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseTEC
- Industry
- Cross-industry
- Tags
- EM-TEC-07W2subjectVulnerabilityAffectednessAssessmentRemediationExploitEvidence
What it is Filled
Vulnerability description, affectedness assessment, priority and remediation confirmation. A discovered weakness is not identical to its exploitation.
Why it exists Filled
Vulnerability description, affectedness assessment, priority and remediation confirmation. A discovered weakness is not identical to its exploitation.
Distinguishing features Filled
- A discovered weakness is not the same as its exploitation or an incident.
- Affectedness is assessed for a specific version and context, not inherited from the component name.
- Remediation requires evidence that the vulnerable condition was eliminated through a fixed version, component removal or configuration correction, and a closed ticket alone is insufficient.
- CVE is one admissible identifier among others such as vendor advisories.
What robots and AI may and may not do Filled
Must not
- Treat a CVE in a transitive dependency as a confirmed incident.
- Mark a vulnerability remediated because its ticket is closed.
- Use a generic severity score as the contextual risk without assessment.
- Probe or exploit systems to test affectedness without authorisation.
- Publish unpatched vulnerability details outside the agreed disclosure process.
Only with a human decision
- Accepting the risk of an unremediated critical vulnerability.
- Disclosing a vulnerability to external parties.
May
- Match SBOM components against known vulnerabilities and list candidate exposures.
- Record affectedness assessments with the conditions they depend on.
- Report instances still running unfixed versions.
Moral aspects Filled
- Unpatched systems expose users' data and safety.
- Careless disclosure can arm attackers before fixes exist.
- Over-alarming reports waste effort and erode trust in real warnings.
Who is affected
- Users of affected software
- Operators and security teams
- Upstream maintainers
Owners Filled
Steward
The CTO, the CIO or the service owner accountable for the system.
Master systems
- Software catalogue
- Source control
- CI/CD pipeline
- CMDB
- Observability platform
Links to other meta-models Filled
neighbor
- EM-TEC-01
references
- WM-SFT-006 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by CVE or another advisory identifier; assessments by vulnerability, component version and context.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A record names an advisory identifier, an affected component version range and a status.
- Often confused with a security incident or with a scanner finding.
Capabilities and actions required Filled
- SBOM-based matching narrows which products may be affected.
- Not-affected statements can be published with their justification.
Hazards and failure modes required Filled
- Alert floods from unassessed scanner output.
- False closure when tickets close before instances are updated.
- Premature disclosure of exploitable details.
Standards and interfaces required Filled
- CVE Program identifiers for publicly known vulnerabilities.
- FIRST CVSS for generic severity scoring.
- OASIS CSAF for security advisories including VEX statements.
- MITRE CWE for weakness types.
Context of use required Filled
- Used by product security, vulnerability management and operations teams.
- Coordinated disclosure norms and regulation increasingly require handling records.
Sources Filled
- AISMM/WM-SFT and ArchiMate: product, system and architecture
- CSDM: business application, service and runtime instance
- SPDX/OpenTelemetry/Google SRE: delivery, observation and reliability; choose by boundary
- OASIS Common Security Advisory Framework Version 2.0 - Checked live (HTTP 200) on 2026-10-07.
- SPDX Specification - Checked live (HTTP 200) on 2026-10-07.
Open questions
- When is a component version actually affected?
- How to distinguish generic severity from contextual risk?
- How to prove a fix in production?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-tec-07/brief.json, ver-cy/world-models/card-supplements/em-tec-07.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.