ColomboAIDOCS
API ReferenceCookbook
Docs/MC-1 Security/Managed configuration assessments
PublishedGuidanceLAST REVIEWED · 18 NOV 2026

Managed configuration assessments

Approve exact uploaded MCP configuration, run a fixed isolated worker and preserve minimized Trust observations.

Runtime scope

Exact human scope

Default-off engineering preview. The current registered-asset owner supplies exact configuration bytes and digest, written-authorization reference/document hash, explicit authority attestation, deadline, dedicated Trust target and approved control. Another current human administrator approves the immutable revision. This is uploaded JSON inspection only, not remote scanning or legal-ownership verification.

Fixed isolated execution

  • At most8192bytes,128 findings and30seconds per exclusive worker lease.
  • Qualified pinned Node image, absolute fixed entrypoint, no networking, read-only root/source, no capabilities, non-root user and bounded CPU/memory/processes.
  • Customer bytes use a private stdin stream and container temporary memory; no customer plaintext host file, argv or environment.
  • The service key remains in the parent. Current authority checkpoints and an absolute deadline stop the owned container.
  • An independent fixed-profile supervisor removes expired containers after parent crashes; it does not invent mission success.

Emergency halt and recovery

Request emergency stop from the authenticated Defense Command Console. Further bytes, checkpoints and report commits deny immediately. HALT_REQUESTED means termination is not yet acknowledged; HALTED after worker acknowledgement remains worker-reported, not independent containment certification.

Expired leases remain explicit reconciliation states. Only this read-only observation may be repeated; the old lease cannot publish. Production host supervision, identity/data isolation, retention execution, backup and costs require separate qualification.

Observations and retests

Known rule/ordinal observations publish through existing encrypted Trust evidence and invalidate stale assessment/certificate versions. Findings remain POTENTIAL; clean results remain NOT_ASSESSED.

A new separately approved retest of the same retained asset must use another worker credential. This is configuration reobservation, not verified remediation deployment or independent customer administration.

End of guide
Was this page helpful?
Managed configuration assessments | MC-1 Docs