Security & compliance

Governed before execution. Verifiable after it.

Every answer is checked against your rules, recorded in full, and traceable afterwards. You can verify exactly what software you are running before you deploy it.

i
This page is the technical reference. It is written for IT admins, architects and security reviewers who need exact details. If you are evaluating the business case, start with the product overview instead.
Data boundary

Your data stays where it already is.

The gateway queries interfaces your system already exposes at request time. It does not replicate business data into a vendor cloud, it writes no ABAP, and it works in air-gapped environments.

Read-only by design

Connectors consume BAPI / RFC, OData, MCP and REST interfaces. No transports, no Z-code deployed into the ERP, no changes to your SAP release cycle.

Nothing sensitive in the image

Credentials come from environment variables or a secret manager via Fernet key management. Config and skills are YAML files injected through a mounted volume.

Hardened runtime

Container runs as non-root (uid/gid 1000) with a read-only root filesystem. Only /app/data, /app/config and /app/logs are writable.

Before execution

Your rules are applied before anything runs.

A question cannot widen its own reach. Your existing permissions and approval boundaries are applied automatically, and anything outside them is stopped before a report is read.

  • Your access rules are applied to every question
  • Requests that fall outside those rules are blocked
  • Built-in safeguards against misuse and overload
  • Failures are reported clearly instead of silently swallowed
  • Single sign-on is supported when you need it

Failure is controlled, not silent

The gateway never silently retries the pyrfc backend after a saprfclib failure. A failed call fails in a controlled way with the root cause intact. When SSO2 is enabled but the active backend cannot support it, routing happens once at connection-creation time with a warning log — not at authentication time.

error shape
category : CONNECTOR
http     : 502
cause    : preserved, not swallowed
After execution

A signed trail you can hand to an auditor.

01 / RECORD

Tamper-evident audit chain

Every execution is written to a JCS + SHA-256 hash chain and signed with Ed25519. Pre-execution records cover EU AI Act Article 12.

02 / EXPLAIN

Decision explainability

Inspect why a skill was matched and what scope was applied at /api/v1/admin/audit/{trace_id}/explain, plus dependency status lights and full OpenTelemetry / Prometheus observability.

03 / EXPORT

Multi-format compliance export

Export the trail as JSONL, EU AI Act, SOC 2 or ISO 42001 evidence via /api/v1/audit/export, or generate a one-click compliance report.

Ed25519
audit signatures
Art. 12
EU AI Act pre-execution records
1,929
tests passed · 0 failed
15
tables covered by data erasure
Supply chain

You can verify exactly what you are running.

Releases are signed with Cosign Keyless / Sigstore (Fulcio short-lived certificates + Rekor transparency log) by GitHub Actions OIDC. A CycloneDX SBOM is generated during the build and served from the running product for CRA obligations.

terminal — verify this release
cosign verify \
  --certificate-identity=https://github.com/snx-ds/snixia-insight/.github/workflows/release.yml@refs/heads/master \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  snixer/snixia-insight@sha256:616a02226a75929dbaa87392547ec42aa3ed0b356b9d9c46fc1037724ccea1ea

rekor-cli verify --uuid 108e9186e8c5677a58c2fe3fe867a552caf0a63e269c8988a1403365ef7ec1bdd6069e1c163a3d3e

# Without rekor-cli, query the transparency log by UUID (REST):
curl -sS https://rekor.sigstore.dev/api/v1/log/entries/108e9186e8c5677a58c2fe3fe867a552caf0a63e269c8988a1403365ef7ec1bdd6069e1c163a3d3e

What you can independently check

It binds build provenance — the GitHub Actions workflow OIDC identity plus the Rekor transparency-log entry — to the image digest sha256:616a0222…. Default provenance attestation is retained.

Keyless since 2026-11-05. The retired long-lived Cosign key pair is kept in older offline packages for audit traceability only and is no longer used for verification.

What to keep in mind

The created label is stable, but RootFS layers can vary with pip dependency drift, obfuscation output and SBOM timestamps. Rebuilding the same commit does not guarantee the same digest.

Do not use "rebuild locally and compare digests" as a verification method. Use cosign verify + rekor-cli verify.

Note on commits. A release references a build commit (the image's app/ is byte-identical to it) and a final release commit (digest pin + offline packaging only, no change to app/). Confusing the two is the most common cause of "the digest doesn't match the tag". In some releases these two commits are the same; in others the final commit only adds the digest pin and the offline bundle. Either way, the signed digest still proves the image's origin.
Licensing & privacy

Works offline. Fails safely.

Licenses are Ed25519-signed, device-fingerprinted and validated offline with tamper detection. An expired license degrades to read-only — data is not erased, queries and exports still work and history is retained.

  • Fresh install auto-activates a 30-day full-feature trial, anchored in three independent locations
  • Customer data erasure available under the data_erasure license feature (15 tables, two-layer gating)
  • Embedded SBOM at /api/v1/admin/sbom
  • Secrets managed through Fernet keys injected via environment variables

Licensing details →

License states

VALIDFull capacity
EXPIREDRead-only, data retained
INVALIDStartup refused
NO_LICENSEDefault deployment state

Import a valid .lic at /app/config/license.lic or through /admin/license to restore full capacity.

Legal

Compatibility facts, stated plainly.

Snixia Insight is an add-on product compatible with SAP. SAP is a registered trademark of SAP SE. This product is not affiliated with or endorsed by SAP SE.

The public product name is Snixia Insight (the internal PRODUCT_NAME constant contains no SAP wording). References to SAP on this site appear only to describe compatibility facts.

Connection methods are flexible — standard web/HTTP services, OData and customer-owned report endpoints are all supported. An optional SAP-licensed component may be used for one single sign-on path only; where used, it is obtained by the customer and is never redistributed with this product. It is not required for a standard deployment.

Full terms: docs/customer/legal/ — license terms, SAP disclaimer, data flow and erasure policy also ship with the product.

Verify it yourself, then deploy it yourself.

One signed image, one container, a 30-day automatic trial. No signup and no data leaving your network.

Start the free trial See the comparison