The catalogue EngineeringSecurity EngineeringJudgment

Service EN10C

Threat Model Review

Runs judgment. Starts when a break condition on a live position fires. It runs 3 times a week across 6 stations. One of those stations stops for a person and 5 are done by an agent, none of them on the shared spine.

Runs a week

167 in flight right now.

Stations

1 person · 5 agent · 0 spine

Agent share of steps

83%

Autonomy on this service is set at 72% against a ceiling of 82%.

Decisions a person makes

Held by Director, Security Engineering.

Touchless

52%

Share of runs that complete without anybody opening them.

Timetable against actual

655.1h

Actual 708.3h, 53.2h over the timetable.

Operations

The lane diagram

Read it left to right. more

Person1 station and 25% of the dwellAgent5 stations and 75% of the dwellShared spine0 stations and 0% of the dwell1 crossing between lanes

Human

decides

Agent

does the work

GBS

shared spine

System

attributed by rule

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.

Operations

Every station in order

The same stations as a list, with the dwell the estate records against each one and the system a station of that shape would touch.

#	Station	Lane	Who	Layer	Dwell	Target	In flight	System
1	Frame system	Agent	Vulnerability Scanning Agent	strategy	45h 26m	53h 39m	23	Group ERP — Materials and Inventory
2	Model threats	Agent	Dependency Risk Agent	strategy	40h 21m	77h 21m	36	Group ERP — Materials and Inventory
3	Rank	Agent	Secret Detection Agent	strategy	65h 10m	133h 45m	26	Group ERP — Materials and Inventory
4	Draft mitigations	Agent	Threat Modeling Agent	strategy	69h 16m	84h 28m	45	Group ERP — Materials and Inventory
5	Challenge	Agent	Patch Orchestration Agent	strategy	23h 52m	33h 26m	29	Group ERP — Materials and Inventory
6	Security lead ratify 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.	Human	Director, Security Engineering	policy	82h 12m	96h 34m	8	Group ERP — Materials and Inventory

Operations

Run it

Change the volume, move the autonomy line, release a gate, and watch what happens to the hours in each lane and to the time it takes one run to get through. more

Move something

Demand100%

3 a week is what the estate records. more

Decisions handed to agents0 of 0

This service has at most one gate, so there is nothing to hand over without removing the last human decision.

People on the gates8 people

Each one is assumed to have 2,100 productive minutes a week, which is 35 hours.

Agent speed100%

100% is the dwell the estate records today. more

Person time a week

246.6h

3 items at 4,932 minutes of decision each.

Agent time a week

732.3h

14,645 minutes an item, which does not compete for a person.

Gate load

88%

Inside capacity, with 33.4h of headroom.

Stations without a person

83%

1 gate left on 6 stations.

Where an item spends its time

25% waiting on a person

75% in the agent lane

An item now takes 19,577 minutes of worked time end to end against 19,577 in the recorded estate, a change of +0%. This is worked time, not calendar time: nothing here models a queue or a weekend.

What this model is, on Threat Model Review

The simulation is arithmetic on the estate, not a queueing model. more

How it runs

Run it again, going wrong

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

6 stations, walked twice

Once clean, once with the categories the estate counts

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 13.6 days

now Frame system · Vulnerability Scanning Agent · 45 hrs

As the ledger has it

the same stations, plus 3 categories the estate already counts

0 min of 13.8 days

now Frame system · Vulnerability Scanning Agent · 45 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

Live observability

Systems this service would touch

Attributed by rule from the function's system list. more

1 systems attributed

0 of 1 returning records

The system register

Group ERP — Materials and Inventory

SAP S/4HANA MM · supply · bidirectional · high

modeled

6 of 6 stations attributed here · would write back

System attribution is a rule, not a reading. more

Who runs it

Orchestration and accountability

Orchestrated by: Security Engineering Orchestrator
That orchestrator’s remit: Owns finding work end to end inside Engineering. Runs 3 lines across 19 stations, drains the repeatable share into the IT tower, and holds 4 human gates.
Accountable person: Director, Security Engineering
Sub-function: Security Engineering
Shared spine tower: Not on the shared spine
Hand-over points: None — this service stays inside its function

Other services in this sub-function

2 alongside this one

Vulnerability RemediationEN10A Secret Exposure ResponseEN10B

What this page is and is not

This is a catalogue of the modeled estate. more