Building Information Security Culture: How Welcome Training Turned Rules into Engaging Dialogue
A large software company has shared how it replaced dry policy documents with an interactive Welcome Training program to build genuine information security culture among its staff.
The organization already deploys advanced controls such as access restrictions, security policies, an SIEM system, and antivirus solutions. However, these tools proved ineffective when employees lacked basic understanding of why rules exist and what consequences follow from violations.
What did not work
Signing a policy document during onboarding proved insufficient, as staff rarely retained the content. Posting rules on the corporate portal also failed to drive compliance, since no verification mechanism existed.
The target audience consists of developers, analysts, testers, product managers, and designers. While these professionals often master complex product security technologies, many still store passwords in Google Sheets, showing that technical skill does not automatically translate into security culture.
Welcome Training structure
The company therefore introduced 45-minute in-person sessions limited to groups of 7–10 people. The format encourages questions and discussion. The curriculum includes:
- Current threat landscape with examples of major Russian incidents
- Step-by-step attack mechanics to illustrate individual impact
- Assets under protection, including code, data channels, and personal information
- Consequences of sharing credentials or personal data
- Password requirements and use of corporate password managers
- Proper use of corporate email
- Storing sensitive data on encrypted volumes with VeraCrypt
- Secure credential transfer using the pbin service
- File checking via VirusTotal and antivirus tools
- Recognition and response to social engineering
- Signs of workstation compromise and reporting procedures
- Overview of deployed corporate protections such as Kaspersky Endpoint Security, Kaspersky Secure Mail Gateway, and SIEM
Results include higher engagement, better retention, increased awareness of personal responsibility, and a measurable drop in human-factor incidents.
Related articles
Web Certificate Trust Chains and State Access Risks Explained Amid Russian Banking Sanctions
The article explains the hierarchical structure of web certificates used for site authentication and traffic encryption, starting from highly protected root certificates stored in air-gapped facilities with Shamir's secret sharing for key protection. Intermediate certificates extend the chain of trust down to leaf certificates deployed on websites. Russian banks have turned to certificates issued under the MinTsifry root after Western and Chinese CAs refused service due to sanctions. The piece highlights that any nation-state with access to a root private key, whether FSB, NSA, or others, could theoretically issue fraudulent certificates for any domain. It notes the limitations of the X.509 standard, which lacks native support for multi-CA signatures, and suggests that separate browsing environments or PGP-style web-of-trust models could mitigate risks. The author concludes that security is already reduced by reliance on any state-controlled CA and that the choice is ultimately which intelligence agency one prefers to trust.
MAX Messenger to Open Source Code and Launch Developer Program for Alternative Clients
The Russian messenger MAX is preparing to open its platform to third-party developers by launching a dedicated developer program and providing API access. Approved participants will receive the official client's source code, design system, technical documentation, and access tokens to integrate with the platform infrastructure. The initiative targets IT companies from Russia and friendly countries that demonstrate experience with large-scale projects and adherence to strict security standards. All selected developers must implement secure development practices, robust encryption mechanisms, and undergo code audits to protect user data. The program supplies ready-made user registration and anti-fraud tools, while alternative clients remain bound by API usage terms focused on security compliance. Applications will be accepted via the official developer portal, although exact launch dates have not yet been disclosed.
InfoWatch Details ARMA Wall NGFW Development for Industrial Systems Under Russian Import Substitution Rules
InfoWatch has published the second part of its interview series describing the ongoing development of the ARMA Wall next-generation firewall for industrial control systems. The product prioritizes on-premise processing without cloud agents to meet strict customer security policies and certification requirements. Engineers combine proprietary detection feeds with external sources, including indicators from NKCKI, while maintaining hundreds of thousands of signatures without disabling legacy rules for older Siemens controllers. Migration support relies on manual pre-project audits rather than automated tools, and the company works closely with domestic SCADA vendors to embed NGFW capabilities inside long-lifecycle OT environments. ARMA Wall is positioned as a more flexible and cost-effective alternative to data diodes because it allows granular command-level filtering and can emulate one-way traffic when required. The solution is already deployed at Roscosmos subsidiary RKK Energia after full certification and categorization.
WhatsApp Developing AI Content Labeling Feature for Channel Admins to Meet EU Transparency Rules
WhatsApp, owned by Meta, is rolling out a new function that allows channel administrators to mark posts containing AI-generated or AI-edited media. The feature appears in the latest Android beta and stems directly from European Union requirements for transparency around artificial intelligence content. Administrators can long-press a message after publication and select an option to add an AI content label, which then displays a visible tag informing subscribers that the material was created or modified by neural network tools. The requirement applies specifically to images, videos, and other media files, while generated text remains exempt from mandatory labeling. WABetaInfo researchers spotted the change, noting that the label may become permanent once applied and that the rollout could initially target only jurisdictions with relevant legislation. Broader availability for iOS users and global deployment remain under consideration.