The problem: Security says, “This must be fixed.” IT says, “That is the project team’s system.” The project team says, “The client asked for it this way, and we have no time.” Weeks go by. Nothing changes.
Words used here: the IT team means the people who look after servers, laptops, and the network. The project team means the people who build and deliver work for a client.
Think of a door with a broken lock
Picture a shared office building. The lock on the back door is broken. The shop owner says the landlord should fix it. The landlord says the builder fitted it. The builder says the shop owner asked for that lock. Everyone knows the door is open at night. Nobody fixes it, because nobody is the one who decides.
This problem is the same, with computers instead of doors.
What it looks like at work
Your project team built a customer portal for a client. Security notices that anyone can log in with just a password. There is no second check, like a code sent to the phone.
Security tells the IT team: “Please turn on the second check.” IT replies: “We only look after the server. The project team set up the portal.” The project manager says: “The client’s old system cannot handle it. They asked for it this way, and my team is busy until the release.”
Three weeks later, the client’s auditor asks: “Why is there no second check on the portal?” Every team says, “I told someone.”
- 1Security seesPortal login needs only a password.
- 2Asks ITWe only host it. Ask the project.
- 3Asks projectClient asked for it. We have no time.
- 4Weeks passStill waiting for another team.
- 5Auditor asksWhy no second login check?
Each team is right about its own piece. That is why nothing moves.
You will notice it when:
- The same issue goes back and forth by email for weeks.
- Every team has a good reason why it is not theirs.
- Nobody can name the one person who decides.
- “It is the client’s requirement” ends the talk, but nobody has checked what the contract really says.
- The ticket keeps saying “waiting for another team.”
What exactly needs fixing
The first thing to fix is not the setting. It is the missing decision. This card shows the whole problem on one page:
The client portal needs only a password to log in. Three teams know. Nobody decides.
The client portal, its server, and the project behind it.
A stolen password opens client data to a stranger.
- A lost client
- A failed audit
- Leaked data
- Angry calls
- 1Get one decision
- 2Name one owner
- 3Set one date
Head of the project
A decision in 7 days
A blank copy of this card is in the Tools section, so you can use it in your own tickets.
Why it happens
- Each team owns a small piece. Nobody owns the whole thing.
- Security can advise, but cannot give orders to another team.
- “Client requirement” sounds final, so people stop asking. Often the contract only says the system must work with the client’s system. It does not say it must stay weak.
- Project teams are measured on dates and money. A fix costs both.
- IT is paid to keep servers running, not to change the project’s settings.
- Nobody wants to give the client bad news.
What happens if you ignore it
The gap stays open, and every team keeps saying, “I told someone.”
- The weakness stays open for months, because waiting feels safe to every team.
- The client’s auditor finds it, and the client trusts you less.
- When something goes wrong, the blame game starts and the real fix is delayed again.
- Security gets a name for raising issues that never get closed.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Quite likely. Auditors and attackers both look for this. |
| Worst case? | Client data stolen, and the contract lost. |
| What does it cost? | Clean-up time, a failed audit, maybe penalties, and lost trust. |
| What if we wait? | The gap stays open and the blame game gets worse. |
| What does the fix cost? | Usually a few hours of work and one honest talk with the client. |
How to fix it, step by step
Solve the decision first. The technical fix comes second.
- Write the problem on one card. Facts only: what, where, and what could happen. No blame words.
- Find the one person who can say yes. Ask: “Who answers for this system if something goes wrong?” That is usually the head of the project. It is rarely IT or security.
- Get all three teams in one 20-minute meeting. One meeting beats ten emails. Read the card out loud. Ask each team: “What is stopping you?”
- Check each excuse. “It is a client requirement”: what does the contract really say? “No time”: how many hours, really? Often it is less than people fear.
- Offer three choices. Fix it now. Or fix it by a date and protect it in the meantime. Or accept the risk, in writing, by the person who owns it. If the client asked for it, the client signs too.
- Write the decision down. One owner, one date, sent to all three teams.
- If nothing moves in a week, go one level up. Take the card and the three choices. Do not take a complaint about the other teams.
- Check that it was really done. Close the ticket only after you have seen it.
The whole method in one picture: a card, one meeting, and an owner who picks one of three choices.
Who to bring in: The head of the project (the decision), the IT team (the server), the project manager (time and the client), and, if the client asked for it, the person who looks after the client relationship.
Tools and templates
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 failed audit, a lost client |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to call the meeting
Subject: One decision needed: login check on the client portal
Hi all. The client portal has no second login check, and nobody has said yes or no yet. Can we meet for 20 minutes this week? We need to pick one of three things: fix it now, fix it by a date and protect it meanwhile, or accept the risk in writing. I am not looking for someone to blame. I am looking for one decision and one name.
The three choices
| Choice | What it means | Who signs |
|---|---|---|
| Fix it now | The setting is changed and checked | Head of the project |
| Fix it by a date | A date, a stop-gap, and a named owner | Head of the project |
| Accept the risk | The gap stays, and the owner says so in writing | Head of the project, and the client if they asked for it |
A note to the client
We found that the login setup in your requirement is no longer safe. We would like to update it, and it can be done as a small change. If you would rather keep it as it is, we need your written confirmation that you accept the risk.
Field tip
Do not ask, “Whose problem is this?” Ask, “Who decides, and by when?”
Words used in this chapter
- IT team: the people who look after servers, laptops, and the network.
- Project team: the people who build and deliver work for a client.
- Second login check: a code sent to your phone, on top of your password.
- Client requirement: something the client asked for in the contract.
- Audit: a check that a company follows its own rules.
- Accept the risk: the owner decides, in writing, to leave a weakness in place and carry the cost if it goes wrong.