Topic
Sber
PSLC and Agent-Ops: From Product Support to Infrastructure Transformation
Other
GigaChat Creates New Continuation of Gogol's Dead Souls Under Expert Supervision
Other
Russia Weighs Mandatory Use of Sovereign AI Models Like GigaChat in Government Sectors
OtherIT Elements 2026 to Stage IT Apocalypse Simulations and Critique Russian Vendors
The IT Elements 2026 conference has unveiled its full program, centering on business continuity after successful cyberattacks, infrastructure failures, or technological disasters. Scheduled for September 9-10 at the Serp i Molot cultural center in Moscow, the event will host over one hundred reports, discussions, demonstrations, and master classes. The opening plenary will examine whether the primary-backup data center model remains viable, if the 3-2-1 backup rule still protects against modern ransomware, and whether CIOs or CISOs should own cyber resilience. Practical sessions will demonstrate a full Microsoft migration in 60 minutes, moving Exchange and MinIO to Russian alternatives, and a detailed review of domestic hyperconvergence strengths and weaknesses. Comparative test results for routers, NGFW, and VM systems will be presented without marketing gloss. Additional tracks will cover monitoring of corporate AI models from GPU to prompt under FSTEC Order No. 117, OWASP Top 10 for LLM, and MITRE ATLAS, alongside real-world cases from Rosatom, Beeline, Sber, and T-Bank. Trubnaya Metallurgicheskaya Kompaniya will simulate a 48-hour IT outage and show how to restart operations in half a day.
2.2 Million Line Vulnerability Report: What Happens After Discovery and How to Turn Findings Into Action
A massive vulnerability scan produced an 1,819-page report and a 2.2-million-row Excel file that exceeded spreadsheet limits, highlighting the gap between detection and remediation. The article explains that finding vulnerabilities accounts for only 10 percent of the work, while the remaining 90 percent involves prioritization, remediation, verification, and ensuring issues do not reappear. Research from BI.ZONE, Sber, Qualys, Cyentia Institute, Kenna Security, and Hadrian shows that organizations can typically remediate only one in ten open vulnerabilities per month and that Time-to-Exploit has dropped dramatically, with many edge-device flaws exploited on the day of disclosure. The piece stresses that continuous scanning, full infrastructure coverage including shadow IT, and separate high-frequency perimeter scans are essential because 85 percent of KEV-vulnerable assets remain unpatched at disclosure time. It recommends replacing bulky reports with concise, role-specific registries that answer four questions: what to do, where to do it, by when, and the consequences of inaction. Three legitimate outcomes for every vulnerability are outlined: patching, compensating controls, or formal risk acceptance with defined review dates, while false positives such as orphaned OpenSSL libraries must be cleaned rather than ignored.