DKDKCISSP
← Cybersecurity on the GroundCHALLENGE

Two Security Teams, One Audit Finding, No Owner

By Deepak Kumar, CISSP

The problem: In an internal audit, risk and compliance says, “That is technical, so it is not our job.” Security operations says, “Checking controls is audit work, not technical, so it is yours.” Both sound reasonable. The finding has no owner.

Words used here: risk and compliance is the team that writes the rules and checks that they are followed. Security operations is the team that runs the security tools and watches for attacks. A control is a check or safeguard that must happen, such as a monthly review.

Think of a shared flat

Two flatmates share a flat. The rota says: “Clear out the fridge every month, and tick the sheet when it is done.” That is really two jobs. One is the clearing out. The other is the tick sheet. The flatmate who wrote the rota says, “Clearing out is hands-on work, not mine.” The other says, “Ticking a sheet is paperwork, not mine.” Each is right about the other’s job, and forgets their own. The fridge is not cleared, and the sheet is empty.

The same thing happens between two security teams. One word, “technical,” hides two different jobs.

The shared flat: a full fridge and an empty tick sheet
A full fridge, and an empty tick sheet
Clearing out is hands-on work.
Flatmate who wrote the rota
Ticking a sheet is not mine.
Other flatmate
Each is right about the other's job, and forgets their own.

What it looks like at work

The rule says: “Review who used the full-power (admin) accounts, every month.” For most of the year, nobody did. The auditor asks who is responsible, and where the proof is.

The compliance lead says: “Reading admin logins is technical. Operations should do it.” The operations lead says: “Checking that controls are followed is audit work, not technical. That is for compliance.” The auditor waits, and the finding is marked as a repeat issue.

How the monthly admin login review falls between two teams
  1. 11. Rule writtenReview admin logins every month.
  2. 22. A year passesNobody did the review. Nobody saw.
  3. 33. Auditor asksWho owns this? Where is the proof?
  4. 44. Both say noTechnical. Audit. Not mine, yours.
  5. 55. Repeat findingMarked as a repeat issue. No owner.
Each lead described half the job and called it the whole.

Neither lead is lying. Each is describing one half of the job and calling it the whole.

You will notice it when:

  • Audit findings sit for weeks because it is “the other team’s job.”
  • Someone says “that is technical” or “that is just audit” to end the talk.
  • Compliance asks for proof a few days before the audit.
  • Operations first hears about a rule when the auditor asks about it.
  • Nobody can say who does the control, and who checks it was done.

Two jobs hidden in one word

A control has two separate jobs. They need different skills, so they belong to different teams.

Job 1: Do the review. Log in to the tool, look at who used admin accounts, and decide whether each login was expected. This needs the tools and knowledge of the systems. It belongs to security operations, or to the IT team that runs the system.

Job 2: Check that the review was done. Ask for the list and the sign-off. Pick a few cases. Compare them with the rule. Write down what is missing. This needs no tools, only the rule and the proof. It is normal audit work, and it belongs to risk and compliance. Risk and compliance cannot call it “technical,” because checking controls is what that team is for.

There is one small step in between: saving the proof. Security operations builds a saved report once, so compliance can read it later without the tool.

A quick test for any task: “Do I need to log in to the tool and understand what the screen shows?” If yes, it is doing. If you only need a list and the rule, it is checking.

Someone saysAsk thisThe usual answer
“That is technical.”Which part needs the tool?Doing the review, yes. Checking that it happened, no.
“That is audit work, not technical.”Which part needs the tool?Checking, yes, it is audit work. Doing the review, no, it needs the tool.
“Compliance should collect the proof.”Can they read it without the tool?Yes, if operations saves a report once.
“Operations should write the rule.”Who must follow it every day?Operations gives input. Compliance writes and owns the wording.

What exactly needs fixing

The first fix is not the monthly review itself. It is splitting the doing from the checking, and putting one name on each. This card shows the whole problem on one page:

The monthly admin login review has no owner
WHAT IS BROKEN

The monthly admin login review was not done, and nobody checks that it should be.

WHERE IT IS

The admin login review rule, between two security teams.

WHAT COULD GO WRONG

Misuse of an admin account goes unseen until the audit.

WHAT IT COSTS US
  • Repeat finding
  • Audit rush
  • Hidden misuse
  • Lost trust
THE FIX, IN THREE MOVES
  1. 1
    1. Split the two jobs
  2. 2
    2. Save proof monthly
  3. 3
    3. One owner each
WHO FIXES IT

Who fixes it: head of security

BY WHEN

By when: owners in 2 weeks

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

Why it happens

  • One word covers two jobs. “Technical” or “audit work” is used for the whole control, so each team claims only the half it likes.
  • The two teams care about different things. Compliance cares about rules and dates. Operations cares about alerts and keeping systems running.
  • Rules are written without the people who must follow them. So they may not fit daily work.
  • Nobody owns the proof. Everyone hopes it will appear when the auditor asks.
  • Proof is asked for at the last minute. Operations sees it as a distraction.
  • The two leads have different bosses. Nobody below the head of security can settle it.

What happens if you ignore it

Every audit becomes a small fight, and the same findings come back.

  • The same findings return year after year. It looks like a team that does not learn.
  • The auditor and the client trust the security team less.
  • Real problems hide behind the paperwork fight, because nobody is doing the review.
  • The two teams stop sharing information.

At a glance

QuestionAnswer
How likely is it to hurt us?Very likely. It happens in most security teams with more than one sub-team.
Worst case?A real misuse of an admin account goes unseen, and the audit shows it.
What does it cost?Repeat findings, wasted hours before every audit, and lost trust.
What if we wait?The same fight returns before the next audit.
What does the fix cost?A short meeting, one page of owners, and one saved report.

How to fix it, step by step

Think of each rule as a chain: the rule, the review, the proof, the check. Each link needs one owner.

  1. Split doing from checking, in plain words. Write both jobs down for this rule. Doing is the review. Checking is testing that the review happened.
  2. Give security operations the doing. They run the review each month and save the proof as a report, ideally straight from the tool so nobody has to chase it.
  3. Give compliance the checking. They keep the rule, ask for proof on a calendar, test a sample, and host the auditor. They do not need the tool to do this.
  4. Walk through each open finding in one 20-minute meeting. Both leads in the room. Ask: “Which part needs the tool, and which part does not?”
  5. Fix the rule if it cannot be followed. If operations says it is not realistic, rewrite it together instead of arguing.
  6. Agree the proof once. What it is, where it is kept, how often, and who sends it.
  7. Meet every month for 30 minutes. Look at what the next audit will ask for.
  8. Let the head of security settle ties within a week. Bring facts and two options, not a complaint.
  9. Close the finding only after the proof exists. And after compliance has checked it.
Doing, saving and checking: three jobs, named owners
1. Do the reviewSecurity operations log in, read admin logins monthly.
2. Save the proofOne saved report, so others can read it without the tool.
3. Check it was doneCompliance asks for proof, tests a sample. No tool needed.
Ask one question: which part needs the tool?

The picture shows one owner for each link. For the proof there are two named owners: one who saves it, and one who collects it.

Who to bring in: The head of security (the decision), the compliance lead, the security operations lead, and the IT team if the logs belong to them.

Tools and templates

Who does what, for each rule

RuleDoes the review (needs the tool)Saves the proofChecks it was done (audit work)How often
Admin login reviewSecurity operationsSecurity operationsComplianceMonthly
Access list reviewIT teamIT teamComplianceEvery 3 months
Policy reviewComplianceComplianceCompliance, with a second readerYearly

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: Who does the admin login review, and who checks it

Hi both. The audit found that the monthly admin login review is not being done, and nobody checks that it is. It is now a repeat issue. Can we meet for 20 minutes this week? We will split the job in two: who does the review, and who checks it was done. I am not looking for who is at fault. I am looking for one name on each part.

Asking for the proof, simple version

We need: the list of admin logins reviewed in the last 12 months, the date of each review, and the name of the person who did it. Where it is kept: [place]. Who sends it: [name]. When: by the 5th of each month.

Field tip

When someone says “that is technical,” ask one question: “Which part needs the tool?” The answer usually splits the job in two.

Words used in this chapter

  • Risk and compliance: the team that writes the rules and checks they are followed.
  • Security operations: the team that runs security tools and watches for attacks.
  • Control: a check or safeguard that must happen, such as a monthly review.
  • Admin account: an account with full power over a system.
  • Proof (evidence): something that shows the check really happened.
  • Finding: a problem the auditor writes down.