Asset management is presented as the true foundation of vulnerability management because organizations cannot protect assets they do not know exist. The article stresses that without accurate, up-to-date inventory data, vulnerability management produces only meaningless reports.
Data can be collected from multiple sources beyond vulnerability scanners: SIEM systems, NTA/NDR traffic analysis, Active Directory and CMDB, virtualization and orchestration platforms, cloud APIs, and manual input when automation is incomplete. Each source covers only part of the environment, so the central task is merging these fragments into one reliable picture while validating ownership and data accuracy.
A minimal asset record must include network address, MAC address, hostname, owner, department, and approval status. For vulnerability management three additional fields are essential: asset criticality that drives SLA requirements, a named responsible person or team for remediation, and the date of the last successful data collection. Without the last field, teams cannot distinguish between assets that have no vulnerabilities and assets the scanner has been unable to reach for months.
Why Categorization Matters
Assets are grouped by importance to focus limited resources on those involved in attack paths leading to unacceptable events. High-importance assets typically include perimeter web servers, network devices, VPN gateways, and critical business systems such as 1C:Accounting. Medium-importance assets provide indirect access, while low-importance assets do not lead to prohibited outcomes when compromised. Executive and chief accountant workstations are automatically treated as high importance because they often provide direct paths to key systems.
The guiding principle is to treat unknown assets as critical until proven otherwise. NIST CSF 2.0 and CIS Controls both recommend this conservative approach because the cost of an extra scan is far lower than the cost of a missed incident.
Regulatory Requirements
Russian regulations now explicitly require asset inventory. FSTEC Order No. 117 effective 1 March 2026 names inventory systems as a data source for configuration control. Monthly vulnerability detection and 24-hour remediation of critical issues become impossible when half the infrastructure remains unknown. Federal Law No. 58-FZ and Government Decree No. 1762 introduced industry-specific lists of critical information infrastructure objects, shifting categorization from self-defined analysis to comparison against official sector lists.
International standards impose similar obligations. CIS Controls v8.1 Control 1 requires accurate inventory of all corporate assets with semi-annual reviews and weekly reaction to unauthorized devices. NIST CSF 2.0 ID.AM-08 adds explicit lifecycle management, recognizing that decommissioning breaks asset data as severely as onboarding. ISO/IEC 27001:2022 A.5.9 and A.5.12 mandate inventories of information assets and their classification.
New Asset Types and Attack Surface Expansion
The asset landscape has changed dramatically. Forgotten cloud resources continue to incur costs and host real vulnerabilities for an average of 31 days before discovery. SaaS applications adopted by marketing, development, and HR teams often bypass IT registration yet contain corporate data. EU AI Act and ISO/IEC 42001 now require registers of AI systems, while NIST AI RMF pushes similar mapping requirements. Containers, Kubernetes clusters, IoT devices, and industrial control systems further expand the attack surface.
The article concludes that vulnerability management quality depends directly on the completeness, accuracy, and currency of asset data. Continuous reconciliation between CMDB, monitoring systems, and orchestration tools is necessary because no single source remains authoritative over time.
