DigitalInfinity/network-vault
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

udpated README.md

Browse Source
This commit is contained in:
Alexander Gabriel 2021-06-12 00:24:44 +01:00
parent e8e3df738d
commit 99303d9810
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -8,7 +8,7 @@ Ansible playbook for network vault.
* How long the data will be kept depends on settings in rsnapshot.conf * How long the data will be kept depends on settings in rsnapshot.conf
## Use-Case: ## Use-Case:
* Create a immutable, WORM-Like Network-Share that holds REALLY!!! sensitive data like desaster-recovery-plans, password databases, network-plans, all the data you need in worst case and that should not be encrypted by any ransomware. * Create a immutable, WORM-Like Network-Share that holds REALLY!!! sensitive data like disaster-recovery-plans, password databases, network-plans, all the data you need in worst case and that should not be encrypted by any ransomware.
* When ransomware locks down your systems, this is your machine to go, plug in a console and start recovery. * When ransomware locks down your systems, this is your machine to go, plug in a console and start recovery.
* When sealing the vault, you can not access it over ssh any more, change settings, access system over network so no ransomware can to this either. * When sealing the vault, you can not access it over ssh any more, change settings, access system over network so no ransomware can to this either.
* You should **NOT NOT NOT NOT** have a KVM-Console connected because this can be used to access the system over the network * You should **NOT NOT NOT NOT** have a KVM-Console connected because this can be used to access the system over the network