US Mandates Removal of Acronis from Federal Systems by January 2027 Over Russian Ties
US federal civilian agencies have been directed to remove Acronis products from their information systems by January 27, 2027, with new acquisitions also banned. The order, issued by the Department of Homeland Security, applies to Acronis AG and its related entities including Acronis Inc. and Acronis SCS.
The directive was signed on July 31 but only published in the Federal Register on October 30. It stems from a review lasting nearly a decade that focused on potential ongoing Russian developer involvement in the code and the adequacy of supply chain risk reductions. No concrete evidence of backdoors linking products to Moscow was disclosed by the sources cited by Nextgov/FCW.
Following the 2022 events, Acronis halted its operations in Russia and relocated its specialists to other countries. In 2025, Swedish investment firm EQT acquired a controlling stake, a transaction that received approval from the CFIUS committee. The company states that more than 75 percent of its shares are now held by Western investors.
Despite these changes, the measures were deemed insufficient for continued presence in federal systems. Purchasing the software through intermediaries is also prohibited under the new rules. The restrictions do not apply to the broader private-sector market in the United States.
Related articles
Russian CA TCI Integrates ACME Protocol to Automate TLS Certificate Issuance
The Technical Center Internet (TCI), part of RTK-COD, has deployed a production ACME server compatible with standard clients such as acme.sh, Certbot and lego. The implementation aligns the ACME state machine with the existing isolated signing infrastructure, Domain Control Validation mechanisms and mandatory Certificate Transparency logging to Yandex and VK CT logs. Certificate lifetimes are shortening industry-wide, with Web PKI limits dropping to 47 days by 2029, making manual issuance unsustainable. The service supports HTTP-01 and DNS-01 challenges, ECDSA P-256 keys and certificate revocation, while preserving the requirement for Subject/CN in CSRs and mandatory revocation reasons. A separate staging environment uses an internal CT log simulator for safe testing. Future plans include full multi-SAN support, ARI (RFC 9773) and removal of the Subject/CN restriction.
Russia Pushes Corporate Multibanking Forward with Updated Open API Standards
The Bank of Russia and AFT have advanced Open Banking standards that enable corporate clients to aggregate account data across multiple banks within a single interface. The new specifications cover consent management, security profiles based on STO BR FAPI and OpenID Connect, and account information retrieval for both individuals and legal entities. While the 2025 pilot results demonstrated practical use cases such as personal financial assistants and corporate multibanking, the updated standards effective from October 2026 still lack a unified initiation-of-transfer component. Developers must therefore combine the new account-data APIs with separate bank-specific payment initiation mechanisms. The article explores how accounting systems or independent fintech services could become the primary workspace for financial directors managing payments, payroll, and liquidity across several banks. It also examines real-world challenges including idempotency handling, status reconciliation after network failures, and the separation of application permissions from signer authority. Examples from the UK Open Banking Limited sweeping VRP statistics illustrate how pre-authorized variable recurring payments can streamline operations while highlighting the additional policy work required for corporate supplier payments in Russia.
Hacker Attacks as Force Majeure: Russian and International Courts Diverge on Liability for Cyber Incidents
In November 2026, Russian hosting provider Beget suffered a major cyber attack that disrupted websites, virtual servers, email, DNS, and control panels for thousands of clients. Beget notified customers of circumstances resembling force majeure under Article 401 of the Russian Civil Code but stopped short of claiming automatic court recognition. Russian courts have reached inconsistent rulings on whether DDoS attacks and ransomware qualify as extraordinary and unavoidable events, examining factors such as attack scale, provider preparedness, and contractual obligations. International cases from France, Norway, the United States, and the Netherlands further illustrate that outcomes depend on evidence of prior security measures, backup integrity, and specific contractual language rather than the mere occurrence of an attack. Key precedents include disputes involving Timeweb, Expeditors, and Nordlo Haugesund where liability was limited or denied despite confirmed incidents. The analysis shows that even when force majeure is rejected, clients often struggle to recover full losses due to liability caps and proof requirements. Businesses are advised to maintain independent backups, review service agreements, and document incidents thoroughly to protect against financial exposure.
Google to Back Unified robots.txt Standard for Blocking AI Training Data Use
Google has announced plans to support a common mechanism in robots.txt that allows website owners to opt out of having their content used for training generative AI models. The feature will be based on work by the AIPREF working group at IETF and is scheduled for rollout in 2027. Instead of issuing separate instructions to each AI provider, publishers will be able to set a single policy marker that participating companies are expected to respect. Google intends to treat an unspecified general marker the same way it currently handles its own Google-Extended directive. Existing per-company rules will continue to function, letting site owners combine a broad default with specific exceptions. The approach simplifies management as the number of AI crawlers grows, though compliance will remain voluntary and dependent on which organizations adopt the standard.