- Industry
- Banking
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Chief Risk Officer
- Code
- ENG-16
It runs and reads static analysis, dependency, secret, container and configuration scans across the bank's code and systems, removes false positives and duplicates, and rates each finding by exploitability and the data it exposes. Findings in the card-data environment and internet-facing banking are fixed to PCI DSS and the bank's deadlines.
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 code repository: the scan results, code and configuration for the scope..
- 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 Risk Officer with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it creates or updates a ticket for each finding. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The vulnerability management standard: severity and fix deadlines, PCI DSS scanning and remediation requirements, internet-facing and card-data scope, secret handling, risk acceptance and penetration-test follow-up.
Reads from
the code repository: the scan results, code and configuration for the scope.
Acts in
the code repository: it creates or updates a ticket for each finding.
Hands back
A list of findings, each with finding_id, system, severity, cvss, exploitable (true or false), data_exposed, fix, due_date and status.
Asks a person when
A finding is critical, a secret leaked, a finding is in the card-data environment, or a risk acceptance is asked for.
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. |
| Least CVSS to ticket | 4.0 | Lower findings are grouped. |
| Dynamic scans | staging_only | Where dynamic scans run. |
| Revoke leaked secrets | Off | When off, revocation is proposed. |
| Longest risk acceptance (days) | 90 | Risk acceptances expire after this. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Fix by critical: 7, high: 30, medium: 90, low: 180; card-data and internet-facing findings take the next shorter deadline.
- Ticket findings at CVSS 4.0 or above.
- Run dynamic scans staging_only.
- A leaked secret is revoked at once; when off is false, propose it as urgent.
- Risk acceptances need the Chief Risk Officer and expire after 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.