TZUTC: -0500
MSGID: 1621.consprcy@1:2320/105 2d5f7134
PID: Synchronet 3.21a-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
TID: SBBSecho 3.28-Linux master/123f2d28a Jul 12 2025 GCC 12.2.0
BBSID: CAPCITY2
CHRS: ASCII 1
FORMAT: flowed
One in five security breaches now thought to be caused by AI-written code

Date:
Thu, 23 Oct 2025 10:03:50 +0000

Description:
Nearly a quarter of production code globally is now AI-generated, and yet 69%
admit to finding vulnerabilities, report finds.

FULL STORY

New research has claimed more than two-thirds (69%) of organizations have
found vulnerabilities in AI-generated code, even though 24% of production 
code is now written by AI globally. 

The State of AI in Security & Development report from Aikido Security found
despite companies pushing AI agendas to improve efficiency and boost output,
security teams (53%), developers (45%) and mergers (42%) still get the blame
when AI code goes wrong. 

Aikido says this is creating confusion over the ownership of AI-caused
vulnerabilities, which could ultimately make them harder to track down and
remediate.

AI-generated code isnt perfect 

Developers didnt write the code, infosec didn't get to review it and legal is
unable to determine liability should something go wrong. It's a real 
nightmare of risk, Aikido CISO Mike Wilkes noted. No one knows whos
accountable when AI-generated code causes a breach. 

In Europe, 20% of companies have had serious incidents, while their US
counterparts have seen more than twice as many (43%), which Aikido puts down
to two factors: the higher likelihood that US developers would bypass 
security controls (72% vs 61%), and Europes stricter compliance. Still, half
(53%) of European companies admit to having near misses. 

 AI tools might not be the enemy, but having an overly complicated ecosystem
could be. The report reveals how 90% of those using six to eight tools
experienced incidents, compared to 64% of those using just one or two tools. 

Remediation time also gets prolonged for those using more tools (3.3 days for
1-2 tools vs 7.8 days for 5+ tools). 

The outlook is more positive, though. Most (96%) agree that AI will 
eventually write secure, reliable code in the next five years, with nearly as
many (90%) believing AI will be able to handle penetration testing within 5.5
years. 

Better still (for the workforce), only 21% think this will happen without
human oversight, highlighting the importance of human workers in the
development process. 

======================================================================
Link to news story:
https://www.techradar.com/pro/security/one-in-five-security-breaches-now-thoug
ht-to-be-caused-by-ai-written-code

$$
--- SBBSecho 3.28-Linux
 * Origin: capitolcityonline.net * Telnet/SSH:2022/HTTP (1:2320/105)
SEEN-BY: 105/81 106/201 128/187 129/14 305 153/7715 154/110 218/700
SEEN-BY: 226/30 227/114 229/110 111 206 300 307 317 400 426 428 470
SEEN-BY: 229/664 700 705 266/512 291/111 320/219 322/757 342/200 396/45
SEEN-BY: 460/58 633/280 712/848 902/26 2320/0 105 304 3634/12 5075/35
PATH: 2320/105 229/426