AntiMalware•September 1, 2026•🇷🇺Translated from Russian

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

Habr•Policy & Regulation

Protecting Data Centers from Kinetic and Cyber Attacks: What Regulators Worldwide Are Proposing

InfoWatch experts have updated their April report on data center resilience, highlighting how physical and cyber threats now directly threaten business continuity and national security. Regulators in the United States, European Union, and Russia are treating data centers as strategic infrastructure requiring layered defenses that combine physical hardening, geographic distribution, and strict cybersecurity controls. The United States has launched the Cyberstrategy for America 2026 emphasizing offensive operations, Zero Trust modernization, and supply-chain restrictions. The European Union is implementing ProtectEU and the Cyber Solidarity Act with real-time threat sharing and mandatory resilience standards under DORA. Russia is advancing technological sovereignty targets, new siting rules for data centers, and Presidential Decree No. 604 that enables temporary state management of inadequately protected critical facilities. The report also notes growing recognition that attacks on data centers can constitute acts of aggression under the Tallinn Manual.

BoletimSec•Policy & Regulation

US Department of Homeland Security Orders Federal Agencies to Remove DeepSeek Products

The US Department of Homeland Security issued an order on October 19 requiring federal civilian agencies to cease purchasing products from DeepSeek and to remove related technology from government systems. The directive, published the following day, targets Hangzhou DeepSeek Artificial Intelligence, its affiliates, and any third-party products or services built on DeepSeek implementations. The measure stems from the Federal Acquisition Supply Chain Security Act of 2018 and follows a recommendation by the Federal Acquisition Security Council, though no specific incidents or evidence were detailed in the notice. The restriction applies only to federal environments and does not prohibit private sector or individual use outside government systems. No removal deadline was set, and the document does not name the signing authority. The order is filed under docket DHS-2026-0628 with the CISA implementation team listed as the contact point.

AntiMalware•Policy & Regulation

AKIT Requests Temporary Permission for Russian Companies to Transfer Personal Data Abroad After Data Center Incidents

The Association of Internet Trade Companies (AKIT) has sent a formal letter to Russian Prime Minister Mikhail Mishustin proposing a temporary exemption from strict data localization rules. The measure would allow affected companies to move critical systems and Russian citizens' personal data to data centers in friendly countries when domestic infrastructure is unavailable due to accidents or damage. Members including Ozon, Wildberries, Cooper, and Yandex Market argue that services must continue operating even if Russian facilities are compromised. The proposed special regime would apply only after an officially confirmed incident, require compliance with information security standards, and end no later than March 1, 2028. After recovery, companies would be required to return to normal data processing within Russia. Expert Alexey Muntyan noted that the mechanism activates only after incidents occur and questioned whether countries should be selected based on data protection levels rather than political alignment.

BoletimSec•Policy & Regulation

Anthropic Model Reconstructs NSA Seeds for NIST Elliptic Curves in Under 30 Minutes

An internal Anthropic research model traced the origins of the five seeds used by the NSA to generate the NIST elliptic curves P-192, P-224, P-256, P-384, and P-521. The discovery resolves a 25-year-old question that arose when the curves were standardized in FIPS 186-2 for ECDSA in 2000. Researchers combined analysis of 1990s random number generators, 34 generator-output combinations, and lattice reduction techniques to identify lrand48 initialized with Unix timestamps from May 1997 to April 1998. The P-256 seed corresponds to the 1842nd candidate from a run started on 16 August 1997, and example seeds from ANSI X9.62 follow the same pattern. The work does not demonstrate any cryptographic break or backdoor in the curves and does not recommend changes to production systems. Several questions remain open, including the seed for curve B-163 and the reason certain candidate values were discarded.