Skip to main content
Third-Party Verified · 2026-04-17

Security
Posture Report

We publish our security posture openly — independent pentest results, CVE history, architecture controls, and SOC 2 progress. No marketing spin. Just the numbers.

0
Open findings
A+
SSL Labs
0 CVEs
Unpatched 2026
H2 2026
SOC 2 audit
Independent Penetration Test — A-Lane Security Audit · 2026-04-17

Full-Scope Pentest — Zero Open Findings

Black-box + grey-box pentest across all API endpoints, authentication flows, WebSocket channels, MCP sandbox, and AI pipeline. Every finding fixed before go-live.

0
Critical / High

The two severity levels that indicate exploitable, immediate-impact vulnerabilities. Zero found across all attack surfaces tested.

3
Medium — All Resolved

ReDoS edge case, WebSocket IP spoofing, and CSP nonce gap. All three patched and re-verified before the report was delivered.

2
Low — All Resolved

404 response hardening and debug-mode stack trace removal. Fixed same sprint, before any production traffic was affected.

All 5 Findings — Resolved Before Go-Live

PT-001Medium

ReDoS — catastrophic backtrack in pattern_loader.py on malformed regex

Fix: Input capped at 512 chars; re2-safe pattern substitution applied

Resolved
PT-002Medium

WebSocket XFF bypass — source IP spoofable via forged X-Forwarded-For

Fix: XFF stripped at edge; Cloudflare CF-Connecting-IP enforced as authoritative

Resolved
PT-003Medium

CSP nonce not propagated to dynamically-injected inline scripts

Fix: Nonce injected via middleware on all responses; strict-dynamic enforced

Resolved
PT-004Low

Auth routes returning 200 instead of 404 on non-existent resource

Fix: RFC 9110-compliant 404 responses added to 18 auth handlers

Resolved
PT-005Low

Stack trace exposure in 500 responses under debug mode

Fix: Debug mode removed from all production paths; safe_error wrapper enforced

Resolved

Full NDA-protected pentest report available to enterprise prospects on request. Request report →

Why It Matters

G8KEPR vs Typical SaaS Security

Most SaaS security is checkbox compliance — bolted on after the fact. G8KEPR built security into the core architecture from day one.

Topic
Typical SaaS
G8KEPR
Penetration testing
Annual checkbox — often skipped or internal-only
Full black-box + grey-box — 0 Critical, 0 High. All findings resolved before go-live
Audit logs
Mutable database rows — editable or deletable post-hoc
SHA-256 hash-chain — each record hashes the previous. Tampering breaks the chain
Tenant isolation
WHERE org_id = ? in app code — bypassable if there is a bug
PostgreSQL RLS policies — enforced at DB level, even if app code is wrong
Security headers
Basic HSTS + X-Frame-Options — CSP often missing or report-only
A+ SSL Labs — nonce CSP, Trusted Types, SRI, ModSecurity WAF, Brotli + HTTP/3
Dependency scanning
Periodic manual review or no process
pip-audit + npm audit on every PR as blocking CI gate — SBOM diff on every release
Secrets detection
Hope developers do not commit secrets
TruffleHog scans every commit. Runtime secret-leak detector in the backend pipeline
Field encryption
Full-disk encryption only — PII readable in the database
AES-256-GCM field-level encryption with per-tenant BYOK and zero-downtime DEK rotation
CVE response
Discovered during next sprint, patched weeks later
Next.js CVE-2025-29927 patched same day. P1 patch SLA is 72 hours
Defense in Depth

Four Independent Layers

A breach must defeat every layer independently. Each layer is operated and verified separately — there is no single point of failure.

Layer 1

Cloudflare WAF + Origin Gate

Edge

DDoS mitigation, origin IP hidden, TLS 1.3 terminated at edge

DDoS protectionTLS 1.3Origin masking
Layer 2

ModSecurity + OWASP CRS

Web

926 OWASP Core Rule Set rules active — blocks SQLi, XSS, RCE, path traversal

926 rulesSQLi/XSS blockOWASP Top 10
Layer 3

G8KEPR API Gateway

App

Rate limiting, JWT validation, scoped API keys, circuit breakers, MCP sandbox

JWT hardeningRate limitsMCP sandbox
Layer 4

RLS + Field Encryption

Data

PostgreSQL row-level security enforces tenant isolation at the DB layer

RLS tenant isolationAES-256-GCMBYOK / DEK
Every Header — Passing

Security Headers & TLS Configuration

Verified against SSL Labs, securityheaders.com, and Mozilla Observatory. TLS 1.3 only — TLS 1.1 and 1.2 are disabled. All headers are enforced server-side, not just report-only.

SSL LabsA+
Mozilla ObservatoryA+
securityheaders.comA
SSL/TLS Grade
A+
Content Security Policy
Strict
HSTS
max-age=31536000
X-Frame-Options
DENY
Permissions-Policy
Strict
Subresource Integrity
Enforced
Trusted Types
Enforced
ModSecurity WAF
OWASP CRS

CVE Response & Dependency Hygiene

pip-audit + npm audit run as blocking CI gates on every pull request

0
Critical CVEs ever

No critical dependency vulnerabilities found in project lifetime

1
Medium CVE (2025)

Next.js CVE-2025-29927 — header bypass. Patched same day, before any production traffic was routed

<24h
Avg. patch time

Automated alerts fire when a new CVE matches a pinned dependency version

pip-audit CI gate

Blocks PRs if any Python dependency has a known CVE. No exceptions without documented justification.

TruffleHog secret scan

Scans every commit for accidentally committed API keys, credentials, and tokens. Blocks merge on hit.

SBOM diff on release

Software Bill of Materials diff is generated and attached to every GitHub release artifact.

7 of 9 Controls Complete

SOC 2 Type II Readiness

All technical controls are implemented and independently verifiable. We are not SOC 2 certified — we say so plainly. External auditor engagement is scheduled H2 2026. We disclose our actual status, not a vaporware claim.

Controls complete7 / 9
Technical controlsExternal audit H2 2026
Access Control (CC6)
Done
Encryption at Rest (CC6.7)
Done
Encryption in Transit (CC6.7)
Done
Audit Logging (CC7)
Done
Monitoring & Alerting (CC7.2)
Done
Incident Response (CC7.3)
Done
Change Management (CC8)
Done
Vendor Risk (CC9)
In Progress
Formal SOC 2 Type II Audit
H2 2026
Coordinated Disclosure Policy

Responsible Disclosure

Found a vulnerability? We want to hear from you. Report privately to security@g8kepr.com and we will acknowledge within 24 hours with an initial severity assessment and remediation timeline.

Security contactsecurity@g8kepr.com
Acknowledge SLA< 24 hours
P1 patch SLA< 72 hours
RewardHall of fame + recognition

Disclosure Steps

1

Report privately

Email security@g8kepr.com — description, reproduction steps, and impact. PGP-encrypted reports welcome.

2

We acknowledge within 24h

You receive confirmation and an initial severity assessment. We commit to a remediation timeline.

3

We patch and keep you updated

P1/P2 issues are patched before public disclosure. We will keep you in the loop on progress.

4

Coordinated public disclosure

We work with you on timing and credit for public disclosure after the fix is deployed and verified.

Incident Response SLAs

Defined runbooks for every severity level — DR drills run quarterly

P1 — Critical
Acknowledge15 min
Mitigate1 hour
Resolve4 hours
Data breach, full outage
P2 — High
Acknowledge30 min
Mitigate4 hours
Resolve24 hours
Auth failure, partial outage
P3 — Medium
Acknowledge2 hours
Mitigate24 hours
Resolve72 hours
Performance degradation
P4 — Low
AcknowledgeNext business day
Mitigate1 week
ResolveSprint
Non-critical bug
Open Security Posture

Security questions? Ask them directly.

We publish our posture because we have nothing to hide. Need the full pentest report, an architecture review session, or a call with our security team — reach out.