Cybersecurity Governance and Security Culture
Assign security responsibilities across an organisation and choose governance and culture measures that make people report problems early.
Whose job is security, really?
After a fake invoice email nearly cost Tulsi Health ₹3.2 lakh, Vikram Deshmukh calls a meeting and asks a simple question: whose job is security? Neha says "everyone's", Arjun says "IT's", and Sameer says he assumed the payment software checked invoices. All three answers are partly right, which is exactly the problem. Security governance is how an organisation decides who is responsible for security, what it is trying to achieve, how much risk it will accept and how it checks that the plan is working. Without it, everyone assumes someone else is watching.
The same mistake has two very different endings. What decides it is not the click but whether Arjun feels safe to speak up.
Governance: deciding, directing and checking
Governance is different from the daily work of security. Daily work, often called security management or operations, is installing updates, reviewing alerts and resetting passwords. Governance sits above it and answers bigger questions. Which risks matter most to the business? How much money and time go to security this year? Who owns each important system, and who checks that the controls actually work?
A housing society is a good picture. The managing committee sets the rules, approves the budget for the watchman and CCTV, and reviews every year whether break-ins went up or down. The watchman runs the gate every day. Each resident still locks their own door and does not prop the gate open for a delivery. If the committee never meets, the watchman does his best with no budget and no rules, and residents assume the gate is someone else's problem.
Governance runs as a loop rather than a one-time plan. The owner sets direction, policies turn it into rules, staff and systems put them into practice, the results are measured, and the review feeds the next round of decisions.
Measuring and reviewing are what make it governance. A policy that nobody checks is a wish, not a control.
Who is responsible for what
Organisational responsibilities sit at several levels, and each level has a different kind of duty. At Tulsi Health, Vikram as owner is ultimately accountable: he answers to customers, regulators and the law if things go wrong, and he decides budget and priorities. Neha is responsible for designing and running the controls and for telling Vikram plainly what the risks are. Store managers like Arjun make sure the rules are followed at their counters. Every employee is responsible for their own logins, devices and the messages they act on. Vendors such as Rathi Softech have duties written into their contracts, for example how fast they fix flaws in MedLedger.
Responsibility can be shared out, but accountability stays at the top. Vikram can hand Neha the work, not the answer to 'why did this happen?'
Organisational accountability means every important risk and system has a named owner who must answer for it, and that the organisation as a whole can show what it did. "IT handles it" is not an owner; "Neha owns the backup, and tests a restore every quarter" is. Clear owners stop the situation in Vikram's meeting, where everyone was partly responsible and nobody checked the invoice. Decide who should own each task below.
Security culture and the human firewall
Policies say what should happen. Security culture is what people actually do when nobody is checking: whether a pharmacist questions an odd call, whether a manager props the back door open, whether a mistake is reported or hidden. Culture beats rules because no rulebook covers every situation, and attackers deliberately look for the situations it misses.
The human firewall mindset treats every employee as a layer of defence rather than as the weakest link. A firewall is a filter that blocks dangerous traffic before it reaches a computer; a human firewall is a person who pauses, checks and reports before acting on a suspicious request. Building it takes more than a yearly slideshow. Short, regular practice with realistic examples, an easy way to report, and leaders who follow the same rules all matter. When Vikram uses two-step login himself and never asks Neha for an exception, the stores notice.
Governance writes the rules; culture makes them real. Only the top right holds up when an attacker calls at closing time.
Measuring whether the culture is working
Culture sounds vague, but its effects can be counted, and governance needs those counts to decide what to change. Neha tracks three simple numbers each quarter. The first is how many staff report a practice phishing email, not only how many click it, because reporting is the behaviour that protects everyone else. The second is the time between a mistake and its report: minutes means people trust the system, days means they are afraid. The third is how many systems and vendor accounts have a named owner who reviewed access that quarter.
These numbers go to Vikram in plain language, alongside the top risks, so that the owner can see whether the money spent on security is changing behaviour. A falling click rate with a rising report rate is a healthy store. A low click rate with almost no reports may simply mean people delete suspicious emails quietly, which leaves Neha blind to the attacks that do get through. Like a doctor reading a blood report, the point is not one number but the pattern over time.
Mistakes are information, not crimes
The most important part of culture is how mistakes are treated. If staff are punished for clicking a bad link, they stop admitting it, and the organisation loses its earliest warning. A no-blame reporting rule, where honest mistakes reported quickly are thanked rather than punished, is what turns a three-day silent breach into a five-minute fix. This is not the same as having no consequences: deliberate rule-breaking and repeated carelessness are still handled. The lab below gives you a yearly culture budget for Tulsi Health. Switch on the measures you would fund, run five real situations through them, and see which ones stop, catch or recover from each.