Skip to content
  1. Payment Platform
  2. Report

Payment Platform

DevSecOps security coverage assessment · September 14, 2026

Choose and order sections

In this report

  1. Coverage by capability
  2. Across the lifecycle
  3. Recommended next improvements
  4. What was assessed

Left out

  • The three numbers
  • Where the gaps are
  • Against the frameworks
  • What is in place today
  • How these numbers were produced

Choosing and ordering sections is part of the free assessment. The shape travels in the address, so it survives a reload and can be bookmarked; nothing is stored. A link to your own report still needs your session — a report link somebody else can open is not built yet.

1Coverage by capability

Every capability the profile required, with the share of its scopes that something covers and the maturity of what covers them.

CapabilityCoverageMaturityOpen gaps
API Security Testing0%09
Fuzzing0%04
Kubernetes Security0%09
Runtime Security0%012
Security Requirements0%01
DAST7%0.18
Vulnerability Scanning17%0.325
Penetration Testing29%0.37
Admission Control33%0.73
Network Security33%0.712
Drift Detection50%112
IaC Security50%16
Threat Modeling50%0.51
Secrets Management60%1.22
Cloud Configuration Security67%1.32
Code Review Security67%0.71
Secret Scanning67%2.71
SIEM67%1.31
Workload Identity67%1.36
SCA73%1.59
Container Security100%40
Incident Response100%10
SAST100%3.20
Secure Architecture100%10
Vulnerability Management100%20

2Across the lifecycle

The same scope cells, grouped by where in the delivery lifecycle they are demanded. A phase with nothing required is not a failing phase.

PhaseCoverageOpen gaps
Plan0%1
Design67%1
Code78%10
Build89%6
Test14%15
Release0%12
Deploy29%21
Operate38%58
Monitor / Respond32%7

3Recommended next improvements

  1. 1. Introduce Known Vulnerability ScanCoverage impact +7.2 % · risk reduction critical · closes 15 scopes
  2. 2. Introduce Vulnerable Dependency GateCoverage impact +6.4 % · risk reduction critical · closes 9 scopes
  3. 3. Extend Infrastructure Drift Detection to the rest of your stackCoverage impact +5.7 % · risk reduction critical · closes 12 scopes
  4. 3. Introduce Runtime Threat DetectionCoverage impact +5.7 % · risk reduction critical · closes 12 scopes
  5. 5. Extend Known Vulnerability Scan to every environmentCoverage impact +4.8 % · risk reduction high · closes 10 scopes

At most 5 improvements are ranked here, by what each would move. This is the top of the list, not the whole work list — everything still open is in the CSV export.

4What was assessed

Web application, API, Critical criticality, internet-facing, holds personal data, holds financial data. Built from 11 technologies across 3 environments.

No scanner was connected and no repository was read. Everything below is derived from the answers given in the assessment.