Why Colleges and Universities Are Such Attractive Cyber Targets

Blog Jonathan Kimmitt todayNovember 16, 2026

Background
share close

Ask a university’s IT department what equipment is reachable from the internet. Then go ask Facilities. Then ask the person who runs a research lab on the other side of campus.

You may get three different answers. And all three people may be telling you everything they know.

That’s part of what makes higher education so interesting from a cybersecurity standpoint. A campus has classrooms, residence halls, payment systems, research labs, and buildings full of equipment that someone has to keep running. A vendor may have set up remote access to a building controller years ago. A research team may have put a server online to share data with another university, finished the project, and moved on. Central IT can do a good job managing the systems it knows about and still have equipment on campus that nobody is checking.

Then there’s the size of the internet connection. A research university needs enough bandwidth to move enormous datasets, support thousands of students, and collaborate with institutions around the world. If an attacker gets control of a machine on that network, they can put that bandwidth to work too. But the connection itself is only part of the story. An attacker scanning the internet may come across a vulnerable device before they even know who owns it. From the university’s side, that can feel like being singled out. From the attacker’s side, it may have started with finding a machine that answered.

And once they find one machine, how many others look just like it?

Say you have 500 lab computers built from the same image. That’s a sensible way to manage 500 computers. It also means a vulnerable application or a bad setting in that image can show up 500 times. Whether an attacker can move from one machine to the next depends on what those computers can reach and whether they share things like administrative credentials. The same standardization gives IT a way to fix the problem across the fleet. The part I’d want to see is the list of machines that missed the fix. There’s almost always a reason one was offline, one was tucked away in a lab, and one hasn’t checked in for three months.

**Then there’s the question of who’s there to deal with it.**

In higher ed, you might have someone who’s been on campus for 25 years working alongside someone in their first IT job. The person who’s been there forever knows which building will lose access if you shut down a particular switch. They might also be the only person who knows. The person who just started may be the one watching the alerts at night. If they spot something serious at 2 a.m., do they know who to call? Can that person authorize them to shut something down? Who’s the backup?

Those questions get harder when the university has trouble competing on pay. You can have good people and still struggle to hire or keep enough experienced staff to cover the work. EDUCAUSE has documented those hiring and retention pressures in higher education cybersecurity and privacy. A vacancy on an org chart looks like one open position. To the team, it can mean another night on call and another system review that gets pushed to next month. [EDUCAUSE research on staffing and budgets]

There’s plenty at stake if someone gets in. Universities hold student records, employee information, payment data, and years of research. They also run on deadlines everyone knows about. Registration opens on a certain day. Payroll has to go out. Finals are on the calendar. An attacker who can interrupt one of those operations has a way to put pressure on the institution, even while IT is still trying to figure out what happened.

When Vanderbilt University reported an active cybersecurity incident on November 9, it asked people to shut down university devices and disconnect from campus Wi-Fi. It told anyone who noticed suspicious activity to report it from a separate device or by phone. That detail caught my attention. If I tell my campus to turn off its computers and get off Wi-Fi, how am I going to get the next instruction to everyone? 

That’s a question I’d put in front of campus leadership before the next incident. Pick a Friday evening. The person who knows the network best is out of town, and the service desk has just received three calls about files disappearing. Walk through the first hour. Who answers the phone? Who can take a system offline? And once you do, how do you tell everyone what to do next?

Written by: Jonathan Kimmitt

Rate it

Previous post

Similar posts