Habr•July 29, 2026•🇷🇺Translated from Russian

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

Habr•Policy & Regulation

25-Year Mystery Solved: NIST Elliptic Curve Seeds Came from lrand48 and Unix Timestamps

Researchers at Anthropic used the Claude model to trace the origins of the mysterious seed values embedded in NIST elliptic curves standardized in FIPS 186-2. The seeds for curves including NIST P-192, P-224, P-256, P-384 and P-521 were not derived from hashed humorous phrases as previously rumored but instead generated by the non-cryptographic lrand48 linear congruential generator seeded with Unix timestamps from 1997 and 1998. The discovery also explains the base points of several curves using the FreeLIP library's random number generator. The findings reduce long-standing suspicions of deliberate backdoors inserted by the NSA. Several candidate curves that met the criteria were skipped during selection, leaving open questions about the exact filtering process. The work was performed by a team including Nicholas Carlini and others, with the reproduction code released into the public domain.

Security NEXT•Policy & Regulation

Japan's IPA Opens Special Consultation Desk for Suspected Cyberattack Data Leaks

The Information-technology Promotion Agency (IPA) has launched a dedicated Unauthorized Access Special Consultation Desk to assist companies and organizations affected by cyber attacks resulting in information leaks. The service accepts inquiries from entities that only suspect they may have been victimized, providing initial response guidance even before confirmed incidents. Consultations cover advice on whether unauthorized access or data exfiltration is likely, recommended immediate containment steps, lists of incident response vendors, and reporting obligations to relevant authorities. The hotline operates on weekdays from 9:30 to 17:30 excluding the lunch hour, while email replies may take until the next business day. Separate channels exist for non-access incidents, general security advice, and individual personal data breach concerns. The move responds to a rising number of breaches targeting online services handling personal information.

AntiMalware•Policy & Regulation

Russian State Duma Approves Outsourcing of Banking Secrecy and Client Data Without Consent

The State Duma has passed legislation in its second and third readings permitting Russian banks to transfer client data processing, including banking secrecy and personal information, to external IT contractors and cloud providers. No separate client consent will be required for such transfers. Only accredited Russian IT companies and banks holding a universal license that meet strict domestic control criteria may act as processors, with all servers required to remain inside Russia. Banks must notify the Central Bank of Russia in advance, and contractors must undergo audits by organizations licensed by FSTEC or FSB Russia. Special approval procedures involving the Central Bank, FSB, and Rosfinmonitoring apply to banks under foreign control. The law preserves banking secrecy while expanding the circle of authorized handlers under defined security obligations.

AntiMalware•Policy & Regulation

Russia's MinTsifry Drafts Security Requirements for Trusted Domestic Software

The Russian Ministry of Digital Development has published a draft set of requirements for trusted Russian software that go beyond simple domestic origin. The proposals focus on resilience against external interference, absence of known unpatched vulnerabilities, and full development and build processes conducted inside Russia under controlled conditions. Additional rules cover up-to-date component inventories, in-country technical support, and timely disclosure of software updates. Special compatibility mandates are included for Russian browsers and electronic signature tools across multiple product classes such as operating systems, databases, office suites, and communication applications. Compliance verification would be voluntary through expert review, with results recorded in the official Russian software registry and internal-use software lists.