This page explains what SplitSecure protects in a password, a passkey and one-time codes, and who can see each part. It also explains what an approval from your Guardian Team, the group of devices that together approve each proposal, allows. Read it to decide what to store in a vault and who to give access to.
Encrypted parts and visible parts
Each item has encrypted parts and visible parts. SplitSecure uses the visible parts to list, search and match an item before anyone approves a use.
| Item | Encrypted | Visible |
|---|---|---|
| Password | The password and the custom fields marked hidden | The name, the username, the websites and the other custom fields |
| One-time codes | The setup key | The name, the issuer, the username and the websites |
| Passkey | The private key | The website (the relying party), the username and the display name |
What leaves the enclave
The vault runs every operation in its enclave, an isolated environment that nobody who operates the hardware can see into. Something leaves the enclave only after the Guardian Team approves a request, and the enclave encrypts it for the browser or device that the approved request names.
| Item and use | What leaves the enclave |
|---|---|
| Password | The password and its hidden custom fields |
| One-time codes | The codes for the period the request asked for: 3 minutes, 15 minutes or 1 hour |
| Passkey, One-time use | The signature for that one sign-in |
| Passkey, Use on This Device | One half of a two-party signing key to the device, and the other half to SplitSecure’s signing service. Neither half is the private key. |
A password is a secret you type, so it has to leave the enclave for you to use it. Every password manager shares this weakness. SplitSecure limits what it costs you. Each approved request releases only the passwords it names. Whoever takes over your browser or your device gets the passwords already released to it, and nothing else in the vault. In a typical password manager, the unlocked app holds the key to the whole vault, so whoever takes over the app can read every password in it.
Two secrets stay in the vault:
- One-time codes: Once you add or import the setup key, it never leaves the vault. Nobody can read it or export it, administrators included. After each approval, the vault computes only the codes for the period that the request asked for, and sends those codes. A request can ask for 1 hour at most.
- Passkey: The vault creates the private key, and the key never leaves the vault. Nobody can export it, administrators included. When you create a passkey, you choose how members can use it:
- One-time use: Each sign-in is its own request, with its own approval. After the approval, the vault signs that one sign-in and sends only the signature. It is the stricter choice, but it works only in the browser extension.
- Use on This Device: The vault splits a signing key between the device and SplitSecure’s signing service, with two-party ECDSA signing (opens in a new tab) (Lindell 2017). Neither half can sign alone. The device chooses what it signs and checks every signature against it, so the signing service has no say in what is signed. The signing service only enforces what the Guardian Team approved: it signs only for the approved user and device, and only until the time runs out. A passkey allows Use on This Device unless it was created for One-time use only. It must also use the ES256 algorithm (ECDSA on the P-256 curve).
Who can see an item
The visible parts of an item are readable by:
- The organization’s owners, administrators and auditors.
- Each member with access to the item. You give access with Manage Access on the item.
- The members of the Guardian Team, in each request they vote on.
None of them can read an encrypted part without an approved request of their own.
What an approval allows
Each action is a proposal, and each proposal names exactly what it does. An approval allows that one action, and nobody can change the action after the vote.
| Action | Access level the requester needs |
|---|---|
| Create an item, or add one-time codes | Use, on the folder |
| Reveal a password, get codes, sign in with a passkey | Use, on the item |
| Keep a credential ready in Chrome or on a device | Use, on the item |
| Change or delete an item | Edit, on the item |
A member’s seat also decides what they can do. A Basic seat can create and use items, but it cannot join a Guardian Team or vote.
Credentials kept ready
After an approval, a credential can stay ready for a time the requester chooses: 3 minutes, 15 minutes or 1 hour.
- In the browser extension, the filled values for that tab stay in the browser’s memory. They are gone when the time runs out or when the browser closes.
- On a device, Use on This Device stores the password or the codes in the device’s keychain, on that device only. One-time codes are stored as the codes for that time, never as the setup key. For a passkey, the device stores its half of the signing key. Each sign-in needs the device and SplitSecure’s signing service together, and the signing service refuses to sign after the time runs out.
Clear from This Device ends it early on a device. Signing out of the mobile app removes everything the account kept on the device.
During that time, whoever holds the unlocked device can use what it keeps. Choose the shortest time that covers your sign-in.
How SplitSecure matches a website
Each website on a password or on codes has a Fill on rule:
| Rule | Fills on |
|---|---|
| Any page on this domain | Every page of the domain and its subdomains. This is the default. |
| Only this exact host | That host only, with the same port. |
| Never fill here | Nothing on that host. The credential is never offered there. |
SplitSecure fills only on pages served over https. A passkey signs in only on its own website and its subdomains.
When the same account has several credentials
SplitSecure groups a password and one-time codes into one account when all three conditions hold:
- They are in the same folder of the same vault.
- Their usernames match, ignoring capital letters and spaces at the ends.
- One website of each is on the same domain. Websites set to Never fill here don’t count.
The mobile app also adds a passkey with the same username and website to the account. Nothing links the items: moving one to another folder takes it out of the account.
What a lost device or a stolen account allows
- A stolen account can ask for a password, codes or a sign-in. The Guardian Team still has to approve each request, and its members see the request in the mobile app before they vote.
- A lost device gives access only to what it keeps ready, until the time runs out. To stop it voting, take it out of its Guardian Teams: see Revoke a membership.
- SplitSecure’s servers store the visible parts. The browser encrypts a new secret for the vault before it sends it, and the vault encrypts each result for the person who asked.