
We have frameworks, assessments, audits, maturity models, control catalogs, and spreadsheets with impressive numbers of tabs that help us ask a ton of questions about security controls. All these things have their place. But there’s another question we sometimes forget to ask: How well is the information security program actually working for the people it is supposed to serve?
Information Security Doesn’t Operate in a Vacuum
A campus information security program exists to manage risk while enabling an institution to accomplish its missions of teaching, learning, research, and outreach. That sounds obvious. In practice, supporting an institution’s missions can get lost amid vulnerabilities, regulatory requirements, incidents, and the thousand other things competing for an information security leader’s attention.
The people and teams closest to the institution’s day-to-day work experience the security program differently. They know which processes work well and which ones everyone quietly works around (we all have stories about the server under the desk or the “secret spreadsheet” designed to bypass an irritating security control). These same users also decide when to involve the information security team early and when to wait until the last possible minute to engage. They know about applications, vendors, data flows, research projects, and emerging technologies that may not yet be prominent on the information security team’s radar.
In other words, your stakeholders know things you don’t. This isn’t an indictment of the information security team or the information security program as a whole. It’s simply the consequence of working in a large and complicated organization like a modern college or university.
Feedback Tells You How Your Controls Actually Work
One lesson I’ve learned is that there can be a meaningful difference between deploying a security control and having that control work well in the real world. Take multifactor authentication (MFA). From the security side, MFA is an obvious win. We want an additional layer of protection available if passwords are stolen or compromised. So, we deploy it, measure enrollment, monitor coverage, and perhaps congratulate ourselves on another control successfully implemented.
The user may have a slightly different perspective. Maybe they are asked to authenticate so frequently that MFA becomes a recurring interruption. Maybe the process is particularly painful when they’re traveling, teaching, working in a lab, or using a device that doesn’t fit the standard configuration. Maybe the enrollment instructions make perfect sense to the information security team but considerably less sense to everyone else.
The takeaway isn’t that we get rid of MFA because users find it annoying. Security requirements can’t be decided by popular vote. The useful takeaways for the security professional are twofold. We should:
- Understand why a control is creating friction and figure out whether we can reduce that friction without weakening the protection.
- Learn where users are acting on their own to reduce friction and understand what additional risk that might introduce in the environment.
This is just one of the reasons why stakeholder feedback is so valuable. It gives us information that control metrics alone cannot provide. A dashboard can tell me that nearly everyone is enrolled in MFA (which is great!). It can’t tell me whether the way we’ve implemented it is building good security habits or quietly teaching people to click “Approve” as quickly as possible so they can get back to work. Both are measures worth knowing.
Listening Is Also a Security Control
There is another benefit to listening to your stakeholders, but it is harder to quantify. Most information security programs depend on some version of shared responsibility. Shared responsibility means that protecting an institution’s data and IT resources is everyone’s job, with security professionals providing the tools and guidance while individuals and business units actively manage security risks in their own work.
But there is a corollary to “security is everyone’s responsibility” that I am growing increasingly uncomfortable with. If we expect people to share responsibility for security, we should let them participate meaningfully in shaping it. Asking people about risks, concerns, and priorities does not mean turning information security into a popularity contest. The accounting department doesn’t vote on firewall rules, and faculty members don’t need to select the organization’s endpoint detection platform.
But asking for feedback is the start of a useful conversation. Stakeholders can tell us where new risks are emerging, where information security controls create friction, where accountability is unclear, and where a relatively modest improvement could make a significant difference. That is the kind of actionable intelligence that we really need from our campuses to move our programs forward. Listening can help make a shared responsibility more meaningful.
Listening Means Asking Better Questions
There is an art to asking questions. Depending on how the question is designed, you can often steer someone toward a predetermined response. That is not what we want to do if we are genuinely interested in improving our campus information security programs. Instead, we need to ask questions that elicit full and thoughtful answers. I’m particularly fond of questions that make people stop and think rather than rate something from one to five. For example:
- What do you need from the information security program that you aren’t getting today?
- Where should the information security team be involved earlier?
- What risk worries you most over the next three to five years?
- What emerging risk do you think the institution (or your department) is least prepared to manage?
And one of my favorites: If you could make one investment or governance change to improve information security at our institution, what would it be?
These questions produce much richer information than “Are you satisfied with information security services?” And sometimes the answers will surprise you, which can make for a very good listening session indeed.
Don’t Confuse Feedback with Consensus
There is an important caveat: listening does not mean agreeing.
Stakeholders will sometimes ask for things that aren’t practical. Different parts of an institution may want contradictory things. Someone will almost certainly suggest eliminating a security requirement they find annoying. Occasionally, the annoying requirement is there for a very good reason.
The job of the information security professional is not to implement (or decline) every suggestion. The job is to understand and look for patterns. Where are multiple groups encountering the same problem? Where is responsibility consistently unclear? What emerging risks are stakeholders independently noticing? What security processes are encouraging the wrong behavior? Where could earlier engagement prevent problems rather than force teams to clean them up later?
Those patterns should inform risk management, strategic planning, governance, investment, and program improvement. As one of my favorite colleagues often says, “We need to make it easy for people to do the right thing.” Understanding patterns in the feedback helps you do just that.
Feedback Humanizes Information Security
Information security programs increasingly rely on strong quantitative measures: phishing susceptibility, vulnerability remediation, incident counts, coverage percentages, response times, training completion, and so on. Those metrics matter, especially in a world where higher education institutions must demonstrate that they follow a particular compliance framework or industry best practices.
But they don’t tell the whole story. If your dashboards say the information security program is thriving while the rest of the organization sees security as inaccessible, confusing, or disconnected from its priorities, you have learned something important. Now you need to figure out how to put that on your dashboard.
Over the years, I’ve become convinced that one of the best indicators of a mature security program isn’t simply how many controls it has deployed. It’s whether the program understands the organization, data, and people that it is trying to protect.
The good thing is there’s a wonderfully low-tech way to find out. Ask people. Then listen.
Need Help Listening?
At Vantage Technology Consulting Group, we help colleges and universities take a thoughtful look at their information security programs, including the part that’s easy to overlook: what the people they serve actually experience. We can help you engage campus stakeholders, identify meaningful themes, and turn what you hear into practical priorities for strengthening your security program.
This post was authored by Senior Principal and Partner Joanna Lyn Grama, JD, CISSP. Joanna leads Vantage’s information security practice and works with clients to examine and improve their cybersecurity, data privacy programs, technology governance, and compliance.