Wildberries and Ozon to Accept Digital Rubles from September 1, 2026
Wildberries and Ozon will enable payments using digital rubles starting September 1, 2026. Home users, corporations, fraud protection, payment security, and compliance with Russian legislation are among the key aspects highlighted in the announcement.
Marketplaces have confirmed preparations for the new payment method. Ozon will first activate the digital ruble in test mode, placing it next to bank cards and other payment options. The company then intends to open the feature gradually to all customers, according to RIA Novosti. Wildberries shared no additional details but stated it will meet the requirements of the Bank of Russia and applicable regulations.
From the same date, the largest banks must allow clients to open digital wallets, transfer funds, and pay for goods. Users will access the new currency form through their usual banking application connected to the Central Bank platform. For citizens, operations with digital rubles will stay free of charge.
Mandatory Implementation Timeline
The marketplaces' launch is not a voluntary crypto experiment. Per Bank of Russia rules, from September 1 trading companies with revenue above 120 million rubles must accept digital rubles if serviced by major banks. In 2027 the requirement will extend to sellers with annual revenue over 30 million rubles, and in 2028 to all remaining businesses. Companies with turnover below 5 million rubles are exempt from mandatory connection.
The digital ruble will become the third form of Russian currency alongside cash and regular bank account money. Buyers will not be forced to switch; cards and other payment methods will remain available. The Bank of Russia has also promised banking secrecy for digital ruble holders.
Related articles
Incident Reconstruction Fails When Logs Lack Time Zone Offsets and Proper Synchronization
Reconstructing security incidents from multiple log sources often collapses when timestamps lack time zone information or consistent synchronization. Events from web servers, load balancers, applications, and mail gateways can appear in physically impossible order, such as responses preceding requests or sessions closing before they open. The root causes include clock drift without NTP, mismatched reference points like UTC versus local time, and timestamps recorded at message processing rather than event occurrence. Classic BSD syslog (RFC 3164) omits both year and offset, forcing investigators to consult potentially unavailable source systems. Modern RFC 5424 provides full timestamps with offsets, making normalization possible without external context. Organizations must enforce offset-inclusive formats at ingestion, monitor actual synchronization status rather than service uptime, and document external sources whose timestamps cannot be controlled.
HTTP Methods Explained: GET, POST, PUT, PATCH, DELETE and the New QUERY Standard
HTTP methods define the actions a client requests from a server regarding a resource. The core semantics are outlined in RFC 9110, with extensions for specialized protocols. A new standardized method called QUERY was introduced in June 2026 via RFC 10008 to handle complex queries that include a request body while remaining safe and idempotent. The article details safe and idempotent properties, compares each method including GET, HEAD, POST, PUT, PATCH, DELETE, OPTIONS, TRACE, CONNECT, and QUERY, and explains their correct usage to avoid breaking caches, proxies, and infrastructure expectations. It also covers WebDAV extensions and other registered methods in the IANA registry.
From Web Perimeter Breaches to Domain Takeover: How Standoff Hackbase Trains Pentesters on Real Corporate Infrastructure
wr3dmast3r, a senior pentester and BSCP certification guide author, rose to first place on the Standoff Hackbase ranking by shifting focus from initial perimeter access to full internal infrastructure compromise. The platform replicates large-scale corporate networks from various industries, forcing participants to map service relationships, harvest credentials, escalate privileges, and chain pivots across segments. Unlike CTF challenges that end with a single flag, Hackbase tasks require building complete attack paths that can lead to data theft, process disruption, or cross-domain movement. The interview highlights practical techniques such as time-boxing hypotheses, manually modeling infrastructure after automated scans, and using AI only as an information accelerator rather than an autonomous operator. wr3dmast3r also details a memorable chain that began with a bot, moved through VPN and Outlook access, leveraged SCCM tokens for privilege escalation, and ended with compromise of a second domain containing the target system.
OTUS Publishes September Digest of Free Lessons on Linux Administration, PostgreSQL, CI/CD and Infrastructure Security
OTUS has released a new digest listing free September webinars aimed at infrastructure engineers, DevOps specialists and system administrators. The program covers practical topics including Linux server configuration, PostgreSQL 18 performance tuning, high-availability clusters with Patroni, CI/CD pipelines in GitLab, eBPF observability and infrastructure security practices. All sessions are delivered by practicing OTUS instructors who share real-world production experience. Separate tracks address RAID and LVM management, GPO policies, release management in 1C environments, Go profiling, mitmproxy traffic analysis and responsible use of AI tools for incident investigation and code review. The webinars run throughout September at 19:00 or 20:00 Moscow time and require only free registration. The digest also includes sessions on career growth from tech lead to CTO and effective responsibility distribution for team leads.