Astra Cloud Launches Attested Secure Cloud to Accelerate FSTEC Compliance for Russian Government Systems
Astra Cloud, a division of the Astra Group, has launched a new "Protected Attested Cloud" platform intended for the deployment of state information systems, ISPDn, medical platforms, and other environments handling sensitive data.
The infrastructure has successfully passed attestation according to FSTEC Russia Order No. 117, achieving protection class K1, and Order No. 21, reaching protection level UZ-1. Clients can now use this pre-certified environment when attesting their own contours, which the company estimates will accelerate the overall procedure by three to five times.
Although the service removes the need to build infrastructure components from scratch, each customer's information system must still undergo its own attestation process. The offering includes a full set of certified protection tools such as firewalls, antivirus software, intrusion detection and prevention systems, trusted boot facilities, and SIEM solutions.
Access to the cloud is permitted exclusively through protected channels based on certified cryptographic information protection tools. The entire infrastructure resides in a Tier IV data center constructed using domestic hardware.
The solution targets organizations required to comply with FSTEC Russia regulations but unwilling to construct their own protected data centers, purchase separate security products, or expand their information security teams.
Starting 1 March 2026, Order No. 117 replaces Order No. 17 and extends its requirements beyond state bodies to subordinate institutions and companies interacting with the state segment. Critical vulnerabilities must now be remediated within 24 hours, and protection metrics must be reviewed regularly.
Possible use cases include hosting AI services with sensitive data, fulfilling regulatory prescriptions, and launching projects that require an attested contour, as well as participating in government tenders.
Related articles
Russian Businesses Face 50-Ruble Fee per MVD Query for Passport and Residence Checks
The Russian government has backed a proposal requiring businesses to pay 50 rubles for each completed session querying Ministry of Internal Affairs databases. The fee covers checks on Russian passport validity, residence registration, residence permits, and foreign citizen migration records. Projected annual budget revenue reaches 120 billion rubles. Companies must still perform client identification under Federal Law 115-FZ and the Law on Communications, with fines up to 0.1 percent of own funds for banks or 500,000 rubles for telecom operators. Smart Engines highlights its Sherlock anti-fraud platform as a local alternative that detects over 600 forgery indicators, including deepfakes and NFC chip tampering, without repeated paid queries. The company cites a June 2026 legal opinion from the National Council of Financial Markets confirming that such tools can satisfy compliance requirements.
Russian Court Convicts Former IT Director for Unauthorized Access to Huawei Storage After Moving Servers Offsite
A former IT director at an Omsk manufacturing plant was found guilty under Part 3 of Article 272 of the Russian Criminal Code for blocking and modifying data on a Huawei Dorado 3000 v6 storage array after relocating the entire server infrastructure to a privately rented office. The court relied heavily on detailed logs from the Huawei system that recorded the exact sequence of disk removals, reinsertions in altered order, and the shutdown command, even after the administrator attempted to delete portions of the event journal. The incident occurred on the same day new management took over, causing immediate loss of access to corporate email, 1C systems, design software, and shared network resources. Despite the defendant's claims that he was preparing the array for cloud backup and that a script had frozen, the court rejected the explanation based on audit concealment, lack of notification to owners, and post-incident behavior. The ruling imposed a 400,000-ruble fine and a one-year ban on computer-information work involving protected secrets, while leaving a civil claim for 18.27 million rubles in recovery costs for separate proceedings. The case highlights how storage-array logs can serve as decisive forensic evidence and underscores the legal risks of retaining physical or logical access after employment ends.
False 50,000 Ruble Fine Claims Circulate About Russia's Unified Bank Card Registry
Social media posts falsely warn Russian citizens of a 50,000 ruble fine for failing to submit personal bank card data to a new unified registry. The claims have been identified as fabricated, with the project "Lapsa Media" noting that the accompanying images were likely generated by AI and contain multiple errors and typos. In reality, individual citizens are not required to take any action, as banks themselves will transmit the necessary information. The Bank of Russia has confirmed that banks must upload card numbers, card types, and owners' INN identifiers to the system operated by NSPK no later than September 1, 2027. Starting on that date, banks will begin enforcing a limit of 20 cards per client to hinder mass issuance of cards for fraudulent purposes. Previously issued cards exceeding this limit will remain valid and will not be forcibly closed.
Webiomed AI Platform Processes Millions of Medical Records Daily on Certified RED OS Infrastructure
The Russian Webiomed platform now serves more than 4,000 medical organizations across 55 regions and supports over 300,000 physicians. Its algorithms analyze up to one million electronic health records every day, generating recommendations that physicians must review and approve. The entire server infrastructure runs on RED OS, which holds FSTEC Russia certification for use in critical information infrastructure. Legal responsibility for any harm remains with the medical organization and, in some cases, the individual physician, even when AI suggestions are involved. The article highlights risks such as incomplete data, synchronization errors that could revoke physician access via RED ADM directory services, and the need for selective recovery tools like Granulex Recovery. Joint testing by MDIS and RED SOFT confirmed that Granulex Recovery can restore specific objects and attributes without stopping the directory service. Questions remain about where liability falls when errors occur at the intersection of the algorithm, medical systems, and underlying IT infrastructure.