A trusted client certificate and private-key proof lead to a separate application-policy fork: reader is allowed with HTTP 200 while a valid guest is denied with HTTP 403. Copied software keys can be used elsewhere, so hardware identity needs additional mechanisms.

Client certificates authenticate control of a private key

Mutual TLS authenticates a client’s control of a certificate’s private key as well as the server’s identity. It does not inherently identify a physical device. A copied software key can be used elsewhere; hardware binding and device attestation require additional mechanisms. An enrollment policy can associate a key with a device, but TLS alone does not establish that association. ...

September 6, 2027 · 6 min · XB Field Notes