From c5b0e36ee2ee1b63b7196315325829728f97209c Mon Sep 17 00:00:00 2001 From: Alexander Gabriel Date: Sat, 12 Jun 2021 00:26:21 +0100 Subject: [PATCH] udpated README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 135f764..5d33233 100644 --- a/README.md +++ b/README.md @@ -8,7 +8,7 @@ Ansible playbook for network vault. * How long the data will be kept depends on settings in rsnapshot.conf ## Use-Case: -* 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. +* Create a immutable, WORM-Like Network-Share that holds REALLY!!! sensitive data like disaster-recovery-plans, password databases, network-plans, contact-lists - all the data that should not be encrypted and you need in case of ransomware-attack to bootstrap youself. * 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. * You should **NOT NOT NOT NOT** have a KVM-Console connected because this can be used to access the system over the network