HIPAA & Cybersecurity

How a practice applies sanctions when security rules are missed

What the policy has to say, how a miss is handled, and the page that shows the ladder was used.

8 min read
October 30, 2026
Updated October 30, 2026
Manager reviewing a written sanction note after a security rule was missed
Quick answer
Security sanction policy

A sanction policy says what the practice does when a workforce member breaks its security policies. The Security Rule requires the practice to apply appropriate sanctions. It does not set the penalty. Write the steps, apply them the same way to owners and to new staff, and keep a record of what you did.

Someone shared the front-desk password again, after the huddle that said not to. The manager sighed and reset it. Nothing was written down. The same share happened in June, and that one was not written down either.

The requirement sits in 45 CFR 164.308(a)(1)(ii), under the security management process. The sanction policy is a required implementation specification: apply appropriate sanctions against workforce members who fail to comply with the security policies and procedures. HHS describes the Security Rule on its security rule overview. NIST’s guide for putting that duty into a small organization is NIST SP 800-66r2. None of them names a fine, a suspension, or a script. They require a policy you apply, not a sentence you file.

Appropriate means proportionate to what happened and consistent with how this office treats similar misses. A first accidental click is not the same event as a repeated share of a password after a warning. Write both on the same page so the second one is not invented in the hallway. Keep the page with the rest of the security program.

What the policy has to say

Name who it covers. Workforce includes employees, owners, temps, students, and anyone else under the practice’s direct control. A locum who uses the EHR is covered. A patient is not. A vendor with its own contract is handled under that contract, and the sanction page should say so instead of pretending the vendor is an employee.

Name the kinds of misses you actually see. Shared passwords. Looking at a chart with no job reason. Sending the record on a path the transmission card forbids. Leaving a screen open in a public area. Clicking a link and not telling anyone. You do not need a catalog of every imaginable crime. You need the misses this office has already had, plus the ones the policies you already wrote are about. If the security awareness huddle taught a rule, breaking that rule belongs on the sanction page.

Name the range of responses, in order. A coaching conversation. A written warning. A removal of access. A change in job duties. Separation, if the practice’s other employment rules already allow it. Do not invent a dollar penalty. Do not copy another clinic’s ladder if you will not use it. The ladder you will actually climb is the policy. A ladder that jumps from “nothing” to “fired” will not be used for the middle cases, and those are the ones you have.

Say that the same ladder applies to owners. A policy that disciplines the front desk and coaches the physician in private, with no note, is two policies. Write one. If an owner is the person who decides sanctions, name a backup for the case when the owner is the subject. The backup can be the privacy lead or an outside advisor the practice already uses. The point is that the page still gets a line.

How a miss is handled

Start with the facts, not the penalty. What happened, when, which policy, who was involved, and whether patient information left the office. Write that down before the conversation. A conversation based on a rumor will not match the log. If the question is a login, read the audit log first. If the question is a send, read the transmission path. Then talk.

Match the step on the ladder to the facts. A first miss that was reported by the person who made it is a different fact from a third miss that was found by someone else. Say which step you used and why. “We thought a warning was enough” is acceptable if the page shows that a warning is a real step and this was the right rung. It is not acceptable if the page is blank and the warning was a mood.

Tell the person what the next rung is if it happens again. A warning that does not mention the next step is a sigh. The person should leave the conversation knowing the rule, the response this time, and the response next time. Offer the same facts to anyone who has the same job and the same miss. Consistency is what makes the sanction appropriate. A favorite employee and a new hire do not get different ladders for the same shared password.

Close the access that the miss showed was too wide, the same day, if the miss was access. A sanction conversation on Thursday and a still-open extra login on Friday means the conversation was the whole control. The termination checklist is for people who leave. A narrowed role is for people who stay. Do the one the facts require, and note it on the sanction page.

The record of what you did

One page per event. Date, facts, policy that was missed, rung you used, who decided, and what changed in access or training. Store it where workforce records live, not in a group chat. Do not put the patient’s name in the sanction note if the note can make its point without it. The note is about the workforce member’s conduct. The incident file, if there is one, holds the patient side.

Review the pages twice a year. Count repeats by the same person and repeats of the same miss by different people. A repeat by one person means the next rung. A repeat by many people means the rule is unclear, the button is wrong, or the training did not land. Fix the system when the pattern is the system. Sanctioning the fifth person for a card nobody can find is how the policy becomes theater.

Keep the pages long enough to see a pattern. The Security Rule does not set a retention period for the sanction note. Use the same period you already use for other workforce records, and write that period on the folder. A note thrown away after a month cannot show that June and October were the same miss.

If you decide no sanction is appropriate, write that too, and why. A documented “no sanction, first report, no information left the office, retrained the same day” is an application of the policy. Silence looks like the policy was not applied. The required spec is to apply sanctions when members fail to comply. A reasoned no, written down, is still a decision. A missing page is not.

Privacy lead filing a short written record of a security sanction

What to tell people in advance

People cannot follow a ladder they have never seen. Read the one-page ladder in the same huddle that teaches the rules, and leave a copy where staff can find it without asking. The huddle is not the punishment. The huddle is how the punishment stops being a surprise. New hires hear it before they get a login, in the same hour as the other security topics.

Do not announce a specific person’s sanction in the huddle. Tell the room the rule. Tell the person the outcome in private. A public retelling is a second harm and it teaches people to hide the next miss. The record stays in the file. The lesson for everyone else is the rule, restated, without the name.

Qventive’s assessments at 200 Passaic Street in Hackensack ask for the last time a security rule was broken and the page that shows what the office did. If the answer is a reset password and a shrug, the required spec is not in use. The same file sits with the rest of the HIPAA record so the ladder is not a poster from a binder the desk has never opened.

When you change a security policy, change the sanction page if the new rule creates a new kind of miss. A transmission card that forbids a send, with no rung for using the forbidden send, is an incomplete pair. Update them together. Once a year, read the ladder out loud and ask whether anyone has seen a miss that the ladder does not name. Add that miss. A ladder frozen on the day it was typed will miss the habit that started last spring.

Owners sign the page. Not as a slogan, as the people who will use it on themselves. A signature does not create the habit. A signed page that was actually used for an owner’s miss does. If that case has never happened, the backup decision-maker should still know they exist. Write the backup’s name on the page so the first hard case is not the moment you invent the process.

Look at one closed event with a new manager before they handle a live one. Cover the name. Ask which rung they would have picked and what they would have changed in access the same day. If they cannot find the page, the folder is wrong. Move it before the next miss, not during it.

Sanction policy: common questions

Does the Security Rule set the punishment?
No. It requires the practice to apply appropriate sanctions when workforce members fail to comply with its security policies. The practice writes the ladder. Appropriate means proportionate and consistent, not identical for every miss.
Does a first accidental click require the same step as a repeated password share?
No. Write both on the ladder. A reported first miss with no information lost can be coaching and retraining. A repeat after a warning is a higher rung. Say which rung you used and why.
Are owners covered?
Yes. Workforce includes management. Name a backup decision-maker for the case when the usual decision-maker is the subject. One ladder, including for owners.
What if the office decides no sanction is warranted?
Write that decision and the reason. A documented coaching-only outcome is an application of the policy. A missing page looks like nothing was applied. Include what changed, such as retraining the same day.
Should the person’s name be announced to the staff?
No. Tell the person the outcome in private. Tell the room the rule, without the name. A public retelling teaches people to hide the next miss and can itself be a disclosure.
Qventive Healthcare

Let’s meet

A free practice technology assessment reads the last security miss and the page that shows what the office did about it.