In the past week, thousands of businesses lost email for nearly a day. The Federal Aviation Administration (FAA) halted departures nationwide, a classified communications network at the National Security Administration (NSA) reportedly went dark, millions of employees were locked out of their pay and benefits on a Friday afternoon, and customers at some of the nation’s largest financial institutions saw online banking disrupted. Where causes have been disclosed, they appear unrelated: A software defect, a router replacement, a bug in on-premises hardware. That has not stopped speculation that these disruptions are linked – and news coverage is drawing parallels to prior incidents.
Organizations are now in an especially vulnerable window. Whether or not there is a causal link, stakeholders and the media are likely to connect any new outage to what has already happened and assume the worst. Adding to the challenge, the first hours of an incident rarely come with complete information, but that is when a company must reassure and explain without overstating information that later needs to be taken back.
After supporting clients as they approach these challenges firsthand, the H/Advisors team is advising the following:
Get on-the-record before the fix.
When stakeholders depend on seamless and predictable services, credibility is on the line during a disruption. Social media will fill silence within minutes. If an issue is actively getting addressed, even if it isn’t fully resolved, being on-the-record demonstrates responsiveness and can reassure any impacted stakeholders. If it is determined that the company is not impacted, being on-the-record to clarify is beneficial to those watching.
Be more explicit about what the incident is. Be careful with what it is not.
Stakeholders are asking a lot of questions, and the swirl of speculation is eliciting explanations from “failed software update” to “hostile foreign actors.” We have seen recent on-the-record commentary confirming not only what an incident is, but what it is not—not cybersecurity-related, not affecting our company, not an industry-wide, systemic issue, or not originating from our company. Given the risks in the current narrative landscape, there are some circumstances where it may be important to clarify if a disruption has not been caused by a cybersecurity breach. At the same time, if you are not entirely sure, bear in mind that having to reverse your initial position will impact credibility and become a story in itself.
Understand the sequencing of software and hardware updates.
For years, faulty software updates have been a risk that can draw global attention for disruption on a global scale. We have noticed that over the past few months, as organizations work to reinforce their software against emerging threats, software updates are getting pushed more frequently. It is doubtless that continuous updates are critical—but knowing which day the update gets pushed out and how it gets pushed out (whether on a rolling or broad scale basis) can help to foreshadow a higher-risk day for a technological disruption.
Know whose outage it really is.
Several disruptions this week cascaded from a single provider. When a vendor’s failure becomes your customers’ problem, own the customer experience and the fix. Pointing to a partner may be accurate, but customers rarely accept it as an answer. Agree now with critical vendors on how you will problem solve and coordinate communications before an issue arises.