SaibleDocs
Coverage

Control coverage, in seven areas

Which controls each system has. The Control Plane reaches six areas; the gateway adds Enforce.

  • KnowDo we know it exists, and what it costs?needs any AI platform connector, or registering itControl Plane
  • OwnIs someone accountable?needs nothing more: the owner claims it in SaibleControl Plane
  • ContextDo we know what it uses?needs a repository, data platform or knowledge systemControl Plane
  • ConfigureIs it set up the way policy says?needs a platform read role; a write role for write-backControl Plane
  • ValidateDoes it work, and do changes get tested?needs the evaluation workbench, no connectorControl Plane
  • ObserveCan we see each call, and did it follow policy?needs your own logs, or the gatewayControl Plane, from your logs
  • EnforceCan a bad call be stopped?needs the Saible gatewaywith the Gateway

Know and Own start with discovery: a system is found on a platform, in a repository or at the gateway (the browser extension is coming), then claimed by its owner. How the inventory is discovered →

Seven areas, no order between them · dashed: only with a gateway
  • Coveredevery control in the area is met
  • Partlysome of its controls are met
  • Not yetnone are; the console names the next control to add and how
Each area, for each system · readiness of the controls, never a verdict of compliance
  • Strongwritten by Saible and chained: snapshots, write-backs, approvals, and with the gateway a record of every call
  • Mediumcalls read from your own logs, which Saible does not control; the check over them is chained
  • Declaredwhat a person states: an owner's attestation, imported training records
How strong each piece of evidence is · a source Saible cannot read leaves its control unmet
Do it
  1. 1Open Home in the new console. Control coverage shows, per area, the share of your registered systems that have it.
  2. 2Select an area to see the systems missing it.
  3. 3Open a system and its Coverage tab: each control met or not, with its evidence or the reason.
  4. 4Add the next control it names: claim the system, confirm its context, scope a policy, connect your call logs, or add the gateway.
For your agents

This topic is also written as Agent Skills your agents can load: console-coverage, catalog, data-map, observe, human-ai-use. Ask us for them.

Next · Control Plane · InventoryYour AI inventory, from what you already run →