Standard operating procedure · EN10B · Engineering

Secret Exposure Response

Transactional procedure owned by Security Engineering in Engineering. 6 numbered steps, 2 of them a person deciding and 4 of them agent work … more

Engineering manual Service view

Procedure code

EN10B

Transactional

Rule versions in force

v1.6 · v3.4 · v5.1

3 governing rules stacked over it

In force since

2025-07-02

Earliest effective date across those rules

Last reviewed

2026-06-20

Latest review date across those rules

Rules approved by

Director, Security Engineering

Rule health

3/3

0 under review · 0 superseded

There is no document register behind this header. The version, the dates and the approver names are read off the governing rules this procedure runs inside, which is the closest thing the estate holds to a document control record. Nobody wrote these procedures. There is no document library behind this page and no Word file anywhere in the estate. Every procedure below is generated from rows this platform already holds: the line and its ordered stations, the owning team and the person accountable for it, the policy items bound to that team, and the governance gates seeded against the function. The steps, the owners, the gates, the approvers, the dwell times and the volumes are read straight off those rows. The sentences that join them together are generated. Read a procedure as the estate describing itself, not as a document somebody signed.

Purpose and scope

What this procedure is for and where it stops

To run secret exposure response to one repeatable standard inside Security Engineering, part of Engineering. more

Entry condition

Runs transactional. Starts when an upstream system posts an event.

Exit condition

The unit clears close, released by Director, Security Engineering. more

In scope

Every unit of secret exposure response raised inside Security Engineering, from the trigger below through to the final step.
4 of the 6 steps, which run without a person present.
2 decisions that stop the line until a named person releases it.

Out of scope

Anything outside the envelope set by the owning team. It leaves the line at a gate and becomes the named approver's decision.
Work that belongs to another function. This line records no handoff, so nothing leaves it mid-flow.
The 3 steps carried on the shared AI GBS spine. They are done for this line but not by this function.

Who owns it

Runs the line

Security Engineering Orchestrator

Accountable person

Director, Security Engineering

The end of the escalation path. Above them sits Engineering Chief of Staff for the function.

That team’s remit

Owns finding work end to end inside Engineering. more

That remit describes the whole team, not this one procedure, so its counts are larger than the ones on this page.

Autonomy

72% now · ceiling 82%

Scanning, credential revocation and low-risk patching are automatic because speed is the control. more

The procedure, step by step

6 numbered steps · 2 of them stop for a person

A step is one station on the line. more

No.	Step	Who does it	What happens	System of record	Time on the step	In flight
01	Detect GBSgbs	Vulnerability Scanning Agent	Vulnerability Scanning Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.	Group ERP — Materials and Inventory	2.6 hrsstandard 4.9 hrs	21
02	Revoke credential GBSgbs	Vulnerability Scanning Agent	Vulnerability Scanning Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.	Group ERP — Materials and Inventory	1.9 hrsstandard 3.4 hrs	6
03	Notify HumanpolicyDecision	Director, Security Engineering Releases: Director, Security Engineering	Work stops. Director, Security Engineering reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the finding decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Group ERP — Materials and Inventory	3.5 hrsstandard 4.2 hrs	6
04	Rotate GBSgbs	Vulnerability Scanning Agent	Vulnerability Scanning Agent performs this step unattended on the shared AI GBS transaction spine, outside the function, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.	Group ERP — Materials and Inventory	1.6 hrsstandard 2.1 hrs	25
05	Investigate Agentworkflow	Patch Orchestration Agent	Patch Orchestration Agent performs this step unattended at the workflow layer, inside the envelope its owning team has set, and writes an evidence record naming the actor, the authority it acted under and the digests of what it read and wrote.	Configuration Management Database	39 minstandard 1.2 hrs	30
06	Close HumanpolicyDecision	Director, Security Engineering Releases: Director, Security Engineering	Work stops. Director, Security Engineering reviews what the line has produced and either releases the unit or sends it back. Nothing downstream of this step runs until that decision is made.Holds until: Held for a named human when the unit exceeds the finding decision envelope, when confidence falls below the floor, or when a policy clause is engaged.	Group ERP — Materials and Inventory	3.5 hrsstandard 4.1 hrs	4

The swimlane

The same steps, laid out by who is holding the work

Three lanes: a person deciding, an agent working, and the shared services spine. more

Person2 stations and 51% of the dwellAgent1 station and 5% of the dwellShared spine3 stations and 44% of the dwell4 crossings between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

Group ERP — Materials and Inventory

Configuration Management Database

Group ERP — Materials and Inventory

Click any station to see who does it, what it costs in time, the rule that gates it and the system attributed to it.

Run the procedure

One unit walked along that swimlane on the happy viable agentified path

Press run and a single unit enters at station 01. Each station takes exactly the dwell this platform records for it and is held by whoever the estate says holds it. more

speed

worked clock

00:00

allowance clock

00:00

stations cleared

0/6

the happy path, worked time0 min of 14 hrs

the same run against its allowance0 min of 20 hrs

Human

decides · 2

Agent

does the work · 1

GBS

shared spine · 3

run log

Nothing has happened yet. more

where the worked time goes14 hrs a unit

Person7.0 hrs · 51%Agent39 min · 5%Shared spine6.0 hrs · 44%4 crossings between lanes

what makes this path viable

The lanes are the recorded lanes. 2 of the 6 stations stop for a person and every one of them still does on this run.
Every one of the 2 decisions is still taken by the people who hold them. The happy path is that each one is released first time, not that it is skipped.
The owning team is held to a 82% autonomy ceiling and this run sits at 49% unattended, inside it.
2 systems are attributed across the stations, and 0 of them are connected. Nothing in this run has been watched executing against a real system of record.

what would have to change

1 of the 2 decisions can be handed over inside the 82% ceiling. more

could move to the agent lane

03 Notify — held by Director, Security Engineering, 3.5 hrs a unit

stays with a person

06 Close — The last decision on the line. Something on every procedure ends with a person, so this one is never offered.

what this run is, and what it is not

This is a run, not a forecast. more

Happy means nothing goes wrong: no station raises an exception, no gate sends the unit back, no rework loop fires and nothing sits in a queue between stations. more

The second clock is the allowance. more

A decision may be handed to the agent lane only if two things hold … more

The run reads the station rows only. more

What this run does not model: arrival patterns, contention between procedures for the same person, shift patterns, weekends, learning curves, and the cost of anything. more

Run it again, going wrong

The same unit, the same stations, broken the way the estate already records breaking

This is the same unit on the same stations, breaking. more

No break below was chosen. more

One play head, two tracks, the same scale. The clean run stops when it runs out of stations; the other one keeps going.

As written

6 stations, nothing waiting, nothing sent back

0 min of 14 hrs

now Detect · Vulnerability Scanning Agent · 2.6 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 30 hrs

now Detect · Vulnerability Scanning Agent · 2.6 hrs

personagentshared spinework the break addsnobody working it

What breaks, and where it is counted

No break below was chosen. more

What the two runs say together

3 counted categories land on this procedure. more

What this run cannot claim

These breaks are shown together on one unit so the shape of a bad day fits on one screen. more

Two clocks run. Worked time is the sum of the time the work is actually being done … more

Roles and responsibilities

4 named parties

The responsibility grid is assigned by a rule, not lifted from a chart. more

Party	RACI	Steps	Duty	Escalates to
Security Engineering Orchestrator orchestrator	Runs the line	0	Sequences this line, holds its timetable and decides what has to surface to a person. more	Raises to Director, Security Engineering when a unit falls outside the envelope or confidence drops below the floor.
Vulnerability Scanning Agent agent A3% autonomy · ceiling A3% 91% clean · 3% overridden	Responsible	3	Runs the repeatable portion of security engineering inside the shared transaction spine at spine cost and spine controls.	Escalates to Director, Security Engineering when the unit falls outside the decision envelope or confidence drops below the floor.
Director, Security Engineering person	Accountable and responsible	2	Holds 2 decisions on this line. more	Accountable to Director, Security Engineering for the decisions held here.
Patch Orchestration Agent agent A3% autonomy · ceiling A3% 92% clean · 3% overridden	Responsible	1	Executes the security engineering step it owns, posts its evidence, and hands the unit to the next stage.	Escalates to Director, Security Engineering when the unit falls outside the decision envelope or confidence drops below the floor.

Decision points and escalation

2 places this procedure stops

03 · Notify

3.5 hrs

Held for a named human when the unit exceeds the finding decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

Director, Security Engineering

06 · Close

3.5 hrs

Held for a named human when the unit exceeds the finding decision envelope, when confidence falls below the floor, or when a policy clause is engaged.

Director, Security Engineering

Handoffs out of this procedure

Nothing leaves this procedure for another function. It completes inside Security Engineering.

The rules this procedure runs inside

3 governing rules

Security Engineering Decision Envelope

active

EN10-POL-200 · envelope · vv1.6

Agents in this lane may act without a human when the finding sits inside the stated value, risk and confidence envelope. more

Approved by Director, Security Engineering · in force 2025-07-02 · reviewed 2026-06-20

Binds Vulnerability Scanning Agent, Dependency Risk Agent, Threat Modeling Agent, Patch Orchestration Agent

APAC

Security Engineering Evidence Standard

active

EN10-POL-201 · evidence · vv3.4

Every autonomous decision writes inputs, the rule version applied, the model and prompt version, the output and a reversal path. more

Approved by Director, Security Engineering · in force 2026-02-02 · reviewed 2026-06-08

Binds Vulnerability Scanning Agent, Dependency Risk Agent, Threat Modeling Agent, Patch Orchestration Agent

Global

Security Engineering Escalation Rule

active

EN10-POL-202 · escalation · vv5.1

Escalation is mandatory when confidence falls below the floor, when two options sit inside the confidence band, or when a break condition on a ratified position fires. more

Approved by Director, Security Engineering · in force 2025-07-15 · reviewed 2026-05-17

Binds Vulnerability Scanning Agent, Dependency Risk Agent, Threat Modeling Agent, Patch Orchestration Agent

Global

Systems this procedure touches

2 named · 0 connected

System attribution is a rule, not a reading. more

System	Vendor	Domain	Criticality	Steps	Connection
Group ERP — Materials and Inventory	SAP S/4HANA MM	supply	high	5	modeled
Configuration Management Database	ServiceNow CMDB	itsm	high	1	modeled

0 of the 2 systems on this procedure is connected to the platform, and none of the twenty-six in the estate register is. 1 of them are marked as taking a write back, which is a property of the system, not a live path from here.

How it performs

End to end

13.7 hrs

Summed from the time each step sits, standard 19.9 hrs — running at 69% of the standard.

Touchless

80%

Agent share

67%

A week

4,241

In flight

Effort a week

421 human minutes · 402 agent minutes

Volume multiplied by the time on each step. more

Assurance over this procedure

4 governance gates sit above it

The twenty-four controls and eighteen exception classes in this platform are held at estate level … more

Gate	What trips it	Who releases it	Clock	Waivable
Production release authorization approval	Any deployment to a production environment	Release manager and service owner	1 business day	No
Security-sensitive or public API change approval	Authentication, cryptography, payment paths or any published interface contract	Senior engineer and security engineer	1 business day	No
Database migration approval	Any schema change or irreversible data operation	Data owner and CTO delegate	2 business days	No
Agent-authored code sample review oversight	Weekly review of 10% of agent-authored merged changes	Engineering governance	Weekly	Yes

Next to it on the same team

Security Engineering

Vulnerability Remediation

EN10A

Threat Model Review

EN10C

All of Engineering

What this document is and is not

These procedures describe the modeled estate. more

Actions

What is waiting on a person

What one procedure document gives you, and what to check before you treat it as the standard.

151

named approvers appear across the library

Every decision point on every procedure carries a job title, not a queue. more

143

steps in the library hand their unit to another function

A handoff is where a procedure stops being one team’s problem. more

controls exist in the estate, and they belong to no procedure in particular

Controls and exception classes are held estate-wide. more

Operations

What this desk is allowed to start

A surface that only reports is not operable. more

Trigger and bound

A procedure document prints purpose, scope, entry and exit, the numbered steps with the actor on each, the roles and their RACI position, the swimlane, the decision points and escalation, the handoffs, the governing rules with version and approver, the systems by rule and the timings. more

Live observability

What the record shows right now

The whole library, by lane, so a single document can be read against the estate it came from. more

Current distribution

2,748 steps

Agent, inside the function1,38951%

Agent, on the shared spine85131%

Person deciding at a gate50818%

Is policy and strategy coming to fruition

Whether the written intent is holding here

Half. The document is complete and every actor on it is measured more

Not holding on the record

A procedure here carries a version, an approver, an in-force date and a last-review date. more