DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

The Partner Finishes and Leaves, Half Set Up

By Deepak Kumar, CISSP

The problem: A company hires an implementation partner (an outside firm that sets up a product for you) to add a second sign-in step, such as a code on a phone, to 40 business apps in 12 weeks. At the end of the contract, 28 apps are done. The partner says the rest are “phase two.” The project is closed, the partner leaves, and there is no written list of which 12 apps are still on password only.

Words used here: an implementation partner is an outside firm that installs and sets up a product. A second sign-in step, also called multi-factor sign-in, asks for something more than a password. A handover is the formal passing of work and knowledge from one team to another. Phase two means work that is pushed to a later stage.

Think of a locksmith who fits only the front door

A locksmith is paid to secure a house. He fits a strong lock on the front door, writes “done” on the invoice and leaves. The back door has the old lock. The owner did not check. The locksmith did what was on the quote, or most of it, and he may well have meant to come back. But when the owner is asked which doors are secure, nobody can answer.

The 12 apps are the back door.

The locksmith and the back door
Front door: new lock. Back door: old lock.
Front door done. Invoice sent.
Locksmith
Which doors are secure?
Owner
Nobody can say which doors are still open.

What it looks like at work

The partner is competent and the first 28 apps are done well. The last 12 are harder: older systems, awkward settings, and owners who are slow to reply. These are example numbers. As the end date comes close, the partner puts the rest in a “phase two” note, and the steering group is pleased with 70 percent and agrees to close the project.

The project team moves on to new work. The IT admin who inherits the setup finds no list of the 12 and no notes on how the 28 were configured. Six months later, the auditor tests a sample of apps and finds some with password only.

How a partner leaves a rollout half done
  1. 11. Easy apps first28 of 40 done well, the hard ones wait
  2. 22. “Phase two”The rest goes in a note with no budget
  3. 33. Project closed70 percent is accepted
  4. 44. Partner leavesNo list of the 12, no setup notes
  5. 55. AuditSome apps found password only
Nobody owned the unfinished part after the contract ended.

Both sides have a fair point. The partner delivered what the budget and time allowed, and some apps really are hard. The company is right that it asked for all 40 and should know exactly where the work stands. Neither side lied. The gap is that nobody owned the unfinished part after the contract ended.

You will notice it when:

  • A project closes with “phase two” on the last slide and no budget behind it.
  • Nobody can list which apps, servers or sites are not covered.
  • The partner is the only one who knows how it was set up.
  • The final invoice is paid before anyone checks the work.
  • The person who inherits the system asks, “Where are the notes?”

What exactly needs fixing

The fix is not to distrust partners. It is a written handover, a final payment that depends on proof, and one named owner for every unfinished item. This card shows the whole problem on one page:

A rollout closed at 70 percent
WHAT IS BROKEN

28 of 40 apps have a second sign-in step, and nobody has a written list of the other 12.

HIGH
WHERE IT IS

The rollout contract, the project close, and the inherited setup.

WHAT COULD GO WRONG

An attacker uses a password-only app that was reported as covered.

WHAT IT COSTS US
  • A second contract
  • Exposed apps
  • False claim to the board
  • Knowledge lost
THE FIX, IN THREE MOVES
  1. 1
    1. Written handoverA done list, an open list and the settings used, in the contract
  2. 2
    2. Pay on proofHold back 10 to 15 percent until your team checks the work
  3. 3
    3. An owner eachEvery open item gets a name and a date, and phase two is funded or not
WHO FIXES IT

Who fixes it: project lead and the IT admin who inherits it

BY WHEN

By when: open list and owners in 2 weeks

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

Why it happens

  • The easy part is done first. The hard part is left to the end, when time is short.
  • “Phase two” has no owner or budget. So it never starts.
  • Handover is not in the contract. It is treated as a favour.
  • The final payment is not tied to proof. So there is no reason to finish.
  • The project team moves on. The inheritor was not in the room.

What happens if you ignore it

The company believes it is protected while part of it is not.

  • Some apps stay on password only, and the report says “roll-out complete.”
  • The company pays a second time to finish what the first contract covered.
  • When the partner’s engineer leaves, the knowledge leaves with them.
  • An audit finds a claim that was not true.

At a glance

QuestionAnswer
How likely is it to hurt us?Likely, wherever a partner is paid by contract end date.
Worst case?An attacker uses a password-only app that was reported as covered.
What does it cost?A second contract, exposed apps, and a false claim to the board.
What if we wait?Staff change and the list is never found.
What does the fix cost?A handover template and a held final payment.

How to fix it, step by step

Hand over in writing, pay on proof, then keep an owner for every open item.

  1. Write the handover into the contract. A done list, an open list, and the settings used for each app.
  2. Hold back the final payment. For example, 10 to 15 percent, released after a check by your own team.
  3. Ask for the open list before the last week. Not on the last day.
  4. Give each open item a name and a date. The owner can be the partner or your own team.
  5. Fund phase two or say it is not funded. Do not leave it as a hope.
  6. Have the inheritor attend the last two weeks. They learn it while the partner is still here.
  7. Check a sample on the ground. Open three apps and test the second sign-in step yourself.
Written handover, pay on proof, an owner
1. Written handoverA done list, an open list and the settings.
2. Pay on proofFinal payment after your own team checks.
3. An ownerEvery open item has a name and a date.
The middle step gives the partner a reason to finish properly.

The picture shows the order: hand over in writing, pay on proof, then keep an owner for every open item. The middle step is the one that gives the partner a reason to finish properly.

Who to bring in: The project lead (owns the handover), the IT admin who inherits it, procurement (writes the payment terms), and the partner’s lead engineer (supplies the written notes).

Tools and templates

Handover checklist

ItemWritten?Owner
List of apps done, with dateYes / NoName
List of apps not done, with reasonYes / NoName
Settings used for each appYes / NoName
Who to call when it breaksYes / NoName
Test we ran to confirm it worksYes / NoName

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 failed audit, lost trust
The fixThe exact action
Who fixes itOne name or one team
By whenA date, not “soon”

Email to the partner

Subject: Handover list for the second sign-in rollout

Hi. Thank you for the work on the rollout. Before we close the project, could we agree a written list of the apps that are done, the apps that are not, and the settings used? I would also like each open app to have a named owner and a date. I am not questioning the work so far. I want to make sure the last 12 apps do not fall between the contract and our own team. Can we meet for 30 minutes this week?

Field tip

Before you sign off any project, ask: “If the partner vanished tomorrow, could my team finish this from the notes?” If the answer is no, the handover is not done.

Words used in this chapter

  • Implementation partner: an outside firm that installs and sets up a product.
  • Second sign-in step: a code or prompt on top of a password.
  • Handover: the formal passing of work and knowledge to another team.
  • Phase two: work pushed to a later stage, often with no budget.
  • Open list: the items still not done.
  • Sign off: to accept work as finished.