Why Vulnerability Management Specialists Must Master Compliance: Closing All CVEs but Leaving admin:admin
Compliance has become a core component of vulnerability management rather than a separate bureaucratic task. Russian organizations now face real financial and criminal consequences for failing to meet regulatory requirements on vulnerability handling and system configuration.
Over the past years regulators have significantly raised the stakes. FSTEC Order 117, effective from 1 March 2026, makes vulnerability management mandatory for state systems with strict deadlines: 24 hours for critical vulnerabilities and 7 days for high-severity issues. Turnover fines for personal-data leaks introduced in May 2025 range from 3 to 15 million rubles for the first incident and up to 1–3 % of annual revenue for repeat violations. Presidential Decree No. 250 assigns personal responsibility to deputy heads of organizations for information security and bans the use of protective equipment from unfriendly countries starting 1 January 2025.
Three main approaches to building compliance exist. The first is to rely on historical practices only, which is now considered high-risk. The second follows regulator requirements from FSTEC and the Central Bank of Russia, creating internal standards and checking systems against them. The third uses international benchmarks such as CIS Benchmarks, although full compliance across thousands of hosts is practically impossible and organizations realistically achieve around 70 % coverage.
The recommended path is to develop an organization-specific standard that reflects its threat model. CISO and compliance specialists jointly define requirements, document change procedures, run continuous checks, and agree on SLAs for remediation. Automated tools such as MaxPatrol HCC, RedCheck, ScanOVAL, and modules in R-Vision and Security Vision perform configuration scanning and generate reports.
A more mature approach shifts compliance left by embedding controls into golden images built with Packer, Ansible or similar tools. These pre-hardened images are then deployed through CI/CD pipelines, reducing configuration drift. Regular scanning remains necessary because systems still deviate over time.
The article concludes with a practical warning: even a fully patched firewall offers no protection if it retains the password admin:admin. Configuration errors such as weak credentials and exposed management interfaces constitute exploitable vulnerabilities and must be treated as part of the vulnerability management process alongside CVE remediation.
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.