EnvSpec Naming Standard Introduces Strict Six-Environment Hierarchy for Zero Trust Infrastructure
The open standard EnvSpec Naming 1.0.0 argues that traditional host naming practices undermine security long before firewalls are configured. It claims that any environment labelled test, uat or pilot that processes real data is functionally prod and must be protected accordingly.
The specification defines a five-level hierarchy—environment, perimeter, system, slot, node—and mandates the canonical FQDN format {node}.{slot}.{system}.{perimeter}.{env}.{domain}. Names must be parseable by regular expressions and validating webhooks, allowing policies to be written against name suffixes rather than IP lists.
Only six environments are permitted: dev, test, stage, prod, infrastructure and workplace. Sandboxes, load-testing and pilot projects are treated as contours inside these environments, not new top-level categories. The decisive criterion is the nature of consumers and data, not hardware or project phase.
Key trust rules include: linear environments may not communicate directly; infrastructure alone may exchange artefacts and telemetry with all tiers; workplace devices reach any environment only via an access gateway; external parties are represented as external.{env} contours.
The standard explicitly forbids encoding mutable attributes such as site location, SLA or lifecycle status in names. It projects the same hierarchy into SPIFFE IDs, Kubernetes namespaces and three mandatory tags: envspec.io/env, envspec.io/perimeter and envspec.io/system.
Compliance can be verified automatically without maintaining a separate CMDB. Existing legacy hosts do not require renaming; applying the three tags at the hypervisor or cloud layer is accepted as full conformance.
Related articles
Unconfirmed Reports of Steam Blockade in Russia: Valve Faces User Data Demands and Tax Scrutiny
On November 16, media outlets and Telegram channels reported that Russian authorities are demanding user data from Valve's Steam platform, including accounts registered in Kazakhstan, while threatening to block the service. The claims also suggested plans to track undeclared income from high-value in-game skins, but no official statements or documents have confirmed these assertions. The original source was an analytical piece by ProFinance that cited unnamed sources without specifying any government agency, official, or legal document. Roskomnadzor, the Federal Tax Service, and other agencies have made no such announcements, and Valve has not confirmed receiving any requests. Confirmed information is limited to tax payments: Kazakhstan's Committee of State Revenues reported that Valve paid approximately 2 billion rubles in VAT for the first half of 2026, the highest among foreign internet companies. This amount more than doubled compared to the same period in 2025, attributed to Russian users relocating their accounts to the Kazakh region after Visa and Mastercard exited Russia. Vice Speaker of the State Duma Vladislav Davankov opposed any potential blockade, comparing it to freezing bank deposits, and pledged to raise the issue at the Duma session on November 17.
Russia's MinTsifry Mandates Qualified Electronic Signatures for Remote eSIM Registration to Combat Fraud
Russia's Ministry of Digital Development has directed telecom operators to allow remote eSIM issuance and contract signing exclusively through enhanced qualified electronic signatures (UKEP). The use of enhanced unqualified electronic signatures (UNEP) via the GosKlyuch system will be prohibited starting December 1. Operators must re-integrate with GosKlyuch exclusively through the SMEV interagency system and verify all remotely issued eSIMs registered before November 15. The measures address widespread fraud involving unauthorized number porting to attacker-controlled eSIMs, enabling interception of SMS codes for banking and messenger access. Independent experts note that UNEP certificates require only a verified Gosuslugi account, making them vulnerable to account takeover, while UKEP demands stricter identity verification. Over 15.7 million UNEP certificates were issued through GosKlyuch in the first eight months of 2026.
Employee Data Transfers Within Russian Holdings: Why Affiliates Count as Third Parties Under 152-FZ
Russian data protection law treats companies within the same holding as separate operators, requiring written employee consent for any transfer of personal data during internal job moves. The analysis examines five practical routes for handling transfers between legal entities such as ООО «Торговый дом» and ООО «Логистика» while complying with both 152-FZ and the Labor Code. Direct exchange of documents is generally prohibited without consent under Article 88 of the Labor Code, but routes through the employee, separate consent forms, or data processing agreements with a central HR entity can reduce risk. Storage of records after termination remains lawful for statutory accounting and archival periods without additional consent. The article provides detailed decision trees, consent templates, and warnings about fines ranging from 150,000 to 700,000 rubles for non-compliance. Roskomnadzor guidance and recent amendments to Article 9 of 152-FZ are also addressed.
Access Under Control: Experts to Discuss SSO Risks, Legacy System Migration and AI Agent Permissions
On November 26, 2026, at 11:00, a webinar titled 'Managing access to corporate systems: how to bring order and reduce risks' will bring together leading Russian information security professionals. Participants will examine how organizations can control user permissions when integrating new applications while maintaining support for legacy systems. The discussion will cover excessive privileges, accounts of former employees, and contractor access, highlighting common mistakes that enable attackers to compromise corporate environments using legitimate credentials. A dedicated segment will address access management challenges during import substitution, including architecture selection and criteria for choosing between unified platforms and specialized solutions. Experts will also analyze bypass techniques for SSO and MFA, the impact of authentication service outages, and pre-deployment validation steps. Additional topics include the privileges of AI agents within corporate systems and regulatory requirements for centralized access control, with measurable outcomes such as faster rights revocation and reduced manual operations.