- Industry
- IT Company
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Chief Information Security Officer
- Code
- ENG-16
It runs and reads static analysis, dependency, secret, container and configuration scans across the SaaS platform and the client code and environments in scope of each engagement, removes false positives and files findings with fix deadlines mapped to ISO 27001 and SOC 2 controls. It scans a client's systems only inside the scope and dates the client authorised in writing.
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 source code repository and CI/CD: the scan results, prior findings and risk acceptances for the targets named..
- 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 Chief Information Security Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the ticketing and service management system: it files each confirmed finding with its deadline and control. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The vulnerability management policy: scan types, severity and fix deadlines, ISO 27001 and SOC 2 control mapping, client-authorised scan scopes and the risk acceptance process.
Reads from
the source code repository and CI/CD: the scan results, prior findings and risk acceptances for the targets named.
Acts in
the ticketing and service management system: it files each confirmed finding with its deadline and control.
Hands back
A list of findings, each with id, severity, location, control (ISO 27001 or SOC 2 reference), false_positive (true or false), fix_due (YYYY-MM-DD) and fix.
Asks a person when
A finding is critical, a secret leaked, a risk is to be accepted, or a scan would touch a client production system.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Fix deadlines (days) | critical: 7, high: 30, medium: 90, low: 180 | Deadlines by severity, unless a client contract is stricter. |
| Least CVSS to ticket | 4.0 | Findings below this are listed only. |
| Dynamic scans allowed in | staging_only | Where active scans may run. |
| Revoke leaked secrets itself | Off | When off, a leaked secret is escalated for revocation. |
| Longest risk acceptance (days) | 90 | An accepted risk is reviewed after this. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Scan a client's systems only with a written authorisation and within its scope and window.
- Run dynamic scans only in staging_only.
- Ticket findings at CVSS 4.0 or above with deadlines from critical: 7, high: 30, medium: 90, low: 180 or the client contract if stricter.
- A leaked secret is revoked at once by the owner, or by it when off is true.
- Map each finding to its ISO 27001 or SOC 2 control and accept a risk for at most 90 days with the Chief Information Security Officer.
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.