The images in this article were generated with artificial intelligence. How we publish
The eruption of artificial intelligence into the hands of attackers has transformed the nature of time into cyberspace: what was before a deliberate and slow operation can now be a chain assault that lasts minutes. Models that generate custom emails and messages, test real-time variations and automatically pivote between targets reduce the detection and response window to something many security teams are not designed to handle.
This jump is not just a matter of speed: it is of scale and adaptation. An AI-assisted opponent writes baits that convert low success rates into sustained accesses, collects context over victims and configures almost instant side movements. The consequence is clear: the defenses focused on perimeter inspection or static rules are at a disadvantage against campaigns that change before the second alert is fired.

To close that gap, it is essential to rethink priorities. Identity, segmentation and automation they are no longer optional good practices and become the operating core. The Zero Trust architecture offers a proven framework for this: to assume that no connection is of default confidence, to verify each access and to limit the scope of each identity drastically reduces what an attacker can discover and exploit. The NIST guide on Zero Trust is a good starting point for translating this concept into specific controls ( https: / / csrc.nist.gov / publications / detail / sp / 800-207 / final).
In practice, the foundations should be first attacked. A real and updated inventory of exposed identities, privileges and services reveals where to cut the risk with the least operational effort. Implement robust multifactor authentication, conditional access policies based on device position and short-term access sessions reduce the effect of committed credentials. Complementing this with minimum privilege policies and periodic permit reviews is a response to potential damage when an opponent gets in.
Breaking the possibility of lateral movement is the second critical line. Microsegmentation, network policies by application and flow control between workloads force the attacker to scale privileges before accessing valuable resources, increasing the probability of detection. This strategy includes removing implicit confidence in internal networks and applying explicit rules that allow only the necessary connections between services, users and systems.
Detecting fast and automating containment is as important as preventing. Alerts are not enough: telemetry must be transformed into operational decisions in seconds. Plant intelligent tripwires - service canaries, decoys with credentials and behavior-based detections - and link them to automated playbooks allows to contain an intrusion before the adversary solves a base of operations. To map observable techniques and behaviors it is appropriate to rely on models such as MITRE ATT & CK to design detections that do not depend on static signatures ( https: / / attack.mitre.org /).

All this sounds like more tools, but operational reality demands the opposite: integration and simplification. Before buying, check which signs already collect your estate (endpoints, proxies, IAM, cloud) and prioritize merging them into a central telemetry channel. Adjusting and automating the responses of the already existing reduces noise and prevents the creation of more working tails for already saturated equipment.
It is not a purely technical exercise: the coordination between business, security and operations defines success. Simulates accelerated campaigns with Red Team exercises and purple teaching adapted to IA-assisted scenarios, measures detection and response times and adjusts success metrics to minutes, not days. Tools and emulation frames allow for internal pressure of the stack before an adversary does so in production.
Finally, keep in mind the cost and limits. Malcalibrated automation generates false contentions and erodes business confidence; too restrictive policies paralyze operations. The appropriate formula combines technical controls that limit the scope available to an attacker with reliable tripwires and automated runbooks that are tested and adjusted with regular exercises. In a world where IA accelerates attacks, the advantage is that it reduces what is there to find, prevents lateral movement and acts automatically and precisely when the first alarm rings.
Related
More news on the same subject.

GhostAction Expands Attack: phishing to steal credentials and persistence in VS Code
A group behind the GhostAction campaign - already known for infiltrating GitHub Actions workflows into open source projects - has expanded its arsenal: in addition to installing...

ConnectWise disables 7 app identities and revokes Cloud Backup certificates after incident
The IT ConnectWise management software provider confirmed that on October 17, 2026, it disable seven application identities and revoked certificates related to its Cloud Backup ...

Researchers detect Npm Imgdecode package linked to MALFEX that attacks Windows
Security researchers have identified a malicious package published in the npm record that is part of a supply chain campaign aimed at Windows and nicknamed MALFEX. The package, ...

OpenBSD 7.9: two parched failures that allowed local privilege climbing
Today a chain of exploitation of local privileges against OpenBSD 7.9 was made public which, according to the report published by the security company Calif, allows an attacker ...

OpenAI reveals unaligned IA incidents; a GPT-5.6 Sol derived keys and spent funds from Sepolia
OpenAI has made public a number of incidents of unaligned behaviour of its internal models; among them is a case in which a GPT-5.6 family research model Sol derived private key...

Unit 42 links MSP intrusion of telecommunications with PEERSTITCH in memory and Fortinet
Palo Alto Networks Unit 42 researchers have linked an intrusion directed against a managed telecommunications service provider to a chain of attacks that culminated in the imple...