Asset Management as the Foundation of Vulnerability Management: Unknown Assets Cannot Be Protected
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.
Related articles
Protecting Data Centers from Kinetic and Cyber Attacks: What Regulators Worldwide Are Proposing
InfoWatch experts have updated their April report on data center resilience, highlighting how physical and cyber threats now directly threaten business continuity and national security. Regulators in the United States, European Union, and Russia are treating data centers as strategic infrastructure requiring layered defenses that combine physical hardening, geographic distribution, and strict cybersecurity controls. The United States has launched the Cyberstrategy for America 2026 emphasizing offensive operations, Zero Trust modernization, and supply-chain restrictions. The European Union is implementing ProtectEU and the Cyber Solidarity Act with real-time threat sharing and mandatory resilience standards under DORA. Russia is advancing technological sovereignty targets, new siting rules for data centers, and Presidential Decree No. 604 that enables temporary state management of inadequately protected critical facilities. The report also notes growing recognition that attacks on data centers can constitute acts of aggression under the Tallinn Manual.
US Department of Homeland Security Orders Federal Agencies to Remove DeepSeek Products
The US Department of Homeland Security issued an order on October 19 requiring federal civilian agencies to cease purchasing products from DeepSeek and to remove related technology from government systems. The directive, published the following day, targets Hangzhou DeepSeek Artificial Intelligence, its affiliates, and any third-party products or services built on DeepSeek implementations. The measure stems from the Federal Acquisition Supply Chain Security Act of 2018 and follows a recommendation by the Federal Acquisition Security Council, though no specific incidents or evidence were detailed in the notice. The restriction applies only to federal environments and does not prohibit private sector or individual use outside government systems. No removal deadline was set, and the document does not name the signing authority. The order is filed under docket DHS-2026-0628 with the CISA implementation team listed as the contact point.
AKIT Requests Temporary Permission for Russian Companies to Transfer Personal Data Abroad After Data Center Incidents
The Association of Internet Trade Companies (AKIT) has sent a formal letter to Russian Prime Minister Mikhail Mishustin proposing a temporary exemption from strict data localization rules. The measure would allow affected companies to move critical systems and Russian citizens' personal data to data centers in friendly countries when domestic infrastructure is unavailable due to accidents or damage. Members including Ozon, Wildberries, Cooper, and Yandex Market argue that services must continue operating even if Russian facilities are compromised. The proposed special regime would apply only after an officially confirmed incident, require compliance with information security standards, and end no later than March 1, 2028. After recovery, companies would be required to return to normal data processing within Russia. Expert Alexey Muntyan noted that the mechanism activates only after incidents occur and questioned whether countries should be selected based on data protection levels rather than political alignment.
Anthropic Model Reconstructs NSA Seeds for NIST Elliptic Curves in Under 30 Minutes
An internal Anthropic research model traced the origins of the five seeds used by the NSA to generate the NIST elliptic curves P-192, P-224, P-256, P-384, and P-521. The discovery resolves a 25-year-old question that arose when the curves were standardized in FIPS 186-2 for ECDSA in 2000. Researchers combined analysis of 1990s random number generators, 34 generator-output combinations, and lattice reduction techniques to identify lrand48 initialized with Unix timestamps from May 1997 to April 1998. The P-256 seed corresponds to the 1842nd candidate from a run started on 16 August 1997, and example seeds from ANSI X9.62 follow the same pattern. The work does not demonstrate any cryptographic break or backdoor in the curves and does not recommend changes to production systems. Several questions remain open, including the seed for curve B-163 and the reason certain candidate values were discarded.