Sources and customer vaults
Connect supported data sources, keep control of keys and API secrets, and authorize protected retrieval and processing.
Let an agent request work on private data using references. You select the source, grant scoped access and approve the work. Standard’s attested confidential components retrieve and validate the authorized material, process it and deliver the permitted result with Standard Proof.
Two input routes
Local encrypted files. The participant host prepares and encrypts a file, retains its expected digest and contributes it after runtime appraisal. Use this route when your existing workflow prepares the input locally.
Connected sources. The request names an approved connection and data selection. Confidential ingress retrieves the selected material with scoped access, validates the required bindings and contributes it to the operation worker. The requesting agent uses references rather than raw source credentials or conversation contents.
Source connectivity does not give the approved function a general network interface: retrieval happens in confidential ingress under scoped permission, and the function receives only validated inputs through its declared interface.
Connections and selections
A connection identifies a configured provider and access relationship. A selection identifies the resource the operation may use. Approval binds the required connection, resource selection, version and data bindings to the permitted work.
Supported adapters cover object storage and bounded query sources. An object selection uses the provider’s version identifier. A query selection uses a saved query, bounded time range and approved snapshot digest. The connection family and request route determine which selectors are supported.
For example, the Analytics agent requests category counts for batch-042 in the input owner’s approved storage connection. Substituting another connection, resource or version fails selection validation before retrieval. If retrieved bytes fail the required digest or size checks, they are refused before reaching the approved function.
Zero custody of your master encryption keys
For supported connections, Standard does not receive your non-exportable master encryption keys. They remain in your own vault or KMS. Scoped policies determine which confidential components may request their use and for what purpose.
- Master encryption keys: Authorized decryption and key-unwrapping operations use these keys inside the customer’s key store.
- Temporary data keys: Authorized confidential components may use these keys in confidential memory to decrypt permitted inputs.
- Recipient decryption keys: These stay on the recipient's host or in the recipient's browser. Standard does not generate, hold or unwrap them. A result-sink delivery writes only the sealed result to your bucket; the recipient opens it on its own host with
standard receive --sealed. - Connector credentials: API secrets remain under customer control in the configured vault or secret store. An authorized confidential component may retrieve them for permitted use when the provider and policy support that route.
- Agent-facing references: The requesting agent identifies approved sources and secrets through references without receiving the raw credentials.
Customer-store adapters differ in authentication, credential lifetime and attestation enforcement. AWS, Google Cloud and Vault integrations use their configured trust, roles and conditions. For Azure, Standard checks the owner-accepted image condition and records provider-side image enforcement as false. Participant-host custody is a separate supported route.
From connection to permitted result
- Connect and select. Configure a supported source and customer-store access. Select the resources and versions the work requires.
- Verify and approve. Connection verification and approval-time snapshots use separate scoped permissions and can happen before final operation approval. Each required owner approves the permitted work and release scope.
- Retrieve and validate. Attested confidential ingress checks the grant, owner approval, connection, selection, version and required data bindings. It retrieves authorized material, then verifies the bytes before contribution.
- Process in confidence. Ingress uses permitted source credentials within its confidential boundary. The operation worker receives validated inputs through a protected session and runs the approved function with its declared interfaces and limits.
- Release and verify. Release rules govern the result and recipient. The receiving integration verifies the supported claims in Standard Proof against accepted references before use and applies its next-action policy.
Raw protected material stays out of the requesting agent and Standard’s coordination services. It exists at the customer/provider source endpoints and in the appropriate confidential components. Authorized recipients receive permitted results. The Analytics integration receives permitted category counts, while the underlying conversations and source credentials remain outside its process.
Request a connected-source operation
For a configured hosted principal, this command illustrates the connected-source request syntax for a published conversation-categories profile. The connection UUID, object path and generation are sample values, not an installed source or the human-readable batch-042 alias. The hosted continuation limit still applies:
standard run conversation-categories --source conversations=11111111-1111-4111-8111-111111111111/conversations/batch-042.json@1740000000000000The reference names the connection, object and version. The installed SDK and installed MCP integration use the corresponding sources map. Hosted MCP uses its discovered protected-task schemas. Hosted receive returns delivery metadata and, when permitted, the location of the sealed result; the recipient opens it and verifies Standard Proof on its own host.
See the CLI, SDK and MCP request examples for the complete contracts. Local files use the local encrypted-file route.
From source checks to business checks
Source selection and byte verification establish the input supplied to the operation. The approved customer function then applies the business rule: for example, select completed transactions, reject duplicate IDs and calculate the total. Its checks and failure behavior are part of the accepted workload. See Write a protected function.
What receiving systems verify
Standard Proof binds supported workload, authority, input, execution and result/release claims through the delivered contract. Input digests identify the bytes used by the operation. Source checks enforce approved retrieval internally; independently verifying a source claim uses authenticated source records included in the delivered verification contract.
See Inputs and permissions, Verification checks and the threat model and AI risk mapping.