ServicesIV — Security, Data Privacy and LLMOps / Production Management
Isolated Infrastructure Topology, Access Control and Proof of Compliance
Installing the model inside the company is not security by itself. If the network it runs on, the model and embedding files on disk, the keys between services and the query logs go unaudited, data can leak inside the company too. In an audit, saying "the data never leaves" is not enough; you are asked to prove which user reached which document.
We build a security envelope around the closed-circuit deployment. AI services move into their own network segment and outbound traffic is reduced to an allow list. Model and embedding files are stored signed, keys between services are distributed through a vault (Vault/HSM) and rotate on expiry. Authorisation connects to the organisation’s own identity provider (SSO/LDAP): role-based access and row-level permissions apply to every document fragment the model retrieves. Every query, every source retrieved and every answer given is written to an immutable audit log. Data residency, backup and disaster recovery are designed as part of the same topology.
A chain of records you can show an auditor: which user, with which question, reached which fragment. Keys and model artefacts stay inside the organisation’s boundary, and the same topology moves between on-premise servers and an isolated private cloud.
This service applies when having the model inside the building is not enough — when an auditor asks "who accessed what" and there is no answer. What has to be on your side is someone with authority over the network topology, and knowledge of what your existing identity management is. If the source of permissions is unclear we settle that first; it is the ground the audit trail is built on.
Outbound traffic first: AI services are moved into their own network segment and their outbound paths are reduced to an allowlist — you cannot know where a supposedly closed installation talks to without measuring it. Then signed storage: model and embedding files are signed and inter-service keys are given expiry. The record chain is built at the beginning, not at the end, because a log cannot be produced retroactively.
This service does not issue a compliance certificate and does not promise that you will pass an audit; it produces a record chain that can be shown to an auditor, and the auditor decides. Legal assessment, the record of processing activities and retention policy are out of scope. We also do not close the security gaps in the rest of the organisation — the envelope is built around the AI layer, not around the whole company.