DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

Two Answers From the Same Security Team

By Deepak Kumar, CISSP

The problem: A project is building a customer portal. The security architect writes: “Use the company login system, with a second step.” The same day the application security lead writes: “Build a separate login with a lockout.” The project lead now has two answers from one department and no way to know which is right. He picks the quicker one.

Words used here: a security architect designs how systems should be built safely. Application security (AppSec) checks that the software itself is written safely. A login lockout blocks an account after too many wrong tries. A penetration (pen) test is a planned attempt to break in, done by an expert.

Think of two navigators

A driver has two navigators in the car. One says, “Take the left road.” The other says, “No, take the right road.” Both know the area. Both are probably right about something. The driver, with a van to deliver and a clock ticking, takes the road that looks easier.

The driver is not at fault. The two navigators never agreed before they spoke.

Two navigators at a fork
A fork in the road, a van to deliver
Take the left road.
Navigator A
No, take the right.
Navigator B
The driver is not wrong. The navigators never agreed first.

What it looks like at work

The customer portal is due in six weeks. The architect has a design standard that says all new systems use the company login. The AppSec lead has seen attacks on shared logins and prefers a separate one with its own limits. Each writes to the project lead, who is not a security person.

The project lead asks, “Which one?” and gets two long replies, each polite and each different. With the date close, he builds the simpler separate login and skips the lockout. The pen test finds that anyone can try thousands of passwords against it.

How two answers become a weak launch
  1. 11. Two repliesArchitect and AppSec differ on the login
  2. 22. Project asks“Which one?” Two long replies
  3. 33. Date is closeHe picks the quicker option
  4. 44. Lockout skippedA separate login, no limit on tries
  5. 55. Pen testThousands of password tries get through
Two answers leave the choice to the one who is not an expert.

Both sub-teams have a fair point. The architect wants fewer logins to protect, which is a real gain. The AppSec lead wants a login that can be defended, which is also a real gain. They are not enemies. They simply sit in different parts of the department and each answers the question as it reaches them.

You will notice it when:

  • A project says “security told us two different things.”
  • Replies come from different people on the same question, a day apart.
  • Projects go to the person they know best, not the right one.
  • Security gives advice in a meeting that contradicts advice given in writing.
  • The pen test finds something one sub-team had already warned about.

What exactly needs fixing

The fix is not to decide which sub-team is right. It is to give projects one door and make sure the answer behind it has already been agreed. This card shows the whole problem on one page:

Two answers, one department
WHAT IS BROKEN

The project got two different login designs from two security leads on the same day.

HIGH
WHERE IT IS

The customer portal login, and the way security answers projects.

WHAT COULD GO WRONG

The project picks the easier answer and a weak login goes live.

WHAT IT COSTS US
  • Weak design ships
  • One to two weeks lost
  • Late redesign
  • Projects stop asking
THE FIX, IN THREE MOVES
  1. 1
    1. One front doorOne named person or shared mailbox for project questions
  2. 2
    2. Settle insideBoth leads in one room for 30 minutes, head of security breaks ties
  3. 3
    3. One written answerOne reply with the reason, kept on file
WHO FIXES IT

Who fixes it: head of security, architect and AppSec lead

BY WHEN

By when: front door named in 1 week

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

Why it happens

  • There is no single front door. Projects ask whoever they know.
  • Each sub-team answers its own part of the question. Nobody joins the answers before they leave.
  • Standards and advice are written separately. The architecture standard and the AppSec guide were never read side by side.
  • Speed beats agreement. A quick reply feels more helpful than a late joint reply.
  • Nobody is named to settle a tie. Both leads have the same level.

What happens if you ignore it

Projects learn that security gives mixed answers, and stop treating any of them as firm.

  • Projects choose the easier answer and ship the weaker design.
  • A week or two is lost each time the project waits for security to agree.
  • The pen test finds the issue late, when it costs the most to fix.
  • Security as a whole looks disorganised, and projects start to avoid asking.

At a glance

QuestionAnswer
How likely is it to hurt us?Likely, in any security team with more than one sub-team.
Worst case?A weak sign-in goes live on a customer portal.
What does it cost?One to two weeks per clash, late redesign, and trust.
What if we wait?Projects keep picking the easier answer.
What does the fix cost?One named contact and a 30-minute habit.

How to fix it, step by step

One door, settle it inside, then give one written answer.

  1. Name one front door. One named person or one shared mailbox that projects write to. The head of security decides who.
  2. Route every project question through it. Other security people forward, they do not answer alone.
  3. Gather the sub-team views inside. The contact asks the architect and the AppSec lead for their view.
  4. Settle any clash in 30 minutes. Both leads in one room, with the question and the facts. If they cannot agree, the head of security decides the same week.
  5. Write one answer with the reason. Include why the other option was not chosen.
  6. Send it to the project lead in plain words. One message, one owner of the reply.
  7. Keep the answer on file. The next project asking the same thing gets the same reply.
One door, settle inside, one answer
1. One doorEvery project question goes to one contact.
2. Settle insideBoth leads agree in 30 minutes.
3. One answerA written reply with the reason.
The middle step is where most of the value is.

The picture shows the order: one door, settle it inside, then one written answer. The middle step is where most of the value is.

Who to bring in: The head of security (names the door and settles ties), the architect and the AppSec lead (agree the answer), the project lead (receives it), and the project’s sponsor if the answer changes the plan.

Tools and templates

Who answers what

Question from a projectAnswered byAgreed withReply within
How should users sign in?Security contactArchitect and AppSec lead3 working days
Do we need a pen test?Security contactAppSec lead3 working days
Can we use this cloud service?Security contactArchitect5 working days

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 start the talk

Subject: One answer for the customer portal login

Hi both. The portal team received two different answers about the login design, one from each of you, within a day. I would like us to agree one answer before it goes back to them. Can we meet for 30 minutes tomorrow? Each of you could bring your reason in two lines. I am not looking for a winner. I am looking for the one design we can defend, with the reason written down.

Field tip

If two security people are about to give different answers, hold both replies for a day. A late joint answer is worth more than two quick ones.

Words used in this chapter

  • Security architect: the person who designs how systems should be built safely.
  • Application security (AppSec): the team that checks that software is written safely.
  • Login lockout: blocking an account after too many wrong tries.
  • Pen test: a planned attempt to break in, done by an expert.
  • Project lead: the person responsible for delivering the project.
  • Front door: one named place where all questions go in.