Natalia Kasperskaya Advises Against Mass Biometric Rollout in Russia Citing High Costs, Reliability Issues and Deepfake Threats
Natalia Kasperskaya, president of InfoWatch and chair of the board of the Domestic Software association, has cautioned against the indiscriminate rollout of biometric authentication systems throughout Russia, describing the approach as both costly and insufficiently secure.
In an interview with TASS, Kasperskaya stated that mass adoption of biometrics represents an expensive and not particularly reliable undertaking. She recommended restricting its use to selected processes and employing it solely as an additional layer of identity verification rather than a universal solution.
One of the principal obstacles, she noted, is the substantial financial outlay required. Facial recognition systems generate a digital model of a person’s face using thousands of reference points. Face ID, for example, projects more than 30,000 invisible points onto the user’s face. Scaling comparable technology nationwide would demand significant computational resources and vast data-storage infrastructure.
Practical challenges further complicate deployment. Biometric performance depends heavily on camera quality, lighting conditions and the clarity of the original image. Attempts to enrol or authenticate using older smartphones in dimly lit environments frequently fail to produce usable results.
An additional and increasingly serious threat comes from deepfakes. Artificial images and videos are becoming progressively more convincing, to the point where the human eye can no longer reliably differentiate between genuine photographs and sophisticated fakes. This development complicates identity verification and creates fresh opportunities for fraudsters.
Consequently, Kasperskaya sees no justification for positioning biometrics as a universal key for all services. In her view, the technology should be applied selectively and should complement, rather than replace, existing identification methods.
Russia already operates the Unified Biometric System, which allows citizens to access Gosuslugi, obtain electronic signatures or eSIM cards, and perform certain banking operations such as opening accounts or obtaining loans.
Related articles
SOC Forum 2026: Experts Warn Generative AI Lowers Attacker Skill Barriers While Raising SOC Complexity
At SOC Forum 2026 in Moscow, cybersecurity leaders examined how generative AI reduces the expertise needed for cyberattacks while complicating defensive operations. BI.ZONE's Oleg Skulkin noted that AI has effectively lowered attacker preparation requirements to near zero. Kaspersky researcher Georgy Kucher warned that unverified AI-generated code can expose threat actors, and overly perfect Russian-language phishing text now triggers suspicion. Solar Group’s Alexander Shepilov advocated treating AI agents as distinct non-human identities with strictly limited privileges. Alexander Kuznetsov from the same company recommended gradual automation of SOC tasks rather than abrupt AI integration. Participants also cautioned that managing AI agents may increase spending on skilled personnel instead of delivering cost savings.
Anthropic's Research Claude Model Generates Exploit Bypassing Linux Protections for Root RCE via MPTCP and CVE-2026-98432
Anthropic's internal research model of Claude autonomously wrote an exploit that achieved remote command execution with root privileges on a Linux server configured with multipath TCP (MPTCP). The exploit targets CVE-2026-98432, a use-after-free vulnerability in the Linux kernel's networking stack that occurs during parallel TCP request processing. The attack first bypassed KASLR in 48 minutes to locate the required kernel address, then took an additional five minutes to seize control and execute commands as root without any password or user interaction. Anthropic disclosed the results in a technical report but noted that the experiment used an unreleased model and cannot be reliably reproduced with public chat interfaces. The Linux team rated the flaw 9.8 on CVSS while Red Hat assigned it 5.9, citing exploitation complexity; a patch has already been merged into mainline and stable branches, though users must verify updates from their distribution vendor.
Local LLMs in AppSec: What Open Tools and Models Can Handle in Application Security
The article examines how local large language models can be integrated into application security workflows without relying on cloud subscriptions. It traces the evolution from llama.cpp in 2023 through agentic frameworks like PentAGI and Strix in 2025-2026. Teams can now run models on local hardware, connect them to code analyzers such as Semgrep, and delegate specific tasks like vulnerability path reconstruction or multi-step application testing. The piece highlights practical scenarios including static code review, dynamic testing with browser and terminal agents, and security evaluation of embedded AI assistants using tools like Garak and PyRIT. It stresses the importance of task decomposition, context management, and verification of model outputs to avoid misleading results. Hardware performance, model selection, and custom agent configurations are presented as key factors for successful adoption.
From Accessible to Controllable: Ruishu Information Launches AITM for AI Agent Lifecycle Security
As AI Agents become digital employees in enterprise R&D, office, and business workflows, organizations must now ensure they are manageable, controllable, and auditable. A multinational consulting firm’s internal AI platform was compromised by an autonomous agent attack that progressed from interface reconnaissance to vulnerability exploitation and database read-write access. Conventional scanners missed the injection points, but the agent inferred query structures from database error messages. Ruishu Information has responded with its Agent Intelligent Lifecycle Management system (AITM), which enforces security across admission, runtime, permissions, and data flows. The platform combines static scanning, behavioral analysis, semantic judgment, and sandbox execution for pre-deployment checks, followed by continuous runtime validation and LLM data-plane protection. AITM applies HMAC-SHA256 signatures, tool whitelists, PII tokenization, and four-stage Trace auditing to reduce blind spots throughout the agent lifecycle.