Tenant-aware
by default.
Organizations, roles, service accounts, gateway keys, provider configuration, policies and security events are isolated by tenant context.
Security model / Controls + boundaries
Security as a verifiable property
We distinguish implemented controls, design decisions and external validation. CI evidence is not called a certificate, and a penetration test is not complete without an independent report.
Security gates activeIndependent pentest gate
01 / PRODUCT CONTROLSProtecting access,
Protecting access,
secrets and events.
Baseline controls operate inside the on-premise environment and are covered by regression tests.
Tenant-aware
Secret handlingAPI keys are hashed; provider keys are encrypted with AES-GCM using a deployment-held master key.
Minimal eventsThe security-event schema stores metadata, not prompt or model-response content.
Container hardeningRead-only web containers, UID 101, restricted tmpfs, no-new-privileges.
Network boundariesLoopback bindings, controlled ingress and an optional egress hostname allowlist.
02 / RELEASE GATESChecks run in
Checks run in
every main build.
The goal is to block known defect classes and produce reproducible evidence artifacts.
CI
SAST & SCA
Bandit, pip-audit and Trivy for source, dependencies, configuration and container images.
Regression
Security tests
Tenant boundaries, unsafe regex, Unicode DLP bypass, fuzz corpus and gateway policy behavior.
Evidence
SBOM & Sigstore
CycloneDX SBOM, checksums, source archive and a keyless-signed evidence bundle for the source snapshot.
03 / CLAIM BOUNDARYWhat these controls
What these controls
do not prove.
Engineering maturity and compliance with specific requirements are different tasks.
| Claim | Status | Accurate wording |
|---|---|---|
| Independent penetration test | Not complete | Scope is prepared; an authorized provider, report and Critical/High retest are still required. |
| Bank certification | Not claimed | Requirements mapping and certification work are defined under a separate scope. |
| Prompt injection coverage | Risk reduction | Guard reduces risk and explains signals; 100% detection is not promised. |
| Tamper-proof audit | Checksum | An event checksum detects changes during comparison, but it is not an immutable chained ledger. |
| HA / DR | Design only | Recovery runbooks and scaling design exist; customer RTO/RPO still require validation. |
04 / REPORTINGFound a problem?
Found a problem?
Report it safely.
Do not send real secrets, personal data or production prompts in the initial email.
For a security report, write to security@cyberpass.kz. Include the version, component, impact and safe reproduction steps. Public disclosure is coordinated after remediation.
Validate the boundary before production.
The pilot defines the threat model, data classes, fail modes and an independent validation gate.
Discuss a security pilot →