Kwetsbaarheden en dreigingen volgen
Review threat posture · Trace threat evidence
Voor wie
Beheerders, medewerkers en IT-teams die ITLedger gebruiken voor dienstverlening, assets, compliance en rapportages.
Taken
Kies je taak. De volledige werkwijze, voorwaarden en aandachtspunten staan hieronder in het Engels.
Review threat posture
Review threat posture.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- Threat detection depends on trustworthy CPE mappings; unmapped or unconfirmed products reduce coverage.
- The Vulnerability Risk widget only reflects open findings that have been scanned into asset vulnerability records.
- KEV and ransomware-linked signals should drive prioritization, but teams still need to consider business context and exposure path.
- A clean asset vulnerability tab means no active findings were returned for that mapped asset, not that the entire environment has no risk.
- Open the dashboard and add or review the Vulnerability Risk widget.
- Check whether exposure is concentrated in critical, KEV, or ransomware-linked findings.
- Open the affected asset record and review the Vulnerabilities tab.
- Update the finding status as it moves through acknowledged, remediated, or accepted risk.
- Use CPE Mapping Coverage and Vulnerability Registry views to close mapping gaps that reduce detection quality.
Expected outcome: The user has reviewed the result of review threat posture in the application.
Trace threat evidence
Trace an asset finding back to its observed version, confirmed product mapping, scan time and vulnerability evidence. Risk signals help prioritization and do not by themselves prove an incident.
Who can do this: Tenant administrator, Operator
Before you start
- Use an account with access to the stated page and permission for the chosen action.
Safeguards
- Threat detection depends on trustworthy CPE mappings; unmapped or unconfirmed products reduce coverage.
- The Vulnerability Risk widget only reflects open findings that have been scanned into asset vulnerability records.
- KEV and ransomware-linked signals should drive prioritization, but teams still need to consider business context and exposure path.
- A clean asset vulnerability tab means no active findings were returned for that mapped asset, not that the entire environment has no risk.
- Open the affected asset record and review the Vulnerabilities tab.
- Inspect CVE ID, alert level, CVSS, EPSS, KEV status, ransomware-use signal, affected versions, and scan date.
- Use the Mapping action if the product mapping needs review or confirmation.
- Use CPE Mapping Coverage and Vulnerability Registry views to close mapping gaps that reduce detection quality.
Expected outcome: The user has reviewed the result of trace threat evidence in the application.
Aanbevolen werkwijze
- Wijs eigenaren toe voor bewijs en herstelwerk.
- Controleer verouderde informatie vóór gebruik bij een audit.
Gerelateerde handleidingen
Lees verder in Compliance
Bewijs, NIS2, risico’s, gegevensprofielen en kwetsbaarheden.