4 ms·
If it only takes 1 mistake, would having a hot backup or failover be a best practice, so that if something does happen, you can immediately channel traffic to a
by JakeFratelli 15y ago
If it only takes 1 mistake, would having a hot backup or failover be a best practice, so that if something does happen, you can immediately channel traffic to a live site?
- EwanToo 15y agoQuite often the failover is just a DNS change to a static page saying "Sorry, we're currently unavailable". The difficulty of having a hot backup is preventing a hacker repeating their attack immediately after you fail over.
- JakeFratelli 15y agoThanks EwanToo - that makes perfect sense. A combination of some security monitoring system that notifies you of the vulnerabilities along with someone to update your system is needed. But what if the updates have dependencies, for instance, incompatible Ruby gems or so. At that point, do you have to make the tradeoff of security risk vs time to update all gems/resolve incompatibility issues/deal with bugs in latest release?
- EwanToo 15y agoExactly, if you've got a complex environment, you might not even know that one of your suppliers deployed an insecure ruby gem (or any other package), but you'll want to do full testing before upgrading. All this leaves big windows of opportunity for attacks.