Personal Laptops, Corporate Secrets: 70% of Companies Err with BYOD Policies
Personal smartphones and laptops have long been integrated into corporate infrastructure. According to Crosstech experts, up to 90% of employees at Russian organizations use their own devices for work-related tasks. At the same time, approximately 70% of companies implement BYOD programs with critical errors, exposing themselves to data leaks and other cyber incidents.
The concept of Bring Your Own Device appears attractive at first glance: businesses save on hardware purchases while employees work on familiar equipment. Problems arise when organizations choose one of two extremes. The first is a completely permissive approach with no rules, restrictions, or data separation. An employee might download a work contract to a smartphone, edit it at home in the evening, and then leave the device in a taxi the next day. The same gadget could be handed to a child who installs questionable games, potentially compromising corporate data along with it.
The second extreme involves transforming an employee’s personal laptop into an extension of the security department. The company installs monitoring software that tracks user actions, which employees often perceive as surveillance. This frequently produces the opposite effect: documents migrate to personal messengers, unauthorized cloud services, and other unofficial platforms. The result is shadow IT that the organization can no longer control.
Crosstech recommends avoiding full-device monitoring and instead separating work and personal spaces. On smartphones, corporate data can be placed inside an encrypted container that can be wiped independently if needed. For home desktops, companies should provide secure access through isolated virtual desktops without direct connections to the internal network.
“Companies should care only about how their data is processed, not about what a person does in their free time on their own device,” noted Egor Norkin, Information Security Architect at Crosstech.
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.