Control catalogue
Every shipped capability has a stable code, so a reviewer can refer to it, and a mapping to the frameworks buyers score against. Mapped means a control supports a requirement. It never means certified.
Detection
6 controls| Code | Control | OWASP LLM Top 10 | NIST AI RMF | ISO 27001 Annex A |
|---|---|---|---|---|
| SC-01 | Sensitive-data detection: 31 classes via rules, in-house entity models, a vision model and a verifier, plus a semantic layer for nine categories of stated disclosure | LLM02 | Measure | A.8.12 |
| SC-02 | National identifier validators: TCKN checksum, VKN, IBAN mod-97, LuhnRejects look-alike numbers. | LLM02 | Measure | A.8.12 |
| SC-03 | Telecom identifiers: IMSI, ICCID, IMEI, MSISDN, coordinates | LLM02 | Measure | A.8.12 |
| SC-04 | Verifier gate: a second model re-checks every candidate before action | LLM02 | Measure | A.8.12 |
| SC-05 | Tenant rules: custom classes per tenant or global, activated at runtime | LLM02 | Govern | A.5.12 |
| SC-06 | Document and image protection in place: PDF, DOCX, XLSX, PPTX, PNG, JPG and scanned pagesSignatures, identity documents and faces are blocked, never sent. Unreadable input is refused. | LLM02 | Manage | A.8.12 |
Protection and restoration
6 controls| Code | Control | OWASP LLM Top 10 | NIST AI RMF | ISO 27001 Annex A |
|---|---|---|---|---|
| SC-07 | Context tokenisation: opaque per-case tokens, one token per entity | LLM02 | Manage | A.8.11 |
| SC-08 | Format-preserving encryption mode, opt-in, key held by the customer | LLM02 | Manage | A.8.24 |
| SC-09 | Restoration inside the perimeter, scoped to the case | LLM05 | Manage | A.8.11 |
| SC-10 | Fail-closed: protection failure or unreadable input stops the request | LLM02 | Manage | A.8.12 |
| SC-11 | Gateway guardrail: streaming protect and restore for gateway-fronted traffic | LLM02LLM05 | Manage | A.8.12 |
| SC-12 | Endpoint deployment with human review before send | LLM02 | Manage | A.8.12 |
Tenancy, identity, operations
4 controls| Code | Control | OWASP LLM Top 10 | NIST AI RMF | ISO 27001 Annex A |
|---|---|---|---|---|
| SC-13 | Tenant-scoped API keys and organisation isolation | LLM10 | Govern | A.5.15A.8.3 |
| SC-14 | Rate limiting and distributed ledger | LLM10 | Manage | A.8.6 |
| SC-15 | Administrator console, local accounts, API-key lifecycle | — | Govern | A.5.16 |
| SC-16 | Reviewer feedback loop: corrections captured, never silently retrained | LLM02 | Measure | A.8.16 |
Evidence and audit
3 controls| Code | Control | OWASP LLM Top 10 | NIST AI RMF | ISO 27001 Annex A |
|---|---|---|---|---|
| SC-17 | Security event logging: ECS JSON with stable codes to your SIEM, no values reprinted | — | Govern | A.8.15 |
| SC-18 | Durable audit store of detection runs (PostgreSQL) | — | Govern | A.8.15 |
| SC-19 | Service metrics (OpenMetrics) | — | Measure | A.8.16 |
Deployment and supply chain
4 controls| Code | Control | OWASP LLM Top 10 | NIST AI RMF | ISO 27001 Annex A |
|---|---|---|---|---|
| SC-22 | In-perimeter delivery: private OCI Helm chart, six images, OpenShift 4.x, mirrored-registry install | LLM03 | Govern | A.5.23A.8.9 |
| SC-23 | Signed release manifest and CycloneDX SBOM per release | LLM03 | Govern | A.5.21 |
| SC-24 | No Salus-side data, keys or telemetry | LLM02 | Govern | A.5.23 |
| SC-25 | CPU-only inference, no GPU dependency | — | Manage | A.8.6 |
Administration and operations
Administration console
Web console in English and Turkish. Detection classes on and off, custom rules by keyword or pattern, API keys per calling system, review screen with CSV export.
Your directory, your roles
Administrators authenticate against Active Directory or LDAP; rights follow group membership. Three roles: administrator, rules editor, reviewer. No local privileged accounts, no shared logins. Single sign-on on request.
Policy per calling system
Each caller gets its own key and its own policy: tokenise, suppress, allow or block, per class. Deterministic, versioned, and rolled back with the release.
Tamper-evident audit trail
Write-only: every detection, restoration, configuration change, key rotation and login attempt, with hashes instead of content. Exported as JSON lines with a CEF mapping to your SIEM.
Monitoring you already have
OpenMetrics on every service: request rate, p50 and p95 latency, error rate, detector availability. A Grafana dashboard and a default alert set ship with the release.
Sized for a CPU node
Reference production node: 16 cores, 32 GB RAM, no GPU. Stateless services with replicas for availability; a disaster-recovery instance is covered by the licence.
Models and rules are versioned artefacts pinned to each release. A release is either active or rolled back; nothing retrains silently.
Every control listed is shipped. KVKK and EU AI Act mappings are provided with the datasheet.
Deliberately out of scope: prompt-injection classification, agent and tool control, retrieval access control, brand and toxicity filtering, red teaming of models. Salus is the data-transformation layer under those tools, not a replacement for them.