Why Separate Corporate and Personal Email Accounts: Risks of Mixing Work and Private Communications
Mixing work and personal email may seem harmless when a large attachment needs to be sent quickly, but the practice creates lasting security and compliance problems. Corporate mailboxes are managed by the organization, which controls domains, applies filters, maintains backups, and can revoke access upon employee departure. Personal accounts, by contrast, remain fully under individual control even after termination, leaving contracts, client correspondence, and internal documents outside any company oversight.
152-FZ and the Labor Code impose obligations to protect personal data during processing, while 98-FZ governs trade secrets. When work files leave the corporate environment, additional uncontrolled copies appear in mobile caches, tablet downloads, and synchronized cloud storage. Recovering or auditing these copies becomes nearly impossible, complicating incident investigations and regulatory compliance.
Using a corporate address for online purchases, subscriptions, and password recovery also expands the attack surface. The work mailbox receives marketing lists, phishing attempts, and breach notifications, while personal services become dependent on an account the employer can disable at any time. After dismissal, employees lose access to tickets, receipts, and recovery codes tied to the corporate domain.
Security experts recommend clear separation of roles. All client communications, contracts, reports, and internal notifications should stay within the corporate system. Personal registrations, banking alerts, and private correspondence belong exclusively to the individual mailbox. Both accounts must use unique strong passwords and multi-factor authentication to prevent credential reuse from turning a minor leak into a major incident.
If mixing has already occurred, organizations advise locating work messages and attachments in personal accounts, disabling forwarding rules, returning files to approved repositories through official procedures, and notifying security teams when confidential data may be involved. Automatic forwarding between accounts is particularly dangerous because it creates an uncontrolled, persistent channel for sensitive information.
Related articles
Three Hypotheses on Information Security Risk Assessment: Where Automation Truly Saves Time at Avito
Avito expert Irina Sozinova details how the company tested automation in its risk assessment process after scaling issues emerged with thousands of risks in the GRC system. The team formulated and piloted three hypotheses focused on automating typical risks, eliminating manual team preparation, and validating data to reduce InfoSec workload. Results showed a 16% drop in total risks registered, zero preparation time for teams, and improved coverage and context quality, though overall expert time savings were partially offset by new post-processing tasks. The pilot confirmed that automation works best on repeatable scenarios with stable data sources rather than promising immediate proportional time cuts. Avito plans to complete automation of context collection and finding classification this year to expand risk assessments across the company next year.
Integrating OAuth 2.0 with PDP Architectures Without Modifying Core Authorization Engines
The article explores how to combine OAuth 2.0 delegated access with traditional PEP/PDP authorization systems. It proposes an OAuth-aware PDP layer that translates access tokens into standard PDP checks while preserving the original PDP implementation. Three main use cases are analyzed: stored user grants, tenant-level administrative grants, and scopes carried directly inside tokens. The design relies on synthetic subjects such as u+c and t+c pairs, ephemeral policies for token-embedded scopes, and optional OAuth-aware PAP components. Special attention is given to token contents, policy storage via PAP, and the need for deterministic subject identifiers. The approach supports both classic scope models and structured RAR-style authorizations while maintaining separation between OAuth grants and subject permissions.
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.