Google: A Collection of Best Practices for Production Services
Fail Sanely
Sanitize and validate configuration inputs, and respond to implausible inputs by both continuing to operate in the previous state and alerting to the receipt of bad input. Bad input often falls into one of these categories:
Incorrect data
Validate both syntax and, if possible, semantics. Watch for empty data and partial or truncated data (e.g., alert if the configuration is N% smaller than the previous version).
Delayed data
This may invalidate current data due to timeouts. Alert well before the data is expected to expire.
Fail in a way that preserves function, possibly at the expense of being overly permissive or overly simplistic. We’ve found that it’s generally safer for systems to continue functioning with their previous configuration and await a human’s approval before using the new, perhaps invalid, data.
Examples
In 2005, Google’s global DNS load- and latency-balancing system received an empty DNS entry file as a result of file permissions. It accepted this empty file and served NXDOMAIN for Continue reading
Making that digital transition will not be simple. Take advantage of the resources available on the Verizon Enterprise Solutions channel and learn how to drive positive results while maintaining the security of your network
It added new email security services, visibility and malware protection features, and managed security offerings through IT services company ConnectWise.
This technology uncovered last year’s Dragonfly 2.0 attacks targeting energy companies to gain access to the power grid.