- Industry
- Oil & Gas
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Decision-maker
- Approver
- Platform Tech Lead
- Code
- ENG-17
It keeps third-party libraries, base images and runtimes patched across the company's applications and OT DMZ servers, checking each against advisories, end-of-life dates and the licence policy. It decides which updates to take now, batch, defer or hold, and holds anything on OT-facing systems for the vendor-qualified patch list and a site window.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the package registry and advisory feed: versions, advisories and licences..
- 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.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Platform Tech Lead with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the code repository: it opens the upgrade changes. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The dependency policy: allowed licences, patch timelines, the OT patch qualification process and end-of-life rules.
Reads from
the package registry and advisory feed: versions, advisories and licences.
Acts in
the code repository: it opens the upgrade changes.
Hands back
A list of updates, each with package, from, to, decision (now, batch, defer or hold) and reason.
Asks a person when
The update is on an OT-facing system, is major, or adds a licence outside MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Auto-merge | patch | Which updates merge after tests. |
| Security patch within (days) | 7 | For IT systems. |
| Allowed licences | MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC | Comma-separated. |
| OT needs qualified patches | On | OT-facing systems take only patches the control system vendor has qualified. |
| Most updates per change | 10 | Per change. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Auto-merge patch updates only after tests pass.
- Patch IT security issues within 7 days.
- On OT-facing systems take only qualified patches when on is on, and schedule them in the site's window.
- Allow only MIT, Apache-2.0, BSD-2-Clause, BSD-3-Clause, ISC and batch at most 10 updates.
See the Dependency Management Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.