Share secrets from the console

Cloak keeps a secret out of the agent's context on one machine. The org vault does the same for a whole team: you add the secret once in the console, Prismor seals it to each machine's own key and sends it to the devices you pick, and every agent there uses @@SECRET:NAME@@ without anyone pasting the value around. Rotate it once and every copy updates. Takes about five minutes.

You'll need

  • An org on the Prismor console, with the owner or admin role.
  • At least one device enrolled to the org. See Enroll a device.
  • prismor on that device, updated to the latest release.

1. Add a secret to the org vault

In the console, open Secrets & PII and click Add secret in the Org vault card.

  • Name is what agents type: STRIPE_API_KEY becomes @@SECRET:STRIPE_API_KEY@@.
  • Value is stored encrypted. Nobody can read it back in the console, you included.
  • Who gets it is every device in the org, or only the people, devices and agent keys you pick. Picking a person covers every machine they have enrolled.
  • Only send it to (recommended) lists the hosts the secret is for, like api.stripe.com or *.stripe.com. Devices then resolve it only into a curl, wget, http or xh call to those hosts. An agent can not echo it, encode it or send it anywhere else. Leave it empty for a secret that an env var, a script or an SDK app must read.

Each device gets its own copy, sealed to that machine's key. Only that machine can open it.

2. Use it on a device

Each device checks the console about every 30 seconds while an agent is working, and picks up new secrets by itself. To pull right away:

prismor cloak sync
prismor cloak list

cloak list marks the secret from org vault, v1. Agents and commands now use the placeholder exactly as with a local secret:

prismor cloak run -- curl -s https://api.example.com/v1/charges \
  -H "Authorization: Bearer @@SECRET:STRIPE_API_KEY@@"

The request carries the real key. The output, the transcript and the model see only the placeholder.

3. Watch delivery

The Delivered column counts the devices that hold the current version. Click it to see each device:

StateMeaning
WaitingThe device gets it on its next check, about 30 seconds after it is next online.
Not checked inThe device has not asked for org secrets yet. If this stays, it runs an older Prismor: update it.
ConflictThe device already has its own local secret with this name and kept it. Rename one of the two.

4. Rotate

Click Rotate, paste the new value and save. The secret becomes v2 and every device replaces its copy on its next check. The placeholder does not change, so nothing that uses it needs an edit.

5. Take access away

Access changes who gets the secret. Delete removes it from the org. Either way, each device that loses it deletes its copy on its next check:

A process that already read the value keeps it. When a key must stop working, rotate it at its provider too.


Troubleshooting

SymptomFix
A device stays Not checked inUpdate prismor on it, then run prismor cloak sync. The device must be enrolled to this org.
A device shows ConflictIt has a local secret with the same name. Remove it there with prismor cloak remove NAME, or rename the org secret.
cloak remove on an org secret comes backExpected: the next sync restores anything the console still grants. Take access away in the console instead.
prismor cloak refused: ... is bound to its hostsThe secret has Only send it to hosts. Use it in a curl/wget/http/xh call to one of them, or edit the hosts in the console.
cloak add --from-ref prismor://NAME failsOrg secrets arrive by sync only. They can't be added by reference.

Next