Search the documentation
Search the documentation...
SplitSecure documentation

On this page

Procedure · 12 steps

Sign with a signing key or a Nitro EIF signer

Create a signing key or a Nitro EIF signer in a threshold vault, and sign data or enclave images only after your Guardian Team approves.

Updated

Before you start

  • A Basic or Guardian seat, on any plan. The members who vote need a Guardian seat.

  • The SplitSecure mobile app, set up and signed in to the same account as the Web App. See Set up your device and browser.

  • A Guardian Team, the group of devices that together approve each proposal, formed and usable. See Form your Guardian Team.

  • Use or Edit access to a vault backed by that Guardian Team. Forming a Guardian Team creates one, named after the team.

A signing key signs data your systems check later, such as a release artifact or a token. A Nitro EIF signer is a single-purpose key that signs AWS Nitro Enclave images (EIF files). Each image it signs reports a PCR8 measured from the signer’s certificate, so an attestation policy can require images from this signer. Both keys live in a threshold vault. Your Guardian Team, the group of devices that together approve each proposal, votes on every signature.

Passkeys, X.509 CAs, SSH principals, signing keys, OpenPGP identities, wallets, secrets and connected apps share one Secrets limit. Each seat adds the allowance your plan sets for its kind. By default, a Guardian seat adds to the limit and a Basic seat adds nothing. An administrator sees the count under Organization → Overview, on the Resource usage card. To make room, delete any of these resources, or add seats of a kind that carries an allowance. See the plans (opens in a new tab).

Create the key

In the Web App

  1. Open the Web App (opens the SplitSecure web app).
  2. In the sidebar, under Vaults, click your threshold vault.
  3. Click New resource.
  4. Under Signing & certificates, click Signing key or Nitro EIF signer.
Field Value
Name Release signingRequired. The name the Guardian Team sees on every proposal
Description Optional
Key algorithm Ed25519Signing key only. Also Ed448, ECDSA, RSA, ML-DSA and SLH-DSA. Can’t be changed later

A Nitro EIF signer has no algorithm to choose: it always uses ECDSA P-384, as AWS requires.

Under Advanced Options, you can turn on Selective notifications and set the Account Sensitivity. Click Continue.

The Review step lists the details, the Location and the Guardian Team under Protected by. The What voters will see box shows the text of the proposal.

  1. Check the details.
  2. If your Guardian Team lets you choose who gets notified, pick the members under Who to Notify.
  3. Optionally, enter a Reason for creation.
  4. Click Propose creation.

The Web App opens the proposal under Requests.

Now on each member’s device

On each member’s device, the proposal appears under Requests. The member opens it, checks the details, then taps Approve. The proposal passes when the approvals reach the Guardian Team’s threshold.

The proposal asks to create a raw signing key or an AWS Nitro EIF signer, with its name.

Sign data with a signing key

Now in the Web App
  1. In your vault, open the signing key.
  2. On the Keys (1) card, click the download icon (Download Public Key) on the key’s row. An SLH-DSA key has no download: click Copy Public Key to copy it in base64.
  3. Give the public key to the systems that check your signatures.
  1. Click Propose signature. The Sign with signing key page opens.
  2. Under Data to sign, choose Text, Base64 or COSE Sig_structure (base64), then paste the data. A COSE Sig_structure must use the context Signature1.
  3. For an ECDSA or RSA key, check the Digest. To sign a hash you computed yourself, turn on Data is already a digest. The switch forces Base64, so paste the hash’s raw bytes in base64, not the hex that sha256sum prints. For example, run sha256sum release.tar.gz | cut -d' ' -f1 | xxd -r -p | base64. The length must match the Digest: 32 bytes for SHA-256, 48 for SHA-384, 64 for SHA-512.
  4. Optionally, open Advanced Settings. An RSA key can use PSS under Signature scheme. An EdDSA key takes a Context and the Ed25519ph / Ed448ph switch. ML-DSA and SLH-DSA keys take a Context.
  5. Optionally, enter a Reason for signing.
  6. Click Propose signature.
Now on each member’s device

On each member’s device, the proposal appears under Requests. The member opens it, checks the details, then taps Approve. The proposal passes when the approvals reach the Guardian Team’s threshold.

The proposal asks to produce a raw signature. Its Raw signature section shows the message size and its SHA-256 digest. For a COSE Sig_structure, a COSE Sig_structure section adds the envelope and the payload preview.

Now in the Web App

When the vote passes, the proposal page shows the Signature card.

  1. Copy the Signature (hex) or the Signature (base64), or click Download signature to save signature.sig.
  2. Publish the signature with the data.

Sign an enclave image with a Nitro EIF signer

In the Web App

  1. In your vault, open the Nitro EIF signer.
  2. On the PCR8 for attestation policies card, click Download certificate (PEM). Your EIF tooling attaches this certificate to each image it signs.
  3. On the same card, copy the PCR8 value.

The certificate is fixed when the signer is created, so every image this signer signs has the same PCR8. PCR8 pins the signer, not one image. To allow only an image you approved, require its PCR0 too, the measurement of the image itself. In an AWS KMS key policy, use the kms:RecipientAttestation:PCR0 condition key beside kms:RecipientAttestation:PCR8.

  1. Click Propose signature. The Sign Nitro attestation page opens.
  2. Under Input method, keep Paste signing request (TBS), and paste the image’s to-be-signed bytes under AWS Nitro TBS (base64). Your EIF tooling prints this value. To sign a measurement instead, choose Build from PCR values and enter the PCR index and the PCR value (hex).
  3. Check the Nitro TBS preview: the PCR index and value must match your image.
  4. Optionally, enter a Reason for signing.
  5. Click Propose attestation signature.
Now on each member’s device

On each member’s device, the proposal appears under Requests. The member opens it, checks the details, then taps Approve. The proposal passes when the approvals reach the Guardian Team’s threshold.

The proposal asks to produce an AWS Nitro EIF signature. Its AWS Nitro EIF TBS section shows the PCR index and value. Members compare the value with the measurement of the image the team expects.

Now in the Web App

When the vote passes, the proposal page shows the Signature card.

  1. Click Download signature to save signature.sig.
  2. Attach the signature and the certificate to the EIF with your EIF tooling.

Troubleshooting

Issue Solution
The card cannot be selected, or the page reads “You have no seat in this organization.” You have no seat in this organizationAsk an organization administrator to assign you a seat
Propose signature is disabled with “You don’t have permission to use this resource.” You have no Use access to the keyAsk someone with Edit access to give you Use access
“The data is not valid base64.” The pasted data is not base64Paste the data again as base64. For plain text, turn off Data is already a digest and choose Text
“is_prehashed=true but payload length … != hash output …” The digest’s length does not match the Digest, often because it was pasted as hexPaste the digest’s raw bytes in base64, and check the Digest
“This is not valid base64.” The TBS value holds characters that are not base64, such as hex or extra textCopy the TBS value again from your EIF tooling
“parsing COSE Sig_structure” The TBS value is incomplete, or is not a Nitro TBSCopy the whole value from your EIF tooling
“The PCR value is not valid hex.” The PCR value has an odd number of digits or a character that is not hexPaste the measurement as hex. The proposal must show PCR Value (bytes) as 48
A signature does not check The verifier hashed the data differentlyCheck the Digest and Data is already a digest settings
The proposal stays at Collecting Votes The approvals have not reached the threshold yetAsk the Guardian Team members to open Requests on their devices

External resources