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
Passphrases vs. Leetspeak Passwords: Why Four Random Words Outperform P@ssw0rd!2026
The article explains why a passphrase made of four randomly selected words provides far greater resistance to offline attacks than a complex-looking password constructed with substitutions and appended symbols. It details how password strength is measured in bits of entropy rather than visual complexity, showing that four words drawn from a 50,000-word list yield approximately 62 bits while common leetspeak transformations add almost none. The piece contrasts fast legacy hashing with modern slow algorithms such as Argon2 and emphasizes the protective effect of per-password salting. It criticizes registration forms that reward predictable patterns and highlights NIST guidance favoring length over mandatory character rotation. The author recommends diceware-style generation for master passwords and password managers for everything else, noting that passkeys ultimately eliminate the need for memorizable secrets altogether.
Building the Foundation of Digital Trust: Why Identity Security Remains Undervalued
Identity Security is presented as one of the most underestimated pillars of cybersecurity because granting access involves trusting individuals with sensitive information and systems. The article examines the deep intersection of IT and security functions, the costs of manual access errors, and the need to align business processes with technical controls. It references a 2026 Identity Conf study showing 43.5% of organizations experienced errors in manual rights assignment and 33.5% left access for former employees. Recommendations draw on NIST Human-Centered Cybersecurity concepts, SP 800-53, and Russian FSTEC Order No. 117 to design lifecycle processes covering account provisioning, privilege reviews, and continuous monitoring. Models such as RBAC and ABAC are discussed alongside IGA and IdM solutions to ensure business permissions map correctly to application rights. The piece stresses that successful projects require joint IT and security efforts from the initial survey through pilot and acceptance phases while measuring both risk reduction and operational efficiency.
VK Files Lawsuit in EU Court Seeking to Overturn Sanctions Imposed in July
Russian internet company VK has submitted a formal challenge to the European Union's sanctions regime by filing a case with the Court of Justice of the European Union. The company argues that the restrictions placed on VK and its subsidiary Communication Platform LLC are both unjustified and unlawful. The lawsuit, registered under case number T-664/26 on 7 October, directly contests the July sanctions that targeted the developer of the MAX messenger. Earlier restrictions had already led to the removal of multiple VK ecosystem applications from Apple App Store and Google Play, forcing users toward alternative distribution channels such as RuStore, Huawei AppGallery, Samsung Galaxy Store and Xiaomi GetApps. While installed Android applications continue to function and receive updates, iOS users face disrupted push notifications after the apps were delisted. The legal action itself does not automatically restore app availability in the affected stores.
VPN Rules in Russia 2026: No Fine for Ordinary Users but Strict Penalties for Advertising and Extremist Content Access
As of September 2026, Russia maintains no separate administrative fine for ordinary citizens simply connecting to a VPN service. Responsibility arises only for specific actions such as deliberately searching for known extremist materials, advertising tools to bypass restrictions, or failing to comply with Roskomnadzor demands as a service operator. Corporate VPNs used for remote access to company networks remain fully legal under exceptions in Article 15.8 of Law No. 149-FZ. New provisions in the Code of Administrative Offenses, including Articles 13.53, 13.52 and 14.3 introduced by Laws 281-FZ and 282-FZ, impose fines ranging from 3,000 to 500,000 rubles depending on the violation and the offender category. The rules distinguish clearly between end users, service owners and advertisers. VPN technology itself is not banned, yet public services face ongoing blocking and operators must integrate with state filtering systems. The material reflects the regulatory situation on 24 September 2026.