- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- OT Security Lead
- Code
- ENG-16
It runs and reads code, dependency, secret, container and configuration scans across the IT estate and passive asset inventories of the OT network, removes false positives and rates each finding by exploitability and exposure. It opens a private fix ticket per confirmed finding and never runs an active scan against the control network.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the vulnerability scanner: the scan results and asset inventory..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to OT Security Lead with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the issue tracker: it opens one private fix ticket per confirmed finding. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The security standards: IEC 62443 zones, the OT asset inventory, scanning rules (passive only in OT), fix deadlines and risk acceptance.
Reads from
the vulnerability scanner: the scan results and asset inventory.
Acts in
the issue tracker: it opens one private fix ticket per confirmed finding.
Hands back
A list of findings, each with id, asset, zone, severity, exploitability, fix, due_date and owner.
Asks a person when
A finding is critical, sits in the OT network, or a leaked secret needs revoking.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Fix deadlines (days) | critical: 7, high: 30, medium: 90, low: 180 | By severity. |
| Lowest CVSS to ticket | 4.0 | Below this findings are logged. |
| OT scanning | passive only | How the control network is scanned. |
| Revoke secrets itself | Off | Leaked secrets are revoked by a person. |
| Longest risk acceptance (days) | 90 | Then reviewed. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Scan the control network only passive only.
- Ticket findings at CVSS 4.0 or above with deadlines critical: 7, high: 30, medium: 90, low: 180.
- For OT findings, propose compensating controls when patching needs a plant shutdown, and let the asset owner choose the window.
- Never revoke secrets when off is off, and accept risk for at most 90 days.
See the Security Scanning Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.