- Industry
- Hotel
- Department
- Engineering
- Team
- Platform and Reliability
- Kind
- Assistant
- Approver
- Information Security Manager
- Code
- ENG-16
It runs and reads code, dependency, secret, container and configuration scans across the booking engine, reservation services, integrations and each hotel's point-of-sale and card-data network, removes false positives and duplicates, and rates each finding by exploitability, exposure and PCI DSS scope. It opens a private fix ticket per confirmed finding with an owner and due date by severity, and sends critical findings, exposed secrets and risk acceptances to the security lead.
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 vulnerability scanner: the latest scan results and finding history for the targets and hotels 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 Information Security Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the issue tracker: it opens a private fix ticket for each confirmed finding. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The security policy: the PCI DSS requirements and quarterly scan obligations, the card-data environment boundary, guest data protection rules, fix deadlines by severity and the risk acceptance process.
Reads from
the vulnerability scanner: the latest scan results and finding history for the targets and hotels named.
Acts in
the issue tracker: it opens a private fix ticket for each confirmed finding.
Hands back
A list, each with id, title, target, property (or null), severity, cvss, pci_scope (true or false), exploitable (true or false), owner, due (YYYY-MM-DD) and fix.
Asks a person when
A finding is critical, a secret or card data is exposed, the finding is in PCI DSS scope, or a risk acceptance is asked for.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Fix deadlines by severity (days) | critical: 7, high: 30, medium: 90, low: 180 | Due dates for fix tickets. |
| Lowest score that gets a ticket | 4.0 | Findings below this are listed but not ticketed, except in the card-data environment. |
| Fix deadline for high findings in card-data scope (days) | 30 | High and critical findings in the card-data environment must be fixed and rescanned within this. |
| Revoke exposed secrets itself | Off | When off, revoking a leaked credential needs the security lead. |
| Longest risk acceptance (days) | 90 | A risk acceptance expires after this and is re-reviewed. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Remove false positives and duplicates with the reason, and rate each confirmed finding by exploitability, exposure and whether it is in PCI DSS scope.
- Ticket findings at or above 4.0, and every finding in the card-data environment, with due dates from critical: 7, high: 30, medium: 90, low: 180.
- High and critical findings in card-data scope are fixed and rescanned within 30 days.
- Any card number, payment key or guest data found in code, logs or scans is critical and goes to the Information Security Manager at once.
- Revoke exposed secrets only when off is true; otherwise escalate.
- Keep tickets private and grant risk acceptances for at most 90 days, never for card-data exposure.
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.