DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

Bought, But Nobody Has Time to Install It

By Deepak Kumar, CISSP

The problem: Security buys a tool that watches every laptop for attacks. It is a small program, called an agent, that must be installed on each of the 500 laptops. The tool is handed to IT to roll out. IT has one person free, and two other projects. Months later, only 40 laptops are covered. The money is spent, but the protection is not there.

Words used here: an endpoint is a laptop, desktop or server that a person or system uses. An agent is a small program installed on each endpoint, so a security tool can watch it. A rollout is installing something on all the machines that need it. Coverage means how many of your machines have the tool working.

Think of a dishwasher still in its box

A family buys a new dishwasher. It arrives, and the box is put in the corner of the kitchen. Nobody has the weekend to fit the water pipe and the plug. For months, the family keeps washing dishes by hand, and walks past the box. The money has been spent, but nothing has changed in the kitchen.

Bought, but still in the box
A dishwasher, still in its box
Bought it!
Buyer
Who has time to fit it?
Person washing by hand
Paid for is not the same as switched on.

What it looks like at work

Security buys an endpoint protection tool for 500 laptops, as a result of an audit finding. The contract is signed in January. IT is asked to install the agent on every laptop by March. The IT team has one person available. That person has to test the agent on each laptop model, fix the cases where it slows the machine, and ask staff to restart. By May, 40 laptops are covered. Security reports to management that the tool is “deployed.” The auditor asks how many laptops are covered, and the number is 40.

How a bought tool never reaches the laptops
  1. 11. Security buysNew tool for all 500 laptops.
  2. 22. Handed to ITPlease roll it out by March.
  3. 33. IT is fullOne person, two other projects.
  4. 44. Months passOnly 40 of 500 laptops covered.
  5. 55. ResultPaid for, but not protecting us.
Nobody counted the hours of installing it, before buying it.

Both sides are half right. Security is right that the risk is real, and that the audit finding needs an answer. IT is right that a rollout takes real hours: testing, fixing, and calls from staff. Nobody counted those hours when the tool was bought. What is missing is an honest estimate of the rollout effort before the purchase, and a plan with people, time and a weekly count.

You will notice it when:

  • The tool was bought before IT was asked how long the rollout would take.
  • Coverage is reported as “deployed”, not as a number out of a total.
  • The rollout has one owner, who is also doing other work.
  • Staff complaints about slow laptops stall the rollout.
  • Licences are paid for, but a small share are used.

What exactly needs fixing

The first fix is not the tool. It is the plan: who installs it, how many hours, and how coverage is counted. This card shows the whole problem on one page:

A tool was bought, but only 40 of 500 laptops are covered
WHAT IS BROKEN

A security tool was bought for 500 laptops, but IT has no time, so only 40 are covered.

WHERE IT IS

The laptop fleet and IT's project list.

WHAT COULD GO WRONG

Attacks on the other 460 laptops go unseen.

WHAT IT COSTS US
  • Wasted licences
  • Blind spots
  • Audit finding
  • Tired IT team
THE FIX, IN THREE MOVES
  1. 1
    1. Count the effort
  2. 2
    2. Fund the rollout
  3. 3
    3. Roll out in waves
WHO FIXES IT

Who fixes it: security and IT heads

BY WHEN

By when: plan in 2 weeks

A blank copy of this card is in the Tools section.

Why it happens

  • Buying is quick and installing is slow. The purchase takes a signature. The rollout takes months of small jobs.
  • IT is asked after the decision. So it cannot say “we need two more people.”
  • The budget covers the licence only. Not the time to install it.
  • The tool breaks things. Some laptops slow down, and each case needs a fix.
  • Reports say “deployed.” Not “40 of 500.”
  • Nobody owns the end result. Security owns the purchase, IT owns the work, and the gap is between them.

What happens if you ignore it

The company has paid for protection and does not have it.

  • Attacks on the 460 laptops without the tool go unseen.
  • Licences are paid for but not used, so money is wasted every month.
  • The auditor finds a gap between what was reported and what is real.
  • IT feels blamed for a plan it was never part of.

At a glance

QuestionAnswer
How likely is it to hurt us?Very likely. It happens whenever a tool is bought without a rollout plan.
Worst case?An attack on an uncovered laptop that the tool would have caught.
What does it cost?Wasted licences, an audit finding, and a worn-out IT team.
What if we wait?Coverage stays low, and the contract renews anyway.
What does the fix cost?A planning talk before buying, and some budget for the rollout.

How to fix it, step by step

Count the hours before buying, pay for the rollout, and roll out in waves, with a number you report every week.

  1. Ask IT before you buy. “If we buy this for 500 laptops, how many hours does the rollout take, and who does it?”
  2. Count the hours honestly. Testing on each laptop model, fixing slow machines, and staff calls. Add 30 percent for surprises (set your own).
  3. Put the rollout in the budget. Extra hands, a contractor, or vendor help. Not just the licence.
  4. Name one owner for coverage. Not for the purchase, for the number of laptops protected.
  5. Start with a small pilot. About 20 laptops across different models. Fix what breaks.
  6. Then roll out in waves. For example, 100 laptops a week. Each wave learns from the last.
  7. Report coverage as a number. “140 of 500 laptops protected.” Both teams see it every week.
  8. Switch off what you do not use. If coverage stalls, ask why, before the contract renews.
Buy the tool, and the time to install it
A. Count the hours firstIT estimates the rollout effort before we buy.
B. Pay for the rolloutBudget includes extra hands or vendor help.
C. Roll out in waves20 laptops, then groups. Count them every week.
A tool is only bought when it is switched on.

The picture shows the three parts: count the hours first, pay for the rollout, and roll out in waves.

Who to bring in: The security lead (who wants the tool), the IT lead (who installs it), the budget owner, the vendor (for help), and the owner of the audit finding.

Tools and templates

Rollout effort estimate (example)

StepWhat it coversHours (set your own)
Pilot20 laptops across all models
Fixing problemsSlow machines, clashes with other software
WavesInstalling on the rest, in groups
Staff supportCalls, restarts, questions
ReserveA margin for surprises

Weekly coverage report

WeekLaptops coveredTotalPercentageMain blocker
1500
2500

Blank finding card

FieldWrite here
What is brokenOne line, in plain words
Where it isThe system, team, or process
What could go wrongIn one sentence
What it costs usMoney, time, a leak, lost trust
The fixThe exact action
Who fixes itOne name or one team
By whenA date, not “soon”

Email to the IT lead

Subject: A rollout plan for the laptop protection tool

Hi [name]. I know the tool was bought without asking you how long the rollout would take, and I would like to fix that. Could we sit down for 30 minutes and work out the hours, the people and the order of the rollout? I would like to find budget for extra help, so it does not all fall on one person. We can then report coverage as a weekly number, like “140 of 500 laptops”, so we both see progress.

Field tip

Do not report “the tool is deployed.” Report “140 of 500 laptops are protected.” One is a claim. The other is a fact.

Words used in this chapter

  • Endpoint: a laptop, desktop or server that a person or system uses.
  • Agent: a small program on each endpoint that lets a security tool watch it.
  • Rollout: installing something on all the machines that need it.
  • Coverage: how many of your machines have the tool working.
  • Pilot: a small first trial, to find problems before the full rollout.