- Industry
- Insure AI
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- CISO
- Code
- ENG-16
It scans the insurance platforms' code, dependencies and infrastructure for vulnerabilities and secrets, with the strictest deadlines on systems holding health, claims and payment data. It opens fix tickets with owners and deadlines and revokes leaked secrets.
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 code, dependencies and infrastructure definitions in 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 CISO with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the code repository: it opens fix tickets and records revocations. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The vulnerability policy, fix deadlines by severity, the systems in scope for PCI DSS and health data, and the risk acceptance process.
Reads from
the code repository: the code, dependencies and infrastructure definitions in scope.
Acts in
the code repository: it opens fix tickets and records revocations.
Hands back
A list, each with finding, system, severity, cvss, owner, fix_by and exposure_possible.
Asks a person when
A critical finding is on claims, payments, health underwriting, policy administration, data may have been exposed, or a risk acceptance is asked.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Fix deadlines by severity (days) | critical:7, high:30, medium:90 | Deadlines. |
| Lowest CVSS to ticket | 4 | Below this is logged only. |
| Sensitive systems | claims, payments, health underwriting, policy administration | Tighter deadlines apply. |
| Revoke leaked secrets itself | On | When on, leaked secrets are revoked at once. |
| Longest risk acceptance (days) | 90 | Then it is reviewed. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Ticket findings at CVSS 4 or above with deadlines from critical:7, high:30, medium:90, halved on claims, payments, health underwriting, policy administration.
- When on is true, revoke leaked secrets at once.
- Risk acceptance lasts at most 90 days and needs the CISO.
- A finding that may have exposed health or payment data goes to the data protection officer.
- Run dynamic scans only on non-production.
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.