| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <3FBCF583.9050305@eiv.com> From: smcmahon at eiv.com (Shawn McMahon) Subject: Sidewinder G2 Schmehl, Paul L wrote: > > Maybe your network policy states that, but I would prefer for single > point of failure devices to fail open, rather than closed. For us, > network availability is a higher priority than protection is. If the > firewall fails, I don't want the entire network down while we're waiting > for a vendor to fix it. I'd be surprised if most networks aren't that > way. The problem with this, as I'm sure you know (but it bears repeating for the peanut gallery) is that it turns any DoS on your firewall into an instant security hole. That escalates the severity of DoS bugs on the firewall, which greatly increases the need to upgrade it when they're found, which can increase your downtime. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 252 bytes Desc: not available Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20031120/f743ada3/attachment.bin
Powered by blists - more mailing lists