udpated README.md
This commit is contained in:
parent
ad24c3baa8
commit
2591e704db
@ -10,7 +10,7 @@ Ansible playbook for network vault.
|
|||||||
## 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 desaster-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 so no ransomware can access the system.
|
* 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
|
||||||
* Place this machine on something like an Intel NUC, paint it red and put it into a safe place.
|
* Place this machine on something like an Intel NUC, paint it red and put it into a safe place.
|
||||||
* Create any job to copy your DR-plans there regular.
|
* Create any job to copy your DR-plans there regular.
|
||||||
|
Loading…
Reference in New Issue
Block a user