A safer, smaller public footprint
A public-facing university system can be reached from anywhere on the internet. As vulnerabilities are found and exploited more quickly, each unnecessary opening creates avoidable risk for university work, data, and people.
Every publicly exposed university asset must have an active security exception on file with UT-ISO.
Why we are changing our approach
Software weaknesses are being reported at a rapid pace. Artificial intelligence can help researchers find weaknesses, and it can also help attackers speed up parts of their work. A 2026 analysis by Google Threat Intelligence Group describes these trends. We cannot assume a system is safe simply because no problem has been reported in it yet.
The UT Information Security Office (UT-ISO) is reducing unnecessary exposure to the global internet while continuing to assess and address vulnerabilities. The first question is whether the system or service needs to be publicly reachable at all. Removing an opening can eliminate a whole category of potential attacks, including attacks against weaknesses that have not yet been discovered.
Public access requires registration. The Security Exception Reporting process is UT-ISO’s public network registration process. It applies to publicly exposed university assets whether hosted on campus, in the cloud, or through a university web service. An active exception records the need for access and the plan to manage its risk.
Start by removing what is no longer needed
UT-ISO will work with responsible units and system administrators through these options, in order:
- Retire the system. If it no longer serves a current university purpose, take it out of service. Preserve needed records and follow the unit’s retirement process.
- Turn off unnecessary public services. If the system is still needed, close any web, remote access, database, or other network service that does not need to be reachable from the global internet.
- Use a more protected network. If people at UT still need the system, consider moving it to the General Network or an appropriate protected virtual network (VRF) or limited connection to campus networks. Work with IT and network teams to confirm that public inbound access has actually been removed.
- Use an established university web service. If you need a public website, ask whether University Blog Service, UT Web, Pantheon Web Hosting, or another university web service can meet the need in place of a web server promoting a lab, class, etc.
- Register any exposure that must remain. Every university asset that remains publicly reachable must be covered by an active exception on file with UT-ISO. The responsible unit uses the Security Exception Reporting process to document the business need, affected asset, protections, and review date. A submitted request is not an active exception, and approval is not automatic.
How UT-ISO prioritizes the work
We use a risk-based approach. An internet-facing system with a known exploited weakness or sensitive university data may need urgent attention. Another system may be addressed through a planned change. We consider the whole situation, including:
- How exposed it is: What can the public reach? Is access restricted, or can anyone connect?
- How likely an attack is: Are there known weaknesses, active exploitation, easy attack paths, or unsupported software?
- What could be harmed: What university service, research, personal information, or connected systems could be affected?
Urgent risk may call for a faster response, including protective network action under the Vulnerability Management Program. Units should not wait for a vulnerability notice to review unnecessary public exposure.
For faculty and unit leaders
You do not need to inspect servers yourself. Ask the IT staff who support your work to identify systems your unit operates that can be reached from the public internet, including systems hosted outside campus.
- Which systems or services are still needed, and who owns them?
- Which ones truly need public access for teaching, research, or university operations?
- Can an old system be retired, a service closed, or a site moved to a university web service?
- For every asset that remains public, is there an active exception on file with an owner, protections, and review date?
Work with your unit’s IT staff and the Information Security Office for help.
Common questions
Does this mean public university websites must close?
No. Public access can be essential. The aim is to remove access that is unnecessary. Every asset that remains public, including a university website, needs an active exception on file documenting its purpose and risk management plan.
Does moving a system to a different network automatically make it safe?
No. The destination network and access rules must be checked with your IT and network teams. The goal is to remove public inbound access where it is not needed; patching and other safeguards still matter.
What is a security exception?
It is the university’s documented process for reviewing a needed departure from security requirements. UT-ISO uses this process to register publicly exposed assets. The Security Exception Reporting page explains the approval path and required information, including affected systems, duration, risk, alternate protections, and a review date. The exception must be active; submitting a request alone is not enough.