Add audit page

BlackDex 2024-11-18 20:53:40 +01:00
parent de6d6783f1
commit 7f46428a43
No known key found for this signature in database
GPG Key ID: 58C80A2AA6C765E1
4 changed files with 24 additions and 2 deletions

19
Audits.md Normal file

@ -0,0 +1,19 @@
# Vaultwarden Audits
Vaultwarden has been audit by security companies which helps keeping Vaultwarden secure.
Some audits were done without publishing anything data publicly because the companies which requested the audit with those security companies didn't allowed it, but those researchers did provide the results.
Some audits are publicly published and can be accessed by everyone.
## Audit by BSI
> [!NOTE]
> The site and report are both in German
[BSI (Bundesamt für Sicherheit in der Informationstechnik)](https://www.bsi.bund.de/EN/Home/home_node.html), a German institute performed an audit on [Vaultwarden v1.30.3](https://github.com/dani-garcia/vaultwarden/releases/tag/1.30.3) under there [CAOS (Codeanalyse von Open Source Software) project](https://www.bsi.bund.de/DE/Service-Navi/Publikationen/Studien/Projekt_P486/projekt_P486_node.html).
The press release, including the PDF with the results for Vaultwarden can be found here: https://www.bsi.bund.de/DE/Service-Navi/Presse/Alle-Meldungen-News/Meldungen/Codeanalyse-KeePass-Vaultwarden_241014.html
They even have a more detailed ZIP file with all raw information located here: https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/Downloadserver/P486/CAOS_Vaultwarden.html

@ -54,7 +54,7 @@ Assuming this command is run on January 1, 2021 at 12:34pm (local time), this ba
You can run this command via a cron job periodically (preferably at least once a day). If you are running via Docker, note that the Docker images do not include an `sqlite3` binary or `cron` daemon, so you would generally install these on the Docker host itself and run the cron job outside of the container. If you really want to run backups from within the container for some reason, you can install any necessary packages during [container startup](https://github.com/dani-garcia/vaultwarden/wiki/Starting-a-Container#customizing-container-startup), or create your own custom Docker image with your preferred `vaultwarden/server:<tag>` image as the parent.
If you want to copy your backup data to cloud storage, [rclone](https://rclone.org/) is a useful tool for interfacing with various cloud storage systems. [restic](https://restic.net/) is another good option, especially if you have larger attachments and want to avoid recopying them as part of each backup.
If you want to copy your backup data to cloud storage, [rclone](https://rclone.org/) is a useful tool for interfacing with various cloud storage systems. [restic](https://restic.net/) or [rustic](https://rustic.cli.rs/) are other good options, especially if you have larger attachments and want to avoid recopying them as part of each backup.
### The `attachments` dir
@ -102,7 +102,7 @@ Make sure vaultwarden is stopped, and then simply replace each file or directory
When restoring a backup created using `.backup` or `VACUUM INTO`, make sure to first delete any existing `db.sqlite3-wal` file, as this could potentially result in database corruption when SQLite tries to recover `db.sqlite3` using a stale/mismatched WAL file. However, if you backed up the database using a straight copy of `db.sqlite3` and its matching `db.sqlite3-wal` file, then you must restore both files as a pair. You don't need to back up or restore the `db.sqlite3-shm` file.
It's a good idea to run through the process of restoring from backup periodically, just to verify that your backups are working properly. When doing this, make sure to move or keep a copy of your original data in case your backups do not in fact work properly.
It's a good idea to run through the process of restoring from backup periodically, just to verify that your backups are working properly. When doing this, make sure to move or keep a copy of your original data in case your backups do not in fact work properly.
## Examples

@ -4,6 +4,8 @@ Vaultwarden is an unofficial Bitwarden server implementation written in Rust. It
Vaultwarden is targeted towards individuals, families, and smaller organizations. Development of features that are mainly useful to larger organizations (e.g., single sign-on, directory syncing, etc.) is not a priority, though high-quality PRs that implement such features would be welcome.
There have been several audits done on Vaultwarden of which some are publicly available, read more about it on our [[Vaultwarden Audit|Audit]] wiki page.
## Supported features
Vaultwarden implements the Bitwarden APIs required for most functionality, including:

@ -1,5 +1,6 @@
## FAQs
1. [[FAQs]]
1. [[Audits]]
## Container Image Usage
1. [[Which container image to use|Which-Container-image-to-use]]