The problem: Security wants all 120 servers patched every month. A patch is a small update that closes a known weakness. Security says, “You run the servers, so patching is your job.” IT says, “Security wants it, so security must give us the time and the budget. We also take the blame when a patch breaks something.” The patch cycle slips from monthly to quarterly.
Words used here: a service provider is a team that does work for others, such as IT running servers for the business. A service agreement is a short written deal about what work is done, how often and by when. A patch window is the planned time when servers can be updated and restarted.
Think of a chirping smoke alarm
A smoke alarm in a rented flat starts to chirp, because the battery is low. The landlord says, “The alarm is inside your home, so you change the battery.” The tenant says, “The alarm belongs to the building, so you pay and fix it.” Both have a point. The alarm keeps chirping. Nobody has agreed who climbs the ladder.
What it looks like at work
A scan shows that 90 of the 120 servers are more than 60 days behind on patches. Security asks IT to patch all servers every month. IT replies that patching is a security task. Security replies that IT runs the servers. IT says that patching needs night work, testing, and a restart of services, and no extra people. It also says that if a patch breaks an application, IT gets the blame, and security does not. Both teams send emails. The patch cycle moves to quarterly, quietly.
- 11. Security asksPatch all 120 servers monthly.
- 22. IT repliesPatching is a security task.
- 33. Security saysYou run the servers. Do it.
- 44. IT saysNo time, no budget, and we take blame.
- 55. ResultPatches slip to every quarter.
Both sides are half right. Security is right that known weaknesses must be closed on time, because attackers use them quickly. IT is right that patching takes people and planned time, and that outages caused by patches land on IT. What is missing is a written service agreement: who does what, how often, how many hours, who pays, and what happens if a patch breaks something.
You will notice it when:
- The words “not our job” appear in emails between the two teams.
- The patch cycle has no written schedule.
- Nobody knows how many hours a month patching takes.
- When a patch breaks something, nobody is sure who explains it to the business.
- Patch numbers are different in IT’s report and in security’s scan.
What exactly needs fixing
The first fix is not the patching. It is the agreement about the patching. This card shows the whole problem on one page:
Security expects IT to patch 120 servers monthly. IT says it is not its job, and the work is slipping.
The monthly patch cycle for 120 servers, between two teams.
Known weaknesses stay open for months on many servers.
- Open weaknesses
- Stalled work
- Blame game
- Audit finding
- 11. Write the service
- 22. Agree cost, time
- 33. Report monthly
Who fixes it: IT head, security head
By when: agreement in 4 weeks
A blank copy of this card is in the Tools section.
Why it happens
- The two teams see the work from opposite sides. Security sees risk. IT sees workload and outages.
- Nobody wrote the deal. So each team uses its own picture of it.
- The cost sits with IT. The benefit sits with security and the business.
- Blame is uneven. An outage after a patch is visible. A breach through an unpatched server is later, and invisible.
- There is no agreed target. “Monthly” was never signed by both.
- Capacity is not counted. The hours for patching are not in anyone’s plan.
What happens if you ignore it
Known weaknesses stay open, while both teams argue about whose job it is.
- An attacker uses a weakness that has had a fix available for months.
- The patch cycle slips again each quarter, and nobody decides it.
- The relationship between IT and security gets worse, and spreads to other topics.
- An audit finds old patches, and each team points at the other.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Very likely. Late patching is one of the most common causes of break-ins. |
| Worst case? | A break-in through a weakness with a fix that was available for months. |
| What does it cost? | A breach clean-up, a failed audit, and a broken working relationship. |
| What if we wait? | The cycle slips more, and the arguments get older and sharper. |
| What does the fix cost? | A few meetings, a one-page agreement, and a number for the hours. |
How to fix it, step by step
Write the deal, count the cost, and report the same numbers to both teams every month.
- Stop arguing about whose job it is. Say, “We both need this done. Let us agree how.”
- Write the service on one page. What is patched, how often, in which time window, and within how many days of a critical fix being released.
- Split the roles. Security sets the target and checks the result. IT plans the work and does it.
- Count the hours. How many hours a month does patching really take for 120 servers? Include testing and restarts.
- Agree who pays. If it is more work than IT can do, then security, or the business, funds extra hands, or the target is relaxed in writing.
- Agree what happens when a patch breaks something. A rollback plan, who explains it to the business, and that it is a shared risk, not IT’s fault alone.
- Use patch windows. A fixed monthly night, announced in advance, so the business expects the restart.
- Report the same numbers. One monthly report, from one source, that both teams read. “110 of 120 servers within 30 days.”
The picture shows the three parts: write the service, agree cost and time, and report each month.
Who to bring in: The IT lead (who plans and does the work), the security lead (who sets the target and checks it), a budget owner, and a business owner for the servers (who agrees the patch window).
Tools and templates
One-page patch service agreement (example)
| Item | What to agree |
|---|---|
| Scope | Which servers: all 120, or the critical ones first |
| Target | Critical fixes within 7 days, others within 30 days (set your own) |
| Patch window | Second Saturday of the month, 10 pm to 2 am |
| Hours needed | Agreed number per month |
| Who pays | Budget owner named |
| If a patch breaks something | Rollback within 1 hour, and a shared note to the business |
| Report | One monthly report, same numbers for both teams |
Blank finding card
| Field | Write here |
|---|---|
| What is broken | One line, in plain words |
| Where it is | The system, team, or process |
| What could go wrong | In one sentence |
| What it costs us | Money, time, a leak, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to the IT lead
Subject: Writing down how we patch the servers
Hi [name]. I think we are both right and we have never written it down. Security needs known weaknesses closed on time. IT needs people, time, and a fair share of the blame when a patch breaks something. Could we meet for 30 minutes and write a one-page agreement? It would cover what is patched, how often, the monthly window, the hours it takes, and who explains it if something goes wrong. I will bring the scan numbers and you bring the hours.
Field tip
Do not say, “This is your job.” Say, “Here is what we both need, and here is what each of us does.” The first starts an argument. The second starts a deal.
Words used in this chapter
- Patch: a small update that closes a known weakness.
- Service provider: a team that does work for others, such as IT running servers for the business.
- Service agreement: a short written deal about what work is done, how often and by when.
- Patch window: the planned time when servers can be updated and restarted.
- Rollback: undoing a change to get back to how things were before.