Yandex 360 Email Archive Documentation Shows Search Snapshots and Former Employee Log Filters
The Yandex 360 administrator documentation defines the email archive as a feature that preserves copies of every message sent or received by employees whose mailboxes belong to the organization's domain. Once enabled, the archive continues to retain messages even if the original owner deletes them from their mailbox. The guide explicitly warns that messages deleted before the archive was turned on cannot be restored.
Search functionality is implemented as named objects rather than live queries. The documentation states: “Each search runs once. The results do not update as employees send and receive new messages.” Administrators must either create a new search with identical parameters or use the “Clone search” button and adjust the date range to obtain fresh results. No method exists in the documented Yandex 360 API to automate this process.
The action log records every interaction with the archive and promises that “you can always see who searched for what.” However, the employee filter only lists active accounts. The documentation advises that if an administrator has left the organization, their actions cannot be selected by name in the filter and other criteria such as event type and time period must be used instead.
Additional constraints listed in the FAQ section include the permanent loss of messages belonging to fully deleted accounts and the exclusion of any mail from mailboxes that were imported rather than created on the organization's domain. These documented limitations affect routine tasks such as retrieving correspondence of a departed employee or reconstructing an audit trail after an administrator departure.
Related articles
25-Year Mystery Solved: NIST Elliptic Curve Seeds Came from lrand48 and Unix Timestamps
Researchers at Anthropic used the Claude model to trace the origins of the mysterious seed values embedded in NIST elliptic curves standardized in FIPS 186-2. The seeds for curves including NIST P-192, P-224, P-256, P-384 and P-521 were not derived from hashed humorous phrases as previously rumored but instead generated by the non-cryptographic lrand48 linear congruential generator seeded with Unix timestamps from 1997 and 1998. The discovery also explains the base points of several curves using the FreeLIP library's random number generator. The findings reduce long-standing suspicions of deliberate backdoors inserted by the NSA. Several candidate curves that met the criteria were skipped during selection, leaving open questions about the exact filtering process. The work was performed by a team including Nicholas Carlini and others, with the reproduction code released into the public domain.
Japan's IPA Opens Special Consultation Desk for Suspected Cyberattack Data Leaks
The Information-technology Promotion Agency (IPA) has launched a dedicated Unauthorized Access Special Consultation Desk to assist companies and organizations affected by cyber attacks resulting in information leaks. The service accepts inquiries from entities that only suspect they may have been victimized, providing initial response guidance even before confirmed incidents. Consultations cover advice on whether unauthorized access or data exfiltration is likely, recommended immediate containment steps, lists of incident response vendors, and reporting obligations to relevant authorities. The hotline operates on weekdays from 9:30 to 17:30 excluding the lunch hour, while email replies may take until the next business day. Separate channels exist for non-access incidents, general security advice, and individual personal data breach concerns. The move responds to a rising number of breaches targeting online services handling personal information.
Russian State Duma Approves Outsourcing of Banking Secrecy and Client Data Without Consent
The State Duma has passed legislation in its second and third readings permitting Russian banks to transfer client data processing, including banking secrecy and personal information, to external IT contractors and cloud providers. No separate client consent will be required for such transfers. Only accredited Russian IT companies and banks holding a universal license that meet strict domestic control criteria may act as processors, with all servers required to remain inside Russia. Banks must notify the Central Bank of Russia in advance, and contractors must undergo audits by organizations licensed by FSTEC or FSB Russia. Special approval procedures involving the Central Bank, FSB, and Rosfinmonitoring apply to banks under foreign control. The law preserves banking secrecy while expanding the circle of authorized handlers under defined security obligations.
Russia's MinTsifry Drafts Security Requirements for Trusted Domestic Software
The Russian Ministry of Digital Development has published a draft set of requirements for trusted Russian software that go beyond simple domestic origin. The proposals focus on resilience against external interference, absence of known unpatched vulnerabilities, and full development and build processes conducted inside Russia under controlled conditions. Additional rules cover up-to-date component inventories, in-country technical support, and timely disclosure of software updates. Special compatibility mandates are included for Russian browsers and electronic signature tools across multiple product classes such as operating systems, databases, office suites, and communication applications. Compliance verification would be voluntary through expert review, with results recorded in the official Russian software registry and internal-use software lists.