Security Exceptions: Writing Them Down With an Owner and End Date

The old medication-room printer cannot be updated, and the vendor says the label software only works on that machine. So someone says, "Just leave it for now." That was two years ago. The printer is still there, still on the network, and nobody remembers who agreed or why. When a surveyor or an auditor asks about it, there is no answer.

A security exception is a deliberate, approved departure from a security rule. Exceptions are normal in care settings, where old equipment, vendor limits and clinical needs sometimes collide with policy. The problem is not the exception. The problem is the one that was never written down.

What counts as an exception

Anything where you knowingly do not follow your own rule, or your IT provider's recommendation, for a period of time.

A device that cannot be updated or is no longer supported by its maker.

A shared login used on a unit because a clinical system requires it.

A user who is not required to use multi-factor authentication for now.

A vendor with remote access that stays open longer than intended.

A computer allowed to keep a local admin account.

A door that stays propped or unlocked for a specific operational reason.

If someone says "we know, but we have to," that is an exception. Write it down.

The fields every exception needs

One short form or a row in a shared sheet is enough. Capture these:

The rule being set aside, in plain words.

Why, including what would break or what it would cost to comply.

The risk it creates, stated honestly.

What reduces the risk in the meantime, such as isolating the device, limiting who uses it, or watching it more closely.

Owner, one named person who is accountable.

Approver, usually the administrator or someone with authority.

Start date and end date, or a review date.

What happens at the end: fixed, renewed with a new decision, or retired.

Why the end date matters most

Without an end date, an exception turns into a permanent condition. Nobody decides that. It happens by default. An end date forces a choice. On that date, the owner either reports that the issue is fixed, or the approver reviews the reasons again and renews it on purpose. Even a renewal is useful, because it shows that someone looked.

Keep the period reasonable for the risk. A higher-risk exception gets a shorter window. Ask your IT provider what is realistic for each case.

Compensating controls are not optional

Whenever you accept a gap, add something to cover it. For the old printer, that might mean placing it on its own separate network segment, switching off features it does not need, and watching for replacement options. For a shared login, it might mean a locked screen policy, added supervision or a record of who used it when. A written exception without any risk reduction is not a plan, it is a delay.

Where to keep them and who sees them

Keep the exceptions in one place, such as a shared folder or sheet with limited access, since it describes weak points. Review them at a regular meeting, such as a quarterly security check-in, and look at anything expiring soon. When someone leaves, reassign their owned exceptions. When equipment is replaced, close the matching entry.

When someone asks you about it

During an audit, an insurer review or a conversation with a surveyor or customer, a written exception record shows that you knew, you weighed it and you managed it. What counts as acceptable documentation depends on the framework, your insurer and your counsel, so confirm with them. In general, a clear paper trail is far stronger than "we have always done it that way."

Start small

You do not need to find every exception at once. Begin with the ones you already know about. Ask your IT provider for a list of devices and settings that are out of line with the standard, and ask department heads what workarounds exist. Write each one up, give it an owner and an end date, and move on.

How we can help

UnityCare IT can help you identify the exceptions hiding in your environment, such as unsupported devices and special-case accounts, and suggest sensible safeguards for each. We can provide a simple exception form and keep the list current with you. We also remind owners when an end date is approaching, so decisions get made on time.

Related service

Security monitoring, HIPAA safeguards, backups and staff training for healthcare and small businesses.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support