Habr•August 31, 2026•🇷🇺Translated from Russian

Corporate Wi-Fi Passwords Stored in Plain Text on Every Connected Device

Any company laptop that has connected to the corporate Wi-Fi network retains the network password in plain text. When an employee departs, the device is returned, yet the password remains accessible through simple operating-system commands.

Windows

The built-in netsh utility lists all saved wireless profiles with the command netsh wlan show profiles. The password for a specific network is retrieved by running netsh wlan show profile name="CorpNet" key=clear. The resulting Key Content line displays the passphrase in clear text. No administrative privileges are required; the command works under the same user account that originally joined the network.

Linux

NetworkManager stores connection details in files located at /etc/NetworkManager/system-connections/. The command sudo grep -r 'psk=' /etc/NetworkManager/system-connections/ extracts the pre-shared key in plain text. Ordinary users can list connection names without elevated rights using nmcli -t -f NAME,TYPE,AUTOCONNECT connection show.

macOS

Passwords reside in the system Keychain. The command security find-generic-password -ga "CorpNet" will display the password, but the operating system first prompts the user for explicit confirmation, providing a stronger access-control model than Windows or Linux defaults.

This behavior is not a vulnerability; devices must retain credentials to reconnect automatically. The real issue lies in organizational policy. A shared Wi-Fi password is known to every employee, contractor, and guest who has ever connected. Changing it requires reconfiguring every corporate device, so rotation is often postponed for years. Personal devices that joined the network may also carry the password into cloud backups.

Recommended alternatives include WPA2/WPA3-Enterprise authentication, which ties network access to individual user accounts and automatically revokes access upon account deactivation. A separate, time-limited guest network with strong isolation from internal resources allows frequent password changes without affecting staff devices. When a shared password remains unavoidable, it should be stored in a password manager, rotated after every employee departure or contractor engagement, and never posted visibly in meeting rooms.

Related articles

Habr•Policy & Regulation

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.

Habr•Policy & Regulation

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.

Habr•Policy & Regulation

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.

AntiMalware•Policy & Regulation

False 50,000 Ruble Fine Claims Circulate About Russia's Unified Bank Card Registry

Social media posts falsely warn Russian citizens of a 50,000 ruble fine for failing to submit personal bank card data to a new unified registry. The claims have been identified as fabricated, with the project "Lapsa Media" noting that the accompanying images were likely generated by AI and contain multiple errors and typos. In reality, individual citizens are not required to take any action, as banks themselves will transmit the necessary information. The Bank of Russia has confirmed that banks must upload card numbers, card types, and owners' INN identifiers to the system operated by NSPK no later than September 1, 2027. Starting on that date, banks will begin enforcing a limit of 20 cards per client to hinder mass issuance of cards for fraudulent purposes. Previously issued cards exceeding this limit will remain valid and will not be forcibly closed.