FAQ

Deployment and licensing

Virtual or not?

Q: Can I run StoredSafe as a virtual appliance?

A: Yes, you can. If you can settle for a lower assurance level (A instead of AAA), you can deploy StoredSafe as a virtual appliance on any modern hypervisor. StoredSafe has been tested on Xen, XCP-ng and VMware, and is expected to work on others such as KVM and Proxmox.

What are the different assurance levels?

Level

Deployment

On-premises

2FA validation

AAA+

Redundant hardware appliances

Yes

Hardware HSM

AAA

Hardware appliance

Yes

Hardware HSM

AA

VM hosted in StoredSafe cloud

No

YubiCloud, SoftHSM

A

VM on any modern hypervisor

Yes

YubiCloud, SoftHSM

All assurance levels support YubiKeys, TOTP-based authenticators (such as Google Authenticator) and X.509 client certificates. The difference lies in how one-time passwords are validated:

  • Hardware HSM: both YubiKey and TOTP secrets are validated in the appliance’s hardware security module.

  • YubiCloud, SoftHSM: YubiKeys are validated using Yubico’s YubiCloud service, and TOTP secrets in a local software HSM.

What happens when my license expires?

Q: Do I lose access to my information if the StoredSafe license expires?

A: No. Everything already stored in StoredSafe remains readable, but you can no longer create or edit objects until a valid license has been installed. See StoredSafe License.

Which browsers are supported?

A: See Supported Browsers.

Authentication

Which MFA methods are supported?

A: StoredSafe is designed to be MFA-agnostic. The following methods are available today:

  • YubiKey OTP

  • TOTP (such as Google Authenticator)

  • X.509 client certificates (smartcards, mTLS)

Support for BankID (Sweden), Smart-ID (Estonia) and Duo is prepared in the platform, but not yet implemented. Most other MFA mechanisms can in principle be integrated as well. If your organization needs a method that is not yet available, please contact us and we can implement it.

Which methods are allowed is configured under Login Settings.

Why is there no SAML/ADFS single sign-on?

Q: Can users log in to StoredSafe using SAML, ADFS or another single sign-on solution?

A: No, and this is by design. In StoredSafe, the user’s password is not just checked against a stored hash: it is the passphrase that unlocks the user’s personal PGP private key, which in turn is needed to decrypt the information in the user’s vaults.

With federated login, the user authenticates against the identity provider, and StoredSafe only receives a signed statement saying who the user is. The password never reaches StoredSafe, so there is nothing to unlock the private key with. Making single sign-on work would require StoredSafe, or the identity provider, to hold the users’ keys. That would break a fundamental principle of StoredSafe, that not even the system administrators have access to the stored information, and it would make the identity provider a single key to every vault.

MFA methods do not have this problem, since they are added on top of the passphrase rather than replacing it.

Some of the benefits of a directory service can still be achieved. For example, ldap-utils-storedsafe can deactivate StoredSafe users based on an LDAP search, such as users that have been disabled in Active Directory, to simplify offboarding.

Help! I’ve lost my password!

Q: How do I help a user who has forgotten their password?

A: A forgotten password cannot be reset. Each user is protected by a personal PGP key pair, and the password is the passphrase to the user’s private key, so a lost password means a lost key pair.

Instead, deactivate the old user and create a new user with the same user details. Another user with the data custodian permission then shares the vaults back to the new user. Vaults left without a data custodian have to be recovered using the key escrow procedure. See Lost password for the full procedure.

A user has lost their YubiKey

Q: What do I do when a user has lost their YubiKey?

A: A system administrator can replace the user’s YubiKeys from the console. Note that this replaces all YubiKeys assigned to the user; to manage multiple YubiKeys for a single user, use the web interface. See Replace a lost Yubikey for a user.

What if I lose an escrow YubiKey?

Q: What happens if I lose one or both of my escrow YubiKeys?

A: The escrow user’s private key should be stored air-gapped, on paper and on USB. The passphrase protecting that private key is split in two halves, each stored on a separate YubiKey. This enables separation of duties: no single person can use the escrow key on their own.

If you lose one of the YubiKeys, you lose half of the passphrase to the escrow user’s private key, which means that you are in trouble. We strongly suggest that you keep the escrow YubiKeys in two different fireproof safes.

If you would like to secure your escrow functionality even more, you can add multiple escrow users. That way you are able to store a pair of keys at your disaster recovery site. See Key Escrow Management.

Users, vaults and objects

Can I delete a user permanently?

A: No. Users are never deleted, only deactivated, to keep the audit log complete. A deactivated user can be reactivated at any time. See Deleting Users and Recover Users.

Can deleted vaults and objects be recovered?

A: Yes. Deleted vaults and objects can be restored from the console, as long as a system administrator has not permanently removed them to recover disk space. See Undelete Vault or Objects.

Operations and integration

How are backups protected?

A: Backups are encrypted with PGP and transferred using SSH. Keep every PGP secret key you have ever used for backups: each backup stays encrypted to the key that was active when it was created, so losing an old key means losing the ability to restore backups made with it. See Backup Management.

How do I monitor StoredSafe?

A: StoredSafe exposes health metrics via SNMPv3, which can be collected by Prometheus and visualized in Grafana. See StoredSafe Metrics via SNMPv3 and Using Grafana / Prometheus with StoredSafe. A ready-made reference stack is available in storedsafe-monitoring.

Can I automate or integrate with StoredSafe?

A: Yes. StoredSafe has a REST-like API (see StoredSafe REST-like API), and API keys are managed from the console. StoredSafe also maintains several open source projects, such as client libraries, a browser extension and Ansible and Hiera integrations. See Opensource.

How do we migrate from spreadsheets or another password manager?

A: Most spreadsheets and password managers can export to CSV. csv-importer converts a CSV file into StoredSafe objects, either by producing JSON that can be pasted into the web interface when creating new objects, or by importing the objects directly via the REST API.

Is there a browser extension?

A: Yes, for Firefox, Chrome and Edge. See storedsafe.com/addons/browser for download links. Besides being configured by each user, the extension can be configured centrally by an administrator through the browser’s policy management. The source code is available at storedsafe-browser-extension.

How can we use secrets in automation without hard-coding them?

A: StoredSafe provides integrations that retrieve secrets at runtime, so they never need to be stored in code or configuration files:

Every retrieval of a secret is recorded in the StoredSafe audit log.

Can StoredSafe keep track of expiring certificates?

A: Yes. x509-vacuumer locates X.509 certificates on your network and stores them in StoredSafe together with their metadata. StoredSafe then issues an alert 30 days before each certificate expires. Alerts are sent via syslog, so forward them to your log management or SIEM solution, see Syslog Settings.