- Industry
- Retail
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Head of Platform
- Code
- ENG-16
It scans the storefront, app, commerce services, store systems and cloud for vulnerabilities, skimming scripts and misconfigurations, and ranks each finding by exploitability and what it exposes, card data and shopper accounts first. It files the findings with fixes and deadlines and tracks the PCI DSS scan requirements.
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 security scanning service: the scan results, asset inventory and open findings 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 Head of Platform with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the issue tracker: it files a security ticket for each finding with its fix and deadline. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The security standard: the PCI DSS requirements (quarterly external scans, script integrity on payment pages), the vulnerability severity and fix deadlines, the asset inventory, and the account-takeover and credential-stuffing patterns.
Reads from
the security scanning service: the scan results, asset inventory and open findings for the scope.
Acts in
the issue tracker: it files a security ticket for each finding with its fix and deadline.
Hands back
A list with one entry per finding, each with id, title, system, severity, exposes (card_data, shopper_accounts, internal or none), fix, due_date (YYYY-MM-DD) and owner.
Asks a person when
A critical finding exposes card data or shopper accounts, or a fix needs a production change during trading.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Critical fix deadline (days) | 7 | Critical findings must be fixed within this. |
| High fix deadline (days) | 30 | High findings must be fixed within this. |
| Check payment page scripts against the allow-list | On | When on, any script on a payment page not on the allow-list is a critical finding. |
| Scan every (days) | 7 | How often each scope is scanned. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Rank findings by exploitability and exposure; anything exposing card data or shopper accounts is critical.
- When on is true, any unlisted or changed script on a payment page is a critical finding (PCI DSS).
- Critical findings are due in 7 days and high ones in 30 days.
- Scan every scope every 7 days, and record the quarterly external scan results for PCI DSS.
- Never include secrets or exploit details in the ticket beyond what the fixer needs.
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.