The more important question is: Do we have it?
Is the affected technology running somewhere at uOttawa? Where is it? Who looks after it? What service depends on it? Is it exposed to the Internet? And, if we need to act quickly, who do we call?
A vulnerability is simply a weakness in technology that someone could take advantage of. When a serious vulnerability becomes known, finding and fixing affected systems quickly matters because the longer the weakness remains exposed, the more opportunity there is for it to be used against us.
In theory, those sound like simple questions, but in reality, they are not always easy to answer.
Knowing what we have matters
Think about everything that makes up the University’s technology environment: applications, servers, cloud services, network equipment, research systems, specialized devices and services provided by external companies.
uOttawa’s Policy 116 reflects that reality. Its definition of IT assets extends well beyond traditional computers and includes software, systems, networks, cloud-based resources, storage, mobile and IoT devices, and technology operated on the University’s behalf by external organizations
Cybersecurity is a shared responsibility
This is where cybersecurity becomes much more a team sport than an individual one.
Information Security can monitor threats, investigate suspicious activity and help teams understand vulnerabilities. But we depend on faculties, services, researchers and IT teams to know the technology they operate and the services they support.
The University’s own security guidance puts it simply: security is everyone’s responsibility.
For those of us who manage technology at uOttawa, that means a few practical things:
- Know what your team operates. Systems, applications, infrastructure and externally hosted services all count.
- Know who is responsible for them. When something happens, we need to reach someone who understands the technology and the service it supports.
- Keep that information current. A contact or inventory that was accurate two years ago may not help us during an incident today.
- Let us know when things change. New systems, significant changes and new third-party services can change our exposure.
Bring Security in early. It is much easier to work through a security concern while options are still open than after a system has gone into production.
When the next vulnerability arrives
There will be another critical vulnerability. Probably sooner than any of us would like.
When it arrives, our first conversation should be about what we need to do, not about trying to figure out whether we have the technology or who owns it.
Are we affected? What does it support? Who needs to act?
If we can answer those three questions quickly, we are already in a much better position to protect the University.
And that starts with something very basic: knowing what we have and who is responsible for it.