Files

Benjamin Admin 8dfab4ba14 feat: Payment Compliance Pack — Semgrep + CodeQL + State Machine + Schema

Ausfuehrbares Pruefpaket fuer Payment-Terminal-Systeme:

1. Semgrep-Regeln (25 Regeln in 5 Dateien):
   - Logging: Sensitive Daten, Tokens, Debug-Flags
   - Crypto: MD5/SHA1/DES/ECB, Hardcoded Secrets, Weak Random, TLS
   - API: Debug-Routes, Exception Leaks, IDOR, Input Validation
   - Config: Test-Endpoints, CORS, Cookies, Retry
   - Data: Telemetrie, Cache, Export, Queue, Testdaten

2. CodeQL Query-Specs (5 Briefings):
   - Sensitive Data → Logs
   - Sensitive Data → HTTP Response
   - Tenant Context Loss
   - Sensitive Data → Telemetry
   - Cache/Export Leak

3. State-Machine-Tests (10 Testfaelle):
   - 11 Zustaende, 15 Events, 8 Invarianten
   - Duplicate Response, Timeout+Late Success, Decline
   - Invalid Reversal, Cancel, Backend Timeout
   - Parallel Reversal, Unknown Response, Reconnect
   - Late Response after Cancel

4. Finding Schema (JSON Schema):
   - Einheitliches Format fuer alle Engines
   - control_id, engine, status, confidence, evidence, verdict_text

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

2026-04-13 14:59:49 +02:00

621 B

Raw Blame History

CodeQL Query: Tenant Context Loss

Ziel

Finde Datenbank-, Cache- oder Exportpfade ohne durchgehenden Tenant-Kontext.

Sources

Request tenant (header, token, session)
Device tenant
User tenant

Danger Patterns

DB Query ohne tenant filter / WHERE clause
Cache key ohne tenant prefix
Export job ohne tenant binding
Report query ohne Mandanteneinschraenkung

Mapped Controls

TENANT-001: Mandantenkontext serverseitig validiert
TENANT-002: Datenabfragen mandantenbeschraenkt
TENANT-006: Caching beruecksichtigt Mandantenkontext
TENANT-008: Datenexporte erzwingen Mandantenisolation

621 B Raw Blame History

CodeQL Query: Tenant Context Loss

Ziel

Sources

Danger Patterns

Mapped Controls

621 B

Raw Blame History