Tracking Security Fixes to Done: A Simple Remediation Log

An assessment report arrives with 23 pages and a long list of findings. The administrator reads it, nods, and puts it in a folder. Six months later, a new auditor or insurance renewal asks what was done about the report, and nobody can say. Half the items were fixed, some were forgotten and a few were discussed in a hallway and dropped.

A remediation log is the antidote. It is one list, in one place, of every issue you know about, with who is fixing it and what state it is in. It turns a report from a document you read once into a work list you finish. For a small operator, a shared spreadsheet is enough.

What goes into the log

Findings come from many places, and all of them belong on the same list.

Security or risk assessments.

Incident reviews, including near misses.

Notes from a surveyor, auditor or insurer.

Vendor or IT provider recommendations.

Staff reports, such as a propped door or a posted password.

Gaps found during a backup test or a drill.

Keeping one list prevents the same issue from being tracked in three places, and none of them accurately.

The columns to use

Keep them minimal so the list gets maintained.

ID or number, so you can refer to it.

Finding, in a sentence anyone can understand.

Source and date found.

Priority, such as high, medium or low, based on the effect on residents, operations and data.

Owner, one named person.

Planned action, the specific step.

Target date.

Status: open, in progress, done, or accepted.

Date closed and how it was verified.

Triage in an hour

When a new report arrives, resist the urge to fix everything at once. Sit down with the security lead, the administrator and IT.

Enter every finding in the log, even ones that look small.

Mark anything that affects safety, resident information or the ability to run the building as high.

Group related items, since one project often closes several findings.

Assign owners, and agree on dates you can keep.

Mark items that are not worth doing now as candidates for formal acceptance, covered below.

Closed means checked

An item is not done because someone says it is. Decide how each fix will be verified, and record it. For a backup fix, that might be a successful test restore. For an access change, a check of the account list. For a physical fix, a walk-through by the person who found it. Verification protects you from the quiet assumption that a task was completed.

Accepting a finding on purpose

Some findings will not be fixed this year, because of cost, a vendor limit or low risk. That can be sensible, but it has to be a decision. Mark the item as accepted, note who approved it, the reason, what reduces the risk in the meantime and a date to look again. This is a close cousin of a written security exception. Ask your insurer and counsel how they view documented acceptance of risk.

Keeping the log alive

A log only works if people open it.

Review it at a regular check-in with department heads, even briefly.

Highlight items past their target date and ask what is blocking them.

Report progress to the owner or administrator in a few lines, such as how many items are open, closed and accepted.

Do not delete closed items. Keep them as a record, and archive old ones once a year.

Limit access, since the log describes weaknesses.

Over time, the log tells a story: what you found, how fast you responded and what you decided. When an auditor or insurer asks, that story is better than any recollection.

Report progress in plain terms

Once a month, send the administrator or owner a few lines: how many items are open, how many were closed since last time, which high-priority items are late and what help is needed. A short note keeps the log in view without another meeting. If an item has been late through several reviews, say so directly and ask for a decision, whether that means more time, a different owner, a budget approval or a formal acceptance with a new review date.

How we can help

UnityCare IT can enter the technical findings from an assessment into a log for you, translate each into plain language and propose a realistic order of work. We carry out many of the fixes ourselves, and we can verify and report back so items are closed with evidence. We can also join your regular check-in to review the list.

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