The problem: A developer wants to use a new file-sharing tool for a project. There is no place to ask security, so he messages Sam, an engineer he knows. Sam is on leave. A week later he asks Priya, who is busy, glances at it, and says it looks fine. The tool goes into use. Nothing is written down, and no review ever happened.
Words used here: a request is any question or ask sent to the security team. Intake means the way requests come in. Triage means sorting requests by how urgent and important they are. A service level is a promised reply time.
Think of a shop with no counter
A customer walks into a large shop with no counter and no sign. He asks the first assistant he sees. “Not my aisle.” He asks another. “Try my colleague.” In the end, one tired assistant says, “Yes, take it,” without checking the price or the stock. The assistants are not rude. The shop simply has no place where a question lands and gets an owner.
A security team with no front door works the same way.
What it looks like at work
The security team has eleven people. Developers, HR, finance and project managers all send requests: can we use this tool, can we share this data, is this vendor safe. They send them by chat, by email, in meetings, and in the corridor. These are example numbers.
Sam is away for ten days, so his messages sit unread. Priya gets the same question from the same developer and says yes in two minutes because she does not know a review is needed. Three months later, the auditor asks for the review record for that tool. There is none.
- 11. Developer asksNo front door, so he messages Sam
- 22. Sam is awayThe message sits unread for ten days
- 33. Asks PriyaBusy, says “looks fine” in two minutes
- 44. Tool goes liveNothing written down, no review done
- 55. Audit“Show me the review record.” There is none.
Both sides have a fair point. The developer is trying to get on with work and asked the people he trusts. The security team is small and does not want to put forms between colleagues and their jobs. Nobody is being careless. There is simply no shared place where a request becomes a case with an owner and a date.
You will notice it when:
- Requests arrive through chat, email, meetings and the corridor.
- The same person is asked the same question by three people.
- Nobody can say how many requests are open.
- A request is answered “yes” in two minutes by someone who is not the right person.
- A colleague on leave means a request goes cold.
What exactly needs fixing
The fix is not to tell people to be more careful. It is one place for requests to land, one person who sorts them each day, and a promised reply time. This card shows the whole problem on one page:
Security requests arrive by chat, email and the corridor, and nobody owns them or records them.
The security team’s eleven people, and every team that asks them for help.
An unreviewed tool holds sensitive data and has a breach.
- Days of delay
- Unrecorded decisions
- Tired staff
- No audit record
- 11. Build one doorA short form and a shared mailbox, with the link shown everywhere
- 22. Sort dailyOne person sorts each day, rotated weekly
- 33. Promise a replyA first answer within three working days, kept with the request
Who fixes it: head of security
By when: front door live in 2 weeks
A blank copy of this card is in the Tools section.
Why it happens
- People ask the person they know. It feels faster and friendlier.
- The team grew without a front door. At five people, it worked.
- There is no promised reply time. So a silent week looks normal.
- Nothing is written down. A chat message is not a record.
- Everyone assumes someone else owns intake. Nobody was asked.
What happens if you ignore it
The team gets busier and the answers get worse.
- Requests are lost when one person is away.
- Risky tools and sharing are approved by whoever happened to be asked.
- Auditors find no record of reviews that really took place, or never did.
- The same few people are flooded, and they start to dread the chat.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Very likely, wherever there is no single route in. |
| Worst case? | An unreviewed tool holds sensitive data and has a breach. |
| What does it cost? | Days of delay, unrecorded decisions, and tired staff. |
| What if we wait? | The team grows and the problem grows with it. |
| What does the fix cost? | One form, one mailbox, and a daily 15 minutes. |
How to fix it, step by step
Build the door, sort every day, then review the pattern each week.
- Build one front door. A short form and a shared mailbox. Ask only what is needed to start: what, why, who, by when.
- Say where it is. Put the link in the staff handbook, the chat channel header and the signature of everyone on the team.
- Name one person to sort each day. Rotate it weekly so it does not fall on one person.
- Promise a reply. Say, for example, a first answer within three working days.
- Redirect, kindly. When someone asks you in chat, reply: “Good question, please send it here so it is not lost.”
- Keep the answer with the request. The record is the proof of review.
- Look at the list once a week. Spot repeat questions and write a standing answer.
The picture shows the order: build the door, sort every day, then review the pattern each week. The weekly review turns the same question into a standing answer.
Who to bring in: The head of security (names the owner and agrees the promise), the daily sorter (rotating), a representative from the busiest requesting team, and the internal auditor (agrees what counts as a record).
Tools and templates
Request form fields
| Field | What to ask |
|---|---|
| What do you want to do | One line in plain words |
| Why | The business reason |
| What data is involved | Customer, staff, public, none |
| Who is affected | Team or project |
| Needed by | A date |
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, lost trust |
| The fix | The exact action |
| Who fixes it | One name or one team |
| By when | A date, not “soon” |
Email to start the talk
Subject: One place for security requests
Hi all. We get requests by chat, email and in the corridor, and we cannot say how many are open or who has them. I would like us to try one request form and one shared mailbox, with a first reply within three working days. Can we meet for 30 minutes this week? I am not looking to add paperwork. I am looking for a way that no request is lost and every decision leaves a record.
Field tip
When someone asks you in chat, do not answer. Reply: “Please send it to the request mailbox.” It is kind to them, and it protects you.
Words used in this chapter
- Request: any question or ask sent to the security team.
- Intake: the way requests come in.
- Triage: sorting requests by urgency and importance.
- Service level: a promised reply time.
- Front door: one named place where all questions go in.
- Record: a written trace that something was reviewed.