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
Ideco NGFW Novum Earns Highest Customer Rating in Quadrant Technologies Import Substitution Study
Ideco NGFW Novum achieved the top customer score of 6.9 out of 10 in the Matrix of Import Substitution 2026: NGFW research conducted by Quadrant Technologies, surpassing the market average of 6.3 and outperforming seven competing Russian solutions. The study evaluated vendors based on specialized revenue alongside 18 criteria covering product quality and functionality, with ratings provided directly by specialists who deploy and operate the firewalls in production environments. Ideco excelled in 11 parameters above seven points, including administration convenience at 7.9, technical support and partner network at 7.6, Zero Trust segmentation at 7.3, and both integration capabilities and core NGFW functionality at 7.2. Despite strong product scores, Ideco remains in the Development quadrant rather than Leadership due to lower profile revenue volume, positioning the company as a prime candidate for advancement with increased sales and large-scale deployments. Complementary testing by Infosystems Jet laboratory showed Ideco NGFW Novum passing 189 of 242 checks under Methodology 3.0 and becoming the sole participant to complete an eight-hour stress test. The broader Russian NGFW market is shifting away from emergency import substitution toward demands for real-world stability, updates, documentation, support, and usability, with product cost cited as a rejection factor by 37.5 percent of respondents.
Kubernetes Audit Policy Review: Checklist Targets Common Blind Spots in Rules
An experienced Kubernetes administrator shared a detailed review process for audit policies that often remain untouched for years after initial deployment. The 580-line policy was rebuilt using the Kubernetes Threat Matrix from RedGuard as the primary reference. The author highlights recurring issues such as outdated exceptions, missing coverage for new components, and legacy comments that obscure actual security intent. The resulting checklist focuses on principles rather than cluster-specific findings to help other teams perform effective policy audits. Key recommendations address rule completeness, exception management, and periodic full-scale reviews instead of incremental patching. The approach aims to restore audit policies as active security controls rather than accumulated technical debt.
Avoiding a Leaky Kubernetes Audit Policy: Real-World Configuration Breakdown
Kubernetes Audit Policy is typically configured once during cluster setup and then left untouched for years while accumulating exceptions for new components. Over time the policy stops functioning as a security control and instead becomes an archaeological layer of outdated comments such as "# temporary, TODO remove" that date back three years or more. The author recently reviewed their own 580-line configuration file that had been assembled from multiple sources. Primary reference was the Kubernetes Threat Matrix, which explains why many rules are designed to detect security-relevant actions rather than simply reduce log noise. Examples include targeted monitoring of RBAC modifications and deletion of events. The article emphasizes the need for periodic full reviews instead of incremental patching to maintain effective detection coverage.
CryptoPro Develops CryptoPro-Browser with Russian Cryptography for FSB Compliance
CryptoPro is creating its own browser called CryptoPro-Browser as part of the CryptoPro CSP 6.0 cryptographic information protection system. The product will include built-in cryptographic tools, support for the company's plugin, and TLS connections using Russian cryptographic algorithms. The development follows Google's removal of the CryptoPro extension from the Chrome Web Store in February 2025, which left new users without an easy installation method. The project has been coordinated with the FSB of Russia and targets scenarios requiring compliance with Russian information security regulations. CryptoPro plans to incorporate experience from its earlier Chromium-Gost project started in 2017, while also recommending Yandex Browser as an alternative. Analysts estimate the development cost at several tens of millions of rubles, with the main focus on corporate customers needing certificate management and specialized support.