Reducing exposure to zero-click exploits
Understand attacks that don't need a click, maintain supported devices and use a specialist response when targeted spyware is suspected.

A zero-click exploit can take advantage of software processing incoming content without requiring the recipient to open a link or accept a download. Avoiding suspicious clicks still helps, but it doesn’t cover every way in. In 2019, for example, WhatsApp fixed a flaw that let spyware be installed on a phone through a voice call the owner never answered.
Zero-click describes the interaction required. A zero-day attack exploits a previously unknown vulnerability. The terms aren’t interchangeable; a known vulnerability can still support an attack that requires no click.
Keep the discussion specific
An exploit’s effect depends on the vulnerability, device and software version. Some incidents involve targeted spyware; a general warning doesn’t mean every device is exposed to the same attack.
Ask IT to evaluate credible vendor advisories against the devices your business uses. Record affected versions and available mitigations.
Don’t infer compromise from an ordinary battery problem or slow application alone.
Maintain supported software
Keep operating systems and applications on supported versions and install security updates promptly. Check that updates reached every device, including phones that rarely check in with your management tools.
Review unused applications and services with their owners. Remove the ones you don’t need through your normal change process.
If a device can’t get the updates it needs, work out with IT whether to replace it or limit what it’s used for.
Match additional protection to the risk
Apple’s Lockdown Mode guidance describes an optional protection intended for people who may face highly targeted attacks, including mercenary spyware. It restricts features and can affect ordinary work.
For an Apple user facing that risk, review the mode and what it switches off with IT. It doesn’t replace updates, and the fact that Apple offers it doesn’t mean you’ve been attacked.
Apply vendor-specific advice to other platforms. Don’t assume a mobile device provides the same inspection capabilities as a managed desktop.
Keep response routes available
Give staff a known way to report a vendor threat notification or a credible targeting concern. Verify notifications through the vendor’s official instructions, reached independently.
Apple’s threat-notification guidance explains verification and support for suspected mercenary spyware targeting.
Keep the incident lead’s contact details outside the potentially affected device.
Preserve evidence under direction
If a credible incident is suspected, coordinate with qualified incident responders. Avoid repeatedly opening the suspect content, installing diagnostic tools the responders haven’t asked for, or wiping the device before receiving instructions.
Containment, evidence collection and recovery decisions can conflict if performed independently. Have the incident lead coordinate them.
Keep protection claims realistic
Endpoint tools and network controls may help with particular detection or containment tasks. Don’t assume they can reliably find or block every zero-click exploit.
Record the protection available on each platform and the remaining gaps. Use the incident-response guide for the business coordination that accompanies specialist technical work.


