DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

Security Sign-Off Is Asked For, but Given Two Days at the End

By Deepak Kumar, CISSP

The problem: A client contract says the system needs a security sign-off before go-live. The project team builds for three months and then asks security to sign off in the last two days. Security finds that the file upload feature accepts any type of file, and the fix needs about a week. The team must either launch late or launch with the risk.

Words used here: a sign-off is a written “yes, this is safe enough to go live” from the security team. Go-live is the day the system is opened to real users. A risk acceptance is a signed note from a business owner saying, “We know about this risk and we accept it, until this date.”

Think of the inspector invited the day before opening

A restaurant owner is opening tomorrow. Today she calls the fire inspector and says, “Please check everything.” The inspector needs a week to check, and to check again after any repairs. At this point, the inspector can only say yes, or stop the opening. Neither is a real inspection. An inspector invited in the first month could have shown her where to put the exits.

The inspector is invited the day before the grand opening
Banner: Grand opening, tomorrow
Please check everything today.
Restaurant owner
I need a week to check and recheck.
Fire inspector
A check that comes last can only say yes, or stop the opening.

What it looks like at work

The contract says, “The supplier shall obtain security sign-off before go-live.” Nobody talks about it for three months. Two days before the launch, the project manager sends a message to security: “Please sign off by Friday.” Security starts testing and finds that the file upload feature accepts any file type, including programs. The fix is not a small one. The upload code has to be changed and tested again, and that takes about a week. Now the project manager says, “We cannot slip, the client is waiting.” Security says, “I cannot sign this off.”

How the security sign-off ends up with two days left
  1. 11. ContractSecurity sign-off before go-live.
  2. 22. Build runsThree months of building. No check.
  3. 33. Two days leftPlease sign off by Friday.
  4. 44. Security findsUpload accepts any file. Fix: a week.
  5. 55. ResultLaunch late, or launch with risk.
Both choices were forced on the team by the calendar.

Both sides are half right. The project team is right that the date is fixed, and that a late stop is costly. Security is right that a rushed yes is not a real sign-off. What is missing is a plan: when security sees the work, how long it needs, and what happens when it finds something big late.

You will notice it when:

  • The contract mentions security sign-off, but the project plan does not.
  • Security first hears about the project in the final weeks.
  • “Sign off by Friday” is the first message security gets.
  • Findings are argued about, instead of being fixed or accepted by name.
  • Go-live goes ahead with open findings and no signed record.

What exactly needs fixing

The fix is not a better test. It is a plan that puts security in early, and a rule for what happens with late findings. This card shows the whole problem on one page:

Security sign-off is asked for, but given two days at the end
WHAT IS BROKEN

The contract needs a security sign-off, but security sees the product two days before go-live.

WHERE IT IS

The project plan and the go-live date in the contract.

WHAT COULD GO WRONG

A big flaw is found too late, or the sign-off is just rushed.

WHAT IT COSTS US
  • Late launch
  • Rushed review
  • Unfixed risk
  • Client trust
THE FIX, IN THREE MOVES
  1. 1
    1. Test from day one
  2. 2
    2. Plan the sign-off
  3. 3
    3. Agree late finds
WHO FIXES IT

Who fixes it: security, project head

BY WHEN

By when: plan in 2 weeks

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

Why it happens

  • The contract is signed by sales, and the plan is made by delivery. The sign-off clause falls in the gap between them.
  • Security is seen as a gate at the end. So it is booked at the end.
  • Nobody counts the days security needs. Testing and re-testing take about ten working days.
  • Early builds are not ready to test. So the team waits for the finished product.
  • There is no rule for late findings. So every late finding becomes a fight.
  • Dates are promised to the client first. Security time is not part of the promise.

What happens if you ignore it

The sign-off turns into a stamp, or into a stop.

  • The system goes live with a known flaw, such as an upload feature that accepts any file.
  • Or go-live is delayed by a week, and the client loses trust.
  • Security is blamed either way: “the blocker”, or “the team that signed it.”
  • The next project repeats the same pattern.

At a glance

QuestionAnswer
How likely is it to hurt us?Very likely. It happens on most client projects with a sign-off clause.
Worst case?A flaw goes live under a “signed off” label, and is used by an attacker.
What does it cost?A late launch, or a security incident for the client.
What if we wait?The next deadline will look the same.
What does the fix cost?A line in the plan, ten working days, and one agreed rule.

How to fix it, step by step

Start early, agree the plan, and decide late findings in advance.

  1. Find the sign-off clause at the start. Read the contract when the project begins and tell security about it that week.
  2. Put security in the project plan. Add dates for design review, early testing, and the final check.
  3. Test each release as it is built. A small test every few weeks finds the upload problem when it costs a day to fix, not a week.
  4. Write the sign-off plan. Who signs, what they check, how many days they need (for example, ten working days), and what must be ready before they start.
  5. Give security an entry checklist. The team hands over a test environment, a list of features, and test accounts. If the checklist is not complete, the clock does not start.
  6. Agree the late-finding rule in advance. For a high finding: fix it before go-live, or go live with a signed risk acceptance from a named business owner, a safe workaround if one exists, and a fix date.
  7. Tell the client early. If a finding will move the date, the client hears it from the project manager, with the options.
  8. Review it after go-live. What did security find, and when? What can be moved earlier next time?
Three ways to make security sign-off work
A. Security from day oneTest each release as it is built, not at the end.
B. A plan in the contract10 working days, and a ready-to-test checklist.
C. Risk-based go-liveLate find: fix it, or go live with signed risk and a date.
Start early, agree the plan, and decide late finds in advance.

The picture shows the three parts that work together. Without the first, the other two are only a way to manage a late surprise.

Who to bring in: The security lead (who needs the days), the project manager (who owns the plan), the account or sales lead (who knows the contract), and the client contact.

Tools and templates

Sign-off plan (example)

StepWhenOwner
Read the sign-off clauseProject startProject manager
Design reviewMonth 1Security
Early test of each releaseEvery 3 to 4 weeksSecurity and developers
Entry checklist complete15 working days before go-liveProject manager
Final check and re-check10 working daysSecurity
Sign-off or risk acceptance3 days before go-liveSecurity and business owner

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 project manager

Subject: Security sign-off plan for [project name]

Hi [name]. The client contract needs a security sign-off before go-live on [date]. To make that date safe, I would like to put security into the plan now. I suggest a design review this month, a short test of each release, and ten working days for the final check, with a ready-to-test checklist from your team 15 working days before go-live. I would also like us to agree today what happens if we find something big late: either we fix it, or the business owner signs a risk acceptance with a fix date. Can we meet for 30 minutes this week?

Field tip

Do not ask, “Can you sign this off by Friday?” Ask, “When can you first see something to test, and how many days do you need at the end?”

Words used in this chapter

  • Sign-off: a written “yes, this is safe enough to go live” from security.
  • Go-live: the day the system is opened to real users.
  • Risk acceptance: a signed note from a business owner saying they know about a risk and accept it until a date.
  • Entry checklist: the list of things the team must hand over before security can begin testing.
  • File upload flaw: a feature that lets users send files, but does not check what kind of file it is.