"In the computer world, we're all taught to install firmware updates only if there is a real problem [...]" This is the best way to have a lot of problems. Let see this scenario. A system is in production since 3 years, never got any firmware updates. Someday, a raid controller breaks. A service call is open to get a replacement part. Of course, the replacement part has been flashed with the latest firmware level from the manufacturer. Try to install the new controller, failed. Why? Because the firmware level of the motherboard is too old. Result? You have to upgrade your firmware level in a catastrophic situation where you can't perform a lot of test/validation. Here are the policies I’ve put in place. Rule #1) Firmware must never get older than 1 year except if it's the latest stable available (this ensure we never have catastrophic updates to do in a critical situation because we are never "Too old") Rule #2) Firmware must never be installed in the first month of its release (this leave time to the manufacturer to publish fixes in case of a major problem in the firmware). Keep in mind that in case of hardware failure, you may have to be at a recent firmware level. You can decide if you do the update in a proactive manner or in the middle of a major outage.