Platform-managed
Talvium or a qualified provider operates keys within the published service boundary.
Trust / Encryption & Key Control
Declare custody instead of saying ‘encrypted’
Every future Talvium service record must state protection in transit, at rest, and—where supported—in use, along with key owner, custody, location, administrators, rotation, recovery, revocation, and evidence.
Design target
Design targetcurrent lifecycle
Region-specificfuture availability
Evidencebefore commitment
Capability set
Capability scope
Customer-managed
Customer-controlled key material and authorization gates are integrated where the service supports them.
Dedicated custody
Named HSM, personnel, location, quorum, ceremony, and recovery procedures for bounded environments.
Attested use
Eligible confidential-compute configurations may bind workload release to verified hardware and software state.
Evidence matrix
What must be true before deployment
| Decision | Required record |
|---|---|
| Eligibility | Customer, mission, workload, data, jurisdiction, identity, device, and export conditions |
| Availability | Region, environment, service, configuration, quantity, delivery window, support, and exceptions |
| Control | Operator, network, keys, access, data movement, change, incident, recovery, and customer duties |
| Evidence | Owner, source, test or assessment, findings, limitations, approval, issue date, expiry, and revalidation |
Next decision
Convert the requirement into a bounded brief
Define the mission, jurisdiction, workload, sensitivity, environment, capacity, connectivity, continuity, timing, and evidence priorities without submitting restricted information.