Skip to main content
CID222 Docs

Glossary

The terms this documentation uses, defined once, with the page that covers each in full.

  • Version: 0.4
  • Role: admin_user, normal_user, viewer
  • Type: reference

Terms as this documentation uses them. Where a term has a page of its own, the definition ends with a link to it.

Deployment

TermDefinition
ApplianceCID222 delivered as one virtual machine, whose containers, schema and host configuration are all carried by a signed release and applied by a privileged updater on its host.
Direct installCID222 running from the compose files on a host you administer, updated with ./update.sh rather than from the dashboard. Ends up running the same signed images. See compose profiles and CLI.
Deployment modeWhich traffic path this installation serves — API gateway, inline proxy, or both. Chosen in the setup wizard and changed afterwards under Settings → System Updates.
Release channelThe signed manifest and image registry an appliance pulls an update from. It is never contacted unless an operator asks for an update.
BundleA single signed .cidupd file carrying a release's images, compose file and migrations, for an appliance with no internet. See update the appliance.
ManifestThe signed description of a release: its version, its images pinned by digest, its compose file and its migrations.
Trust anchorA public key on the appliance that a release or a licence must verify against. An appliance accepts any of several, so the signing key can rotate without stranding boxes.
Host repairFixes a signed release applies to the appliance's host — the updater, systemd units, the deployment mode, environment keys — which a container update cannot reach on its own. Reported under Settings → System Updates.
Installation idThe identifier an appliance's licence is bound to. Changing it invalidates the licence. See licensing and activation.

Identity and access

TermDefinition
TenantAn account in CID222. A tenant is both a user who signs in and the owner of the sessions, credentials and detections recorded against it. See tenants.
Tenant groupA set of tenants that can share a provider credential and be reported on together. See tenant groups.
Department scopeThe rule that limits what a caller reads and writes to their own part of the estate. Enforced at the query layer, so a scoped user sees fewer rows rather than a refusal.
RoleOne of five fixed roles: superadmin, admin_user, normal_user, viewer and auditor. See roles, capabilities and pages.
ViewerA read-only demonstration account. It satisfies any role requirement on a read, and every mutating request it makes is refused globally by the property of the request rather than by which endpoints it may call.
AuditorAn external reviewer. Reads compliance and governance evidence across every tenant and the audit trail, changes nothing, never sees message content, and cannot hold a chat session in the estate it audits.
CapabilityOne of sixty named permissions in the access model. At 0.4 the model runs in shadow mode: every verdict is computed and compared, and access is still decided by the five roles and the page matrix.
Page matrixThe mapping of dashboard pages to the roles allowed to open them. An operator can change which roles see which pages. See access control.
Gateway API keyA cid_key_… credential that authenticates a program calling the CID222 API. Distinct from a provider credential. See access keys.
Provider credentialThe API key CID222 uses to call OpenAI or Anthropic on a tenant's behalf, resolved tenant first and then tenant group. See credentials.

Licensing

TermDefinition
Package, or tierStarter, Professional or Enterprise. One build; the licence file decides which capabilities are unlocked.
Feature keyThe named capability a licence grants. Entitlements resolve as the union of the keys in the licence file and the keys of its tier, so a key added after a licence was signed still works. See licence tiers and feature keys.
TrialThe built-in 30-day Starter-level period a fresh appliance runs, stamped from first boot rather than from the image build date.
GraceThe period after expiry, named by the licence itself, during which the product keeps operating with a banner.
Seat capA limit on accounts carried by the licence. Reaching it refuses new accounts; existing users are never blocked from signing in.

Detection

TermDefinition
GuardrailsThe detection pipeline as a whole: normalisation, then PII, toxicity and attack detection in parallel, then one decision. See the content safety pipeline.
Entity typeWhat a detector reports having found — a PII type, a secret category, a toxicity label or an attack label. See entity and label types.
Input filterA rule that decides what happens when an entity type is found in what a user sends. See security filters.
Output filterThe same, for what the model sends back.
ActionWhat a filter does with a detection: FLAG records it, MASK replaces the value, REJECT refuses the request. The strictest action among a request's detections wins.
OverrideA tenant-level or group-level change to a filter's action, applied on every path that can carry it.
PIIPersonally identifiable information, detected by a regex layer and an ONNX named-entity model together. See PII detection.
ToxicityHarmful content across thirteen labels, in over a hundred languages.
JailbreakAn attempt to make the model disregard its instructions.
Prompt injectionInstructions hidden in content that the model is meant to treat as data.
Hallucination detectionA second-tier check on a model's answer against the context it was given, in English and Turkish.
Reversible maskingMasking that can be undone for the session that produced it, because the value map is stored encrypted. See sessions.
PseudonymisationReplacing a value with a stable substitute so records stay linkable without carrying the original.
DecisionBOMThe record of why a decision was made — the rules that applied, in what order — including a statement of what the record cannot prove.

Traffic paths

TermDefinition
API gateway modeApplications call CID222's own API, and CID222 calls the model provider.
Inline proxyCID222 as a forward proxy that decrypts client browser traffic and inspects it. See inline proxy.
ICAPInternet Content Adaptation Protocol — how a third-party secure web gateway hands CID222 a request to inspect. See ICAP and third-party gateways.
SWGSecure web gateway: the third-party product in the traffic path that calls CID222 over ICAP.
Browser extensionThe managed browser add-on that inspects what a user pastes into a chat site. See browser extension.
Endpoint agentThe operating-system agent that enforces AI usage on a managed machine. Pilot-grade at 0.4 and hidden on licensed builds.
User-ID attributionResolving an inspected request's source address to an Active Directory user. See user-ID attribution.
Shadow AIUse of an AI service that the organisation has not sanctioned, discovered from extension and proxy traffic. See AI usage.

Analysis and evidence

TermDefinition
LLM Risk AnalystA local model that reviews a user whose jailbreak and prompt-injection detections have filled a sliding window, and records a verdict. Enterprise tier.
MCP serverThe read-only interface over the CID222 database that the analyst reads through. It can never write.
LockA restriction placed on a user by a review, honoured on every enforcement surface until it is explicitly cleared.
FindingThe recorded answer to "and what did you do about it?" against a detection: a state, an owner and a resolution.
Evidence packAn export an auditor can verify without trusting the appliance that produced it.
Mapping versionThe version of the regulatory mapping under which a piece of evidence was captured. Evidence is pinned to it, so a later mapping change does not silently rewrite history.
Frozen periodA reporting period fixed in place so it stops following the data.
Governance inventoryThe record of which AI assets are in use, who owns them, and their EU AI Act risk tier. See governance.
MITRE ATLASThe public catalogue of adversarial techniques against AI systems, shipped as reference tables.
OWASP AI security documentsSix pinned OWASP publications, shipped the same way, with OWASP's own crosswalks to ATLAS.

Operations

TermDefinition
Event logThe audit trail. Every entry carries an event type and a category. See event types.
Retention policyHow long each class of record is kept before it is deleted, set explicitly and applied on a schedule.
RunbookA machine-readable troubleshooting procedure — symptom, checks, causes, fixes — rendered as a checklist and executed by the in-product assistant. See guided runbooks.
Diagnostic snapshotThe support bundle an appliance produces about itself, and the data a runbook's automatic checks read. See the diagnostic snapshot.
MigrationA versioned, recorded schema change. Migrations own the schema on every deployment and apply on boot.
ProfileA compose label that opts a set of optional services in. See compose profiles and CLI.
Setup wizardThe first-boot procedure that creates the administrator and records the deployment mode. It cannot be re-run. See the setup wizard.

Last updated on

On this page

Download PDF