Enterprise
Your review comes before our access.
The terms agreed before any code is read, the controls a run must have, and what waits for demand.
Pre-launch: a local prototype, not yet run live · requirements written downWhat a security review gets.
Commitments before code access, run containment, data flow, assurance limits. No certifications yet.
Settled before the first run.
Agreed in writing
Scope, storage, providers and their data terms, retention, revocation and incident contacts. Their absence would block access to customer data.
Data kept scoped
Content sent to models would be minimized, and the actual providers, regions and retention would be disclosed.
Independent assessment
None yet. Architecture documents are not certification; one will be named only once an independent assessment exists.
The controls we expect reviewers to ask about.
Separated identities, tenant-scoped data, durable audit, egress allowlists and a named response owner, among others.
Tenant isolation
Tenant-scoped data access, with negative cross-tenant tests
Durable audit
Decision and grant transitions stored with their audit events
Revocation that ends things
Repository access and runner grants revoked when an evaluation ends
Organization credentials
Keys would never enter the agent’s workspace
Egress on an allowlist
Runner egress restricted to an allowlist, and recorded
Separate identities
A runner identity that can’t merge, publish the required check or change policy
LaterStage labels are targets, not availability. Nothing is available yet.
What waits for demand
Identity, access separation, audit, isolation and data handling would come early enough for a real pilot. These would come only when repeated paid demand justifies the operating burden:
- SCIM
- Regional or dedicated execution pools
- Private networking
- Single tenancy
- A proof-of-decision audit export
Nothing implied before it exists.
If an evaluation needs self-hosting, a certification or a dedicated pool, we choose another mode or say no.
Questions procurement asks.
From our own list, answered only as far as the documents answer them.
All questionsCan an external service process our selected code?
Only under a written agreement on scope, storage, providers, retention, revocation and incident contacts. Discovery would start with read access to the repositories you select.
Security and procurement · Before accessing customer repositoriesUnder whose provider accounts do the agents run?
Organization-level credentials only, to be injected by a proxy outside the sandbox. Personal credentials and subscriptions would never be used.
Nonfunctional requirements · Security and privacyIs single sign-on required for an evaluation?
It may be, before a serious pilot, and it won’t be pushed to a late milestone. SCIM would wait for repeated demand.
Security and procurement · Enterprise sequencingWho can bypass the required check?
Not the runner: a trusted publisher separate from it would publish the check. Administrators may hold bypass powers in your Git provider; those boundaries must be disclosed and recorded, and Assent claims no control over changes made outside the configured workflow.
Authority and enforcement · Final merge evidence
Bring your review checklist.
Scope and data handling are agreed in writing before any access.