The first malware created with artificial intelligence: managing cybersecurity risks

What it is about

The webinar focuses on the technical, operational and compliance risks associated with the first malware created with artificial intelligence and their implications for banking.

Session summary

The speaker starts from a practical question: how prepared organizations are to use artificial intelligence and to defend themselves against those who use it maliciously. He points out that many have no acceptable-use policy, that users are creative but not always aware of the risk, and how generative artificial intelligence boosts phishing, voice and video cloning, and fraud aimed at executives. He explains polymorphic malware, which can change its code to evade defenses, and warns that signature-based detection is no longer enough and that fully autonomous attacks are close.

His central message is that cybersecurity is much more than technology and that the human factor remains decisive: people, processes and technology must be combined, training for whoever operates each tool must be funded, the purpose of controls must be explained so that security is an ally of the business, and complying with a standard is not the same as being secure. He stresses immutable backups, an inventory of talent and critical providers and constant updating of knowledge. In the discussion with the Cybersecurity Working Group, they covered the differences from traditional malware, first measures for banks, how to persuade other areas, the real cost of an attack, third-party risk and the need to go beyond compliance.

Topics covered

• Acceptable-use policy for artificial intelligence in organizations
• Phishing, voice and video cloning and fraud aimed at executives
• Polymorphic malware and increasingly autonomous attacks
• People, processes and technology: the human factor and training
• Incident readiness: immutable backups, talent and critical providers
• Security as a business ally and going beyond compliance
• Questions: first measures for banks, cost of an attack and third-party risk