top of page
Indigo logo: Digital Intelligence

How to create an internal information security culture

Writer: Indigo Inteligência Digital
Indigo Inteligência Digital
Nov 12
6 min read

Most companies treat information security as a technology problem.

Encryption, firewalls, antivirus, two-factor authentication, backups — all of these are extremely important, but insufficient. Because the most vulnerable link in any security chain is not a system, it's a person.


IBM research indicates that over 90% of security incidents have human error as the root cause: clicking on a phishing link, a weak password reused across multiple systems, a file sent to the wrong recipient, or access not revoked after an employee leaves the system. Technology solves part of the problem. Culture solves the rest.


And culture, unlike software, cannot be installed. It needs to be built.




Why the traditional approach doesn't work.

The most common model of "safety awareness" in companies follows a predictable script: mandatory annual training, a warning email after an incident, a set of policies that no one has read to the end. The result is equally predictable: employees who know that safety is important in the abstract, but do not change their concrete behaviors in their daily lives.


The problem with this approach is structural. It treats safety as an event—something that happens once a year—instead of continuous behavior. It communicates rules without building understanding. And, most importantly, it places the employee in the position of a passive recipient of information, not an active agent of protection.


A genuine safety culture works in a completely different way.




What does it mean to have a safety culture?

A security culture is not the absence of incidents. It is the set of values, behaviors, and practices that an organization collectively adopts to protect its information assets—consistently, even when no one is watching.


In companies with a mature security culture, employees question suspicious emails before clicking on them. They report vulnerabilities without fear of punishment. They ask for confirmation before sharing sensitive data. They understand why policies exist—not just what they dictate.


This maturity doesn't emerge spontaneously. It's the result of consistent leadership, well-designed processes, and continuous communication.



The pillars of an effective safety culture


1. Leadership that models behavior

Culture comes from the top. If the CEO shares passwords with the assistant "to make things easier," if managers ignore access policies because "they hinder productivity," or if the board treats security as an exclusive problem for the IT team, the signal that reaches the rest of the organization is clear: this is not a real priority.


The reverse is also true. Leaders who visibly follow policies, who talk about safety in results meetings, and who respond quickly and transparently to incidents create an environment where safe behavior is the norm—not the exception.


Leadership commitment needs to be genuine and visible. Words without consistent action don't create a culture.



2. Continuous education, not isolated events.

Replacing annual training with a continuous learning approach is one of the most impactful changes. This can happen in several ways:


Frequent micro-training sessions: short 5-10 minute modules, delivered monthly or bi-weekly, on specific topics—such as identifying phishing, password best practices, and security in remote work. The frequency keeps the topic fresh without overwhelming the learner.


Phishing simulations: sending simulated phishing emails to the team — with immediate feedback for those who click — is one of the most effective tools for developing security reflexes. Not as punishment, but as experiential learning.


Contextualized real-life cases: security incidents that occurred in other companies in the same sector are far more impactful than generic examples. "This happened to a company similar to ours" captures attention in a way that "this could happen to anyone" cannot.



3. Policies that people are able to follow

Security policies that generate excessive friction are sabotaged—not out of bad faith, but out of practical necessity. If the password policy requires such a complex combination that no one can memorize it, the result is passwords written on sticky notes or reused across all systems. If the process of accessing critical systems is so bureaucratic that people share credentials to speed things up, the policy has created the very risk it was trying to prevent.


Good security policies balance protection and usability. This requires security teams and operational teams to work together in defining the rules—and for the policies to be regularly reviewed in light of what actually happens in practice.


Adopting enterprise password managers, SSO (Single Sign-On), and well-implemented multifactor authentication reduces friction without reducing protection.



4. An environment where reporting is safe.

One of the most revealing indicators of the maturity of a security culture is the willingness of employees to report incidents and vulnerabilities. In companies where those who report a problem are punished or shamed, the problems cease to be reported—and continue to exist, invisibly, until they become crises.


Creating secure and anonymous reporting channels, celebrating those who identify vulnerabilities before they are exploited, and responding to reports quickly and without blame are practices that build the trust necessary for the organization to learn from its own risks.



5. Security integrated into the processes, not parallel to them.

Security that lives in a separate department, with its own policies and processes, rarely truly penetrates the organizational culture. Integration happens when security is considered in every new project, product, or process from the outset—not added as a final layer before launch.


In software development, this is called DevSecOps : security practices integrated into the development lifecycle, with security-oriented code reviews, automated vulnerability testing, and access policies defined along with the system architecture.


In the broader context of the organization, this means including risk assessments in supplier onboarding processes, product launches, infrastructure changes, and any situation where sensitive data changes hands.



Metrics that reveal the true state of the culture.

You can't manage what you don't measure. Here are some metrics that help diagnose and monitor the evolution of safety culture:


Click-through rate in phishing simulations: the lower the better — but more important than the absolute number is the trend over time. Consistent reduction indicates that the training is working.


Volume of spontaneous reports: an increase in the number of incidents reported internally, paradoxically, can be a positive sign — it indicates that people are more aware and more comfortable reporting.


Average vulnerability resolution time: how long does it take between identifying a vulnerability and fixing it? Long times indicate that security is not a real priority in the processes.


Training coverage: percentage of the team that completed the awareness modules. Goals below 100% indicate that the topic is not treated as truly mandatory.

Incidents caused by human error: tracing the root cause of incidents over time reveals whether investments in culture are reducing human vulnerability.




The role of technology as a support, not a replacement.

Well-implemented security tools reduce the risk surface and limit the impact of human error. But they work best when the people using them understand what they are for.


A collaborator who understands why multifactor authentication exists will genuinely enable it—not just out of obligation. A developer who understands the risks of SQL injection will write more secure code, regardless of whether the automated scanner is running or not.


Technology closes gaps. Culture closes the gaps that technology cannot reach.



Where to begin: an initial roadmap

For companies that are taking their first steps, here are some high-impact, affordable actions:


Make an honest assessment. Where are the greatest human risks today? What policies exist on paper but are not followed in practice? What is the team's actual level of awareness of common threats?


Involve leadership before anything else. Without genuine sponsorship from the top, safety culture initiatives don't survive the first hurdle.


Start by doing the basics well. Password management, multi-factor authentication, minimum required access policies, and phishing training cover most common attack vectors. Doing this well is worth more than poorly implemented sophisticated projects.


Communicate in business language, not IT language. "Protecting customer data" resonates more than "mitigating attack vectors." Translate risks into the impact they have on the business—financial, regulatory, reputational.


Use data as a basis. Measure, adjust, and evolve. Safety culture is an ongoing process, not a project with a deadline.




Conclusion

Companies that treat security solely as a technology problem are only solving half the problem. Those that invest in building a culture where every employee is an active agent of protection—informed, engaged, and empowered—are building the most robust defense possible: an organization that learns, adapts, and protects its assets collectively and continuously.


Technology protects systems. Culture protects the organization.



Indigo ID develops systems and solutions with integrated security from the design stage — and supports companies in building digital architectures that reduce the risk surface without compromising productivity. If your company wants to evolve its information security maturity, our team is ready to help.





Did you enjoy this content? Share it with your team and follow the Indigo ID blog for more articles on technology, management, and digital security.


Comments


bottom of page