From e8e3df738d9bdeb2f6da00bd9306be3c6d6aae3c Mon Sep 17 00:00:00 2001 From: Alexander Gabriel Date: Sat, 12 Jun 2021 00:23:56 +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 86d01aa..95bbe7b 100644 --- a/README.md +++ b/README.md @@ -11,7 +11,7 @@ Ansible playbook for network vault. * 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 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. * Create any job to copy your DR-plans there regular. * It uses cron-apt to update the system and reboots at 6 in the morning to keep kernel up to date