DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

The Partner Nobody Agreed On

By Deepak Kumar, CISSP

The problem: The IT team and the security team want different partners to install a new security tool. One side wins the vote. When the work hits trouble, the other side says, “It was your partner, your choice,” and stops helping.

Words used here: a partner is an outside company that installs and sets up a tool for you. The IT team is the group that looks after servers, laptops, and the network.

Think of painting your house

You and your partner at home cannot agree on who should paint the house. You want one painter. Your partner wants another. You win. Your partner says nothing. On the first day, the painters need the gate opened, the ladder moved, and the furniture covered. Your partner says, “Your painter, your choice,” and goes out. Half the wall is painted, and the painters wait and charge for the waiting.

The same happens at work with security tools.

Painting the house: half a wall, and a painter waiting
Half a wall painted, a ladder waiting
The gate is locked. We wait.
Painter (paid by the hour)
Your painter, your choice.
Partner who lost the vote
The losing side got no job, so it stepped back. The bill grows.

What it looks like at work

The company buys a new protection tool for its laptops and servers. IT suggests Partner A, a company it has worked with for years. Security suggests Partner B, which knows this tool well. In a meeting, leadership picks Partner B. The IT lead nods and says nothing.

Three weeks into the work, the partner needs access to servers and slots in the change calendar. The requests sit in IT’s queue. Security asks why. IT says: “Your partner, your choice. We have our own work to do.” The partner says IT is slowing them down. The contract clock keeps running, and the tool is only half installed.

How a partner dispute stalls an endpoint protection rollout
  1. 11. Two choicesIT wants Partner A. Security: Partner B.
  2. 22. Leaders pickPartner B it is. IT says nothing.
  3. 33. Week threeI need access to the 60 servers.
  4. 44. IT queueYour partner, your choice. We are busy.
  5. 55. StalledTool half installed. Waiting time billed.
Security cannot move IT's queue, and neither can the partner.

Security cannot move another team’s queue, and neither can the partner. That is why it feels stuck.

You will notice it when:

  • The choice of partner was made in a meeting, with no written reasons.
  • The team that lost the vote has no task and no say in the plan.
  • The partner’s access and change requests wait in a queue like any other ticket.
  • You hear “your partner” or “your tool” from the team that runs the systems.
  • The partner’s status reports mostly list what is waiting on someone else.

What exactly needs fixing

The fix is not a better partner. It is a shared plan where both teams own part of the work. This card shows the whole problem on one page:

IT stopped helping the endpoint tool rollout
WHAT IS BROKEN

Security's partner is installing the endpoint tool, and IT says, “your partner, your choice.”

WHERE IT IS

The tool rollout on laptops and servers, and IT's queue.

WHAT COULD GO WRONG

The tool stays half installed while an attack hits the gap.

WHAT IT COSTS US
  • Unused licences
  • Waiting fees
  • Months of delay
  • Broken trust
THE FIX, IN THREE MOVES
  1. 1
    1. Score together
  2. 2
    2. Give IT a job
  3. 3
    3. Date the tasks
WHO FIXES IT

Who fixes it: leader, IT, security

BY WHEN

By when: plan agreed in 2 weeks

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

Why it happens

  • The choice is made on feeling, not on a list. Nobody wrote down what a good partner looks like.
  • The team that will run the tool is not really asked. Or it is asked and then overruled.
  • The losing side gets no job. It is easy to step back when you have no part in the plan.
  • The contract binds the partner, not the IT team. Nothing makes IT deliver access on time.
  • Friendships get in the way. One side may have a long relationship with a partner or a vendor.
  • Nobody writes the decision down. A year later, everyone remembers it differently.

What happens if you ignore it

You pay for a tool and a partner, and you do not get the protection.

  • The rollout drags, and the gap stays open.
  • Licences are paid for but only partly used.
  • The partner’s bill goes up, because waiting time is charged.
  • Trust between IT and security drops, which makes the next project harder.

At a glance

QuestionAnswer
How likely is it to hurt us?Very likely, whenever the team that supports the work was not part of the choice.
Worst case?The tool never gets fully installed, and an attack hits the gap it was bought to close.
What does it cost?Wasted licence money, fees for waiting time, and months of delay.
What if we wait?The partner leaves, the tool stays half set up, and everyone blames everyone.
What does the fix cost?A few hours of planning and a short written agreement before work starts.

How to fix it, step by step

Make the choice together, and make the plan together.

  1. Agree on a list before anyone picks. For example: skill with this tool, price, fit with what IT already uses, help after go-live, who runs the tool later, and how to leave if it goes badly.
  2. Score the partners together. Both teams score each partner on the same list.
  3. Write the decision down. Who agreed, who did not, and why. Keep it where both teams can see it.
  4. Give the other side a real job. IT reviews the plan and owns the server, access, and change tasks.
  5. Get IT’s promises in writing. For example: access within a set number of days, and reserved change slots.
  6. Put IT’s tasks in the partner’s plan, with dates. A dated task is much harder to ignore than a request.
  7. Meet for 15 minutes every week. The partner, IT, and security look at the same plan.
  8. If IT blocks the work, go up with the plan. Show the dated task that is waiting. Do not argue about the choice.
  9. Name who runs the tool afterwards, before go-live. Otherwise the next argument starts on day one.
Choose together, then plan together
1. Score both partnersIT and security score A and B on the same list.
2. Give IT a real jobServer access and change slots, with dates in the plan.
3. Meet every week15 minutes. Partner, IT and security look at one plan.
People rarely walk away from a plan they own part of.

The picture shows both halves: a fair choice first, then a plan that both teams own.

Who to bring in: The leader who made the final choice, the security lead, the IT lead, the partner’s project manager, and procurement if they hold the contract.

Tools and templates

Partner scorecard

What mattersHow much (1 to 5)Partner APartner B
Skill with this tool5
Price, all costs included4
Fit with what IT already uses4
Help after go-live4
Who runs the tool afterwards3
How to leave if it goes badly3

Decision record

FieldWrite here
DecisionWhich partner, and the date
ReasonsThe top three, from the scorecard
Who agreedNames
Who did not agree, and whyNames and one line each
What IT will provideAccess, change slots, and by when
Who runs the tool afterwardsOne name

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 gap left open
The fixThe exact action
Who fixes itOne name or one team
By whenA date, not “soon”

Email to get IT’s promise

Subject: What we need from IT for the rollout

Hi [name]. We have chosen the partner, and I want the plan to work for IT too. The partner needs three things from your team: server access, a set of change slots, and one contact person. Could you tell me by [date] what you can promise? If a date does not work, I would rather change the plan now than find out in week three.

Field tip

The side that lost the vote needs a job in the plan. People rarely walk away from a plan they own part of.

Words used in this chapter

  • Partner: an outside company that installs and sets up a tool for you.
  • IT team: the group that looks after servers, laptops, and the network.
  • Rollout: putting a new tool onto all the machines that need it.
  • Change slot: a set time when IT is allowed to change live systems.
  • Go-live: the day the tool is declared ready for real use.