Product tour

See the platform your team will actually live in

This is the dashboard, exactly as it ships. Thirteen chapters below cover posture, proof, cloud, AI security, mobile, Kubernetes and the gate.

Self-hosted · air-gapped capable · your code never leaves your infrastructure

apPosture security overview dashboard
01 / 13

One score the board can read

A deterministic 0-100 posture score and A-F grade across every application, with open-vulnerability and risk-burndown trends, a posture forecast and a pre-emptive exploit radar. The number is reproducible: the same evidence always produces the same score.

Deterministic scoringA-F gradeTrend and forecastExploit radar
apPosture One score the board can read
02 / 13

From 6,170 to the twelve that matter

Raw findings collapse by correlation into unique vulnerabilities, then rank by what is reachable, exploit-confirmed and known-exploited. Each carries KEV, internet-facing and exploitability signals. It is a queue someone can finish, not a backlog nobody trusts.

Cross-tool dedupReachabilityKEV and EPSSSignal vs all
apPosture From 6,170 to the twelve that matter
03 / 13

Proof, not a CVSS number

Every confirmed finding carries its evidence: the exploit that proved it, the correlated source location, an AI triage that cites only that evidence, and a one-click fix ticket. Probes are safe by construction - benign markers, never a real destructive action.

Proof of exploitMasked evidenceCode correlationOne-click ticket
PROVEN Object-graph IDOR reaches another tenant's invoice
01 GET /api/invoices/8814 -> 200 own record
02 GET /api/invoices/8815 -> 200 tenant_id 4471 (not ours)
03 assertion: response body carries a foreign tenant id
SAFE Read-only, nothing written or deletednon-destructive
SOURCE InvoiceController.java:118 · no ownership checkSAST correlated
IMPACT Any authenticated user reads any tenant's billingCWE-639
The verdict cites this evidence and nothing else. No proof, no confirmed status.
04 / 13

Code to runtime, including the APIs nobody declared

One API risk grade, the toxic-combination endpoints (public plus sensitive plus not provably authenticated), OWASP API Top 10 coverage, and code-to-runtime provenance that names the shadow APIs no scanned source declared.

A-F API gradeToxic combinationsShadow API discoveryContract diff
apPosture Code to runtime, including the APIs nobody declared
05 / 13

Cloud misconfiguration, told as an attack path

Agentless, read-only assessment of AWS, GCP and Azure against CIS and OWASP Cloud-Native controls, with CIEM privilege-escalation analysis and attack paths drawn only where every edge actually exists. A control that cannot see its target resource reports N/A, never a pass.

CSPMCIEM privescAttack pathsDriftRemediation as code
CRITICAL PATH internet → security group → instance → IAM role → account admin
IMDSv1 Instance credentials reachable by SSRFEC2.8
OPEN 0.0.0.0/0 → 2375 Docker daemonunauthenticated
CIEM Role escalates to admin via iam:PassRoleT1548
Every edge in the path exists in the snapshot. A missing link means no path is drawn.
06 / 13

The attack surface your AI adoption just created

An AI-BOM of every model, framework, vector store and MCP tool your code pulls in. Poisoned agent-config detection catches instruction injection in rules files, and slopsquat screening flags dependencies an assistant hallucinated before someone registers the name.

AI-BOMInjected instructionsSlopsquatMCP governance
Models
7
AI SDKs
12
Vector stores
3
MCP tools
5
CWE-1427 Agent rules file tells the assistant to disable a control.cursorrules
SLOPSQUAT Dependency does not exist in the registry404 · hallucinated
MCP Agent wired to a remote tool surfaceunreviewed
The AI-BOM is a lens over the components already scanned, not a separate crawl.
07 / 13

Android and iOS, scored against MASVS

Upload an APK, AAB or IPA and get native and Flutter static analysis, dependency and bundled-library CVEs, manifest and plist configuration, an embedded-tracker privacy map and a MASVS grade with L1, L2 and R depth. The backend endpoints found inside the app bridge straight into a dynamic scan.

MASVS gradeNative and Dart SASTTracker privacy mapBridge to DAST
C
MASVS grade C
4 of 7 control groups passing · L1 12/18 · L2 5/11 · R 1/4
CWE-295 Empty checkServerTrusted, TLS accepts any certificateKotlin
CWE-359 9 trackers embedded, 4 can reach location and contactsprivacy
CWE-1104 Bundled OpenSSL 1.1.1c inside libnative.soCVE-2021-3711
Static and offline. No emulator, no app-store round trip, no artifact leaves the estate.
08 / 13

Clusters, scored the same way

Every cluster assessed against CIS-aligned controls with a clear pass and fail breakdown, internet-facing and critical issues ranked first, RBAC and toxic-image analysis, and each failing control folded into the same unified posture as everything else.

CIS controlsRBAC analysisToxic imagesCluster drift
Clusters
4
CIS controls passing
78%
▲ 9%
Internet-facing issues
5
ranked first
CRITICAL ServiceAccount can create pods in kube-systemprivilege escalation
HIGH Container runs privileged with hostPath mountprod-eu-1
DRIFT NetworkPolicy removed 3 days agonamespace opened
Every failing control folds into the same posture score as everything else.
09 / 13

Do your defences actually stop this?

Breach and attack simulation replays the attack shapes apPosture has already proven and reports a control-efficacy percentage: how many your existing defences blocked, and which ones walked straight through. Every probe is non-destructive.

Control efficacySafe replayWAF validation
Shapes replayed
14
Blocked
11
79%
Reached the app
3
gap
BLOCKED SQL injection probeWAF rule 942100
BLOCKED Path traversalWAF
PASSED THROUGH Host header injectionno rule matched
Non-destructive by construction: benign markers only, nothing weaponised.
10 / 13

Where one fix breaks the whole chain

Attack paths ranked by exploitability and business impact, with choke-point analysis showing where a single change collapses several paths at once. Runtime-confirmed chains are marked, so a proven hop is never mistaken for a theoretical one.

Ranked by proofChoke pointsN-hop lateral movement
apPosture Where one fix breaks the whole chain
11 / 13

Evidence an auditor cannot argue with

Control-by-control coverage across OWASP, PCI-DSS, ISO 27001, NIST 800-53, HIPAA and GDPR, with attestation, maturity scoring and per-application benchmarking. Evidence is immutable and timestamped, not regenerated at report time.

7 frameworksImmutable evidenceMaturity scoringAuditor portal
apPosture Evidence an auditor cannot argue with
12 / 13

Risky code stops before it ships

Break the build on unacceptable risk. Roll a service from Monitor to Block from the UI without editing a pipeline, watch the gate pass rate, and see exactly which application is failing and why.

Fail closedMonitor to BlockNo pipeline editPer-service policy
apPosture Risky code stops before it ships
13 / 13

Nine engines, one posture

DAST, SAST, SCA, secrets, IaC, container, cloud, Kubernetes and mobile, plus any report you import from another scanner, all feed one deduplicated findings hub. Fix a root cause once instead of the same issue five times.

Import any scannerOne fingerprintRoot-cause dedup
apPosture Nine engines, one posture
apPosture

See it on your own app - live in 30 minutes

From discovery to a proven attack chain. A PoC in your own environment.