Your inspection root can mint any name: what custody evidence shows a customer's auditor that no insider mints one silently, and what does it cost?

## The question behind the question An auditor, or your own staff, is not asking whether you *intend* to behave. They are asking what would happen if you did not. Every answer that reduces to "our policy forbids it" fails, because the policy is written and enforced by the same team that holds the key. Useful evidence has one property: **its failure is visible to somebody who is not you.** ## The credible ladder **Hardware custody.** The key is generated inside a hardware security module and never exists outside it. Exporting is not an administrative action but a physically constrained one. This converts "a copy could exist" from an unfalsifiable worry into an event that would leave traces, and it is the single most expensive item on the list. **A witnessed ceremony.** Generation happens once, in a scripted session, with named witnesses from outside the operating team, and produces a signed transcript. It is the only moment when everyone agrees the key had no copies, and it is the anchor for every later claim. **Dual control.** No single administrator can invoke the key outside the proxy's normal path. This is genuinely inconvenient: it slows you down in the middle of the night when a certificate operation is on the critical path of a restoration, and that inconvenience is precisely what makes it evidence rather than a slogan. **An issuance record you do not own.** Every certificate the proxy mints is logged with its names and time, and shipped continuously to storage that a different team, or the customer, retains under append-only retention. If your CA operators can edit the record, the record proves nothing about them. This is an organisational control disguised as a technical one: it requires a team willing to hold your logs and to refuse you when you ask to change them. **Name constraints in the root.** This is the only item the auditor can check without trusting your account of it: they read the root as installed on a device and see for themselves which subtrees can never be minted for. Evidence an outsider can verify unaided is worth several times the evidence they must accept from you. **Reconciliation.** Somebody outside the CA team periodically compares the names in the issuance log against what the decrypt policy permits, and investigates the difference. Without this step the log is an archive, not a control. ## What you must refuse to claim You cannot prove that no certificate was ever minted silently. Logs are produced by a system whose operators are the population you are being asked about, and the honest formulation is: **minting outside policy is detectable and attributable, not impossible.** Auditors, and staff, place more weight on a team that draws that line clearly than on one that overstates. It also protects you contractually: a promise that "we cannot" becomes a breach the day someone demonstrates that you could. ## The cost, and the decision a lead owns | Control | What it costs | |---|---| | Hardware custody plus ceremony | Real money, procurement time, and a calendar with outside witnesses | | Dual control | Slower response when key operations sit on a restoration path | | Externally held issuance log | Another team's ongoing commitment, and their willingness to refuse you | | Name constraints | An exclusion list frozen until the next fleet-wide root distribution | | Reconciliation | A standing review owned by someone who does not report to the CA team | And the cheapest control of all is the one people skip: **reduce the scope of what you decrypt.** Categories you never intercept need no evidence, because nothing is minted for them. That reduction costs inspection coverage, so it is not the CA custodian's call alone; whoever owns the detection outcome has to sign for the blind spot they are accepting. There is a second audience with standing here. In a remote-first company, staff are also a party that does not trust the team by default, and in several jurisdictions interception of personal traffic on managed devices requires consultation, notice, and a published exclusion list before it is switched on. The evidence pack you build for a customer's auditor is largely the same pack that makes the staff conversation survivable, and building it once for both audiences is the efficient move. ## How to answer Name the controls, say which one the auditor can verify unaided, state plainly what cannot be proven, and then put a price on each so the person holding the budget can choose. A principal-level answer ends with a recommendation and its trade, not with a list.