This is an original planning guide. It is not a vendor manual, an official standard, or legal advice. Example addresses use documentation ranges. Review every command before you paste it.
What this hour is for
The calculator writes a date from the clock and the severity you enter. It does not connect to a patch system.
A test system exists for a fragile application. The owner is a person. You do not disable the firewall or antivirus as part of the window.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep.
The change you can finish
Apply nothing while you are writing the note. When the lab window opens, it is one change on the system named in the ticket. Read the draft, then the system, then decide.
Rollback is the file, the record, or the snapshot you saved first. You do not invent a rollback after the only copy is gone.
- Name the finding and the severity.
- Read the date.
- Name the owner.
- Write the exception date if you need one.
- Stop.
Mistakes that outlive the statement
Patch Management Process goes wrong in a small set of ways. The list is here so the ticket can forbid them before the window.
- An exception with no end.
- A control disabled to patch.
- Production patched during the reading.
Decisions to write down
One decision for Patch Management Process: The date is written. The owner is a person. And no control was disabled.
Checks before you call it done
Confirm this before you call the change done: The finding is written. The date was read. The owner is named. No control was disabled. And nothing was installed during the reading. If one of those fails, stop.
# A due date. Not a reason to disable a control.
# 192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. A sample password is replaced. It is not a password you keep.Before you leave the system
Patch Management Process ends when the system in the note is the system in the ticket. If it is not, stop.
The draft stays a draft until a person has read the names in it. A generator does not log in, does not scan, and does not send mail.
192.0.2.10/24, gateway 192.0.2.1, 198.51.100.0/24, 203.0.113.0/24, and 2001:db8::/32 are documentation. example.com is a documentation name. They belong in the note. They are not values you publish because a draft included them.
prompt-for-this is a reminder that a secret is missing. It is not a password, a key, or a token you save. A sample password is replaced. It is not a password you keep.
One change is the window. If two things move and the result is wrong, you will not know which one did it.
If the same step fails twice, stop for the day. Restore the copy you took first.
A second person reads the scope aloud. If they cannot find it in the ticket, the note is not done.
This page is a planning guide. It is not legal advice, not an audit opinion, not a vendor manual, and not the text of a standard. You do not disable a security control to make a check pass. You do not use the page against a system you do not administer.
Tools for this guide
These tools run in the browser on this site. They do not log into your machines.
Related pillar guides
More in this cluster
The pillar for this page, and the next published pages filed with it.
- Pillar: Vulnerability Management Guide
- Explainer: Software Supply Chain Security and SBOMs
- Comparison: Vulnerability Scanning Tools Compared
- How-To: Writing Vulnerability Reports
Companion: System: Patch Management Guide for Sysadmins.