DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

Invited in the Last Week

By Deepak Kumar, CISSP

The problem: Security hears about a project when it is almost finished. It is asked to “just sign off.” When it finds a big problem, the project team says, “It is too late to change that.” Security is blamed for either delaying the launch, or for letting a weak system out.

Words used here: a sign-off is a formal “yes, this can go live.” A design review is a short meeting where the team shows how a system will be built, before it is built.

Think of an electrician who arrives after the plaster

A family builds an extension. The walls go up and the plaster goes on. Only then does someone ask the electrician to “quickly check the wiring.” The electrician sees that the wiring is not safe, but it is inside the walls. To fix it, the plaster has to come off. The builder says, “The walls are done.”

The electrician who arrives after the plaster
Hidden wiring inside the plastered wall
Can I check the wiring?
Electrician
The walls are done.
Builder
A check after the plastering costs the most.

Security checked at the end is the electrician after the plaster.

What it looks like at work

A project builds a new customer app. The idea, the design, and most of the code are finished without anyone from security. In the last week, security is asked to approve it. It finds that customer data is stored in a way that anyone with a link can read. Fixing it means changing the design. The project team says, “The client demo is on Friday.” Security has two bad options: block the launch, or approve something it knows is weak.

Security joins in the last week
  1. 11. IdeaNobody from security is there
  2. 22. DesignBig choices are made without it
  3. 33. BuildWork is done as fast as it can
  4. 44. Last weekSecurity is asked to sign off
  5. 55. ResultBig findings, no time to fix
The later security joins, the more it costs and the less can change.

Both sides are half right. The project team is right that it has a fixed date, and that security was not part of the planning. Security is right that the problem is real. What is missing is a few short checkpoints early in the project, when changes are still cheap.

You will notice it when:

  • Security first sees the project when it is almost done.
  • The sign-off is a form on the last day.
  • Findings are big, and the answer is “we will fix it later.”
  • Project teams see security as a gate at the end, not as help along the way.
  • Nobody knows when to call security.

What exactly needs fixing

The first fix is not a stricter gate at the end. It is a few early, short checkpoints that everyone knows about. This card shows the whole problem on one page:

Security is invited when it is too late
WHAT IS BROKEN

Security sees a project in the last week, when the big choices are made.

WHERE IT IS

The project plan, the design stage, and the go-live sign-off.

WHAT COULD GO WRONG

Big flaws are found when there is no time or money left to fix them.

WHAT IT COSTS US
  • Late rework
  • Missed dates
  • Weak launch
  • Blame on security
THE FIX, IN THREE MOVES
  1. 1
    1. Add early checkpoints
  2. 2
    2. Keep each one short
  3. 3
    3. Agree who can stop
WHO FIXES IT

Who fixes it: the head of delivery

BY WHEN

By when: the next project start

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

Why it happens

  • Nobody told security. Projects start in the business, and security is not on the list.
  • Teams think security slows them down. So they call it as late as possible.
  • There is no agreed moment to involve security. It depends on who remembers.
  • Security is small. It cannot join every project from the start.
  • Design decisions feel “not security.” But the biggest risks are often decided in design.
  • The sign-off is the only formal step. So everything lands on it.

What happens if you ignore it

The biggest problems are found when they cost the most.

  • Big flaws are found when changing them means rebuilding.
  • The launch slips, or a weak system goes live.
  • Security is blamed whichever way it goes.
  • Project teams hide work from security next time.

At a glance

QuestionAnswer
How likely is it to hurt us?Very likely, on any project that has a fixed launch date.
Worst case?A weak system goes live because there was no time to fix it.
What does it cost?Rework, missed dates, and a damaged relationship.
What if we wait?The next project does the same, and the cost grows.
What does the fix cost?A few short meetings per project.

How to fix it, step by step

Move security earlier, in small steps, and agree the moments in advance.

  1. Agree the checkpoints with the head of delivery. Four moments: idea, design, build, and before go-live.
  2. Keep each one short. A 10-minute chat at the idea stage, and a 30-minute look at the design.
  3. Give the project team a short list of questions. What data do we hold, who will see it, how do people log in, what do we connect to?
  4. Set automatic checks in the build. They run every time code changes, so nobody has to remember.
  5. Make the final check a quick look at what changed. Not a new review from scratch.
  6. Agree who can stop a launch. And for what: only critical issues, and the head of delivery decides.
  7. Put the checkpoints into the project plan template. So they are there from day one.
  8. Follow up on the first few projects. Ask what worked and what felt like a delay, and adjust.
Four small checks along the way
Idea10-minute chat: what data, and who sees it
Design30-minute look at the main risks
BuildAutomatic checks on every change
Before go-liveA quick look at what changed since design
Four small checks beat one big surprise at the end.

The picture shows four small checks. Each one is short, and together they replace one big surprise.

Who to bring in: The head of delivery, project managers, the lead architect or developer, and security.

Tools and templates

Questions for the 10-minute idea chat

QuestionWhy it matters
What data will this hold?Sets how strong the protection must be
Who will use it, and from where?Decides how people log in
What other systems does it connect to?Shows where problems can spread
Does a client or law set rules for it?Brings in contract and legal needs
Who owns it after go-live?Avoids the “whose is it” fight later

Four checkpoints at a glance

StageLengthWhat happensWho comes
Idea10 minutesChat about data, users, connectionsProject lead, security
Design30 minutesLook at the main risksArchitect, project lead, security
BuildAutomaticChecks run on every changeDevelopers, security sets them up
Before go-live30 minutesLook at what changed since designProject lead, security

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 head of delivery

Subject: Four short security checkpoints for every project

Hi [name]. Security is often asked to sign off in the last week, when big changes cost the most. I would like to agree four short checkpoints, at the idea, design, build, and before go-live. Together they take about an hour per project, and they should save the last-week panic. Can we meet for 30 minutes to look at a one-page plan?

Field tip

Do not ask to be invited earlier. Offer a 10-minute chat at the start. It is hard to say no to, and it changes the whole project.

Words used in this chapter

  • Sign-off: a formal “yes, this can go live.”
  • Design review: a short meeting where the team shows how a system will be built.
  • Checkpoint: a planned moment when a project pauses for a quick check.
  • Go-live: the day a project is released for real use.