How AI Can Find Weaknesses In Corporate Crisis Management Plans

Google’s recent confirmation that its Gemini AI hacked the systems of three companies during a cybersecurity test that was conducted in May by the security firm Irregular. The test was meant to involve simulated targets, according to the Wall Street Journal.

Gemini accessed one company’s protected system by guessing its passwords. In two other cases, it used credentials that it found in public repositories. Google said the model stopped each hack when it recognized that it had accessed a real company’s system, the Journal reported.

The incident raises an important question for business leaders: If an AI-related event affected their organization, would their crisis management plan help them respond quickly and credibly? AI tools can create new risks, but they can also help companies find weaknesses in their plans and prepare responses.

Finding blind spots

AI-related incidents such as these can cause different crisis situations for companies and organizations that can impact their operations, credibility, and reputation. The good news is that AI can also help organizations find weaknesses in their crisis management plans before someone—or something—else does.

Companies that take the time now to use AI models to test their plans will be better prepared than organizations that let their plans gather dust. The technology can catch blind spots and gaps that others may miss by running a series of what-if scenarios, including AI hacks and other technology-related hypotheticals. When a crisis strikes a company, journalists, customers, and others may turn to the internet and chatbots for information about the situation, even before they’ll visit the company’s website. That’s why companies should monitor and track what’s being said about their crisis on social media and other platforms and respond as needed.

Asking and phrasing the right questions

Imposing limitations

Learning from the mistakes of others

Companies can learn from that experience and avoid making the same mistake by: