HabrAugust 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

AntiMalwarePolicy & Regulation

Ideco NGFW Novum Earns Highest Customer Rating in Quadrant Technologies Import Substitution Study

Ideco NGFW Novum achieved the top customer score of 6.9 out of 10 in the Matrix of Import Substitution 2026: NGFW research conducted by Quadrant Technologies, surpassing the market average of 6.3 and outperforming seven competing Russian solutions. The study evaluated vendors based on specialized revenue alongside 18 criteria covering product quality and functionality, with ratings provided directly by specialists who deploy and operate the firewalls in production environments. Ideco excelled in 11 parameters above seven points, including administration convenience at 7.9, technical support and partner network at 7.6, Zero Trust segmentation at 7.3, and both integration capabilities and core NGFW functionality at 7.2. Despite strong product scores, Ideco remains in the Development quadrant rather than Leadership due to lower profile revenue volume, positioning the company as a prime candidate for advancement with increased sales and large-scale deployments. Complementary testing by Infosystems Jet laboratory showed Ideco NGFW Novum passing 189 of 242 checks under Methodology 3.0 and becoming the sole participant to complete an eight-hour stress test. The broader Russian NGFW market is shifting away from emergency import substitution toward demands for real-world stability, updates, documentation, support, and usability, with product cost cited as a rejection factor by 37.5 percent of respondents.

HabrPolicy & Regulation

Kubernetes Audit Policy Review: Checklist Targets Common Blind Spots in Rules

An experienced Kubernetes administrator shared a detailed review process for audit policies that often remain untouched for years after initial deployment. The 580-line policy was rebuilt using the Kubernetes Threat Matrix from RedGuard as the primary reference. The author highlights recurring issues such as outdated exceptions, missing coverage for new components, and legacy comments that obscure actual security intent. The resulting checklist focuses on principles rather than cluster-specific findings to help other teams perform effective policy audits. Key recommendations address rule completeness, exception management, and periodic full-scale reviews instead of incremental patching. The approach aims to restore audit policies as active security controls rather than accumulated technical debt.

HabrPolicy & Regulation

Avoiding a Leaky Kubernetes Audit Policy: Real-World Configuration Breakdown

Kubernetes Audit Policy is typically configured once during cluster setup and then left untouched for years while accumulating exceptions for new components. Over time the policy stops functioning as a security control and instead becomes an archaeological layer of outdated comments such as "# temporary, TODO remove" that date back three years or more. The author recently reviewed their own 580-line configuration file that had been assembled from multiple sources. Primary reference was the Kubernetes Threat Matrix, which explains why many rules are designed to detect security-relevant actions rather than simply reduce log noise. Examples include targeted monitoring of RBAC modifications and deletion of events. The article emphasizes the need for periodic full reviews instead of incremental patching to maintain effective detection coverage.

AntiMalwarePolicy & Regulation

CryptoPro Develops CryptoPro-Browser with Russian Cryptography for FSB Compliance

CryptoPro is creating its own browser called CryptoPro-Browser as part of the CryptoPro CSP 6.0 cryptographic information protection system. The product will include built-in cryptographic tools, support for the company's plugin, and TLS connections using Russian cryptographic algorithms. The development follows Google's removal of the CryptoPro extension from the Chrome Web Store in February 2025, which left new users without an easy installation method. The project has been coordinated with the FSB of Russia and targets scenarios requiring compliance with Russian information security regulations. CryptoPro plans to incorporate experience from its earlier Chromium-Gost project started in 2017, while also recommending Yandex Browser as an alternative. Analysts estimate the development cost at several tens of millions of rubles, with the main focus on corporate customers needing certificate management and specialized support.