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
Costly Mistakes: How Russian Businesses Risk Millions in Fines for Personal Data Violations
A year after stricter Russian personal data protection fines took effect, many entrepreneurs continue to commit violations that could trigger multimillion-ruble penalties from Roskomnadzor. The article details ten common breaches, including the prohibited use of Google Forms for data collection, missing cookie banners, absent or invalid consent forms under forms, and failure to obtain separate consents for publishing reviews. Additional violations cover missing privacy policies, outdated notifications to Roskomnadzor, improper transfer of employee data to third parties without written consent, lack of data processing agreements, and absence of records for paper-based data storage locations. Each violation is explained with direct references to the Law on Personal Data, the Code of Administrative Offenses, and specific government orders, along with exact fine ranges for citizens, individual entrepreneurs, and legal entities. Practical remediation steps are provided, such as replacing foreign services with Yandex Forms, drafting compliant consent texts per Article 9, and submitting updated notifications under Order No. 180. The guidance emphasizes conducting a full site audit and implementing all required documents to avoid penalties throughout 2026.
Rethinking SSO: Centralized User Data Provision and Authorization Processing in Corporate Systems
The article examines Single Sign-On systems not merely as authentication gateways but as architectural hubs for delivering user attributes and executing additional authorization logic. It highlights how SSO can aggregate data from sources like Active Directory, HR systems, and IDM platforms, then deliver it via OIDC claims to downstream applications. The discussion covers the shift from fragmented integrations across dozens of apps to a single trusted enforcement point using standards such as aggregated and distributed claims. It also explores the authorization pipeline where SSO acts as a Policy Enforcement Point querying external Policy Decision Points via the AuthZEN Authorization API 1.0. Practical examples include electronic business cards, role assignment, access routing, and mandatory MFA checks before token issuance. The piece stresses maintaining data ownership with source systems while establishing SSO as the single point of trust for applications.
Bitrix24 Releases Fully On-Premise BI Constructor for Regulated Enterprises
Bitrix24 has introduced a new delivery model for its BI Constructor that allows complete deployment inside a customer's own infrastructure. The update eliminates any requirement for external servers, cloud APIs, or internet connectivity, ensuring that all corporate data remains within the organization's closed perimeter. Previously, even the boxed version of the platform needed access to external infrastructure for updates and auxiliary services, creating conflicts with internal security policies and regulatory demands in highly regulated sectors. The new on-premise variant performs all data processing and storage exclusively on customer servers, giving organizations full control over access rights, backups, updates, and integration with internal protection tools. The solution is compatible with the boxed edition of Bitrix24 running on PostgreSQL and does not connect to external CDNs or cloud services. Bitrix24 expects strong interest from large enterprises and organizations handling restricted-access data that must stay inside the corporate network. Pilot implementations have already been completed, with broader customer pilots planned in the coming months.
Russia's Data Leak Penalties: 2.6 Million Rubles in Fines Despite 1.58 Billion Records Exposed in 2025
Russia introduced turnover-based fines for personal data leaks through Federal Law 420-FZ in late 2024, fundamentally altering the economics of information security investments. Over the first 18 months, Roskomnadzor opened 52 administrative investigations and issued 40 protocols totaling just 2.6 million rubles in penalties, with zero turnover fines applied. This occurred against a backdrop of 1.58 billion compromised records in 2025 alone. Public data leaks dropped fourfold in the first half of 2026, yet trading activity on underground forums rose nearly 60 percent as operators shifted to private sales. The law now ties penalties directly to the number of affected individuals and adds a turnover component for repeat violations under Article 13.11 of the Code of Administrative Offenses. Analysts note that the mere threat of larger fines has prompted companies to reassess data retention policies and risk models even without actual enforcement precedents.