The problem: Risk and compliance writes a new alert policy: “Every alert must be closed within 15 minutes.” The security operations team (the SOC) gets about 300 alerts a day, with three analysts on a shift. They cannot keep the rule. The auditor checks the tickets, sees that most ran over, and writes it up.
Words used here: risk and compliance is the team that writes the rules and checks they are followed. Security operations (the SOC) is the team that watches the alerts and deals with attacks. An alert is a warning from a security tool that something may be wrong. A ticket is the record of one alert.
Think of a restaurant kitchen
A new manager hangs a card on the kitchen wall: “Every dish out in 2 minutes.” He has never worked a Friday night. The kitchen has three cooks and sixty orders. Nobody can keep the card, so the cooks stop reading it. Some dishes leave the kitchen half done, just to beat the clock.
The card is not wrong because the manager is careless. It is wrong because the people who cook were never asked. A policy written without the people who must follow it works the same way.
What it looks like at work
Compliance has to show the auditor a clear rule for handling alerts, so it writes one. The number 15 comes from a template and sounds reasonable. Management approves the policy and it is sent to the SOC by email.
The SOC lead reads it and says: “Nobody asked us.” On a normal day the three analysts see about 300 alerts. Many are false alarms, but each one still needs a look. To meet the clock, analysts start closing tickets fast, with no notes. A real alert can take an hour, so its ticket shows as late.
At the audit, the auditor samples the tickets. Most missed the 15 minutes. The finding is written: “The alert policy is not followed.”
- 11. Rule written15 minutes, from a template
- 22. Sent by emailThe SOC was never asked
- 33. SOC rushes300 alerts, three analysts a shift
- 44. Auditor samplesMost tickets ran over the clock
- 55. Finding“Policy not followed”
Both teams have a fair point. Compliance needs a rule an auditor can test, and “as soon as possible” is hard to test. The SOC needs a rule that lets an analyst look properly at a serious alert. Neither team is being careless. They never sat down together while the rule was written.
You will notice it when:
- The SOC says “we never saw that policy until the audit.”
- Tickets are closed in two minutes with no notes, or sit open for weeks.
- The rule asks for a number the SOC’s own tools cannot measure.
- People quietly use their own way of working and ignore the written one.
- The same finding comes back: “policy not followed.”
What exactly needs fixing
The fix is not to push the SOC to work faster. It is to change the rule so it matches how alerts really arrive, and then let both leads sign it. This card shows the whole problem on one page:
The alert policy asks for every alert to close in 15 minutes, which the SOC cannot do.
The alert handling policy, and the SOC’s daily queue of about 300 alerts.
Real attacks are closed in a rush, and the audit shows the rule is not followed.
- Repeat audit finding
- Alerts closed in a rush
- Rework before audits
- Teams stop trusting each other
- 11. Get real numbersOne day of alert counts, analysts and handling times
- 22. Split by seriousnessA short target for serious alerts, a longer one for routine
- 33. Test, then signOne week of testing, then both leads sign the wording
Who fixes it: compliance lead and SOC lead
By when: new rule tested in 3 weeks
A blank copy of this card is in the Tools section.
Why it happens
- The rule is copied from a template. The 15 minutes came from a document, not from a count of real alerts.
- The people who must follow it were not in the room. Compliance drafts it, management signs it, and the SOC reads it last.
- All alerts are treated the same. A false alarm and a stolen admin login get the same clock.
- The auditor needs something to test. A rule with a number is easy to check, so compliance leans towards one.
- Nobody tests the rule before it is published. The first real test is the audit.
- The two teams want different things. Compliance wants a rule that passes an audit. The SOC wants alerts handled well.
What happens if you ignore it
The rule stays on paper, and the audit keeps finding the same gap.
- The same finding returns every year. It looks like a team that does not learn.
- Analysts close tickets in a rush to hit the number, so a real attack can slip through.
- The SOC stops trusting anything compliance writes.
- Evidence gets built at the last minute, which wastes hours before every audit.
At a glance
| Question | Answer |
|---|---|
| How likely is it to hurt us? | Likely, wherever policy is written away from the people who run it. |
| Worst case? | A real attack is closed in a rush to meet the clock, and the audit shows it. |
| What does it cost? | Repeat findings, rework before every audit, and lost trust between teams. |
| What if we wait? | The same finding comes back at the next audit. |
| What does the fix cost? | One day of real numbers, one hour with the analysts, and a one-week test. |
How to fix it, step by step
Ask first, test second, and only then publish.
- Ask the SOC for one day of real numbers. How many alerts, how many analysts, and how long each kind takes.
- Sit with the analysts for an hour. Watch one alert from arrival to close.
- Split alerts by seriousness. For example, a short target for serious alerts and a longer one for routine alerts.
- Write the rule so it can be tested. Say what “handled” means: looked at, noted, and either closed or passed on.
- Test it for one week. Count how many alerts meet it. If most do not, change the rule, not the analysts.
- Both leads sign the final wording. The SOC lead and the compliance lead.
- Set a review date. Look at the numbers again in six months, and before every audit.
The picture shows the order: ask, test, then publish. The testing step is the one most teams skip.
Who to bring in: The compliance lead (writes the rule), the SOC lead (signs it), the head of security (settles ties), and the internal auditor (agrees what proof will be accepted).
Tools and templates
Can the team follow this rule? Check before you publish
| Question | Ask whom | Example from this case |
|---|---|---|
| How many alerts arrive on a normal day? | SOC lead | About 300 |
| How many people handle them on a shift? | SOC lead | Three analysts |
| How long does a real alert take? | An analyst | Some take an hour or more |
| Can the tool measure the time? | Owner of the SOC tool | Yes, from the ticket times |
| What is the proof? | Compliance | A monthly ticket report from the tool |
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: Before we publish the alert policy
Hi both. The audit found that the alert policy is not followed. I think the rule may not fit the daily load. Can we meet for 30 minutes this week? The SOC could bring one day of real alert numbers, and compliance could bring the wording. I am not looking for who is at fault. I am looking for a rule the team can keep and the auditor can test.
Field tip
Before you publish a rule, ask the team that must follow it one question: “Could you keep this on your busiest day?”
Words used in this chapter
- Risk and compliance: the team that writes the rules and checks they are followed.
- Security operations (SOC): the team that watches alerts and deals with attacks.
- Alert: a warning from a security tool that something may be wrong.
- Ticket: the record of one alert, from arrival to close.
- Policy: a written rule that people in the company must follow.
- Finding: a problem the auditor writes down.