<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
     xmlns:content="http://purl.org/rss/1.0/modules/content/"
     xmlns:dc="http://purl.org/dc/elements/1.1/"
     xmlns:dcterms="http://purl.org/dc/terms/"
     xmlns:media="http://search.yahoo.com/mrss/"
     xmlns:atom="http://www.w3.org/2005/Atom"
     xmlns:cf="https://www.futureplc.com/rss/content-flags"
>
    <channel>
                    <atom:link href="https://www.itpro.com/feeds/tag/application-security" rel="self" type="application/rss+xml" />
                            <title><![CDATA[ Latest from ITPro in Application-security ]]></title>
                <link>https://www.itpro.com/cybersecurity/application-security</link>
        <description><![CDATA[ All the latest application-security content from the ITPro team ]]></description>
                                    <lastBuildDate>Fri, 21 Aug 2026 15:28:38 +0000</lastBuildDate>
                            <language>en</language>
                                <item>
                                                            <title><![CDATA[ Why security teams need to start operating like engineers ]]></title>
                                                                                                <dc:content><![CDATA[ <p>AI represents a prime opportunity for security teams to keep pace with accelerating development timelines, according to GitLab CISO Chaim Mazal. But this will require tweaks to traditional processes. </p><p>The use of AI in software development is fast approaching near-universal levels, with figures from Stack Overflow’s 2025 <a href="https://survey.stackoverflow.co/2025/ai" target="_blank"><u><em>Developer Survey</em></u></a> showing 84% of developers have adopted the technology. </p><p>While AI is helping speed up code production, streamline development lifecycles, and drive productivity, Mazal told <em>ITPro </em>it’s also creating new security risks. </p><p>“Businesses have decided that in order to be successful in this next wave of the journey, AI has to be leveraged and teams have to go full bore,” he said. </p><p>“I think in tandem and parallel, security teams have been working on figuring out how they can build appropriate solutions to be able to enable their organizations to do that.”</p><p>Mazal noted that enterprises are still working around the “same practices and principles that we’ve historically followed” - robust testing, reviews, and security checks. </p><p>But with the advent of agentic AI and the pace of change, there’s a risk that blind spots could emerge somewhere in the process.</p><p>Indeed, it’s an issue that GitLab recently highlighted in a study. <a href="https://www.itpro.com/software/development/enterprises-are-shipping-so-much-ai-generated-code-they-cant-control-or-secure-it"><u>Analysis from the company</u></a> in June warned that eight-in-ten organizations are adopting AI tools faster than they can develop policies to govern them. </p><p>The influx of AI-generated code is also proving troublesome for enterprises, with a <a href="https://www.itpro.com/software/development/enterprises-are-shipping-huge-volumes-of-untested-ai-generated-code-experts-warn-it-will-cause-major-security-issues-and-have-huge-financial-repercussions"><u>study from Tricentis</u></a> showing that roughly 60% of organizations have shipped untested code. </p><p>The result here is that security teams now face a confluence of challenges. Potentially dangerous AI-generated code and increasingly fast development timelines are placing huge pressure on teams to ensure products ship in both a timely and secure manner. </p><h2 id="an-engineering-first-approach">An engineering-first approach</h2><p>Keeping pace with AI-powered development will mean security teams essentially have to start operating more like their counterparts in development in an ‘engineering-first’ approach. </p><p>This is an operating model that takes core engineering principles such as automated testing and <a href="https://www.itpro.com/business/digital-transformation/cicd-comes-into-focus-as-enterprises-ramp-up-application-modernization-efforts">CI/CD </a>pipeline techniques and embeds them within security processes. Simply put, rather than acting like manual auditors and policy enforcers, they play a more involved role in development processes. </p><p>Moreover, they build parallel products designed to support development from the get-go. Fundamentally, this is about being a “first-level contributor” in software development, Mazal said. </p><p>“As our engineering teams move fast, having the security team have the ability to contribute code, make iterative adjustments, and be part and parcel with the development process is key to our success,” he told <em>ITPro</em>. </p><p>“Being able to move fast, iterate fast, and not just be consultative in nature, and being able to really roll up our sleeves and work alongside the rest of the teams to build that secure path and the secure guardrails is something I think most modern security teams don’t have the luxury of foregoing.” </p><p>When it comes to AI, what’s good for the goose is good for the gander. Security teams should view the technology as a means to keep up with development processes – as with developers, teams need to automate where they can. </p><h2 id="humans-in-the-loop">Humans in the loop</h2><p>Ensuring humans remain in the loop throughout the development and testing process will still be vital moving forward, according to Mazal. The exact scope of human involvement is still up for debate, however, and the long-term goal is to automate as much as possible in the safest way </p><p>“I think most organizations who make commercial-level software want to get to a place where there are only humans in the loop in places that it’s absolutely necessary, based on the risk to the organization,” he said. </p><p>“They’d like to be able to have the overwhelming majority of their code auto-generated and auto-reviewed.”</p><p>Mazal said this has the potential to pose new challenges for developers, testers, and security teams alike. Fully-automated pipelines are still evolving, and as <a href="https://www.itpro.com/software/software-teams-should-take-a-leaf-out-of-manufacturers-books-when-it-comes-to-ai-generated-code"><u><em>ITPro </em></u><u>recently reported</u></a>, some enterprises are exploring the concept of ‘dark testing factories’ to ramp up automation with little human input. </p><p>“Collectively we’re still trying to figure out as an industry what those best practices are, but we’re definitely making very big leaps and bounds in very short periods of time.”</p><p>GitLab itself is ramping up the use of agents in a software factory approach, Mazal noted, focusing intently on a security-conscious strategy. Agents need strict guardrails, and enterprises need to implement certain restrictions from the get-go. </p><p>“How we’re thinking about this at GitLab from a software factory perspective is that you have the ability from the very initial inception of design to bake in those security guardrails and requirements,” he explained. </p><p>“You can go ahead and create and craft them and define them based on the data sensitivity and requirements that you have, and you can uniformly implement governance controls across the board.”</p><p>These processes will naturally evolve as requirements change, Mazal said, and teams will “continuously make adjustments along the way”. </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/ai-assisted-software-development-means-security-teams-need-an-engineering-first-mindset</link>
                                                                            <description>
                            <![CDATA[ As AI-powered coding accelerates, security teams need to start operating like developers ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">e35qmwsZr2ozEw7wjELqT7</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/joTCHrxyPvfn3ZLe4VTU6e-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 21 Aug 2026 15:28:38 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:51 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                <author><![CDATA[ ross.kelly@futurenet.com (Ross Kelly) ]]></author>                    <dc:creator><![CDATA[ Ross Kelly ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Y5vrV2V98Np6jHAGmAtCd3-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Ross Kelly is ITPro&#039;s News &amp;amp; Analysis Editor, with a keen interest in cyber security, business leadership and emerging technologies.&lt;/p&gt;
&lt;p&gt;He graduated from Edinburgh Napier University in 2016 with a BA (Hons) in Journalism, and joined ITPro in 2022 after four years working in technology conference research.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In his spare time, Ross enjoys cycling, walking and is an avid reader of history and non-fiction.&lt;/p&gt;
&lt;p&gt;You can contact Ross at ross.kelly@futurenet.com or on &lt;a href=&quot;https://twitter.com/rosswritesetc&quot;&gt;Twitter&lt;/a&gt; and &lt;a href=&quot;https://www.linkedin.com/in/ross-kelly-18a54411a/&quot;&gt;LinkedIn&lt;/a&gt;.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/joTCHrxyPvfn3ZLe4VTU6e-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Female software engineer working on a desktop computer in an office space while male colleague stands over desk checking work on a tablet.]]></media:description>                                                            <media:text><![CDATA[Female software engineer working on a desktop computer in an office space while male colleague stands over desk checking work on a tablet.]]></media:text>
                                <media:title type="plain"><![CDATA[Female software engineer working on a desktop computer in an office space while male colleague stands over desk checking work on a tablet.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/joTCHrxyPvfn3ZLe4VTU6e-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>AI represents a prime opportunity for security teams to keep pace with accelerating development timelines, according to GitLab CISO Chaim Mazal. But this will require tweaks to traditional processes. </p><p>The use of AI in software development is fast approaching near-universal levels, with figures from Stack Overflow’s 2025 <a href="https://survey.stackoverflow.co/2025/ai" target="_blank"><u><em>Developer Survey</em></u></a> showing 84% of developers have adopted the technology. </p><p>While AI is helping speed up code production, streamline development lifecycles, and drive productivity, Mazal told <em>ITPro </em>it’s also creating new security risks. </p><p>“Businesses have decided that in order to be successful in this next wave of the journey, AI has to be leveraged and teams have to go full bore,” he said. </p><p>“I think in tandem and parallel, security teams have been working on figuring out how they can build appropriate solutions to be able to enable their organizations to do that.”</p><p>Mazal noted that enterprises are still working around the “same practices and principles that we’ve historically followed” - robust testing, reviews, and security checks. </p><p>But with the advent of agentic AI and the pace of change, there’s a risk that blind spots could emerge somewhere in the process.</p><p>Indeed, it’s an issue that GitLab recently highlighted in a study. <a href="https://www.itpro.com/software/development/enterprises-are-shipping-so-much-ai-generated-code-they-cant-control-or-secure-it"><u>Analysis from the company</u></a> in June warned that eight-in-ten organizations are adopting AI tools faster than they can develop policies to govern them. </p><p>The influx of AI-generated code is also proving troublesome for enterprises, with a <a href="https://www.itpro.com/software/development/enterprises-are-shipping-huge-volumes-of-untested-ai-generated-code-experts-warn-it-will-cause-major-security-issues-and-have-huge-financial-repercussions"><u>study from Tricentis</u></a> showing that roughly 60% of organizations have shipped untested code. </p><p>The result here is that security teams now face a confluence of challenges. Potentially dangerous AI-generated code and increasingly fast development timelines are placing huge pressure on teams to ensure products ship in both a timely and secure manner. </p><h2 id="an-engineering-first-approach">An engineering-first approach</h2><p>Keeping pace with AI-powered development will mean security teams essentially have to start operating more like their counterparts in development in an ‘engineering-first’ approach. </p><p>This is an operating model that takes core engineering principles such as automated testing and <a href="https://www.itpro.com/business/digital-transformation/cicd-comes-into-focus-as-enterprises-ramp-up-application-modernization-efforts">CI/CD </a>pipeline techniques and embeds them within security processes. Simply put, rather than acting like manual auditors and policy enforcers, they play a more involved role in development processes. </p><p>Moreover, they build parallel products designed to support development from the get-go. Fundamentally, this is about being a “first-level contributor” in software development, Mazal said. </p><p>“As our engineering teams move fast, having the security team have the ability to contribute code, make iterative adjustments, and be part and parcel with the development process is key to our success,” he told <em>ITPro</em>. </p><p>“Being able to move fast, iterate fast, and not just be consultative in nature, and being able to really roll up our sleeves and work alongside the rest of the teams to build that secure path and the secure guardrails is something I think most modern security teams don’t have the luxury of foregoing.” </p><p>When it comes to AI, what’s good for the goose is good for the gander. Security teams should view the technology as a means to keep up with development processes – as with developers, teams need to automate where they can. </p><h2 id="humans-in-the-loop">Humans in the loop</h2><p>Ensuring humans remain in the loop throughout the development and testing process will still be vital moving forward, according to Mazal. The exact scope of human involvement is still up for debate, however, and the long-term goal is to automate as much as possible in the safest way </p><p>“I think most organizations who make commercial-level software want to get to a place where there are only humans in the loop in places that it’s absolutely necessary, based on the risk to the organization,” he said. </p><p>“They’d like to be able to have the overwhelming majority of their code auto-generated and auto-reviewed.”</p><p>Mazal said this has the potential to pose new challenges for developers, testers, and security teams alike. Fully-automated pipelines are still evolving, and as <a href="https://www.itpro.com/software/software-teams-should-take-a-leaf-out-of-manufacturers-books-when-it-comes-to-ai-generated-code"><u><em>ITPro </em></u><u>recently reported</u></a>, some enterprises are exploring the concept of ‘dark testing factories’ to ramp up automation with little human input. </p><p>“Collectively we’re still trying to figure out as an industry what those best practices are, but we’re definitely making very big leaps and bounds in very short periods of time.”</p><p>GitLab itself is ramping up the use of agents in a software factory approach, Mazal noted, focusing intently on a security-conscious strategy. Agents need strict guardrails, and enterprises need to implement certain restrictions from the get-go. </p><p>“How we’re thinking about this at GitLab from a software factory perspective is that you have the ability from the very initial inception of design to bake in those security guardrails and requirements,” he explained. </p><p>“You can go ahead and create and craft them and define them based on the data sensitivity and requirements that you have, and you can uniformly implement governance controls across the board.”</p><p>These processes will naturally evolve as requirements change, Mazal said, and teams will “continuously make adjustments along the way”. </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Why software supply chain security is the next accountability challenge for channel partners ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Modern applications rely heavily on open-source packages and third-party dependencies, meaning almost every application organizations run is built on layers of code written by people outside the organization. </p><p>Channel partners are often responsible for recommending, integrating and managing these environments. As a result, when a dependency is compromised, accountability increasingly lands with the partner managing the stack.</p><h2 id="why-vulnerable-and-malicious-packages-remain-in-production">Why vulnerable and malicious packages remain in production</h2><p>Unfortunately, public disclosure does not equal remediation. Organizations continue running outdated or vulnerable dependencies months after Common Vulnerabilities and Exposures (CVEs) become public, and this is increasingly becoming the norm. <a href="https://www.nist.gov/news-events/news/2026/04/nist-updates-nvd-operations-address-record-cve-growth"><u>CVE volume has grown</u></a> by 263% since 2020, with 2026 already seeing a further 33% increase. At this pace, security teams are struggling to digest the volume of vulnerabilities, let alone prioritise and implement effective remediation plans. </p><p>Many Managed Service Providers (MSPs) and consultancies also inherit environments they didn't originally architect. Combined with security frameworks that were designed around infrastructure and endpoints rather than continuously evolving software dependencies, the challenge becomes even greater. Moreover, the growing use of AI-assisted development is adding another layer of complexity, accelerating software creation while increasing the volume of third-party code and dependencies entering production. </p><p>Modern applications can contain hundreds of transitive dependencies, making it difficult to maintain an accurate inventory of what's actually running in production. Limited adoption of Software Bills of Materials (SBOMs), alongside the challenge of auditing applications thoroughly, only compounds the problem. Meanwhile, CVE severity scores don't always reflect real-world exploitability, making triage more difficult and further delaying remediation.</p><h2 id="how-supply-chain-attacks-are-changing-the-threat-model">How supply chain attacks are changing the threat model</h2><p>A single compromised dependency can now create risk across multiple customer environments simultaneously and at speed. Attackers are increasingly targeting shared development tooling and open-source repositories, exploiting assumptions around shared responsibility and the belief that someone else is managing the risk.</p><p>Traditional perimeter-based security was never designed for trusted software components becoming the attack vector. Increasingly, nation-state actors and organized cybercriminal groups are targeting open-source maintainers directly, recognising that compromising a widely used dependency offers far greater scale than attacking individual endpoints.</p><p>Because these attacks are delivered through trusted, signed software components, they can bypass many traditional detection controls. In many cases, organizations receive few, if any, alerts, leaving security teams unaware until the compromise has already spread.</p><h2 id="new-expectations">New expectations</h2><p>Clients increasingly expect partners to explain software supply chain risk in business terms, marking a shift from reactive remediation to demonstrable governance. Visibility, software inventories, and continuous monitoring are quickly becoming baseline expectations rather than value-added services.</p><p>Cyber insurance underwriters are also asking for evidence of SBOM practices and software inventory controls. Partners who cannot demonstrate these capabilities risk creating challenges for clients during policy renewals, which can ultimately affect the services they are trusted to deliver. At the same time, legal and procurement teams are beginning to include software supply chain requirements in vendor contracts, meaning partners need to be prepared for increasingly detailed conversations.</p><p>For partners, this represents more than another security challenge. Clients increasingly need help understanding software supply chain risk, interpreting SBOMs, assessing third-party dependencies, and embedding these practices into procurement and governance. Those who can provide this expertise move from being technology providers to trusted advisors. </p><h2 id="the-responsibility-and-accountability-expansion">The responsibility and accountability expansion</h2><p>Software supply chain security is becoming a defining issue for partners operating across cloud and DevSecOps environments. As responsibility for managing modern development environments expands, so too does accountability when something goes wrong. To retain client trust, partners must move beyond fragmented tooling and demonstrate a clear, structured approach to managing software supply chain risk at scale.</p><p>Partners that get ahead of this have an opportunity to differentiate themselves. Rather than viewing software supply chain security as another compliance exercise, they can provide credible answers to the questions clients and their boards are already asking.</p><p>The conversation is also changing commercially. It has shifted from the value proposition of fixing vulnerabilities after the event to providing continuous assurance. For partners, that's an opportunity to deepen customer relationships while developing new security services that generate recurring revenue. </p><p>Within boardrooms, conversations are increasingly focused on who owns software supply chain risk, what impact it could have on the business, and what the financial implications might be. </p><p>Partners that cannot answer those questions risk losing credibility and, ultimately, customer relationships. Partners that can answer those questions with a proven strategy are much more likely to have stronger client adoption, expanded revenue opportunity, and longer-lasting relationships.  </p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/why-software-supply-chain-security-is-the-next-accountability-challenge-for-channel-partners</link>
                                                                            <description>
                            <![CDATA[ Partners need to be able to confidently answer key client questions relating to supply chain security going forward... ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">CExBMbRkEmJqrFm3PzvZhb</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/Hr8Z3QGRRnSdJ7oqmTW3V6-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 18 Aug 2026 16:56:40 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:55 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Amir Akhtar ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Ztwq8hts48LYRZxB6r87cW-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/Hr8Z3QGRRnSdJ7oqmTW3V6-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Digital chain link hologram on future tech background.]]></media:description>                                                            <media:text><![CDATA[Digital chain link hologram on future tech background.]]></media:text>
                                <media:title type="plain"><![CDATA[Digital chain link hologram on future tech background.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/Hr8Z3QGRRnSdJ7oqmTW3V6-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Modern applications rely heavily on open-source packages and third-party dependencies, meaning almost every application organizations run is built on layers of code written by people outside the organization. </p><p>Channel partners are often responsible for recommending, integrating and managing these environments. As a result, when a dependency is compromised, accountability increasingly lands with the partner managing the stack.</p><h2 id="why-vulnerable-and-malicious-packages-remain-in-production">Why vulnerable and malicious packages remain in production</h2><p>Unfortunately, public disclosure does not equal remediation. Organizations continue running outdated or vulnerable dependencies months after Common Vulnerabilities and Exposures (CVEs) become public, and this is increasingly becoming the norm. <a href="https://www.nist.gov/news-events/news/2026/04/nist-updates-nvd-operations-address-record-cve-growth"><u>CVE volume has grown</u></a> by 263% since 2020, with 2026 already seeing a further 33% increase. At this pace, security teams are struggling to digest the volume of vulnerabilities, let alone prioritise and implement effective remediation plans. </p><p>Many Managed Service Providers (MSPs) and consultancies also inherit environments they didn't originally architect. Combined with security frameworks that were designed around infrastructure and endpoints rather than continuously evolving software dependencies, the challenge becomes even greater. Moreover, the growing use of AI-assisted development is adding another layer of complexity, accelerating software creation while increasing the volume of third-party code and dependencies entering production. </p><p>Modern applications can contain hundreds of transitive dependencies, making it difficult to maintain an accurate inventory of what's actually running in production. Limited adoption of Software Bills of Materials (SBOMs), alongside the challenge of auditing applications thoroughly, only compounds the problem. Meanwhile, CVE severity scores don't always reflect real-world exploitability, making triage more difficult and further delaying remediation.</p><h2 id="how-supply-chain-attacks-are-changing-the-threat-model">How supply chain attacks are changing the threat model</h2><p>A single compromised dependency can now create risk across multiple customer environments simultaneously and at speed. Attackers are increasingly targeting shared development tooling and open-source repositories, exploiting assumptions around shared responsibility and the belief that someone else is managing the risk.</p><p>Traditional perimeter-based security was never designed for trusted software components becoming the attack vector. Increasingly, nation-state actors and organized cybercriminal groups are targeting open-source maintainers directly, recognising that compromising a widely used dependency offers far greater scale than attacking individual endpoints.</p><p>Because these attacks are delivered through trusted, signed software components, they can bypass many traditional detection controls. In many cases, organizations receive few, if any, alerts, leaving security teams unaware until the compromise has already spread.</p><h2 id="new-expectations">New expectations</h2><p>Clients increasingly expect partners to explain software supply chain risk in business terms, marking a shift from reactive remediation to demonstrable governance. Visibility, software inventories, and continuous monitoring are quickly becoming baseline expectations rather than value-added services.</p><p>Cyber insurance underwriters are also asking for evidence of SBOM practices and software inventory controls. Partners who cannot demonstrate these capabilities risk creating challenges for clients during policy renewals, which can ultimately affect the services they are trusted to deliver. At the same time, legal and procurement teams are beginning to include software supply chain requirements in vendor contracts, meaning partners need to be prepared for increasingly detailed conversations.</p><p>For partners, this represents more than another security challenge. Clients increasingly need help understanding software supply chain risk, interpreting SBOMs, assessing third-party dependencies, and embedding these practices into procurement and governance. Those who can provide this expertise move from being technology providers to trusted advisors. </p><h2 id="the-responsibility-and-accountability-expansion">The responsibility and accountability expansion</h2><p>Software supply chain security is becoming a defining issue for partners operating across cloud and DevSecOps environments. As responsibility for managing modern development environments expands, so too does accountability when something goes wrong. To retain client trust, partners must move beyond fragmented tooling and demonstrate a clear, structured approach to managing software supply chain risk at scale.</p><p>Partners that get ahead of this have an opportunity to differentiate themselves. Rather than viewing software supply chain security as another compliance exercise, they can provide credible answers to the questions clients and their boards are already asking.</p><p>The conversation is also changing commercially. It has shifted from the value proposition of fixing vulnerabilities after the event to providing continuous assurance. For partners, that's an opportunity to deepen customer relationships while developing new security services that generate recurring revenue. </p><p>Within boardrooms, conversations are increasingly focused on who owns software supply chain risk, what impact it could have on the business, and what the financial implications might be. </p><p>Partners that cannot answer those questions risk losing credibility and, ultimately, customer relationships. Partners that can answer those questions with a proven strategy are much more likely to have stronger client adoption, expanded revenue opportunity, and longer-lasting relationships.  </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Cyber experts issue warning over new 'memory poisoning' technique targeting AI agents ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Security experts have issued a warning over a new technique aimed at duping AI agents into producing false information. </p><p><a href="https://www.forcepoint.com/blog/x-labs/persistent-memory-poisoning-ai-agents" target="_blank">Analysis from Forcepoint</a> found a poisoned webpage or document can plant a fake vendor, support contact, or security rule into an agent's memory, with the fake data being surfaced as fact months later.</p><p>While normal <a href="https://www.itpro.com/security/ncsc-issues-urgent-warning-over-growing-ai-prompt-injection-risks-heres-what-you-need-to-know">prompt injection attacks</a> come to an end when the session finishes, Forcepoint said memory poisoning allows attackers to inject misleading or malicious memory items into an assistant's persistent memory layer. </p><p>The aim here, according to researchers, is to ensure the agent retrieves and trusts these malicious items, which could be used in future attacks or to simply harm trust.</p><p>"Persistent memory poisoning is an emerging attack class against AI assistants and agentic systems that store long-term memory items, user preferences, task history or operational context across sessions," warned Forcepoint senior security researcher Syed Hassan Faizan.</p><p>"As AI agents become increasingly capable of storing and reusing long-term memory, the memory itself becomes a new target surface."</p><p>The material concerned could include a fake domain, support contact or vendor, fake internal procedures, security rules, and approval chains, or any preference that weakens security.</p><p>These can come from a number of sources - malicious or compromised web pages, shared documents, support tickets, email footers, <a href="https://www.itpro.com/marketing-comms/business-communications/355389/slack-vs-microsoft-teams-business-messaging-apps">Slack or Teams</a> messages, PDFs with hidden text, or knowledge base articles.</p><p>"Indirect prompt injection is especially relevant here because the victim may never see the malicious instruction. The agent reads it while processing otherwise normal content," said Hassan Faizan. </p><h2 id="compromised-agents">Compromised agents</h2><p>In a proof of concept detailing the attack method, Forcepoint highlighted an example in which a travel assistant with browser capabilities was poisoned. </p><p>Although it can't access the internet directly, a separate browser tool handles that on the assistant's behalf. Thereafter the assistant remembers user preferences and trusted booking instructions across sessions. </p><p>Here, an attacker can create a webpage designed to rank for a search - something like '<em>Emergency Travel Booking Advisory</em>' that looks completely legitimate. </p><p>But when the AI agent visits it, it sees hidden additional text meant for the AI system, not a human reader. The enterprise browser tool downloads the full HTML - including the hidden text. </p><p>"Since <a href="https://www.itpro.com/technology/artificial-intelligence/generative-ai-vs-large-language-models">large language models</a> don't parse raw HTML well, a separate program extracts all the readable text, both visible and hidden, and hands the model plain text instead of markup. The model never sees the webpage itself," said Hassan Faizan. </p><p>The result is that the agent stores this text as a trusted, useful fact in its long-term memory. When asked for travel advice later, it retrieves the poisoned memory and recommends the fake provider inserted by the attacker.</p><h2 id="how-to-tackle-memory-poisoning">How to tackle memory poisoning</h2><p>Forcepoint said prevention will essentially rely on inspecting long-term memory before it's implanted into a trusted environment. </p><p>This can be done through memory risk scoring, a heuristic-based framework that assigns a risk score to each memory object based on multiple security signals. </p><p>High-risk memories can then be rejected, quarantined, flagged for user confirmation, or marked as untrusted.  </p><p>"Securing AI memory should become a fundamental part of <a href="https://www.itpro.com/technology/artificial-intelligence/six-generative-ai-cyber-security-threats-and-how-to-mitigate-them">AI security</a> architecture," said Hassan Faizan. </p><p>"Just as organizations inspect files, emails and network traffic before trusting them, AI systems must also evaluate the trustworthiness of their memory items before those memories influence decision-making."</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/trust-your-ai-agents-new-research-shows-memory-poisoning-can-dupe-them-into-remembering-fake-information-and-its-a-huge-security-risk</link>
                                                                            <description>
                            <![CDATA[ Memory poisoning allows hidden text on a webpage to be treated as fact and used to make harmful decisions ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">UV3iaEsg495eahXyXCSZqg</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/E5oTpGPpaF5BNR6kNs4Zr5-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Mon, 10 Aug 2026 11:20:20 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:50 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/E5oTpGPpaF5BNR6kNs4Zr5-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Cracked and shatter pane of glass fracturing against a black backdrop. ]]></media:description>                                                            <media:text><![CDATA[Cracked and shatter pane of glass fracturing against a black backdrop. ]]></media:text>
                                <media:title type="plain"><![CDATA[Cracked and shatter pane of glass fracturing against a black backdrop. ]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/E5oTpGPpaF5BNR6kNs4Zr5-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Security experts have issued a warning over a new technique aimed at duping AI agents into producing false information. </p><p><a href="https://www.forcepoint.com/blog/x-labs/persistent-memory-poisoning-ai-agents" target="_blank">Analysis from Forcepoint</a> found a poisoned webpage or document can plant a fake vendor, support contact, or security rule into an agent's memory, with the fake data being surfaced as fact months later.</p><p>While normal <a href="https://www.itpro.com/security/ncsc-issues-urgent-warning-over-growing-ai-prompt-injection-risks-heres-what-you-need-to-know">prompt injection attacks</a> come to an end when the session finishes, Forcepoint said memory poisoning allows attackers to inject misleading or malicious memory items into an assistant's persistent memory layer. </p><p>The aim here, according to researchers, is to ensure the agent retrieves and trusts these malicious items, which could be used in future attacks or to simply harm trust.</p><p>"Persistent memory poisoning is an emerging attack class against AI assistants and agentic systems that store long-term memory items, user preferences, task history or operational context across sessions," warned Forcepoint senior security researcher Syed Hassan Faizan.</p><p>"As AI agents become increasingly capable of storing and reusing long-term memory, the memory itself becomes a new target surface."</p><p>The material concerned could include a fake domain, support contact or vendor, fake internal procedures, security rules, and approval chains, or any preference that weakens security.</p><p>These can come from a number of sources - malicious or compromised web pages, shared documents, support tickets, email footers, <a href="https://www.itpro.com/marketing-comms/business-communications/355389/slack-vs-microsoft-teams-business-messaging-apps">Slack or Teams</a> messages, PDFs with hidden text, or knowledge base articles.</p><p>"Indirect prompt injection is especially relevant here because the victim may never see the malicious instruction. The agent reads it while processing otherwise normal content," said Hassan Faizan. </p><h2 id="compromised-agents">Compromised agents</h2><p>In a proof of concept detailing the attack method, Forcepoint highlighted an example in which a travel assistant with browser capabilities was poisoned. </p><p>Although it can't access the internet directly, a separate browser tool handles that on the assistant's behalf. Thereafter the assistant remembers user preferences and trusted booking instructions across sessions. </p><p>Here, an attacker can create a webpage designed to rank for a search - something like '<em>Emergency Travel Booking Advisory</em>' that looks completely legitimate. </p><p>But when the AI agent visits it, it sees hidden additional text meant for the AI system, not a human reader. The enterprise browser tool downloads the full HTML - including the hidden text. </p><p>"Since <a href="https://www.itpro.com/technology/artificial-intelligence/generative-ai-vs-large-language-models">large language models</a> don't parse raw HTML well, a separate program extracts all the readable text, both visible and hidden, and hands the model plain text instead of markup. The model never sees the webpage itself," said Hassan Faizan. </p><p>The result is that the agent stores this text as a trusted, useful fact in its long-term memory. When asked for travel advice later, it retrieves the poisoned memory and recommends the fake provider inserted by the attacker.</p><h2 id="how-to-tackle-memory-poisoning">How to tackle memory poisoning</h2><p>Forcepoint said prevention will essentially rely on inspecting long-term memory before it's implanted into a trusted environment. </p><p>This can be done through memory risk scoring, a heuristic-based framework that assigns a risk score to each memory object based on multiple security signals. </p><p>High-risk memories can then be rejected, quarantined, flagged for user confirmation, or marked as untrusted.  </p><p>"Securing AI memory should become a fundamental part of <a href="https://www.itpro.com/technology/artificial-intelligence/six-generative-ai-cyber-security-threats-and-how-to-mitigate-them">AI security</a> architecture," said Hassan Faizan. </p><p>"Just as organizations inspect files, emails and network traffic before trusting them, AI systems must also evaluate the trustworthiness of their memory items before those memories influence decision-making."</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Cisco launches cyber-focused small language models ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Cisco has unveiled a new range of cyber-capable <a href="https://www.itpro.com/technology/artificial-intelligence/are-small-language-models-finally-having-their-moment">small language models (SLMs)</a> aimed at supercharging security operations.</p><p>The Antares range, which comes in two forms (Antares-350M and Antares-1B) will be made available as open-weight models via Hugging Face. According to Cisco, the aim here is to provide a codebase vulnerability tool that's far cheaper than general of frontier models. </p><p>While the Antares SLMs will operate as specialized models alongside frontier and generalized models, the company promised they will run at a "fraction of the compute expense."</p><p>"Benchmark testing shows that these models outperform many powerful closed- and open-weight models in this critical security task at a fraction of the cost," said Amin Karbasi, VP and chief scientist for Cisco Foundation AI. </p><p>“And they’re compact enough to run locally, heading off the need to send sensitive codebases to the cloud.”</p><p>The move by Cisco comes amidst <a href="https://www.itpro.com/technology/artificial-intelligence/the-ai-pricing-time-bomb"><u>wider concerns about the rising costs of AI</u></a>, exacerbated by <a href="https://www.itpro.com/software/development/github-copilot-pricing-changes-usage-based-billing-explained"><u>changes to billing and pricing</u></a> that have caused bills to shoot up across the industry. </p><p>Some companies, including Accenture, have told staff to <a href="https://www.itpro.com/technology/artificial-intelligence/what-were-seeing-right-now-is-just-rapid-escalation-in-ai-token-spend-accenture-tells-staff-to-stop-using-ai-for-unnecessary-tasks-amid-surging-costs"><u>cut back on AI use</u></a> as a result of skyrocketing prices. Indeed, one report suggested <a href="https://www.itpro.com/software/development/surging-ai-costs-could-exceed-developer-salaries-by-2028-analysts-say-context-engineering-could-be-the-key-to-optimizing-token-consumption"><u>AI could cost more than developer salaries</u></a> within a few years. </p><p>At the same time, AI is making inroads into security – <a href="https://www.itpro.com/security/ai-is-getting-better-at-security-and-its-doing-it-faster-than-expected"><u>faster than some expected</u></a> – with the rise of cyber-focused models such as <a href="https://www.itpro.com/technology/artificial-intelligence/why-the-us-imposed-export-controls-on-anthropics-fable-and-mythos-models-and-why-theyve-been-lifted"><u>Anthropic's Claude Mythos</u></a>.</p><h2 id="how-cisco-s-antares-models-work">How Cisco’s Antares models work</h2><p>Antares is designed to mimic how a human investigator would work their way through a code repository – though Cisco noted the aim wasn't to replace human judgement, but to make it easier to manage the work. </p><p>The models can help with locating files that relate to a vulnerability warning, trigger investigations based on advisories, support development workflows that use vulnerable files, and more. </p><p>Cisco noted that the decision to release the Antares range as open-weight models means they’re easier to work with and improve. </p><p>"We are releasing Antares as open-weight because the security community needs more accessible building blocks for practical, repository-level defense," said Karbasi.</p><p>"Cisco's efforts are connected by a common belief: AI in security has to move beyond impressive one-off demos and toward systems that practitioners can evaluate, govern, and improve."</p><h2 id="tackling-complexity">Tackling complexity</h2><p>Cisco said that Antares was built to address two concerns when it comes to code: the complexity of checking it for vulnerabilities and the costs of using AI for that task. </p><p>First, Karbasi said that it was difficult to apply vulnerability knowledge — advisories, vulnerability alerts and severities, and so on — to a company's internal code. </p><p>"That work is difficult because repositories are large, security signals are noisy, and the relevant evidence is rarely in one obvious place," he said. </p><p>"Analysts often need to search through unfamiliar code, follow naming conventions, inspect call paths, compare candidate files, and decide whether a weakness is actually present."</p><h2 id="how-cheap-is-antares">How cheap is Antares?</h2><p>AI can help with that challenge, but the high costs of general or frontier models mean it often isn't practical, in particular for public sector organizations, universities, and smaller security teams. </p><p>"Compact models reduce inference costs, support local or on-premises operations, and help teams keep sensitive source code within their own environment," Karbasi said. </p><p>So just how cheap are the Antares models? Cisco said that running a 500-entry evaluation using Antares took 15 minutes on a single GPU at a cost of less than $1. </p><p>Cisco noted that this was 15-times cheaper than the best available open source model and a whopping 172-times cheaper than the top-end frontier model. </p><p>"The goal is to build toward a system where all security practitioners, regardless of on-prem or resource constraints, can effectively incorporate AI in everyday security operations," Karbasi added. </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/cisco-just-launched-two-cyber-focused-small-language-models-antares-350m-and-antares-1b-aim-to-supercharge-codebase-analysis-and-they-run-at-a-fraction-of-the-compute-expense-of-popular-frontier-models</link>
                                                                            <description>
                            <![CDATA[ The Antares models unveiled by Cisco aim to cut costs in codebase analysis ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">KG3F7gPysjhhdeKMdaKNAe</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/hQdRvB92xVu7oEhu5EV8Qo-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 21 Jul 2026 13:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:51 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Nicole Kobie ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/8Y8JDDTQ7XDEk49FoAFP2S-320-70.png ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Nicole Kobie first started writing for ITPro in 2007. As a freelance journalist covering technology and business, Nicole&#039;s work includes  bylines in New Scientist, Wired, PC Pro and many more. &lt;/p&gt;&lt;p&gt;Nicole the author of a book about the history of technology, The Long History of the Future.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/hQdRvB92xVu7oEhu5EV8Qo-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Cisco logo and branding illuminated in white against a black backdrop at Web Summit Qatar 2024.]]></media:description>                                                            <media:text><![CDATA[Cisco logo and branding illuminated in white against a black backdrop at Web Summit Qatar 2024.]]></media:text>
                                <media:title type="plain"><![CDATA[Cisco logo and branding illuminated in white against a black backdrop at Web Summit Qatar 2024.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/hQdRvB92xVu7oEhu5EV8Qo-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Cisco has unveiled a new range of cyber-capable <a href="https://www.itpro.com/technology/artificial-intelligence/are-small-language-models-finally-having-their-moment">small language models (SLMs)</a> aimed at supercharging security operations.</p><p>The Antares range, which comes in two forms (Antares-350M and Antares-1B) will be made available as open-weight models via Hugging Face. According to Cisco, the aim here is to provide a codebase vulnerability tool that's far cheaper than general of frontier models. </p><p>While the Antares SLMs will operate as specialized models alongside frontier and generalized models, the company promised they will run at a "fraction of the compute expense."</p><p>"Benchmark testing shows that these models outperform many powerful closed- and open-weight models in this critical security task at a fraction of the cost," said Amin Karbasi, VP and chief scientist for Cisco Foundation AI. </p><p>“And they’re compact enough to run locally, heading off the need to send sensitive codebases to the cloud.”</p><p>The move by Cisco comes amidst <a href="https://www.itpro.com/technology/artificial-intelligence/the-ai-pricing-time-bomb"><u>wider concerns about the rising costs of AI</u></a>, exacerbated by <a href="https://www.itpro.com/software/development/github-copilot-pricing-changes-usage-based-billing-explained"><u>changes to billing and pricing</u></a> that have caused bills to shoot up across the industry. </p><p>Some companies, including Accenture, have told staff to <a href="https://www.itpro.com/technology/artificial-intelligence/what-were-seeing-right-now-is-just-rapid-escalation-in-ai-token-spend-accenture-tells-staff-to-stop-using-ai-for-unnecessary-tasks-amid-surging-costs"><u>cut back on AI use</u></a> as a result of skyrocketing prices. Indeed, one report suggested <a href="https://www.itpro.com/software/development/surging-ai-costs-could-exceed-developer-salaries-by-2028-analysts-say-context-engineering-could-be-the-key-to-optimizing-token-consumption"><u>AI could cost more than developer salaries</u></a> within a few years. </p><p>At the same time, AI is making inroads into security – <a href="https://www.itpro.com/security/ai-is-getting-better-at-security-and-its-doing-it-faster-than-expected"><u>faster than some expected</u></a> – with the rise of cyber-focused models such as <a href="https://www.itpro.com/technology/artificial-intelligence/why-the-us-imposed-export-controls-on-anthropics-fable-and-mythos-models-and-why-theyve-been-lifted"><u>Anthropic's Claude Mythos</u></a>.</p><h2 id="how-cisco-s-antares-models-work">How Cisco’s Antares models work</h2><p>Antares is designed to mimic how a human investigator would work their way through a code repository – though Cisco noted the aim wasn't to replace human judgement, but to make it easier to manage the work. </p><p>The models can help with locating files that relate to a vulnerability warning, trigger investigations based on advisories, support development workflows that use vulnerable files, and more. </p><p>Cisco noted that the decision to release the Antares range as open-weight models means they’re easier to work with and improve. </p><p>"We are releasing Antares as open-weight because the security community needs more accessible building blocks for practical, repository-level defense," said Karbasi.</p><p>"Cisco's efforts are connected by a common belief: AI in security has to move beyond impressive one-off demos and toward systems that practitioners can evaluate, govern, and improve."</p><h2 id="tackling-complexity">Tackling complexity</h2><p>Cisco said that Antares was built to address two concerns when it comes to code: the complexity of checking it for vulnerabilities and the costs of using AI for that task. </p><p>First, Karbasi said that it was difficult to apply vulnerability knowledge — advisories, vulnerability alerts and severities, and so on — to a company's internal code. </p><p>"That work is difficult because repositories are large, security signals are noisy, and the relevant evidence is rarely in one obvious place," he said. </p><p>"Analysts often need to search through unfamiliar code, follow naming conventions, inspect call paths, compare candidate files, and decide whether a weakness is actually present."</p><h2 id="how-cheap-is-antares">How cheap is Antares?</h2><p>AI can help with that challenge, but the high costs of general or frontier models mean it often isn't practical, in particular for public sector organizations, universities, and smaller security teams. </p><p>"Compact models reduce inference costs, support local or on-premises operations, and help teams keep sensitive source code within their own environment," Karbasi said. </p><p>So just how cheap are the Antares models? Cisco said that running a 500-entry evaluation using Antares took 15 minutes on a single GPU at a cost of less than $1. </p><p>Cisco noted that this was 15-times cheaper than the best available open source model and a whopping 172-times cheaper than the top-end frontier model. </p><p>"The goal is to build toward a system where all security practitioners, regardless of on-prem or resource constraints, can effectively incorporate AI in everyday security operations," Karbasi added. </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ The agents you use to beef up cybersecurity could be turned against you ]]></title>
                                                                                                <dc:content><![CDATA[ <p>A proof-of-concept by the AI Now Institute demonstrates remote code execution in Anthropic's Claude Code and OpenAI's Codex when they're running in an autonomous mode that approves their own commands.</p><p>The <a href="https://ainowinstitute.org/publications/friendly-fire-exploit-brief"><u>Friendly Fire attack</u></a> works against an out-of-the-box configuration of Claude Code in 'auto-mode' or Codex in 'auto-review', with researchers testing Claude Sonnet 4.6, Sonnet 5, and Opus 4.8 along with GPT-5.5.</p><p>It leverages prompt injections disseminated across a library’s source code that target AI-enabled cyber defense – without the need for hooks, skills, plugins, MCP servers, or configuration files as an injection vector.</p><p>Researchers noted the study highlights the potential risks associated with rapid adoption of AI-powered security tools. </p><p>Many organizations are doing so without “consideration of the substantial and unmitigated risks associated” with the technology. </p><p>AI-related cybersecurity concerns have been rising following the launch of powerful new models such as <a href="https://www.itpro.com/technology/artificial-intelligence/project-glasswing-anthropic-announces-big-tech-consortium-to-test-claude-mythos-ai-model-that-could-reshape-cybersecurity">Claude Mythos</a>. Anthropic rolled the model out as part of a gated release to prevent misuse, and US authorities <a href="https://www.itpro.com/technology/artificial-intelligence/why-the-us-imposed-export-controls-on-anthropics-fable-and-mythos-models-and-why-theyve-been-lifted">temporarily imposed export controls</a> amidst similar concerns. </p><h2 id="how-the-friendly-fire-attack-works">How the Friendly Fire attack works</h2><p>The attack works by inserting prompt injections into documentation files and adding README files that appear to be part of routine security tooling in an open source library. </p><p>Researchers used geopy, a popular Python used for searching for geographic coordinates, but said it could work with almost any project. </p><p>When a user asks Claude Code or Codex to perform a security assessment of the repository using the default auto-mode or auto-review automated modes, the agent can be persuaded to execute a malicious binary without any warning and without requesting any further user approval. </p><p>The proof of concept is causing alarm amongst security professionals. Roey Eliyahu, CEO and co-founder of Salt Security, said this marks the latest in a string of potential risks in recent months due to manipulation of agents. </p><p>“Friendly Fire, GitLost, Agentjacking, TrustFall. Four documented attacks in the past two months, different techniques, same underlying condition,” he said.  </p><p>“Untrusted text reaches an agent that can run commands. The agent cannot reliably tell the difference between the code it is reviewing and the instructions it is being given. And the attacker's payload executes on the host.”</p><p>Eliyahu emphasized that this is not a “model problem that can be patched”. All four models were vulnerable to the same techniques and payload, without any modifications for each. </p><p>“When the same attack works unchanged across two vendors and four model generations, you are not looking at a software bug. You are looking at a structural property of how these agents work."</p><p>But, said Eljan Mahammadli, head of AI provenance at Polygraf AI, this shouldn't rule out the use of AI for defensive security work.</p><p><em>ITPro </em>approached Anthropic and OpenAI for comment, but did not receive a response by time of publication. </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/the-agents-you-use-to-beef-up-cybersecurity-could-be-turned-against-you-friendly-fire-attacks-can-manipulate-openai-and-anthropic-models-into-running-malicious-code</link>
                                                                            <description>
                            <![CDATA[ Research shows agents can be fooled into executing malicious code while performing security reviews of third-party software ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">FRjVnVPEVarRpVdMovEzam</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/44ktQKgRvmq93jKSBo3pnB-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 10 Jul 2026 10:45:51 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:50 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/44ktQKgRvmq93jKSBo3pnB-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[AI agent concept image showing a digitized human face disintegrating into hundreds of small individual blocks.]]></media:description>                                                            <media:text><![CDATA[AI agent concept image showing a digitized human face disintegrating into hundreds of small individual blocks.]]></media:text>
                                <media:title type="plain"><![CDATA[AI agent concept image showing a digitized human face disintegrating into hundreds of small individual blocks.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/44ktQKgRvmq93jKSBo3pnB-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>A proof-of-concept by the AI Now Institute demonstrates remote code execution in Anthropic's Claude Code and OpenAI's Codex when they're running in an autonomous mode that approves their own commands.</p><p>The <a href="https://ainowinstitute.org/publications/friendly-fire-exploit-brief"><u>Friendly Fire attack</u></a> works against an out-of-the-box configuration of Claude Code in 'auto-mode' or Codex in 'auto-review', with researchers testing Claude Sonnet 4.6, Sonnet 5, and Opus 4.8 along with GPT-5.5.</p><p>It leverages prompt injections disseminated across a library’s source code that target AI-enabled cyber defense – without the need for hooks, skills, plugins, MCP servers, or configuration files as an injection vector.</p><p>Researchers noted the study highlights the potential risks associated with rapid adoption of AI-powered security tools. </p><p>Many organizations are doing so without “consideration of the substantial and unmitigated risks associated” with the technology. </p><p>AI-related cybersecurity concerns have been rising following the launch of powerful new models such as <a href="https://www.itpro.com/technology/artificial-intelligence/project-glasswing-anthropic-announces-big-tech-consortium-to-test-claude-mythos-ai-model-that-could-reshape-cybersecurity">Claude Mythos</a>. Anthropic rolled the model out as part of a gated release to prevent misuse, and US authorities <a href="https://www.itpro.com/technology/artificial-intelligence/why-the-us-imposed-export-controls-on-anthropics-fable-and-mythos-models-and-why-theyve-been-lifted">temporarily imposed export controls</a> amidst similar concerns. </p><h2 id="how-the-friendly-fire-attack-works">How the Friendly Fire attack works</h2><p>The attack works by inserting prompt injections into documentation files and adding README files that appear to be part of routine security tooling in an open source library. </p><p>Researchers used geopy, a popular Python used for searching for geographic coordinates, but said it could work with almost any project. </p><p>When a user asks Claude Code or Codex to perform a security assessment of the repository using the default auto-mode or auto-review automated modes, the agent can be persuaded to execute a malicious binary without any warning and without requesting any further user approval. </p><p>The proof of concept is causing alarm amongst security professionals. Roey Eliyahu, CEO and co-founder of Salt Security, said this marks the latest in a string of potential risks in recent months due to manipulation of agents. </p><p>“Friendly Fire, GitLost, Agentjacking, TrustFall. Four documented attacks in the past two months, different techniques, same underlying condition,” he said.  </p><p>“Untrusted text reaches an agent that can run commands. The agent cannot reliably tell the difference between the code it is reviewing and the instructions it is being given. And the attacker's payload executes on the host.”</p><p>Eliyahu emphasized that this is not a “model problem that can be patched”. All four models were vulnerable to the same techniques and payload, without any modifications for each. </p><p>“When the same attack works unchanged across two vendors and four model generations, you are not looking at a software bug. You are looking at a structural property of how these agents work."</p><p>But, said Eljan Mahammadli, head of AI provenance at Polygraf AI, this shouldn't rule out the use of AI for defensive security work.</p><p><em>ITPro </em>approached Anthropic and OpenAI for comment, but did not receive a response by time of publication. </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Enterprises are shipping so much AI-generated code they can't control or secure it ]]></title>
                                                                                                <dc:content><![CDATA[ <p>AI code generation is running out of control, with eight-in-ten organizations adopting <a href="https://www.itpro.com/technology/artificial-intelligence/amazing-ai-tools-to-try-today">AI tools</a> faster than they can develop policies to govern them, new research has warned. </p><p>According to GitLab's <a href="https://about.gitlab.com/resources/ai-accountability-survey-2026/" target="_blank"><u><em>AI Accountability Report</em></u></a>, 92% are facing governance challenges with AI-generated code as rapid adoption continues.</p><p>More than nine-in-ten have two or more AI coding tools in active use, the study found, while 54% have three or more. Meanwhile, 78% report that developers are writing and committing code faster since adopting AI tools. </p><p>Teams are generally happy with the results, with six-in-ten saying that the ROI of AI coding is better than they'd expected. More than three quarters (78%) also report faster code output and 73% said overall code quality has improved.</p><p>However, while 79% agree that individual developer productivity has improved with AI, the overall software delivery process has not accelerated at the same pace. </p><p>Indeed, 82% say that <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated code risks</a> creating a new form of <a href="https://www.itpro.com/business/digital-transformation/paying-down-technical-problem-for-businesses">technical debt</a> that organizations aren't prepared to manage.</p><p>"AI coding tools have delivered on their promise of speed," said Manav Khurana, chief product and marketing officer at GitLab. </p><p>"But the events of the past few months, including supply chain attacks, reliability issues, and regulators tightening expectations around AI traceability and provenance are making clear that speed without control is a liability, not an advantage." </p><h2 id="ai-coding-is-creating-new-bottlenecks">AI coding is creating new bottlenecks</h2><p>Notably, 85% agree that AI has shifted the bottleneck from writing code to reviewing and validating it, and 84% that the biggest challenge with AI-generated code is governing what happens to it after it's created. </p><p>Nearly-three quarters are concerned about the maintainability of AI-generated code in their organization's codebase.</p><p>GitLab also raised concerns about a prevailing trend of overconfidence when it comes to AI coding. The majority (87%) said they’re confident that teams could determine within 24 hours whether <a href="https://www.itpro.com/software/development/software-developers-not-checking-ai-generated-code-verification-debt">AI-generated code</a> contributed to a production incident, for example. </p><p>Yet more than one-third (34%) of organisations fail to spot potential issues before an incident took place. </p><p>This appears to be down to difficulty distinguishing AI-generated from human-written code (43%), fragmented toolchains (40%), and systems that don't track code origin (39%). </p><p>Only 28% say their <a href="https://www.itpro.com/software/development/ai-isnt-killing-devops-youre-just-using-it-wrong">software development lifecycle (SDLC)</a> tools are fully integrated with shared data and workflows.</p><h2 id="new-governance-practices-are-needed">New governance practices are needed</h2><p>According to GitLab, what’s missing is clarity around governance. The majority (83%) of organizations identify AI-generated code accumulation as a risk to manage now, with 44% calling it a top technology risk. </p><p>On the upside, 91% of survey respondents said they are likely to invest in <a href="https://www.itpro.com/technology/artificial-intelligence/practical-ai-the-age-of-agentic-ai">AI code governance</a> tools in the next 12 months, and 98% have already allocated or expect to allocate budget toward these efforts. </p><p>Crucially, 85% agree the next phase of AI in software will focus less on generating code and more on governing it.</p><p>"The teams thinking ahead are already asking the harder question: can we actually control all the code we’re generating?" said Khurana.</p><p>"The organizations that will ship trusted software faster are the ones building the foundations of accountability with context, traceability, and governance baked into the platform, not just bolted on after the fact."</p><p>AI governance has been a persistent challenge for developers, with <a href="https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually">research</a> from Aikido last year concluding that AI-generated code is now the cause of one-in-five breaches. </p><p>The study noted that 69% of security leaders, engineers, and developers had identified serious vulnerabilities in AI-generated code.</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/enterprises-are-shipping-so-much-ai-generated-code-they-cant-control-or-secure-it</link>
                                                                            <description>
                            <![CDATA[ As AI coding becomes commonplace, organizations are struggling to control what they are shipping ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">n8fz9uxu3VxRDdJ8239CHh</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/Xwb2jn8QiHUXXoPpjugL8K-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 24 Jun 2026 14:08:32 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:52 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/Xwb2jn8QiHUXXoPpjugL8K-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[AI coding concept image showing female software developer wearing headphones while working on a desktop computer in an open plan office space. ]]></media:description>                                                            <media:text><![CDATA[AI coding concept image showing female software developer wearing headphones while working on a desktop computer in an open plan office space. ]]></media:text>
                                <media:title type="plain"><![CDATA[AI coding concept image showing female software developer wearing headphones while working on a desktop computer in an open plan office space. ]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/Xwb2jn8QiHUXXoPpjugL8K-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>AI code generation is running out of control, with eight-in-ten organizations adopting <a href="https://www.itpro.com/technology/artificial-intelligence/amazing-ai-tools-to-try-today">AI tools</a> faster than they can develop policies to govern them, new research has warned. </p><p>According to GitLab's <a href="https://about.gitlab.com/resources/ai-accountability-survey-2026/" target="_blank"><u><em>AI Accountability Report</em></u></a>, 92% are facing governance challenges with AI-generated code as rapid adoption continues.</p><p>More than nine-in-ten have two or more AI coding tools in active use, the study found, while 54% have three or more. Meanwhile, 78% report that developers are writing and committing code faster since adopting AI tools. </p><p>Teams are generally happy with the results, with six-in-ten saying that the ROI of AI coding is better than they'd expected. More than three quarters (78%) also report faster code output and 73% said overall code quality has improved.</p><p>However, while 79% agree that individual developer productivity has improved with AI, the overall software delivery process has not accelerated at the same pace. </p><p>Indeed, 82% say that <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated code risks</a> creating a new form of <a href="https://www.itpro.com/business/digital-transformation/paying-down-technical-problem-for-businesses">technical debt</a> that organizations aren't prepared to manage.</p><p>"AI coding tools have delivered on their promise of speed," said Manav Khurana, chief product and marketing officer at GitLab. </p><p>"But the events of the past few months, including supply chain attacks, reliability issues, and regulators tightening expectations around AI traceability and provenance are making clear that speed without control is a liability, not an advantage." </p><h2 id="ai-coding-is-creating-new-bottlenecks">AI coding is creating new bottlenecks</h2><p>Notably, 85% agree that AI has shifted the bottleneck from writing code to reviewing and validating it, and 84% that the biggest challenge with AI-generated code is governing what happens to it after it's created. </p><p>Nearly-three quarters are concerned about the maintainability of AI-generated code in their organization's codebase.</p><p>GitLab also raised concerns about a prevailing trend of overconfidence when it comes to AI coding. The majority (87%) said they’re confident that teams could determine within 24 hours whether <a href="https://www.itpro.com/software/development/software-developers-not-checking-ai-generated-code-verification-debt">AI-generated code</a> contributed to a production incident, for example. </p><p>Yet more than one-third (34%) of organisations fail to spot potential issues before an incident took place. </p><p>This appears to be down to difficulty distinguishing AI-generated from human-written code (43%), fragmented toolchains (40%), and systems that don't track code origin (39%). </p><p>Only 28% say their <a href="https://www.itpro.com/software/development/ai-isnt-killing-devops-youre-just-using-it-wrong">software development lifecycle (SDLC)</a> tools are fully integrated with shared data and workflows.</p><h2 id="new-governance-practices-are-needed">New governance practices are needed</h2><p>According to GitLab, what’s missing is clarity around governance. The majority (83%) of organizations identify AI-generated code accumulation as a risk to manage now, with 44% calling it a top technology risk. </p><p>On the upside, 91% of survey respondents said they are likely to invest in <a href="https://www.itpro.com/technology/artificial-intelligence/practical-ai-the-age-of-agentic-ai">AI code governance</a> tools in the next 12 months, and 98% have already allocated or expect to allocate budget toward these efforts. </p><p>Crucially, 85% agree the next phase of AI in software will focus less on generating code and more on governing it.</p><p>"The teams thinking ahead are already asking the harder question: can we actually control all the code we’re generating?" said Khurana.</p><p>"The organizations that will ship trusted software faster are the ones building the foundations of accountability with context, traceability, and governance baked into the platform, not just bolted on after the fact."</p><p>AI governance has been a persistent challenge for developers, with <a href="https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually">research</a> from Aikido last year concluding that AI-generated code is now the cause of one-in-five breaches. </p><p>The study noted that 69% of security leaders, engineers, and developers had identified serious vulnerabilities in AI-generated code.</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ MSPs grow wary over supply chain security threats ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Supply chain cyber risk is now a top concern for <a href="https://www.itpro.com/business/why-you-cant-rely-on-traditional-managed-service-providers">managed service providers (MSPs)</a> and their customers, according to new research from CyberSmart.</p><p>The cyber risk management provider’s <em>2026 MSP Survey</em> found that 43% of MSPs and their customers experienced a cyber incident caused by or originating from a supplier or third-party vendor during the last 12 months.</p><p>Conducted by OnePoll, the research gathered responses from 350 MSP leaders across the UK and Ireland spanning a range of industries and customer sizes.</p><p>The results suggest that MSPs are becoming increasingly exposed to supply chain risk due to their privileged access to customer environments – making them attractive targets for cyber criminals seeking to use them as a gateway to potentially hundreds of organizations.</p><p>Among the respondents that experienced a supply chain incident, 39% said the breach affected only the customer, while 16% said it only affected the MSP. Meanwhile, 39% said both were impacted.</p><p>According to CyberSmart, this means over half (55%) of incidents involved the MSP in some capacity.</p><p>Despite this figure, the research found that 55% of MSPs still do not monitor for supply chain risk – while over a third (37%) only assess risk quarterly and 11% do so annually.</p><p>In terms of challenges, MSPs cited managing and enforcing security requirements in contracts (39%), <a href="https://www.itpro.com/business/business-strategy/95-percent-of-organizations-dont-fully-trust-their-cybersecurity-vendors-heres-why">third-party risk assessment</a> and monitoring (37%), and the cost of securing and monitoring supply chains (36%) as the biggest hurdles.</p><p>“<a href="https://www.itpro.com/security/why-is-supply-chain-resilience-under-the-spotlight">Supply chain risk</a> has become a central concern for MSPs and SMEs as cybercriminals increasingly target interconnected business ecosystems,” commented CyberSmart CEO and co-founder Jamie Akhtar. </p><p>“MSPs sit at the centre of these environments, which means a single weak link can have far-reaching consequences for customers, suppliers and partners.” </p><h2 id="growing-regulatory-pressure">Growing regulatory pressure</h2><p>Elsewhere, the report also explored MSP preparedness ahead of the UK’s Cyber Security and Resilience Bill (CSRB), which was introduced back in November 2025 and brings providers into the scope of formal regulation for the first time.</p><p>The CSRB includes mandatory security requirements, stricter incident reporting, and greater accountability as MSPs become increasingly critical components of national cyber resilience.</p><p>According to the findings, 96% of respondents said they felt prepared for the legislation to a certain extent, while 45% described themselves as fully prepared.</p><h2 id="addressing-key-csrb-concerns">Addressing key CSRB concerns</h2><p>However, MSPs pointed to operational and organizational concerns rather than technology and software limitations as the biggest barrier to readiness. </p><p>Instead, they cited skills (41%), clearer customer expectations (41%), stronger support for managing third-party risk (41%), as well as better-defined roles and liability (39%) as key requirements going forward.</p><p>Increased liability and legal exposure emerged as the biggest concern linked to the new legislation, noted by 42% of the survey’s participants, with MSP leaders expressing concern over undefined accountability and how risk will be operationalized in practice.</p><h2 id="improving-accountability-and-resilience">Improving accountability and resilience</h2><p>Despite these concerns, 77% said they believe CSRB goes far enough in helping to protect supply chain organizations – including MSPs themselves – from cyber risk.</p><p>When it comes to what can be done to improve protection for MSPs, participants highlighted clearer guidance and best practice standards (54%), stronger protections around shared liability (52%), and clearer regulatory frameworks specifically for MSPs (51%) as the top three potential improvements.</p><p>“What our research shows is that the industry understands the need for greater accountability and resilience, but MSPs also need clearer guidance, shared responsibility and continuous risk visibility to make that possible in practice,” Akhtar added.</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/msps-grow-wary-over-supply-chain-security-threats</link>
                                                                            <description>
                            <![CDATA[ CyberSmart’s 2026 MSP Survey found that more than two-in-five firms experienced a cyber incident linked to a supplier or third-party vendor over the past year ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">ZAXG94rRPNn48B6Dh8i58a</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/Gmv6VGAN4vkgH2urwaX2Yf-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 12 Jun 2026 08:29:56 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:55 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                <author><![CDATA[ itpro@futurenet.com (Daniel Todd) ]]></author>                    <dc:creator><![CDATA[ Daniel Todd ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/SRyC34qeLpNDj3dJtsVDhT-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/Gmv6VGAN4vkgH2urwaX2Yf-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Cybersecurity concept image symbolizing third-party data breaches with give padlock symbols and one pictured in red, signifying a security breach.]]></media:description>                                                            <media:text><![CDATA[Cybersecurity concept image symbolizing third-party data breaches with give padlock symbols and one pictured in red, signifying a security breach.]]></media:text>
                                <media:title type="plain"><![CDATA[Cybersecurity concept image symbolizing third-party data breaches with give padlock symbols and one pictured in red, signifying a security breach.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/Gmv6VGAN4vkgH2urwaX2Yf-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Supply chain cyber risk is now a top concern for <a href="https://www.itpro.com/business/why-you-cant-rely-on-traditional-managed-service-providers">managed service providers (MSPs)</a> and their customers, according to new research from CyberSmart.</p><p>The cyber risk management provider’s <em>2026 MSP Survey</em> found that 43% of MSPs and their customers experienced a cyber incident caused by or originating from a supplier or third-party vendor during the last 12 months.</p><p>Conducted by OnePoll, the research gathered responses from 350 MSP leaders across the UK and Ireland spanning a range of industries and customer sizes.</p><p>The results suggest that MSPs are becoming increasingly exposed to supply chain risk due to their privileged access to customer environments – making them attractive targets for cyber criminals seeking to use them as a gateway to potentially hundreds of organizations.</p><p>Among the respondents that experienced a supply chain incident, 39% said the breach affected only the customer, while 16% said it only affected the MSP. Meanwhile, 39% said both were impacted.</p><p>According to CyberSmart, this means over half (55%) of incidents involved the MSP in some capacity.</p><p>Despite this figure, the research found that 55% of MSPs still do not monitor for supply chain risk – while over a third (37%) only assess risk quarterly and 11% do so annually.</p><p>In terms of challenges, MSPs cited managing and enforcing security requirements in contracts (39%), <a href="https://www.itpro.com/business/business-strategy/95-percent-of-organizations-dont-fully-trust-their-cybersecurity-vendors-heres-why">third-party risk assessment</a> and monitoring (37%), and the cost of securing and monitoring supply chains (36%) as the biggest hurdles.</p><p>“<a href="https://www.itpro.com/security/why-is-supply-chain-resilience-under-the-spotlight">Supply chain risk</a> has become a central concern for MSPs and SMEs as cybercriminals increasingly target interconnected business ecosystems,” commented CyberSmart CEO and co-founder Jamie Akhtar. </p><p>“MSPs sit at the centre of these environments, which means a single weak link can have far-reaching consequences for customers, suppliers and partners.” </p><h2 id="growing-regulatory-pressure">Growing regulatory pressure</h2><p>Elsewhere, the report also explored MSP preparedness ahead of the UK’s Cyber Security and Resilience Bill (CSRB), which was introduced back in November 2025 and brings providers into the scope of formal regulation for the first time.</p><p>The CSRB includes mandatory security requirements, stricter incident reporting, and greater accountability as MSPs become increasingly critical components of national cyber resilience.</p><p>According to the findings, 96% of respondents said they felt prepared for the legislation to a certain extent, while 45% described themselves as fully prepared.</p><h2 id="addressing-key-csrb-concerns">Addressing key CSRB concerns</h2><p>However, MSPs pointed to operational and organizational concerns rather than technology and software limitations as the biggest barrier to readiness. </p><p>Instead, they cited skills (41%), clearer customer expectations (41%), stronger support for managing third-party risk (41%), as well as better-defined roles and liability (39%) as key requirements going forward.</p><p>Increased liability and legal exposure emerged as the biggest concern linked to the new legislation, noted by 42% of the survey’s participants, with MSP leaders expressing concern over undefined accountability and how risk will be operationalized in practice.</p><h2 id="improving-accountability-and-resilience">Improving accountability and resilience</h2><p>Despite these concerns, 77% said they believe CSRB goes far enough in helping to protect supply chain organizations – including MSPs themselves – from cyber risk.</p><p>When it comes to what can be done to improve protection for MSPs, participants highlighted clearer guidance and best practice standards (54%), stronger protections around shared liability (52%), and clearer regulatory frameworks specifically for MSPs (51%) as the top three potential improvements.</p><p>“What our research shows is that the industry understands the need for greater accountability and resilience, but MSPs also need clearer guidance, shared responsibility and continuous risk visibility to make that possible in practice,” Akhtar added.</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ NCSC urges organizations to shore up supply chain security practices ]]></title>
                                                                                                <dc:content><![CDATA[ <p>The <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do">National Cyber Security Centre (NCSC)</a> has urged organizations to review their dependencies in light of an increasing number of supply chain attacks.</p><p>Recent attacks, the agency noted, have included <a href="https://www.itpro.com/security/cyber-attacks/the-build-pipeline-is-becoming-the-new-frontline-axios-npm-compromise-highlights-growing-software-supply-chain-risks-experts-warn">maintainer account compromise</a>, where attackers steal credentials or tokens that allow a malicious actor to update a trusted package. </p><p>Attackers are also taking over ownership of expired domains connected to package maintainers, or otherwise transferring ownership of a previously legitimate package.</p><p>Meanwhile, typosquatting is on the rise, with packages published using similar names to the genuine article, or with the misspelling of popular legitimate packages in the hope they are installed by mistake. </p><p>Threat actors are also using credentials or tokens stolen from a previous attack to access or modify additional packages.</p><p>These risks arise because one single application may rely on a large number of third-party packages – including libraries, frameworks, snippets, <a href="https://www.itpro.com/technology/artificial-intelligence/openai-agentic-ai-development-tools">software development kits</a> - some of which may not be entirely trustworthy. </p><p>Node.js, Rust and Python, for example, are unusually exposed as they have minimal standard libraries, boosting the use of third-party dependencies and delegation of basic functionalities, and leading to a heavy reliance on external registries. </p><p>Many of these components are retrieved automatically through <a href="https://www.itpro.com/business/digital-transformation/cicd-comes-into-focus-as-enterprises-ramp-up-application-modernization-efforts">continuous integration and continuous delivery (CI/CD)</a> pipelines, often without human intervention. </p><p>"It is this combination of automation, trust and scale which means that malicious code introduced into a single package can spread rapidly across many organisations and services before detection," the NCSC warned.</p><p>The NCSC warned that threat groups are actively targeting developer environments, which are usually less tightly controlled than managed corporate devices, making it easier to compromise and steal the credentials of shared code or package registries. </p><p>A single malicious package can spread quickly across downstream software products and services. Indeed, the impact of compromising a lesser known, but critical, software component can have a significant and far-reaching impact for many organizations and systems. </p><p>The NCSC highlighted Node.js in particular, as its highly modular packages depend on many smaller components.</p><h2 id="ci-cd-threats-are-rising">CI/CD threats are rising</h2><p>Meanwhile, recent attacks have exploited the implicit trust in CI/CD and automation pipelines, where the automation of updates, installation, and execution of scripts and packages allows attackers to execute malicious code. </p><p>"For example, Node.js and Python support scripts that execute on installation, and allow a malicious package to be run immediately. Without human intervention or approval, the code can simply propagate," the NCSC warned.</p><p>Open publishing models increase exposure, with security controls for maintainer registry accounts not currently enforced by all registry providers.</p><h2 id="check-your-dependencies">Check your dependencies</h2><p>The NCSC outlined a series of actions organizations are advised to take, including:</p><ul><li>Pause automatic dependency updates where compromise may be present</li><li>Review and approve new updates, dependencies, or versions manually</li><li>Rotate exposed or potentially exposed credentials</li><li>Enforce MFA for developer and package registry accounts</li><li>Use private or trusted registries where appropriate</li></ul><p>"These attacks highlight the need to revisit how dependencies are introduced and managed, as part of a secure development lifecycle (SDLC)," the NCSC said. </p><p>"Whilst Node.js, Python and Rust are considered higher risk for these attacks, it’s important to be aware that other languages, tools, and package repositories are also at risk."</p><p>Developers should also make use of the Software Security Code of Practice, reviewing how dependencies are introduced and updated, avoiding automatically adopting new dependency versions without review, and striking a balance between deploying patches quickly and updating dependencies slowly. </p><p>This will help minimize the potential impact of compromise, according to the NCSC.</p><p>Elsewhere, they should also ensure deployments occur through controlled CI/CD pipelines rather than developer devices and store sensitive credentials securely, avoiding exposure on developer workstations.</p><p>"Modern software development has transformed how software is created, shared and reused – but recent attacks on these tools highlight the rapidly growing risks of using modern software ecosystems," the NCSC said.</p><p>"Whilst Node.js, Python and Rust are considered higher risk for these attacks, it’s important to be aware that other languages, tools, and package repositories are also at risk."</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/ncsc-urges-organizations-to-shore-up-supply-chain-security-practices</link>
                                                                            <description>
                            <![CDATA[ With attackers increasingly compromising open source packages to spread malware, organizations need to be on their guard ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">4yLzX53j8ACVTzWTEUk9LP</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/upmScpMzZKB4C5Wt2y3h7N-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 05 Jun 2026 11:27:36 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:16 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/upmScpMzZKB4C5Wt2y3h7N-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Logo of the UK&#039;s National Cyber Security Centre (NCSC) pictured on a television screen in London, England. ]]></media:description>                                                            <media:text><![CDATA[Logo of the UK&#039;s National Cyber Security Centre (NCSC) pictured on a television screen in London, England. ]]></media:text>
                                <media:title type="plain"><![CDATA[Logo of the UK&#039;s National Cyber Security Centre (NCSC) pictured on a television screen in London, England. ]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/upmScpMzZKB4C5Wt2y3h7N-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do">National Cyber Security Centre (NCSC)</a> has urged organizations to review their dependencies in light of an increasing number of supply chain attacks.</p><p>Recent attacks, the agency noted, have included <a href="https://www.itpro.com/security/cyber-attacks/the-build-pipeline-is-becoming-the-new-frontline-axios-npm-compromise-highlights-growing-software-supply-chain-risks-experts-warn">maintainer account compromise</a>, where attackers steal credentials or tokens that allow a malicious actor to update a trusted package. </p><p>Attackers are also taking over ownership of expired domains connected to package maintainers, or otherwise transferring ownership of a previously legitimate package.</p><p>Meanwhile, typosquatting is on the rise, with packages published using similar names to the genuine article, or with the misspelling of popular legitimate packages in the hope they are installed by mistake. </p><p>Threat actors are also using credentials or tokens stolen from a previous attack to access or modify additional packages.</p><p>These risks arise because one single application may rely on a large number of third-party packages – including libraries, frameworks, snippets, <a href="https://www.itpro.com/technology/artificial-intelligence/openai-agentic-ai-development-tools">software development kits</a> - some of which may not be entirely trustworthy. </p><p>Node.js, Rust and Python, for example, are unusually exposed as they have minimal standard libraries, boosting the use of third-party dependencies and delegation of basic functionalities, and leading to a heavy reliance on external registries. </p><p>Many of these components are retrieved automatically through <a href="https://www.itpro.com/business/digital-transformation/cicd-comes-into-focus-as-enterprises-ramp-up-application-modernization-efforts">continuous integration and continuous delivery (CI/CD)</a> pipelines, often without human intervention. </p><p>"It is this combination of automation, trust and scale which means that malicious code introduced into a single package can spread rapidly across many organisations and services before detection," the NCSC warned.</p><p>The NCSC warned that threat groups are actively targeting developer environments, which are usually less tightly controlled than managed corporate devices, making it easier to compromise and steal the credentials of shared code or package registries. </p><p>A single malicious package can spread quickly across downstream software products and services. Indeed, the impact of compromising a lesser known, but critical, software component can have a significant and far-reaching impact for many organizations and systems. </p><p>The NCSC highlighted Node.js in particular, as its highly modular packages depend on many smaller components.</p><h2 id="ci-cd-threats-are-rising">CI/CD threats are rising</h2><p>Meanwhile, recent attacks have exploited the implicit trust in CI/CD and automation pipelines, where the automation of updates, installation, and execution of scripts and packages allows attackers to execute malicious code. </p><p>"For example, Node.js and Python support scripts that execute on installation, and allow a malicious package to be run immediately. Without human intervention or approval, the code can simply propagate," the NCSC warned.</p><p>Open publishing models increase exposure, with security controls for maintainer registry accounts not currently enforced by all registry providers.</p><h2 id="check-your-dependencies">Check your dependencies</h2><p>The NCSC outlined a series of actions organizations are advised to take, including:</p><ul><li>Pause automatic dependency updates where compromise may be present</li><li>Review and approve new updates, dependencies, or versions manually</li><li>Rotate exposed or potentially exposed credentials</li><li>Enforce MFA for developer and package registry accounts</li><li>Use private or trusted registries where appropriate</li></ul><p>"These attacks highlight the need to revisit how dependencies are introduced and managed, as part of a secure development lifecycle (SDLC)," the NCSC said. </p><p>"Whilst Node.js, Python and Rust are considered higher risk for these attacks, it’s important to be aware that other languages, tools, and package repositories are also at risk."</p><p>Developers should also make use of the Software Security Code of Practice, reviewing how dependencies are introduced and updated, avoiding automatically adopting new dependency versions without review, and striking a balance between deploying patches quickly and updating dependencies slowly. </p><p>This will help minimize the potential impact of compromise, according to the NCSC.</p><p>Elsewhere, they should also ensure deployments occur through controlled CI/CD pipelines rather than developer devices and store sensitive credentials securely, avoiding exposure on developer workstations.</p><p>"Modern software development has transformed how software is created, shared and reused – but recent attacks on these tools highlight the rapidly growing risks of using modern software ecosystems," the NCSC said.</p><p>"Whilst Node.js, Python and Rust are considered higher risk for these attacks, it’s important to be aware that other languages, tools, and package repositories are also at risk."</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ IBM and Red Hat believe they have the answer to open source security risks ]]></title>
                                                                                                <dc:content><![CDATA[ <p>IBM and its subsidiary Red Hat are pumping $5 billion into improving the security of open-source projects.</p><p><a href="https://www.ibm.com/products/lightwell">Project Lightwell</a> is designed as an enterprise clearinghouse for open source software, with a new AI-driven model for securing the software supply chain.</p><p>The idea is to use advanced AI capabilities, offered through commercial subscriptions, to validate and test fixes across a huge volume of open source code. Enterprises will be able to integrate secure patches directly into their existing software supply chains, say the firms, with enterprise-grade validation and lifecycle management.</p><p>They can report and resolve vulnerabilities, receive patches optimized for production environments, spanning both Red Hat offerings and independent community code, and share fixes upstream so that open source communities can include them in long-term maintenance.</p><p>And all this will be backed by a team of more than 20,000 engineers working across upstream and enterprise environments. The focus will be on upstream maintenance alongside open source community leaders; high-volume, AI-assisted vulnerability review, triage, and prioritization; and secure patch development, dependency hardening, and release engineering.</p><p>"Open source is the backbone of today's digital economy and the foundation of modern AI, and we are at an inflection point in how it is built, secured, and scaled," said Arvind Krishna, chairman and CEO of IBM. </p><p>"With Project Lightwell, IBM and Red Hat are helping define a new industry model, one that brings together AI, engineering expertise, and trusted collaboration, to secure open source software at its source and across the entire supply chain. This is about strengthening trust in the systems that power business, government, and society."</p><p>IBM and Red Hat are already working with a group of early adopters on Project Lightwell, including Bank of America, BNY, Citi, Goldman Sachs, JPMorganChase, Mastercard, Morgan Stanley, Royal Bank of Canada, State Street, Visa, and Wells Fargo. </p><p>"The real-world insights from these initial deployments will actively shape how vulnerabilities are identified, validated, and remediated at scale across complex software supply chains," the firms said.</p><p>More than nine-in-ten Fortune 500 companies rely on open source software - but security is an ever-present problem. Sonatype <a href="https://www.itpro.com/software/open-source/the-open-source-ecosystem-is-booming-thanks-to-ai-but-hackers-are-taking-advantage">identified</a> 454,648 malicious open source packages in 2025, up 67% on the previous year, with one state-linked group alone tied to more than 800 malicious packages.</p><p>Meanwhile, <a href="https://www.itpro.com/software/open-source/86-percent-of-enterprise-codebases-contain-open-source-vulnerabilities">according to Black Duck</a>, 86% of codebases contain <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> vulnerabilities, with 81% of those classified as high or critical risk, up from 74% in the previous year.</p><p>"Most enterprises cannot keep up with the volume, complexity, and speed of risk. AI-driven vulnerability discovery is accelerating both the volume and speed of CVE creation, compounding an already unsustainable remediation gap," said IBM.</p><p>"Project Lightwell delivers validated fixes to the specific open source versions organizations already run. By combining large-scale engineering, AI, and a coordinated clearinghouse model, it enables organizations to move from detection to remediation without disrupting stability, certification, or compliance requirements."</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/ibm-and-red-hat-believe-they-have-the-answer-to-open-source-security-risks</link>
                                                                            <description>
                            <![CDATA[ Project Lightwell is backed by a $5 billion investment and a team of more than 20,000 engineers ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">TcG8EBRspu5V7D6HUtMPmE</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/T3bahCery9gj9T3n8Srp4C-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 29 May 2026 10:19:25 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:16 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/T3bahCery9gj9T3n8Srp4C-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[The IBM booth pictured during the RSA Conference in San Francisco, California, US, on Wednesday, April 26, 2023]]></media:description>                                                            <media:text><![CDATA[The IBM booth pictured during the RSA Conference in San Francisco, California, US, on Wednesday, April 26, 2023]]></media:text>
                                <media:title type="plain"><![CDATA[The IBM booth pictured during the RSA Conference in San Francisco, California, US, on Wednesday, April 26, 2023]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/T3bahCery9gj9T3n8Srp4C-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>IBM and its subsidiary Red Hat are pumping $5 billion into improving the security of open-source projects.</p><p><a href="https://www.ibm.com/products/lightwell">Project Lightwell</a> is designed as an enterprise clearinghouse for open source software, with a new AI-driven model for securing the software supply chain.</p><p>The idea is to use advanced AI capabilities, offered through commercial subscriptions, to validate and test fixes across a huge volume of open source code. Enterprises will be able to integrate secure patches directly into their existing software supply chains, say the firms, with enterprise-grade validation and lifecycle management.</p><p>They can report and resolve vulnerabilities, receive patches optimized for production environments, spanning both Red Hat offerings and independent community code, and share fixes upstream so that open source communities can include them in long-term maintenance.</p><p>And all this will be backed by a team of more than 20,000 engineers working across upstream and enterprise environments. The focus will be on upstream maintenance alongside open source community leaders; high-volume, AI-assisted vulnerability review, triage, and prioritization; and secure patch development, dependency hardening, and release engineering.</p><p>"Open source is the backbone of today's digital economy and the foundation of modern AI, and we are at an inflection point in how it is built, secured, and scaled," said Arvind Krishna, chairman and CEO of IBM. </p><p>"With Project Lightwell, IBM and Red Hat are helping define a new industry model, one that brings together AI, engineering expertise, and trusted collaboration, to secure open source software at its source and across the entire supply chain. This is about strengthening trust in the systems that power business, government, and society."</p><p>IBM and Red Hat are already working with a group of early adopters on Project Lightwell, including Bank of America, BNY, Citi, Goldman Sachs, JPMorganChase, Mastercard, Morgan Stanley, Royal Bank of Canada, State Street, Visa, and Wells Fargo. </p><p>"The real-world insights from these initial deployments will actively shape how vulnerabilities are identified, validated, and remediated at scale across complex software supply chains," the firms said.</p><p>More than nine-in-ten Fortune 500 companies rely on open source software - but security is an ever-present problem. Sonatype <a href="https://www.itpro.com/software/open-source/the-open-source-ecosystem-is-booming-thanks-to-ai-but-hackers-are-taking-advantage">identified</a> 454,648 malicious open source packages in 2025, up 67% on the previous year, with one state-linked group alone tied to more than 800 malicious packages.</p><p>Meanwhile, <a href="https://www.itpro.com/software/open-source/86-percent-of-enterprise-codebases-contain-open-source-vulnerabilities">according to Black Duck</a>, 86% of codebases contain <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> vulnerabilities, with 81% of those classified as high or critical risk, up from 74% in the previous year.</p><p>"Most enterprises cannot keep up with the volume, complexity, and speed of risk. AI-driven vulnerability discovery is accelerating both the volume and speed of CVE creation, compounding an already unsustainable remediation gap," said IBM.</p><p>"Project Lightwell delivers validated fixes to the specific open source versions organizations already run. By combining large-scale engineering, AI, and a coordinated clearinghouse model, it enables organizations to move from detection to remediation without disrupting stability, certification, or compliance requirements."</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Does your business need a software bill of materials? ]]></title>
                                                                                                <dc:content><![CDATA[ <p>At the end of 2021, a now infamous vulnerability was found in the <a href="https://www.itpro.com/security/zero-day-exploit/361819/what-is-log4shell-log4j-vulnerability"><u>Apache Log4j</u></a> open-source logging library. It led to a race against time, with teams struggling to identify which apps and services were affected and apply the <a href="https://logging.apache.org/security.html" target="_blank"><u>patch</u></a> before attackers could exploit the bug.</p><p>As the risk of similar software supply chain threats multiplies, a software bill of materials (SBOM) can help. Essentially an inventory of open source and third party components, an SBOM is now part of regulations including the <a href="https://www.nist.gov/itl/executive-order-14028-improving-nations-cybersecurity" target="_blank"><u>US Executive Order on Cybersecurity</u></a>, the <a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra"><u>EU Cyber Resilience Act</u></a> (CRA) and the EU <a href="https://www.itpro.com/business/policy-legislation/370403/what-is-the-network-and-information-security-2-nis2-directive"><u>Network and Information Systems 2 Directive (NIS2)</u></a>.</p><p>How do SBOMs work, and does your business need one?</p><h2 id="why-firms-need-an-sbom">Why firms need an SBOM</h2><p>Most modern applications include open source and third party components. As a result, a large share of software risk comes from dependencies that teams did not write themselves. </p><p>“When a serious issue like Log4j appears, the first question is simple: Where are we exposed?” says Ilkka Turunen, field CTO at Sonatype. “If you cannot answer this question quickly, you have a real problem.”</p><p>Log4j is “the prime example of why SBOMs can be indispensable”, says Dana Simberkoff, chief risk, privacy and information security officer at AvePoint. “Because the library is very broadly used in consumer and business-facing software applications, the attack on Log4j had catastrophic consequences for a wide range of applications across regions and sectors.”</p><p>An SBOM might have prevented the worst effects of the attack by allowing IT professionals to more easily expose and patch the vulnerability that triggered it, according to Simberkoff.</p><h2 id="visibility-into-software-supply-chains">Visibility into software supply chains</h2><p>As <a href="https://www.itpro.com/software/enterprises-need-to-sharpen-up-on-software-supply-chain-security"><u>software supply chain threats</u></a> become more complex, organizations need complete visibility into the components that make up their applications. This visibility is “critical for security”, says Crystal Morin, senior cybersecurity strategist at Sysdig. </p><p>She points out that modern <a href="https://www.itpro.com/security/cyber-attacks/threat-actors-exploiting-quickly-what-business-leaders-should-do"><u>vulnerabilities are being weaponized much more quickly</u></a>. “So when a vulnerability is discovered in a software component, SBOMs allow organizations to quickly determine whether they are affected and see where that component is in use.”</p><p>It comes at a time when the urgency to fix bugs is increasing. In April, Mozilla said it used Anthropic’s <a href="https://www.itpro.com/technology/artificial-intelligence/project-glasswing-anthropic-announces-big-tech-consortium-to-test-claude-mythos-ai-model-that-could-reshape-cybersecurity"><u>Claude Mythos Preview</u></a> to find and fix 271 <a href="https://www.wired.com/story/mozilla-used-anthropics-mythos-to-find-271-bugs-in-firefox/" target="_blank"><u>bugs in Firefox</u></a>. Anthropic has argued that teams could find many hundreds of vulnerabilities by applying current frontier models. </p><p>As AI super-charges vulnerability discovery, it creates a need for much better visibility into software, says Turunen.</p><p>An SBOM performs this task by offering security, engineering and legal teams a shared understanding of “which components are in use, where they came from, and what needs attention when something goes wrong”, says Turunen. “In practice, this means less guesswork, faster coordination, and a better chance of keeping up as both software complexity and vulnerability discovery speed increase.”</p><h2 id="who-needs-an-sbom">Who needs an SBOM</h2><p>Regulators are now mandating an SBOM across critical sectors. In the US, Executive Order 14028 requires stronger software supply chain security for federal systems, including the use of SBOMs. Meanwhile, agencies such as the <a href="https://www.itpro.com/security/nist-national-vulnerability-database-overhaul-increased-cve-submissions"><u>National Institute of Standards and Technology (NIST)</u></a> and the National Telecommunications and Information Administration (NTIA) have published guidance for federal entities and their software suppliers.</p><p>The EU CRA, set for full enforcement in December 2027, requires SBOMs for products with digital components sold in the EU. In the UK, the government has introduced SBOM guidance through its <a href="https://www.gov.uk/government/publications/software-security-code-of-practice/software-security-code-of-practice" target="_blank"><u>Software Security Code of Practice.</u></a></p><p>The UK’s <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do"><u>National Cyber Security Centre (NCSC)</u></a> encourages organizations to <a href="https://www.ncsc.gov.uk/blog-post/sboms-and-the-importance-of-inventory" target="_blank"><u>adopt SBOMs</u></a> to boost software supply chain security. This is despite the fact they are not yet mandated in domestic regulation, says Ritchie Perry, electronics engineer at ByteSnap Design. “The direction of travel is the same: more transparency over what’s in the software you ship, and better evidence that you’re tracking known vulnerabilities.”</p><p>Even if you are not in a regulated market yet, there is a good chance your larger customers are – and they will start flowing SBOM requirements down the supply chain, Perry adds.</p><p>Industries where SBOMs are most critical are “where the stakes are highest”, says Simberkoff. “For example, software products that interact with critical infrastructure, government agencies and services, and emergency services.”</p><h2 id="how-to-create-an-sbom">How to create an SBOM</h2><p>A typical SBOM consists of supplier name, component name, version, dependency relationship, the author of the SBOM, the time the data was added to the SBOM, and any known risk related to security, legal, and quality. “Together, this information helps secure the intricate and vast systems that constitute software supply chains,” according to Turunen.</p><p>Creating an SBOM should be an “automated, integrated part of your software development lifecycle”, says Simberkoff. “It should not be treated as a one-time task because software changes. Every time software is patched or changed, your SBOM should automatically update.”</p><p>Most teams will lean on tooling, says Perry. He points out that products such as Black Duck, Snyk, Mend and FOSSA can scan codebases and generate SBOMs.</p><p>Meanwhile, platforms such as GitHub and GitLab include SBOM support from their dependency graphs. “These tools are helpful, but not perfect, so it is worth spot checking the output, particularly around high-risk components,” adds Perry.</p><p>SBOMs also must be analyzed for risk using <a href="https://www.itpro.com/security/cyber-attacks/intelligence-sharing-the-boost-for-businesses"><u>threat intelligence</u></a> and policy rules, monitoring each vulnerability proactively in case it needs to be replaced with a more secure alternative.</p><p>To integrate compliance and security throughout business processes, SBOMs must be exported and shared in standard formats for use across teams and external stakeholders, says Turunen.</p><p>Turunen also has a warning: “Even if an organization knows what its developers are using, that doesn’t mean their knowledge extends to vendors. This means not just using SBOMs, but requiring them from vendors as well.’’</p><p>It’s also important to realize that simply generating an SBOM is not enough. Organizations must take proactive steps to ensure SBOMs are “living assets used to drive better security decisions”, says Turunen.</p><p>Keeping SBOMs current is a top priority, concurs Perry. “Components change, dependencies update and <a href="https://www.itpro.com/security/the-cve-system-isnt-working-what-next"><u>new CVEs</u></a> appear constantly. An SBOM that reflects last year’s build is far less useful than one generated from yesterday’s.”</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/does-your-business-need-a-software-bill-of-materials</link>
                                                                            <description>
                            <![CDATA[ An SBOM helps firms to regain control of the supply chain ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">dXKiciJxyx9n2vnS4xtPWS</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/eMajXmJdqtkPdowQCYrcrT-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 26 May 2026 09:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:20 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Kate O&#039;Flaherty ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/LUULv6n7VJ3BHPnaoLHHdg-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/eMajXmJdqtkPdowQCYrcrT-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[A blue padlock stacked on colorful, pastel shapes, against a light blue background.]]></media:description>                                                            <media:text><![CDATA[A blue padlock stacked on colorful, pastel shapes, against a light blue background.]]></media:text>
                                <media:title type="plain"><![CDATA[A blue padlock stacked on colorful, pastel shapes, against a light blue background.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/eMajXmJdqtkPdowQCYrcrT-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>At the end of 2021, a now infamous vulnerability was found in the <a href="https://www.itpro.com/security/zero-day-exploit/361819/what-is-log4shell-log4j-vulnerability"><u>Apache Log4j</u></a> open-source logging library. It led to a race against time, with teams struggling to identify which apps and services were affected and apply the <a href="https://logging.apache.org/security.html" target="_blank"><u>patch</u></a> before attackers could exploit the bug.</p><p>As the risk of similar software supply chain threats multiplies, a software bill of materials (SBOM) can help. Essentially an inventory of open source and third party components, an SBOM is now part of regulations including the <a href="https://www.nist.gov/itl/executive-order-14028-improving-nations-cybersecurity" target="_blank"><u>US Executive Order on Cybersecurity</u></a>, the <a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra"><u>EU Cyber Resilience Act</u></a> (CRA) and the EU <a href="https://www.itpro.com/business/policy-legislation/370403/what-is-the-network-and-information-security-2-nis2-directive"><u>Network and Information Systems 2 Directive (NIS2)</u></a>.</p><p>How do SBOMs work, and does your business need one?</p><h2 id="why-firms-need-an-sbom">Why firms need an SBOM</h2><p>Most modern applications include open source and third party components. As a result, a large share of software risk comes from dependencies that teams did not write themselves. </p><p>“When a serious issue like Log4j appears, the first question is simple: Where are we exposed?” says Ilkka Turunen, field CTO at Sonatype. “If you cannot answer this question quickly, you have a real problem.”</p><p>Log4j is “the prime example of why SBOMs can be indispensable”, says Dana Simberkoff, chief risk, privacy and information security officer at AvePoint. “Because the library is very broadly used in consumer and business-facing software applications, the attack on Log4j had catastrophic consequences for a wide range of applications across regions and sectors.”</p><p>An SBOM might have prevented the worst effects of the attack by allowing IT professionals to more easily expose and patch the vulnerability that triggered it, according to Simberkoff.</p><h2 id="visibility-into-software-supply-chains">Visibility into software supply chains</h2><p>As <a href="https://www.itpro.com/software/enterprises-need-to-sharpen-up-on-software-supply-chain-security"><u>software supply chain threats</u></a> become more complex, organizations need complete visibility into the components that make up their applications. This visibility is “critical for security”, says Crystal Morin, senior cybersecurity strategist at Sysdig. </p><p>She points out that modern <a href="https://www.itpro.com/security/cyber-attacks/threat-actors-exploiting-quickly-what-business-leaders-should-do"><u>vulnerabilities are being weaponized much more quickly</u></a>. “So when a vulnerability is discovered in a software component, SBOMs allow organizations to quickly determine whether they are affected and see where that component is in use.”</p><p>It comes at a time when the urgency to fix bugs is increasing. In April, Mozilla said it used Anthropic’s <a href="https://www.itpro.com/technology/artificial-intelligence/project-glasswing-anthropic-announces-big-tech-consortium-to-test-claude-mythos-ai-model-that-could-reshape-cybersecurity"><u>Claude Mythos Preview</u></a> to find and fix 271 <a href="https://www.wired.com/story/mozilla-used-anthropics-mythos-to-find-271-bugs-in-firefox/" target="_blank"><u>bugs in Firefox</u></a>. Anthropic has argued that teams could find many hundreds of vulnerabilities by applying current frontier models. </p><p>As AI super-charges vulnerability discovery, it creates a need for much better visibility into software, says Turunen.</p><p>An SBOM performs this task by offering security, engineering and legal teams a shared understanding of “which components are in use, where they came from, and what needs attention when something goes wrong”, says Turunen. “In practice, this means less guesswork, faster coordination, and a better chance of keeping up as both software complexity and vulnerability discovery speed increase.”</p><h2 id="who-needs-an-sbom">Who needs an SBOM</h2><p>Regulators are now mandating an SBOM across critical sectors. In the US, Executive Order 14028 requires stronger software supply chain security for federal systems, including the use of SBOMs. Meanwhile, agencies such as the <a href="https://www.itpro.com/security/nist-national-vulnerability-database-overhaul-increased-cve-submissions"><u>National Institute of Standards and Technology (NIST)</u></a> and the National Telecommunications and Information Administration (NTIA) have published guidance for federal entities and their software suppliers.</p><p>The EU CRA, set for full enforcement in December 2027, requires SBOMs for products with digital components sold in the EU. In the UK, the government has introduced SBOM guidance through its <a href="https://www.gov.uk/government/publications/software-security-code-of-practice/software-security-code-of-practice" target="_blank"><u>Software Security Code of Practice.</u></a></p><p>The UK’s <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do"><u>National Cyber Security Centre (NCSC)</u></a> encourages organizations to <a href="https://www.ncsc.gov.uk/blog-post/sboms-and-the-importance-of-inventory" target="_blank"><u>adopt SBOMs</u></a> to boost software supply chain security. This is despite the fact they are not yet mandated in domestic regulation, says Ritchie Perry, electronics engineer at ByteSnap Design. “The direction of travel is the same: more transparency over what’s in the software you ship, and better evidence that you’re tracking known vulnerabilities.”</p><p>Even if you are not in a regulated market yet, there is a good chance your larger customers are – and they will start flowing SBOM requirements down the supply chain, Perry adds.</p><p>Industries where SBOMs are most critical are “where the stakes are highest”, says Simberkoff. “For example, software products that interact with critical infrastructure, government agencies and services, and emergency services.”</p><h2 id="how-to-create-an-sbom">How to create an SBOM</h2><p>A typical SBOM consists of supplier name, component name, version, dependency relationship, the author of the SBOM, the time the data was added to the SBOM, and any known risk related to security, legal, and quality. “Together, this information helps secure the intricate and vast systems that constitute software supply chains,” according to Turunen.</p><p>Creating an SBOM should be an “automated, integrated part of your software development lifecycle”, says Simberkoff. “It should not be treated as a one-time task because software changes. Every time software is patched or changed, your SBOM should automatically update.”</p><p>Most teams will lean on tooling, says Perry. He points out that products such as Black Duck, Snyk, Mend and FOSSA can scan codebases and generate SBOMs.</p><p>Meanwhile, platforms such as GitHub and GitLab include SBOM support from their dependency graphs. “These tools are helpful, but not perfect, so it is worth spot checking the output, particularly around high-risk components,” adds Perry.</p><p>SBOMs also must be analyzed for risk using <a href="https://www.itpro.com/security/cyber-attacks/intelligence-sharing-the-boost-for-businesses"><u>threat intelligence</u></a> and policy rules, monitoring each vulnerability proactively in case it needs to be replaced with a more secure alternative.</p><p>To integrate compliance and security throughout business processes, SBOMs must be exported and shared in standard formats for use across teams and external stakeholders, says Turunen.</p><p>Turunen also has a warning: “Even if an organization knows what its developers are using, that doesn’t mean their knowledge extends to vendors. This means not just using SBOMs, but requiring them from vendors as well.’’</p><p>It’s also important to realize that simply generating an SBOM is not enough. Organizations must take proactive steps to ensure SBOMs are “living assets used to drive better security decisions”, says Turunen.</p><p>Keeping SBOMs current is a top priority, concurs Perry. “Components change, dependencies update and <a href="https://www.itpro.com/security/the-cve-system-isnt-working-what-next"><u>new CVEs</u></a> appear constantly. An SBOM that reflects last year’s build is far less useful than one generated from yesterday’s.”</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Why supply chain resilience is under the spotlight ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Supply chains are still seen as an easy entry point for attackers. Last year, <a href="https://www.verizon.com/business/resources/reports/dbir/" target="_blank"><u>Verizon’s Data Breach Investigations</u></a> report revealed 30% of breaches were linked to third-party involvement. The figure is twice as high as the previous year, driven in part by <a href="https://www.itpro.com/security/the-cve-system-isnt-working-what-next"><u>vulnerability exploitation</u></a> and business interruptions.</p><p>Another survey by <a href="https://securityscorecard.com/wp-content/uploads/2025/06/2025-Supply-Chain-Cybersecurity-Trends.pdf" target="_blank"><u>SecurityScorecard</u></a> found more than 70% of organizations experienced at least one material third-party cybersecurity incident in the past year, with 5% suffering 10 or more.</p><p>The last year has seen numerous high-profile breaches of third parties, including the recent attack on NHS supplier <a href="https://www.itpro.com/security/cyber-attacks/nhs-supplier-dxs-international-confirms-cyber-attack-heres-what-we-know-so-far"><u>DXS International</u></a>. The now infamous <a href="https://www.itpro.com/security/cyber-attacks/m-and-s-reveals-massive-financial-hit-from-cyber-attack"><u>Marks &amp; Spencer breach</u></a> in May 2025 was also traced back to a social engineering attack on a third party contractor. </p><p>These incidents come as regulations such as <a href="https://www.itpro.com/business/policy-and-legislation/cyber-security-and-resilience-bill-security-experts-question-practicality-scope-of-new-legislation"><u>the UK Cyber Security and Resilience Bill</u></a> and EU’s <a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra"><u>Cyber Resilience Act</u></a> (CRA) mandate resilience across the supply chain. </p><p>As attackers continue to focus on third-party suppliers, what can firms do to boost resilience and comply with regulation?</p><h2 id="attractive-targets">Attractive targets</h2><p>Suppliers are attractive targets because they provide “a shortcut into larger organizations”, says Nathan Davies-Webb, principal consultant at Acumen Cyber. “Suppliers can have trusted access to systems, data and networks, but may not have the same level of security maturity as their customers.”</p><p>This leads adversaries to focus on the weakest link in the chain. Supplier access is often “<a href="https://www.itpro.com/security/non-human-identities-are-we-sleepwalking-into-a-security-crisis"><u>over privileged</u></a>, poorly monitored or not regularly reviewed”, allowing attackers to “move quickly and remain undetected once inside”, says Davies-Webb.</p><p>Cyber criminals often view suppliers as “the path of least resistance”, agrees Richard LaTulip, field chief information security officer at Recorded Future. “In most cases, vendors won’t have the same levels of cybersecurity maturity, staffing or budget as their large enterprise customers. Attackers exploit this imbalance in supply chains.”</p><p>The recent DXS International incident is a reminder of “how effectively attackers are targeting the weak underbelly of supply chains”, says LaTulip. “Threat actors are exploiting the trust that exists between large businesses and smaller suppliers, using those vulnerabilities to pick apart and exploit high-value targets.”</p><h2 id="the-core-challenge-to-it-supply-chains">The core challenge to IT supply chains</h2><p>Part of the problem is that many firms lack visibility into their supply chains, creating gaps for adversaries to exploit. “Many organizations depend on hundreds of suppliers, yet have limited insight into how secure they really are,” says Davies-Webb. “The problem quickly compounds when you start to consider fourth and fifth party risk.”</p><p>This is made more complex by the fact that global supply chains are “inherently difficult to monitor”, says Nicola Taylor, chief operating officer at ScotlandIS. “The scale, complexity and interdependence of it all make it harder to <a href="https://www.itpro.com/security/patch-management-why-firms-ignore-vulnerabilities-at-their-own-risk"><u>track vulnerabilities</u></a> and enforce safety standards consistently.” </p><p>At the same time, even when due diligence is carried out at onboarding, security can degrade over time, Davies-Webb warns. </p><p>Additionally, governance strategies aren’t keeping up with the fast-moving threat landscape. “While third party risk is just one element of the supply chain, it is the biggest concern because so many organizations depend on external partners without truly understanding their security maturity,” says Pierre Noel, field CISO at Expel. </p><p>This problem is amplified by “a reactive culture”, says Noel. He thinks many organizations treat cyber risk as “a cost center”, investing meaningfully “only after something bad happens”. </p><p>“Boards understand fraud, but they don’t instinctively <a href="https://www.itpro.com/business/leadership/the-changing-language-of-cyber-communicating-with-the-board"><u>understand breaches</u></a>,” he explains. “Without regulatory pressure or clear return on investment, security remains a box-ticking exercise.”</p><iframe allow="" height="200px" width="100%" id="" style="" class="position-center" data-lazy-priority="high" data-lazy-src="https://player.captivate.fm/episode/0abd7be2-413d-4665-8b77-7ed3e296a2a6/" src="https://player.captivate.fm/episode/0abd7be2-413d-4665-8b77-7ed3e296a2a6/"></iframe><h2 id="supply-chain-regulation">Supply chain regulation</h2><p>Various regulations are forcing organizations to take supply chain risk more seriously, which is a good thing. However, keeping up with a vast set of requirements is also increasing pressure and stress on firms, says Davies-Webb. </p><p>Laws such as the UK Cyber Security and Resilience Bill and the EU CRA require firms to demonstrate oversight of supplier security – not just their own. “That means mapping dependencies, enforcing standards and proving compliance,” Davies-Webb explains.</p><p>Yet organizations are still building the capability to map their suppliers, which is not an easy task for global companies dealing with hundreds or thousands of third parties. “Compliance can quickly become a paperwork exercise unless it is backed by genuine security monitoring and risk management,” says Davies-Webb.</p><p>Another challenge lies in the UK’s Cyber Security and Resilience Bill and the EU CRA’s enforcement of “unprecedented transparency”, adds Ivan Milenkovic, vice president risk technology EMEA at Qualys. The CRA, for instance, mandates a <a href="https://www.ncsc.gov.uk/blog-post/sboms-and-the-importance-of-inventory" target="_blank"><u>Software Bill of Materials</u></a> (SBOM) and requires the reporting of actively exploited vulnerabilities within 24 hours.</p><p>Meanwhile, there is still uncertainty around what the final form of the UK Cyber Security and Resilience Bill will be, says Harry Mason, head of client services at Mason Infotech. Adding to the load, other EU regulations such as the <a href="https://www.itpro.com/business/policy-legislation/370403/what-is-the-network-and-information-security-2-nis2-directive"><u>Network and Information Systems 2,</u></a> (NIS2), also include requirements those operating in the bloc need to consider.</p><h2 id="increasing-resilience">Increasing resilience </h2><p>Supply chain security can be challenging, but there are a few steps businesses can take to ensure they are as resilient as possible. Improving supply chain security requires “a proactive and organization-wide approach”, says Chris Brown SVP UK market leader at NCC Group. </p><p>As a first step, he advises “mapping suppliers across all tiers to uncover hidden dependencies and gain full visibility”.</p><p>One of the most effective ways to increase <a href="https://www.itpro.com/security/supply-chain-and-ai-security-in-the-spotlight-for-cyber-leaders-in-2026"><u>third party security is through procurement</u></a>, says Taylor. This means requiring evidence-based security assurance, clear obligations around patching, access controls and <a href="https://www.itpro.com/security/why-incident-response-has-become-a-core-responsibility-for-msps">incident response</a> as part of the process, she says. “And making sure governance frameworks are formalized, whether through contracts or regular audits, helps companies to stay on top of it.”</p><p>Basics such as <a href="https://www.ncsc.gov.uk/cyberessentials/overview" target="_blank"><u>Cyber Essentials</u></a> certification, strong password policies and <a href="https://www.itpro.com/security/cyber-security/369745/what-is-mfa-fatigue"><u>multi-factor authentication</u></a> “should be non-negotiable”, Mason adds.</p><p>It’s also important to anticipate disruptions through scenario planning and stress-testing, and to continuously monitor suppliers, says Brown.</p><p>To boost supply chain resilience, organizations must treat suppliers as “an extension of their own environment”, Davies-Webb advises. “Start with identifying which suppliers present the greatest risk based on access and data sensitivity, and break these out into an appropriate tiered model.”</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/why-is-supply-chain-resilience-under-the-spotlight</link>
                                                                            <description>
                            <![CDATA[ As attackers continue to target third party suppliers, what can firms do to boost resilience? ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">hbqvq9oqVQoU6gzZeYTNGW</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/DD7oSG7mL3LVWBrNQQCQu7-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 24 Apr 2026 07:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:58 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Kate O&#039;Flaherty ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/LUULv6n7VJ3BHPnaoLHHdg-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/DD7oSG7mL3LVWBrNQQCQu7-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Digital chain concept art]]></media:description>                                                            <media:text><![CDATA[Digital chain concept art]]></media:text>
                                <media:title type="plain"><![CDATA[Digital chain concept art]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/DD7oSG7mL3LVWBrNQQCQu7-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Supply chains are still seen as an easy entry point for attackers. Last year, <a href="https://www.verizon.com/business/resources/reports/dbir/" target="_blank"><u>Verizon’s Data Breach Investigations</u></a> report revealed 30% of breaches were linked to third-party involvement. The figure is twice as high as the previous year, driven in part by <a href="https://www.itpro.com/security/the-cve-system-isnt-working-what-next"><u>vulnerability exploitation</u></a> and business interruptions.</p><p>Another survey by <a href="https://securityscorecard.com/wp-content/uploads/2025/06/2025-Supply-Chain-Cybersecurity-Trends.pdf" target="_blank"><u>SecurityScorecard</u></a> found more than 70% of organizations experienced at least one material third-party cybersecurity incident in the past year, with 5% suffering 10 or more.</p><p>The last year has seen numerous high-profile breaches of third parties, including the recent attack on NHS supplier <a href="https://www.itpro.com/security/cyber-attacks/nhs-supplier-dxs-international-confirms-cyber-attack-heres-what-we-know-so-far"><u>DXS International</u></a>. The now infamous <a href="https://www.itpro.com/security/cyber-attacks/m-and-s-reveals-massive-financial-hit-from-cyber-attack"><u>Marks &amp; Spencer breach</u></a> in May 2025 was also traced back to a social engineering attack on a third party contractor. </p><p>These incidents come as regulations such as <a href="https://www.itpro.com/business/policy-and-legislation/cyber-security-and-resilience-bill-security-experts-question-practicality-scope-of-new-legislation"><u>the UK Cyber Security and Resilience Bill</u></a> and EU’s <a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra"><u>Cyber Resilience Act</u></a> (CRA) mandate resilience across the supply chain. </p><p>As attackers continue to focus on third-party suppliers, what can firms do to boost resilience and comply with regulation?</p><h2 id="attractive-targets">Attractive targets</h2><p>Suppliers are attractive targets because they provide “a shortcut into larger organizations”, says Nathan Davies-Webb, principal consultant at Acumen Cyber. “Suppliers can have trusted access to systems, data and networks, but may not have the same level of security maturity as their customers.”</p><p>This leads adversaries to focus on the weakest link in the chain. Supplier access is often “<a href="https://www.itpro.com/security/non-human-identities-are-we-sleepwalking-into-a-security-crisis"><u>over privileged</u></a>, poorly monitored or not regularly reviewed”, allowing attackers to “move quickly and remain undetected once inside”, says Davies-Webb.</p><p>Cyber criminals often view suppliers as “the path of least resistance”, agrees Richard LaTulip, field chief information security officer at Recorded Future. “In most cases, vendors won’t have the same levels of cybersecurity maturity, staffing or budget as their large enterprise customers. Attackers exploit this imbalance in supply chains.”</p><p>The recent DXS International incident is a reminder of “how effectively attackers are targeting the weak underbelly of supply chains”, says LaTulip. “Threat actors are exploiting the trust that exists between large businesses and smaller suppliers, using those vulnerabilities to pick apart and exploit high-value targets.”</p><h2 id="the-core-challenge-to-it-supply-chains">The core challenge to IT supply chains</h2><p>Part of the problem is that many firms lack visibility into their supply chains, creating gaps for adversaries to exploit. “Many organizations depend on hundreds of suppliers, yet have limited insight into how secure they really are,” says Davies-Webb. “The problem quickly compounds when you start to consider fourth and fifth party risk.”</p><p>This is made more complex by the fact that global supply chains are “inherently difficult to monitor”, says Nicola Taylor, chief operating officer at ScotlandIS. “The scale, complexity and interdependence of it all make it harder to <a href="https://www.itpro.com/security/patch-management-why-firms-ignore-vulnerabilities-at-their-own-risk"><u>track vulnerabilities</u></a> and enforce safety standards consistently.” </p><p>At the same time, even when due diligence is carried out at onboarding, security can degrade over time, Davies-Webb warns. </p><p>Additionally, governance strategies aren’t keeping up with the fast-moving threat landscape. “While third party risk is just one element of the supply chain, it is the biggest concern because so many organizations depend on external partners without truly understanding their security maturity,” says Pierre Noel, field CISO at Expel. </p><p>This problem is amplified by “a reactive culture”, says Noel. He thinks many organizations treat cyber risk as “a cost center”, investing meaningfully “only after something bad happens”. </p><p>“Boards understand fraud, but they don’t instinctively <a href="https://www.itpro.com/business/leadership/the-changing-language-of-cyber-communicating-with-the-board"><u>understand breaches</u></a>,” he explains. “Without regulatory pressure or clear return on investment, security remains a box-ticking exercise.”</p><iframe allow="" height="200px" width="100%" id="" style="" class="position-center" data-lazy-priority="high" data-lazy-src="https://player.captivate.fm/episode/0abd7be2-413d-4665-8b77-7ed3e296a2a6/" src="https://player.captivate.fm/episode/0abd7be2-413d-4665-8b77-7ed3e296a2a6/"></iframe><h2 id="supply-chain-regulation">Supply chain regulation</h2><p>Various regulations are forcing organizations to take supply chain risk more seriously, which is a good thing. However, keeping up with a vast set of requirements is also increasing pressure and stress on firms, says Davies-Webb. </p><p>Laws such as the UK Cyber Security and Resilience Bill and the EU CRA require firms to demonstrate oversight of supplier security – not just their own. “That means mapping dependencies, enforcing standards and proving compliance,” Davies-Webb explains.</p><p>Yet organizations are still building the capability to map their suppliers, which is not an easy task for global companies dealing with hundreds or thousands of third parties. “Compliance can quickly become a paperwork exercise unless it is backed by genuine security monitoring and risk management,” says Davies-Webb.</p><p>Another challenge lies in the UK’s Cyber Security and Resilience Bill and the EU CRA’s enforcement of “unprecedented transparency”, adds Ivan Milenkovic, vice president risk technology EMEA at Qualys. The CRA, for instance, mandates a <a href="https://www.ncsc.gov.uk/blog-post/sboms-and-the-importance-of-inventory" target="_blank"><u>Software Bill of Materials</u></a> (SBOM) and requires the reporting of actively exploited vulnerabilities within 24 hours.</p><p>Meanwhile, there is still uncertainty around what the final form of the UK Cyber Security and Resilience Bill will be, says Harry Mason, head of client services at Mason Infotech. Adding to the load, other EU regulations such as the <a href="https://www.itpro.com/business/policy-legislation/370403/what-is-the-network-and-information-security-2-nis2-directive"><u>Network and Information Systems 2,</u></a> (NIS2), also include requirements those operating in the bloc need to consider.</p><h2 id="increasing-resilience">Increasing resilience </h2><p>Supply chain security can be challenging, but there are a few steps businesses can take to ensure they are as resilient as possible. Improving supply chain security requires “a proactive and organization-wide approach”, says Chris Brown SVP UK market leader at NCC Group. </p><p>As a first step, he advises “mapping suppliers across all tiers to uncover hidden dependencies and gain full visibility”.</p><p>One of the most effective ways to increase <a href="https://www.itpro.com/security/supply-chain-and-ai-security-in-the-spotlight-for-cyber-leaders-in-2026"><u>third party security is through procurement</u></a>, says Taylor. This means requiring evidence-based security assurance, clear obligations around patching, access controls and <a href="https://www.itpro.com/security/why-incident-response-has-become-a-core-responsibility-for-msps">incident response</a> as part of the process, she says. “And making sure governance frameworks are formalized, whether through contracts or regular audits, helps companies to stay on top of it.”</p><p>Basics such as <a href="https://www.ncsc.gov.uk/cyberessentials/overview" target="_blank"><u>Cyber Essentials</u></a> certification, strong password policies and <a href="https://www.itpro.com/security/cyber-security/369745/what-is-mfa-fatigue"><u>multi-factor authentication</u></a> “should be non-negotiable”, Mason adds.</p><p>It’s also important to anticipate disruptions through scenario planning and stress-testing, and to continuously monitor suppliers, says Brown.</p><p>To boost supply chain resilience, organizations must treat suppliers as “an extension of their own environment”, Davies-Webb advises. “Start with identifying which suppliers present the greatest risk based on access and data sensitivity, and break these out into an appropriate tiered model.”</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Shadow AI and the new visibility gap in software development ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Generative AI is becoming increasingly central to how software is developed. However, while this integration vastly improves productivity, a problem is emerging with the rise of shadow AI. </p><p>Recent research shows that shadow AI is already mainstream, with a <a href="https://www.securityweek.com/the-shadow-ai-surge-study-finds-50-of-workers-use-unapproved-ai-tools/"><u>Software AG</u></a> study finding that half of workers rely on unapproved tools. In the UK, the adoption is on an even larger scale, with <a href="https://www.itpro.com/technology/artificial-intelligence/gartner-says-40-percent-of-enterprises-will-experience-shadow-ai-breaches-by-2030-educating-staff-is-the-key-to-avoiding-disaster#:~:text=Artificial%20Intelligence-,Gartner%20says%2040%25%20of%20enterprises%20will%20experience%20'shadow%20AI',the%20key%20to%20avoiding%20disaster&amp;text=Nearly%20half%20of%20enterprises%20could,for%20more%20robust%20governance%20practices."><u>over 70%</u></a> of employees admitting to using unauthorized AI, and more than half doing so on a weekly basis.</p><p>This is a familiar scenario in the tech sector, where shadow IT has long threatened on-premises and cloud network security. Shadow AI, however, introduces more complicated issues, in particular, the “lethal trifecta”. AI agents typically depend on a mix of access to three things: private data, external communication, and openness to untrusted context (prompt injection). When all three of these are present at once, organizations are at risk of an AI agent being tricked by malicious prompts, which can not only make sensitive data more vulnerable to attack but also put the organization at odds with compliance requirements. </p><p>AI systems are actively integrated across workflow processes with agents and AI assistants writing code, executing commands, and automating tasks. They quite literally act as human agents when it comes to writing software programs, and they operate at the level of trust granted to the software. Importantly, this is not the same level of trust that is afforded to human agents.  </p><p>The two-way flow of data that characterizes AI usage in companies also increases the risk of confidential information being leaked. Developers may, even inadvertently, send private code, confidential information, or passwords to external AI models. Meanwhile, potentially vulnerable AI-generated code can flow back into code, where it can introduce breaches, weaknesses, or unsafe patterns if not correctly governed. </p><h2 id="how-shadow-ai-is-creating-a-visibility-gap">How Shadow AI is creating a visibility gap</h2><p>For managed service providers and DevOps channel partners, this creates a gap in what they can monitor and prevent. Many Managed Service Providers (MSPs) have adapted to effectively manage traditional shadow IT using tools such as Cloud Access Security Brokers, SaaS discovery platforms, endpoint monitoring, and network traffic analysis. </p><p>These approaches are designed to identify unsanctioned applications by detecting unusual access patterns, monitoring known SaaS usage, or enforcing policies at the network and device level. However, when it comes to shadow AI, these methods are far less effective. Shadow AI usually exists inside engineering processes that aren’t covered by standard monitoring. Developers running agents on personal laptops or using personal API keys may be completely outside the reach of existing surveillance tools.</p><p>As a result, MSPs lack a clear path to detect or resolve unauthorized AI use in software development environments. Without new approaches, they risk losing control over one of the fastest-growing parts of their customers’ technology stacks.</p><h2 id="how-to-close-the-visibility-gap">How to close the visibility gap</h2><p>One method for this is to help organizations assess where they stand through structured maturity models. Reputable AI maturity tests can help enterprises measure the impact of AI agents being added to software-writing processes and identify where governance, security controls, and operating processes must evolve. For partners, these structures move the discussion beyond risk alone. Rather than simply stopping AI use, which is seldom effective, companies can instead put appropriate limits in place while still allowing developers to write program code. </p><p>This can be achieved by controlling how AI models are accessed by routing usage through centrally managed infrastructure rather than personal accounts or API keys, giving organizations visibility into which tools are being used, by whom, and what data is flowing through them. </p><p>When governance is part of the underlying structure - and largely invisible to developers - organizations can ensure consistent, safe use of AI across code, data, and systems, while still giving teams the freedom to experiment and innovate. The other half of the challenge is agent behavior at runtime. AI agents require network access, but that access can be scoped with process-level controls that can restrict them to approved services only, ensuring a compromised or misdirected agent cannot reach unauthorized endpoints or exfiltrate data. This significantly reduces the impact of risks such as prompt injection.</p><p>When governance is embedded at the infrastructure layer rather than enforced through policy or training, the attack surface shrinks significantly. Developers are able to retain their preferred tools, AI agents can continue to operate as intended, and organizations are able to gain full governance without having to force changes to developer workflows.</p><p>This change also gives partners the opportunity to expand their advisory role. As companies go through different iterations of AI integration, there is a clear three-stage evolution that creates revenue opportunities during specification, implementation, and the delivery of managed services.</p><ul><li>Migrate: Move from legacy environments to cloud-based development<ul><li>At this stage, partners support customers with modernizing their development infrastructure, which includes migrating workloads to cloud environments, standardizing developer workspaces, and establishing secure and centrally managed platforms.</li></ul></li><li>Modernize: Incorporate governed and audited AI into the development lifecycle<ul><li>Here, the focus is on embedding AI safely into workflows. Partners can introduce controlled access to AI models, implement audit and compliance mechanisms, and integrate governance into development pipelines. The goal here is to help customers adopt AI without increasing risk.</li></ul></li><li>Multiply: Extend agentic workflows to handle repetitive, low-value workloads<ul><li>Once governance has been well established, organizations can increase their use of AI agents to automate testing, coding, and operational tasks. For partners, this creates opportunities to design and manage agent workflows, optimize performance, and deliver ongoing managed services that improve efficiency over time.</li></ul></li></ul><p>However, the most important change for partners may be where they focus their attention. The AI world is changing rapidly, and organizations will inevitably change models, tools, and suppliers over time. </p><p>Governance plans that depend on controlling certain tools can quickly become obsolete. Instead, partners should focus on the basic processes developers use to build, test, and supply software. When governance structures are built around those fundamental processes, rather than individual AI products, they will stay strong even as the AI world changes.</p><p>AI use in development environments will only increase, and there will always be a temptation for developers to try new tools if they can speed up delivery times. For MSPs, this makes partner selection critical. Vendors that prioritize security governance and observability and enable enterprise customers to use AI tools safely will be best positioned to deliver the next generation of secure, AI-driven software development. </p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/technology/artificial-intelligence/shadow-ai-and-the-new-visibility-gap-in-software-development</link>
                                                                            <description>
                            <![CDATA[ Shadow AI adoption creates security risks and visibility gaps in development ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">SNJFcCrTnGQaEpVsDKF4kF</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/XUFTVxXHrTRAVBdujTYj6P-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 16 Apr 2026 07:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:51 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Artificial Intelligence]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Simon Gregory ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/mumsvNYY62S3AY4xzVMNUj-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/XUFTVxXHrTRAVBdujTYj6P-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Artificial intelligence (AI) concept image showing a digitized cube with &#039;AI&#039; written on it resting on top of circuit boards.]]></media:description>                                                            <media:text><![CDATA[Artificial intelligence (AI) concept image showing a digitized cube with &#039;AI&#039; written on it resting on top of circuit boards.]]></media:text>
                                <media:title type="plain"><![CDATA[Artificial intelligence (AI) concept image showing a digitized cube with &#039;AI&#039; written on it resting on top of circuit boards.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/XUFTVxXHrTRAVBdujTYj6P-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Generative AI is becoming increasingly central to how software is developed. However, while this integration vastly improves productivity, a problem is emerging with the rise of shadow AI. </p><p>Recent research shows that shadow AI is already mainstream, with a <a href="https://www.securityweek.com/the-shadow-ai-surge-study-finds-50-of-workers-use-unapproved-ai-tools/"><u>Software AG</u></a> study finding that half of workers rely on unapproved tools. In the UK, the adoption is on an even larger scale, with <a href="https://www.itpro.com/technology/artificial-intelligence/gartner-says-40-percent-of-enterprises-will-experience-shadow-ai-breaches-by-2030-educating-staff-is-the-key-to-avoiding-disaster#:~:text=Artificial%20Intelligence-,Gartner%20says%2040%25%20of%20enterprises%20will%20experience%20'shadow%20AI',the%20key%20to%20avoiding%20disaster&amp;text=Nearly%20half%20of%20enterprises%20could,for%20more%20robust%20governance%20practices."><u>over 70%</u></a> of employees admitting to using unauthorized AI, and more than half doing so on a weekly basis.</p><p>This is a familiar scenario in the tech sector, where shadow IT has long threatened on-premises and cloud network security. Shadow AI, however, introduces more complicated issues, in particular, the “lethal trifecta”. AI agents typically depend on a mix of access to three things: private data, external communication, and openness to untrusted context (prompt injection). When all three of these are present at once, organizations are at risk of an AI agent being tricked by malicious prompts, which can not only make sensitive data more vulnerable to attack but also put the organization at odds with compliance requirements. </p><p>AI systems are actively integrated across workflow processes with agents and AI assistants writing code, executing commands, and automating tasks. They quite literally act as human agents when it comes to writing software programs, and they operate at the level of trust granted to the software. Importantly, this is not the same level of trust that is afforded to human agents.  </p><p>The two-way flow of data that characterizes AI usage in companies also increases the risk of confidential information being leaked. Developers may, even inadvertently, send private code, confidential information, or passwords to external AI models. Meanwhile, potentially vulnerable AI-generated code can flow back into code, where it can introduce breaches, weaknesses, or unsafe patterns if not correctly governed. </p><h2 id="how-shadow-ai-is-creating-a-visibility-gap">How Shadow AI is creating a visibility gap</h2><p>For managed service providers and DevOps channel partners, this creates a gap in what they can monitor and prevent. Many Managed Service Providers (MSPs) have adapted to effectively manage traditional shadow IT using tools such as Cloud Access Security Brokers, SaaS discovery platforms, endpoint monitoring, and network traffic analysis. </p><p>These approaches are designed to identify unsanctioned applications by detecting unusual access patterns, monitoring known SaaS usage, or enforcing policies at the network and device level. However, when it comes to shadow AI, these methods are far less effective. Shadow AI usually exists inside engineering processes that aren’t covered by standard monitoring. Developers running agents on personal laptops or using personal API keys may be completely outside the reach of existing surveillance tools.</p><p>As a result, MSPs lack a clear path to detect or resolve unauthorized AI use in software development environments. Without new approaches, they risk losing control over one of the fastest-growing parts of their customers’ technology stacks.</p><h2 id="how-to-close-the-visibility-gap">How to close the visibility gap</h2><p>One method for this is to help organizations assess where they stand through structured maturity models. Reputable AI maturity tests can help enterprises measure the impact of AI agents being added to software-writing processes and identify where governance, security controls, and operating processes must evolve. For partners, these structures move the discussion beyond risk alone. Rather than simply stopping AI use, which is seldom effective, companies can instead put appropriate limits in place while still allowing developers to write program code. </p><p>This can be achieved by controlling how AI models are accessed by routing usage through centrally managed infrastructure rather than personal accounts or API keys, giving organizations visibility into which tools are being used, by whom, and what data is flowing through them. </p><p>When governance is part of the underlying structure - and largely invisible to developers - organizations can ensure consistent, safe use of AI across code, data, and systems, while still giving teams the freedom to experiment and innovate. The other half of the challenge is agent behavior at runtime. AI agents require network access, but that access can be scoped with process-level controls that can restrict them to approved services only, ensuring a compromised or misdirected agent cannot reach unauthorized endpoints or exfiltrate data. This significantly reduces the impact of risks such as prompt injection.</p><p>When governance is embedded at the infrastructure layer rather than enforced through policy or training, the attack surface shrinks significantly. Developers are able to retain their preferred tools, AI agents can continue to operate as intended, and organizations are able to gain full governance without having to force changes to developer workflows.</p><p>This change also gives partners the opportunity to expand their advisory role. As companies go through different iterations of AI integration, there is a clear three-stage evolution that creates revenue opportunities during specification, implementation, and the delivery of managed services.</p><ul><li>Migrate: Move from legacy environments to cloud-based development<ul><li>At this stage, partners support customers with modernizing their development infrastructure, which includes migrating workloads to cloud environments, standardizing developer workspaces, and establishing secure and centrally managed platforms.</li></ul></li><li>Modernize: Incorporate governed and audited AI into the development lifecycle<ul><li>Here, the focus is on embedding AI safely into workflows. Partners can introduce controlled access to AI models, implement audit and compliance mechanisms, and integrate governance into development pipelines. The goal here is to help customers adopt AI without increasing risk.</li></ul></li><li>Multiply: Extend agentic workflows to handle repetitive, low-value workloads<ul><li>Once governance has been well established, organizations can increase their use of AI agents to automate testing, coding, and operational tasks. For partners, this creates opportunities to design and manage agent workflows, optimize performance, and deliver ongoing managed services that improve efficiency over time.</li></ul></li></ul><p>However, the most important change for partners may be where they focus their attention. The AI world is changing rapidly, and organizations will inevitably change models, tools, and suppliers over time. </p><p>Governance plans that depend on controlling certain tools can quickly become obsolete. Instead, partners should focus on the basic processes developers use to build, test, and supply software. When governance structures are built around those fundamental processes, rather than individual AI products, they will stay strong even as the AI world changes.</p><p>AI use in development environments will only increase, and there will always be a temptation for developers to try new tools if they can speed up delivery times. For MSPs, this makes partner selection critical. Vendors that prioritize security governance and observability and enable enterprise customers to use AI tools safely will be best positioned to deliver the next generation of secure, AI-driven software development. </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ AI agents using Anthropic MCP could be a vector for supply chain attacks ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Anthropic’s <a href="https://www.itpro.com/technology/artificial-intelligence/what-is-model-context-protocol-mcp"><u>Model Context Protocol (MCP)</u></a> has a systemic vulnerability that could allow hackers to take control of servers and breach companies’ security, according to OX Security.</p><p>Researchers at OX Security claim the flaw permits “arbitrary command execution of any server running a vulnerable MCP implementation”.</p><p>This gives attackers direct access to: </p><ul><li>user data</li><li>Databases</li><li>API keys</li><li>Chat histories</li></ul><p>and “much more”.</p><p>MCP is a popular <a href="https://www.itpro.com/technology/artificial-intelligence/practical-ai-the-age-of-agentic-ai">AI agent</a> communication standard developed and maintained by Anthropic and used by potentially millions of agents and hundreds-of-thousands of servers.</p><p>In the words of researchers Moshe Ben Siman Tov, Nir Zadok, Mustafa Naamnih, and Roni Bar: “The blast radius is massive. This exploit allowed us to directly execute commands on six official services of real companies with real paying customers.”</p><p>They added that during their research they conducted “over 30 responsible disclosure processes, produced 10 CVEs rated Critical and High, and helped patch numerous projects”.</p><h2 id="not-a-one-off-coding-mistake">“Not a one-off coding mistake”</h2><p>In the report <a href="https://www.ox.security/resource-category/whitepapers-and-reports/mother-of-all-ai-supply-chains/" target="_blank"><u><em>The mother of all AI supply chains</em></u></a>, OX Security researchers said the MCP flaw isn’t a “one-off coding mistake” but is more fundamental.</p><p>They explained that, while reviewing potential AI and LLM-related attack vectors, they found a vulnerability in a GPT Researcher feature that allowed developers to configure a custom STDIO MCP server, where the command and arguments are supplied by the user.</p><p>“Testing revealed that any OS command passed through this interface would execute on the server — even when the face MCP server failed to start,” the OX Security researchers said. “The error was returned to the user; the command ran anyway.”</p><p>This meant that running an arbitrary command gave complete control of the server.</p><p>“To be clear: this should never happen,” they said..</p><p>GPT Researcher uses AI agent engineering platform LangChain’s langchain-mcp-adapters and the OX Security researchers assumed that was where the vulnerability lay. However, further investigation found the root of the issue lay in Anthropic’s original MCP implementation code, modelcontextprotocol.</p><p>When OX Security contacted LangChain and Anthropic about the issue, both organizations said this was “expected behavior”. </p><p>In a statement to OX Security, Anthropic said: “We do not consider this a valid security vulnerability as it requires explicit user permission for the file change where the user is given the opportunity to approve or deny the change.”</p><p>Anthropic has since released an updated security policy, however, stating that MCP adapters and STDIO ones in particular should be used with caution and emphasized that responsibility for securing code lies with the developers, not with Anthropic.</p><p>OX Security argued this represents a supply chain risk that is difficult to resolve.</p><p>“Developers are not security engineers,” the OX Security researchers said, “we cannot expect tens of thousands of implementers to independently discover and mitigate a flaw that’s baked into the official SDKs they trust. By shifting the blame rather than hardening the protocol, the industry leaves user data and organizational infrastructure exposed”</p><p>They added: “This architectural failure highlights an even broader, systemic trend. As AI-assisted code generation accelerates, individuals with limited technical expertise are deploying an unprecedented volume of projects. However, generating more code without foundational security knowledge exponentially widens the gap in organizational defenses.”</p><p>Jake Moore, global cybersecurity advisor at ESET, echoed these sentiments, telling <em>ITPro</em>: “This is potentially the start of what is to come with AI enabled cybercrime. Supply chain attacks are still rife but when we are adding in extremely new technology that hasn't and can't really ever be fully tested, we are putting ourselves in dangerous waters where disastrous attacks can and will occur.”</p><p>He added: "This isn't just a bug that we are used to seeing, this is what happens when an AI standard is built for capability before control and we are likely to see this more and more over the next few years. If it works, it doesn't mean it's safe but refusing to patch it suggests this isn't easily fixable without breaking functionality (which is the bigger concern).”<em> </em></p><p><em>ITPro</em> has approached Anthropic for comment.</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/ai-agents-using-anthropic-mcp-supply-chain-attacks-claim-researchers</link>
                                                                            <description>
                            <![CDATA[ The flaw in Anthropic’s Model Context Protocol agent communication standard could put millions of agents and 200,000 servers at risk, report says ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">pCRDgxhtKFCjEcbXEWtrjJ</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/B5sequrZU2Sim7e6k6gTnH-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 15 Apr 2026 13:32:17 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:50 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                <author><![CDATA[ jane.mccallion@futurenet.com (Jane McCallion) ]]></author>                    <dc:creator><![CDATA[ Jane McCallion ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Wq9nnLr7TNkY8gyBRb7YsA-320-70.jpeg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Jane is managing editor at ITPro and ChannelPro. She started out with the brands as a staff writer specializing in cloud computing before going on to become senior writer and reports editor, managing the content and creation of ITPro’s quarterly whitepapers. During this time, she broadened her expertise to include cybersecurity, data centers and enterprise IT infrastructure. In 2016, she became features editor, managing a pool of freelance and internal writers, while continuing to specialize in enterprise IT infrastructure, data centers, and business strategy.&lt;/p&gt;&lt;p&gt;In October 2021, she became the sites’ deputy editor, before moving to the role of managing editor in June 2024. Although she now has a more strategic role,  she is still a specialist in enterprise IT infrastructure, business strategy, and cybersecurity.&lt;/p&gt;&lt;p&gt;Jane holds an MA in journalism from Goldsmiths, University of London, and a BA in Applied Languages from the University of Portsmouth. She is fluent in French and Spanish, and has written features in both languages.&lt;/p&gt;&lt;p&gt;Prior to joining ITPro, Jane was a freelance business journalist writing as both Jane McCallion and Jane Bordenave for titles such as European CEO, World Finance, and Business Excellence Magazine.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/B5sequrZU2Sim7e6k6gTnH-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[The Anthropic logo, in white on a dark background lit by a web-like light.]]></media:description>                                                            <media:text><![CDATA[The Anthropic logo, in white on a dark background lit by a web-like light.]]></media:text>
                                <media:title type="plain"><![CDATA[The Anthropic logo, in white on a dark background lit by a web-like light.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/B5sequrZU2Sim7e6k6gTnH-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Anthropic’s <a href="https://www.itpro.com/technology/artificial-intelligence/what-is-model-context-protocol-mcp"><u>Model Context Protocol (MCP)</u></a> has a systemic vulnerability that could allow hackers to take control of servers and breach companies’ security, according to OX Security.</p><p>Researchers at OX Security claim the flaw permits “arbitrary command execution of any server running a vulnerable MCP implementation”.</p><p>This gives attackers direct access to: </p><ul><li>user data</li><li>Databases</li><li>API keys</li><li>Chat histories</li></ul><p>and “much more”.</p><p>MCP is a popular <a href="https://www.itpro.com/technology/artificial-intelligence/practical-ai-the-age-of-agentic-ai">AI agent</a> communication standard developed and maintained by Anthropic and used by potentially millions of agents and hundreds-of-thousands of servers.</p><p>In the words of researchers Moshe Ben Siman Tov, Nir Zadok, Mustafa Naamnih, and Roni Bar: “The blast radius is massive. This exploit allowed us to directly execute commands on six official services of real companies with real paying customers.”</p><p>They added that during their research they conducted “over 30 responsible disclosure processes, produced 10 CVEs rated Critical and High, and helped patch numerous projects”.</p><h2 id="not-a-one-off-coding-mistake">“Not a one-off coding mistake”</h2><p>In the report <a href="https://www.ox.security/resource-category/whitepapers-and-reports/mother-of-all-ai-supply-chains/" target="_blank"><u><em>The mother of all AI supply chains</em></u></a>, OX Security researchers said the MCP flaw isn’t a “one-off coding mistake” but is more fundamental.</p><p>They explained that, while reviewing potential AI and LLM-related attack vectors, they found a vulnerability in a GPT Researcher feature that allowed developers to configure a custom STDIO MCP server, where the command and arguments are supplied by the user.</p><p>“Testing revealed that any OS command passed through this interface would execute on the server — even when the face MCP server failed to start,” the OX Security researchers said. “The error was returned to the user; the command ran anyway.”</p><p>This meant that running an arbitrary command gave complete control of the server.</p><p>“To be clear: this should never happen,” they said..</p><p>GPT Researcher uses AI agent engineering platform LangChain’s langchain-mcp-adapters and the OX Security researchers assumed that was where the vulnerability lay. However, further investigation found the root of the issue lay in Anthropic’s original MCP implementation code, modelcontextprotocol.</p><p>When OX Security contacted LangChain and Anthropic about the issue, both organizations said this was “expected behavior”. </p><p>In a statement to OX Security, Anthropic said: “We do not consider this a valid security vulnerability as it requires explicit user permission for the file change where the user is given the opportunity to approve or deny the change.”</p><p>Anthropic has since released an updated security policy, however, stating that MCP adapters and STDIO ones in particular should be used with caution and emphasized that responsibility for securing code lies with the developers, not with Anthropic.</p><p>OX Security argued this represents a supply chain risk that is difficult to resolve.</p><p>“Developers are not security engineers,” the OX Security researchers said, “we cannot expect tens of thousands of implementers to independently discover and mitigate a flaw that’s baked into the official SDKs they trust. By shifting the blame rather than hardening the protocol, the industry leaves user data and organizational infrastructure exposed”</p><p>They added: “This architectural failure highlights an even broader, systemic trend. As AI-assisted code generation accelerates, individuals with limited technical expertise are deploying an unprecedented volume of projects. However, generating more code without foundational security knowledge exponentially widens the gap in organizational defenses.”</p><p>Jake Moore, global cybersecurity advisor at ESET, echoed these sentiments, telling <em>ITPro</em>: “This is potentially the start of what is to come with AI enabled cybercrime. Supply chain attacks are still rife but when we are adding in extremely new technology that hasn't and can't really ever be fully tested, we are putting ourselves in dangerous waters where disastrous attacks can and will occur.”</p><p>He added: "This isn't just a bug that we are used to seeing, this is what happens when an AI standard is built for capability before control and we are likely to see this more and more over the next few years. If it works, it doesn't mean it's safe but refusing to patch it suggests this isn't easily fixable without breaking functionality (which is the bigger concern).”<em> </em></p><p><em>ITPro</em> has approached Anthropic for comment.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Developers are slacking on AI-generated code checks ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Organizations are taking a slapdash approach to <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated code</a>, with many spending far too little time on oversight, new research suggests. </p><p>The vast majority (93%) of respondents to Cloudsmith's 2026 <a href="https://cloudsmith.com/campaigns/2026-artifact-management-report" target="_blank"><u><em>Artifact Management Report</em></u></a> said their organization was using AI-generated code, more than twice as many as last year. </p><p>Yet despite this sharp increase, around than one-third (31%) spend 10 hours or less per month validating, auditing, or securing it. Indeed, just 58% spend at least 11 hours per month on this front while one-in-twenty said they don't audit AI code at all. </p><p>While <a href="https://www.itpro.com/technology/artificial-intelligence/the-risks-of-open-source-ai-models">AI models</a> have become a leading artifact type, only 12% of organizations are managing them using the same security policies and provenance tracking as traditional binaries, such as language packages and operating system libraries.</p><p>This is despite the fact that organizations are mostly aware of the risks, with only 17% very confident that AI is not introducing new vulnerabilities into their codebase.</p><p>“We are at a huge inflection point in the history of software development. In a matter of months, we’ve gone from, ‘<em>How can AI help me write better code?</em>’ to, ‘<em>How can I help AI write better code?</em>’”, said Glenn Weinstein, CEO of Cloudsmith. </p><p>"But at the same time, <a href="https://www.itpro.com/technology/artificial-intelligence/amazing-ai-tools-to-try-today">AI tools</a> are expanding the attack surface, introducing more open source dependencies. And those same tools are being used by malicious actors to find more vulnerabilities in existing libraries, leading to more CVEs.”</p><h2 id="sloppy-practices-could-come-back-to-haunt-devs">Sloppy practices could come back to haunt devs</h2><p>Poor security practices on this front could have wide-reaching regulatory implications for enterprises, the study warned. </p><p>Under the EU’s <a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra">Cyber Resilience Act (CRA)</a>, organizations are required to provide a detailed assessment 48 hours after becoming aware of a breach – and this includes providing provenance data. </p><p>More than half (53%) of respondents told Cloudsmith they'd need to put in a significant amount of manual effort or time to produce a comprehensive report of artifact versions, origins, and security attestations.</p><p>Only a quarter of engineering teams automatically generate and verify <a href="https://www.itpro.com/security/software-security-overhauled-for-the-better-thanks-to-us-legislation">Software Bills of Materials (SBOMs)</a> at every build, with the rest doing it manually, reactively, or only when an auditor asks. </p><p>Notably, nearly three-quarters (74%) said they'd struggle to produce a complete report quickly if they were hit with a surprise audit tomorrow.</p><p>The majority (83%) run outdated artifact management systems, often because they're worried that upgrading is risky or painful.</p><h2 id="software-supply-chain-threats-are-growing">Software supply chain threats are growing</h2><p>Weak software supply chain security has become a high-profile issue over the last year, not least with the <a href="https://www.itpro.com/security/cyber-attacks/the-build-pipeline-is-becoming-the-new-frontline-axios-npm-compromise-highlights-growing-software-supply-chain-risks-experts-warn"><u>Axios npm compromise</u></a> that hit earlier this month. </p><p>With threat campaigns including <a href="https://www.itpro.com/security/cyber-attacks/malicious-github-repositories-target-users-with-malware">Shai Hulud 2.0</a> and SANDWORM_MODE specifically targeting the software supply chain via upstream repositories, 44% of respondents said they'd experienced a security incident caused by a third-party dependency.</p><p>The same number said their organization spent over 50 hours per month investigating potential security issues linked to third-party dependencies, whether or not they resulted in a breach.</p><p>“Agentic development is an incredibly powerful way to build software, and teams will be far more productive and write even more software as a result.  That is a good thing, because the world certainly needs more software and more automation," said Weinstein.</p><p>"For enterprises to manage this new velocity and productivity, automated guardrails and context are the new keys to unlock the production of safer, more efficient code.”</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/developers-are-slacking-on-ai-generated-code-safety-heres-why-it-could-come-back-to-haunt-them</link>
                                                                            <description>
                            <![CDATA[ While organizations are aware of the risks, many are spending little time or effort on tracking artifact versions, origins, and security attestations ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">AZq6Xay2YMUB3atnBA4wMX</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/sr6ojAwVjTo7uxdZYcXXZg-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 10 Apr 2026 14:25:48 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:52 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                <author><![CDATA[ ross.kelly@futurenet.com (Ross Kelly) ]]></author>                    <dc:creator><![CDATA[ Ross Kelly ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Y5vrV2V98Np6jHAGmAtCd3-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Ross Kelly is ITPro&#039;s News &amp;amp; Analysis Editor, with a keen interest in cyber security, business leadership and emerging technologies.&lt;/p&gt;
&lt;p&gt;He graduated from Edinburgh Napier University in 2016 with a BA (Hons) in Journalism, and joined ITPro in 2022 after four years working in technology conference research.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In his spare time, Ross enjoys cycling, walking and is an avid reader of history and non-fiction.&lt;/p&gt;
&lt;p&gt;You can contact Ross at ross.kelly@futurenet.com or on &lt;a href=&quot;https://twitter.com/rosswritesetc&quot;&gt;Twitter&lt;/a&gt; and &lt;a href=&quot;https://www.linkedin.com/in/ross-kelly-18a54411a/&quot;&gt;LinkedIn&lt;/a&gt;.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/sr6ojAwVjTo7uxdZYcXXZg-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Female software developer with long dark hair, wearing a striped suit jacket, coding on a desktop computer with multiple screens while co-workers confer in background.]]></media:description>                                                            <media:text><![CDATA[Female software developer with long dark hair, wearing a striped suit jacket, coding on a desktop computer with multiple screens while co-workers confer in background.]]></media:text>
                                <media:title type="plain"><![CDATA[Female software developer with long dark hair, wearing a striped suit jacket, coding on a desktop computer with multiple screens while co-workers confer in background.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/sr6ojAwVjTo7uxdZYcXXZg-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Organizations are taking a slapdash approach to <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated code</a>, with many spending far too little time on oversight, new research suggests. </p><p>The vast majority (93%) of respondents to Cloudsmith's 2026 <a href="https://cloudsmith.com/campaigns/2026-artifact-management-report" target="_blank"><u><em>Artifact Management Report</em></u></a> said their organization was using AI-generated code, more than twice as many as last year. </p><p>Yet despite this sharp increase, around than one-third (31%) spend 10 hours or less per month validating, auditing, or securing it. Indeed, just 58% spend at least 11 hours per month on this front while one-in-twenty said they don't audit AI code at all. </p><p>While <a href="https://www.itpro.com/technology/artificial-intelligence/the-risks-of-open-source-ai-models">AI models</a> have become a leading artifact type, only 12% of organizations are managing them using the same security policies and provenance tracking as traditional binaries, such as language packages and operating system libraries.</p><p>This is despite the fact that organizations are mostly aware of the risks, with only 17% very confident that AI is not introducing new vulnerabilities into their codebase.</p><p>“We are at a huge inflection point in the history of software development. In a matter of months, we’ve gone from, ‘<em>How can AI help me write better code?</em>’ to, ‘<em>How can I help AI write better code?</em>’”, said Glenn Weinstein, CEO of Cloudsmith. </p><p>"But at the same time, <a href="https://www.itpro.com/technology/artificial-intelligence/amazing-ai-tools-to-try-today">AI tools</a> are expanding the attack surface, introducing more open source dependencies. And those same tools are being used by malicious actors to find more vulnerabilities in existing libraries, leading to more CVEs.”</p><h2 id="sloppy-practices-could-come-back-to-haunt-devs">Sloppy practices could come back to haunt devs</h2><p>Poor security practices on this front could have wide-reaching regulatory implications for enterprises, the study warned. </p><p>Under the EU’s <a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra">Cyber Resilience Act (CRA)</a>, organizations are required to provide a detailed assessment 48 hours after becoming aware of a breach – and this includes providing provenance data. </p><p>More than half (53%) of respondents told Cloudsmith they'd need to put in a significant amount of manual effort or time to produce a comprehensive report of artifact versions, origins, and security attestations.</p><p>Only a quarter of engineering teams automatically generate and verify <a href="https://www.itpro.com/security/software-security-overhauled-for-the-better-thanks-to-us-legislation">Software Bills of Materials (SBOMs)</a> at every build, with the rest doing it manually, reactively, or only when an auditor asks. </p><p>Notably, nearly three-quarters (74%) said they'd struggle to produce a complete report quickly if they were hit with a surprise audit tomorrow.</p><p>The majority (83%) run outdated artifact management systems, often because they're worried that upgrading is risky or painful.</p><h2 id="software-supply-chain-threats-are-growing">Software supply chain threats are growing</h2><p>Weak software supply chain security has become a high-profile issue over the last year, not least with the <a href="https://www.itpro.com/security/cyber-attacks/the-build-pipeline-is-becoming-the-new-frontline-axios-npm-compromise-highlights-growing-software-supply-chain-risks-experts-warn"><u>Axios npm compromise</u></a> that hit earlier this month. </p><p>With threat campaigns including <a href="https://www.itpro.com/security/cyber-attacks/malicious-github-repositories-target-users-with-malware">Shai Hulud 2.0</a> and SANDWORM_MODE specifically targeting the software supply chain via upstream repositories, 44% of respondents said they'd experienced a security incident caused by a third-party dependency.</p><p>The same number said their organization spent over 50 hours per month investigating potential security issues linked to third-party dependencies, whether or not they resulted in a breach.</p><p>“Agentic development is an incredibly powerful way to build software, and teams will be far more productive and write even more software as a result.  That is a good thing, because the world certainly needs more software and more automation," said Weinstein.</p><p>"For enterprises to manage this new velocity and productivity, automated guardrails and context are the new keys to unlock the production of safer, more efficient code.”</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Axios npm compromise highlights growing software supply chain risks, experts warn ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Attackers have compromised the npm account of Axios and published malicious versions to spread <a href="https://www.itpro.com/security/30081/what-is-a-trojan-virus">remote access trojans (RATs)</a> to millions of developers.</p><p>Axios is a JavaScript HTTP client and is one of the most popular packages on npm, with more than 100 million weekly downloads. It manages requests between clients, such as browsers or Node.js apps, and servers.</p><p>On Monday, two malicious updates, <em>axios@1.14.1</em> and <em>axios@0.30.3</em>, were published, apparently through the compromise of the npm account of axios’ primary maintainer Jason Saayman. </p><p>The updates were identified almost immediately by several security firms and remained live for around two or three hours. The malicious versions introduce a dependency that executes during installation and deploys a cross‑platform remote access trojan (RAT) targeting macOS, Windows, and <a href="https://www.itpro.com/operating-systems/24841/windows-vs-linux-whats-the-best-operating-system">Linux</a>. </p><p>The <a href="https://www.itpro.com/malware/28076/what-is-malware">malware </a>communicates with a command and control (C2) server to retrieve platform‑specific second‑stage payloads, researchers noted. After execution, it deletes itself and replaces its own package.json with a clean version to evade forensic detection.</p><p>According to StepSecurity, the malicious dependency was staged 18 hours in advance, with separate payloads pre-built for all three operating systems. Both release branches were poisoned within 39 minutes of each other.</p><p>StepSecurity added that within two seconds of npm install, the malware was already calling home to the attacker's server before npm had even finished resolving dependencies -– making this one of the most operationally-sophisticated supply chain attacks ever documented against a top-10 npm package.</p><p>Because there were no git tags, any manual audit of the <a href="https://www.itpro.com/open-source/31833/what-is-github">GitHub </a>repo would have failed to show anything was wrong.</p><h2 id="axios-npm-incident-highlights-supply-chain-dangers">Axios npm incident highlights supply chain dangers</h2><p>Ilkka Turunen, field CTO at Sonatype, said the latest npm-related incident highlights the growing dangers faced by developers globally, with threat actors ramping up attacks. </p><p>“Attackers have figured out they don’t need to compromise the code people trust if they can compromise the trust around it," Turunen said. </p><p>"In this case, the malicious capability was introduced through a staged dependency and designed to erase its own tracks, which made the attack harder to spot and slower to understand. That’s not just malware — it shows a more deliberate and mature playbook."</p><p>Anyone who installed either version before the takedown should assume their system is compromised and is advised to immediately quarantine hosts, implement their full incident response playbook, and rotate all exposed secrets. </p><p>It's not known who is responsible for the compromise, although many researchers are throwing suspicion on a North Korean actor known as UNC1069 that focuses on stealing cryptocurrency via centralized exchanges (CEX), software developers at financial institutions, tech firms, and venture capital funds. </p><p>The supply chain attack marks the latest in a string of attempts to exploit trust in <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> ecosystems, according to Upwind security researcher Avital Harel.</p><p>"The build pipeline is becoming the new frontline. Attackers know that if they can compromise the systems that build and distribute software, they can inherit trust at scale," Harel commented. </p><p>"Organizations should be looking much more closely at CI/CD systems, package dependencies, and developer environments, because that’s increasingly where attackers are placing their bets." </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/cyber-attacks/the-build-pipeline-is-becoming-the-new-frontline-axios-npm-compromise-highlights-growing-software-supply-chain-risks-experts-warn</link>
                                                                            <description>
                            <![CDATA[ Cyber criminals exploited a hijacked maintainer account to compromise one of the world's most widely used JavaScript libraries ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">FtT83GNxmPjbmsmBPsDEnS</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/4XZYfjMuoUwrLG8MTcaQBi-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 01 Apr 2026 10:32:11 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:59 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Cyber Attacks]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Cyber Resilience]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/4XZYfjMuoUwrLG8MTcaQBi-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Cybersecurity concept image showing digital data storage modules with padlock symbols in a storage environment.]]></media:description>                                                            <media:text><![CDATA[Cybersecurity concept image showing digital data storage modules with padlock symbols in a storage environment.]]></media:text>
                                <media:title type="plain"><![CDATA[Cybersecurity concept image showing digital data storage modules with padlock symbols in a storage environment.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/4XZYfjMuoUwrLG8MTcaQBi-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Attackers have compromised the npm account of Axios and published malicious versions to spread <a href="https://www.itpro.com/security/30081/what-is-a-trojan-virus">remote access trojans (RATs)</a> to millions of developers.</p><p>Axios is a JavaScript HTTP client and is one of the most popular packages on npm, with more than 100 million weekly downloads. It manages requests between clients, such as browsers or Node.js apps, and servers.</p><p>On Monday, two malicious updates, <em>axios@1.14.1</em> and <em>axios@0.30.3</em>, were published, apparently through the compromise of the npm account of axios’ primary maintainer Jason Saayman. </p><p>The updates were identified almost immediately by several security firms and remained live for around two or three hours. The malicious versions introduce a dependency that executes during installation and deploys a cross‑platform remote access trojan (RAT) targeting macOS, Windows, and <a href="https://www.itpro.com/operating-systems/24841/windows-vs-linux-whats-the-best-operating-system">Linux</a>. </p><p>The <a href="https://www.itpro.com/malware/28076/what-is-malware">malware </a>communicates with a command and control (C2) server to retrieve platform‑specific second‑stage payloads, researchers noted. After execution, it deletes itself and replaces its own package.json with a clean version to evade forensic detection.</p><p>According to StepSecurity, the malicious dependency was staged 18 hours in advance, with separate payloads pre-built for all three operating systems. Both release branches were poisoned within 39 minutes of each other.</p><p>StepSecurity added that within two seconds of npm install, the malware was already calling home to the attacker's server before npm had even finished resolving dependencies -– making this one of the most operationally-sophisticated supply chain attacks ever documented against a top-10 npm package.</p><p>Because there were no git tags, any manual audit of the <a href="https://www.itpro.com/open-source/31833/what-is-github">GitHub </a>repo would have failed to show anything was wrong.</p><h2 id="axios-npm-incident-highlights-supply-chain-dangers">Axios npm incident highlights supply chain dangers</h2><p>Ilkka Turunen, field CTO at Sonatype, said the latest npm-related incident highlights the growing dangers faced by developers globally, with threat actors ramping up attacks. </p><p>“Attackers have figured out they don’t need to compromise the code people trust if they can compromise the trust around it," Turunen said. </p><p>"In this case, the malicious capability was introduced through a staged dependency and designed to erase its own tracks, which made the attack harder to spot and slower to understand. That’s not just malware — it shows a more deliberate and mature playbook."</p><p>Anyone who installed either version before the takedown should assume their system is compromised and is advised to immediately quarantine hosts, implement their full incident response playbook, and rotate all exposed secrets. </p><p>It's not known who is responsible for the compromise, although many researchers are throwing suspicion on a North Korean actor known as UNC1069 that focuses on stealing cryptocurrency via centralized exchanges (CEX), software developers at financial institutions, tech firms, and venture capital funds. </p><p>The supply chain attack marks the latest in a string of attempts to exploit trust in <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> ecosystems, according to Upwind security researcher Avital Harel.</p><p>"The build pipeline is becoming the new frontline. Attackers know that if they can compromise the systems that build and distribute software, they can inherit trust at scale," Harel commented. </p><p>"Organizations should be looking much more closely at CI/CD systems, package dependencies, and developer environments, because that’s increasingly where attackers are placing their bets." </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ LiteLLM PyPI compromise: Everything we know so far ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Hackers linked to the TeamPCP threat group have reportedly compromised a Python package with more than 95 million monthly downloads.</p><p>LiteLLM is a widely used <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> library that lets developers route requests across <a href="https://www.itpro.com/technology/artificial-intelligence/generative-ai-vs-large-language-models">large language model (LLM)</a> providers through a single API.</p><p>According to researchers at <a href="https://www.endorlabs.com/learn/teampcp-isnt-done" target="_blank"><u>Endor Labs</u></a>, versions 1.82.7 and 1.82.8 on PyPI contain malicious code not present in the upstream GitHub repository. </p><p>Both versions include a backdoored file that decodes and executes a hidden payload the moment the file is imported; and version 1.82.8 goes even further, installing a .pth file that runs the payload on any Python invocation, even if litellm is never imported. </p><p>The attackers are able to harvest credentials such as SSH keys, cloud tokens, Kubernetes secrets, crypto wallets, and .env files, and attempt lateral movement across Kubernetes clusters by deploying privileged pods to every node. </p><p>Researchers also warned that threat actors are able to install a persistent systemd backdoor that polls for additional binaries. The stolen data is then encrypted and sent to an attacker-controlled domain.</p><p>"The infrastructure and tradecraft match TeamPCP, the actor behind a month-long supply chain campaign that has now crossed five ecosystems: GitHub Actions, Docker Hub, npm (CanisterWorm), OpenVSX, and PyP," said Endor researcher Kiran Raj.</p><p>"The pattern is deliberate. TeamPCP has recently targed security-adjacent tools, including Aqua Security's Trivy, a vulnerability scanner, and Checkmarx's KICS, an IaC analyzer, and now an LLM proxy. These tools run in environments that are likely to contain valuable credentials and other secrets, so compromising them gives the attacker broad access."</p><h2 id="malicious-litellm-versions-removed">Malicious LiteLLM versions removed</h2><p>Both malicious LiteLLM versions have now been removed from PyPI. Users are advised to check whether they're running one of the affected versions, and, for 1.82.8 specifically, also check for the .pth file in site-packages.</p><p>They should search for persistence artifacts such as '~/.config/sysmon/sysmon.py' and related systemd services, and inspect systems for suspicious files such as '/tmp/pglog' and '/tmp/.pg_state'. </p><p>Finally, they should check for attacker pods in Kubernetes clusters where Litellm was deployed, and monitor outbound traffic to known attacker domains.</p><p>If compromise is suspected, all credentials on affected systems should be treated as exposed and rotated immediately.</p><h2 id="litellm-breach-linked-to-trivy-compromise">LiteLLM breach linked to Trivy compromise</h2><p>The breach appears to be linked to the recent compromise of Trivy, in which the abuse of a trusted vulnerability scanner in CI/CD pipelines enabled credential theft that was apparently used to poison LiteLLM’s PyPI release chain.</p><p>“Compared with previous attacks involving AI tools, this is one of the more serious recent incidents because it was not just an abuse of model behavior, prompt injection, or an application bug. It’s a software supply-chain compromise that led to malicious package publication, credential theft, and persistence on affected hosts," said Cory Michal, CISO at AppOmni.</p><p>“What makes it especially notable is that the LiteLLM compromise appears to have been downstream fallout from the earlier Trivy breach, meaning attackers may have used one trusted CI/CD compromise to poison another widely used AI-layer dependency, which is exactly the kind of cascading, transitive risk security teams worry about most."</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/litellm-pypi-compromise-everything-we-know-so-far</link>
                                                                            <description>
                            <![CDATA[ The TeamPCP hacking group is believed to have successfully backdoored the package to harvest credentials ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">vtaXFmN8hjj39BM8iGwyKJ</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/P5BaAXwkDNyHNyRDcZNx5E-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 26 Mar 2026 10:56:03 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:59 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/P5BaAXwkDNyHNyRDcZNx5E-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Red warning symbol imposed over computer code denoting a data security compromise.]]></media:description>                                                            <media:text><![CDATA[Red warning symbol imposed over computer code denoting a data security compromise.]]></media:text>
                                <media:title type="plain"><![CDATA[Red warning symbol imposed over computer code denoting a data security compromise.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/P5BaAXwkDNyHNyRDcZNx5E-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Hackers linked to the TeamPCP threat group have reportedly compromised a Python package with more than 95 million monthly downloads.</p><p>LiteLLM is a widely used <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> library that lets developers route requests across <a href="https://www.itpro.com/technology/artificial-intelligence/generative-ai-vs-large-language-models">large language model (LLM)</a> providers through a single API.</p><p>According to researchers at <a href="https://www.endorlabs.com/learn/teampcp-isnt-done" target="_blank"><u>Endor Labs</u></a>, versions 1.82.7 and 1.82.8 on PyPI contain malicious code not present in the upstream GitHub repository. </p><p>Both versions include a backdoored file that decodes and executes a hidden payload the moment the file is imported; and version 1.82.8 goes even further, installing a .pth file that runs the payload on any Python invocation, even if litellm is never imported. </p><p>The attackers are able to harvest credentials such as SSH keys, cloud tokens, Kubernetes secrets, crypto wallets, and .env files, and attempt lateral movement across Kubernetes clusters by deploying privileged pods to every node. </p><p>Researchers also warned that threat actors are able to install a persistent systemd backdoor that polls for additional binaries. The stolen data is then encrypted and sent to an attacker-controlled domain.</p><p>"The infrastructure and tradecraft match TeamPCP, the actor behind a month-long supply chain campaign that has now crossed five ecosystems: GitHub Actions, Docker Hub, npm (CanisterWorm), OpenVSX, and PyP," said Endor researcher Kiran Raj.</p><p>"The pattern is deliberate. TeamPCP has recently targed security-adjacent tools, including Aqua Security's Trivy, a vulnerability scanner, and Checkmarx's KICS, an IaC analyzer, and now an LLM proxy. These tools run in environments that are likely to contain valuable credentials and other secrets, so compromising them gives the attacker broad access."</p><h2 id="malicious-litellm-versions-removed">Malicious LiteLLM versions removed</h2><p>Both malicious LiteLLM versions have now been removed from PyPI. Users are advised to check whether they're running one of the affected versions, and, for 1.82.8 specifically, also check for the .pth file in site-packages.</p><p>They should search for persistence artifacts such as '~/.config/sysmon/sysmon.py' and related systemd services, and inspect systems for suspicious files such as '/tmp/pglog' and '/tmp/.pg_state'. </p><p>Finally, they should check for attacker pods in Kubernetes clusters where Litellm was deployed, and monitor outbound traffic to known attacker domains.</p><p>If compromise is suspected, all credentials on affected systems should be treated as exposed and rotated immediately.</p><h2 id="litellm-breach-linked-to-trivy-compromise">LiteLLM breach linked to Trivy compromise</h2><p>The breach appears to be linked to the recent compromise of Trivy, in which the abuse of a trusted vulnerability scanner in CI/CD pipelines enabled credential theft that was apparently used to poison LiteLLM’s PyPI release chain.</p><p>“Compared with previous attacks involving AI tools, this is one of the more serious recent incidents because it was not just an abuse of model behavior, prompt injection, or an application bug. It’s a software supply-chain compromise that led to malicious package publication, credential theft, and persistence on affected hosts," said Cory Michal, CISO at AppOmni.</p><p>“What makes it especially notable is that the LiteLLM compromise appears to have been downstream fallout from the earlier Trivy breach, meaning attackers may have used one trusted CI/CD compromise to poison another widely used AI-layer dependency, which is exactly the kind of cascading, transitive risk security teams worry about most."</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ NCSC warns vibe coding poses a major risk to businesses ]]></title>
                                                                                                <dc:content><![CDATA[ <p>The head of the UK’s national cybersecurity agency has called for more <a href="https://www.itpro.com/technology/artificial-intelligence/vibe-coding-security-risks-how-to-mitigate"><u>safeguards around vibe coding</u></a>, describing a “fundamental issue with the quality of technology we use".</p><p><a href="https://www.itpro.com/security/ncsc-appoints-new-ceo"><u>Richard Horne</u></a>, chief executive at the <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do"><u>National Cyber Security Centre (NCSC)</u></a> said the international security community needs to balance using AI to reduce collective vulnerability against the risks the technology can introduce to software.</p><p>"The attractions of vibe coding are clear, and disrupting the status quo of manually produced software that is consistently vulnerable is a huge opportunity, but not without risk of its own," he said.</p><p>“The AI tools we use to develop code must be designed and trained from the outset so that they do not introduce or propagate unintended vulnerabilities."</p><p><a href="https://www.itpro.com/security/vulnerability-management-complexity-is-leaving-enterprises-at-serious-risk"><u>Vulnerability management</u></a> approaches are maturing, he said, but not quickly enough. Meanwhile, NCSC research shows that the rate of defects per line of code has remained broadly static – but that the software source code in systems <a href="https://www.ncsc.gov.uk/speech/ncsc-ceo-rsac-speech"><u>doubles on average every 42 months</u></a>, with <a href="https://www.itpro.com/security/organizations-hit-by-90-zero-day-vulnerabilities-last-year"><u>zero day vulnerabilities</u></a> regularly weaponized before organizations have been able to patch for them.</p><p>"The attractions of vibe coding are clear, and disrupting the status quo of manually produced software that is consistently vulnerable is a huge opportunity, but not without risk of its own," he said. </p><p>Horne's speech, at the RSAC Conference in San Francisco, coincided with the publication of a <a href="https://www.ncsc.gov.uk/blogs/vibe-check-ai-may-replace-saas-but-not-for-a-while" target="_blank"><u>blog post</u></a> warning that AI-generated code currently presents “intolerable risks” for many organizations.</p><p>Developers with little or no technical experience often produce code that's unreliable, hard to maintain, or has critical issues.</p><p>Experienced coders, meanwhile, tend to find AI outputs far below the standard they require, while managers responsible for development teams' efforts also report concerns about the quality and maintainability of AI-generated code.</p><p>Obvious safeguards, said the NCSC, include models that write code that is secure by default, and that haven't been developed in such a way as to maliciously introduce issues in code it produces. The way AI is used to review code, both existing human-written code and that which will be written by AI, needs to be examined.</p><p>But there are also more nuanced considerations. </p><p>"How do we use a deterministic architecture (that is, known controls implemented in rules and code, rather than expecting an AI to limit another AI) to limit what code can do even if it is malicious, compromised, or unsafe?" the NCSC wrote.</p><p>"What platforms for hosting AI-generated services (and even human-generated ones) can we design to implement the controls above and protect the organisation and its data even if the code running is of poor quality?"</p><p>There are growing calls for more consideration of how AI can be used to carry out security hygiene such as documentation, test cases, fuzzing and permanently updating threat models for all software.</p><p>Late last year, a survey from Aikido <a href="https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually"><u>found</u></a> that one-in-five CISOs had suffered major incidents because of AI-generated code, with 69% of security leaders, security engineers, and developers across Europe and the US revealing they'd found serious vulnerabilities in AI-written code.</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/ncsc-warns-vibe-coding-poses-a-major-risk</link>
                                                                            <description>
                            <![CDATA[ Vulnerability management approaches are not maturing fast enough to keep up with the downsides of AI-generated code ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">VAecj6CDFoWazXFV5tuCsN</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/mBrtuEnXSQksScMmrYfW2B-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 25 Mar 2026 12:54:18 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:51 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/mBrtuEnXSQksScMmrYfW2B-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[A visualization of bue code in a futuristic display, lit by red light, to represent vibe coding risks.]]></media:description>                                                            <media:text><![CDATA[A visualization of bue code in a futuristic display, lit by red light, to represent vibe coding risks.]]></media:text>
                                <media:title type="plain"><![CDATA[A visualization of bue code in a futuristic display, lit by red light, to represent vibe coding risks.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/mBrtuEnXSQksScMmrYfW2B-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The head of the UK’s national cybersecurity agency has called for more <a href="https://www.itpro.com/technology/artificial-intelligence/vibe-coding-security-risks-how-to-mitigate"><u>safeguards around vibe coding</u></a>, describing a “fundamental issue with the quality of technology we use".</p><p><a href="https://www.itpro.com/security/ncsc-appoints-new-ceo"><u>Richard Horne</u></a>, chief executive at the <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do"><u>National Cyber Security Centre (NCSC)</u></a> said the international security community needs to balance using AI to reduce collective vulnerability against the risks the technology can introduce to software.</p><p>"The attractions of vibe coding are clear, and disrupting the status quo of manually produced software that is consistently vulnerable is a huge opportunity, but not without risk of its own," he said.</p><p>“The AI tools we use to develop code must be designed and trained from the outset so that they do not introduce or propagate unintended vulnerabilities."</p><p><a href="https://www.itpro.com/security/vulnerability-management-complexity-is-leaving-enterprises-at-serious-risk"><u>Vulnerability management</u></a> approaches are maturing, he said, but not quickly enough. Meanwhile, NCSC research shows that the rate of defects per line of code has remained broadly static – but that the software source code in systems <a href="https://www.ncsc.gov.uk/speech/ncsc-ceo-rsac-speech"><u>doubles on average every 42 months</u></a>, with <a href="https://www.itpro.com/security/organizations-hit-by-90-zero-day-vulnerabilities-last-year"><u>zero day vulnerabilities</u></a> regularly weaponized before organizations have been able to patch for them.</p><p>"The attractions of vibe coding are clear, and disrupting the status quo of manually produced software that is consistently vulnerable is a huge opportunity, but not without risk of its own," he said. </p><p>Horne's speech, at the RSAC Conference in San Francisco, coincided with the publication of a <a href="https://www.ncsc.gov.uk/blogs/vibe-check-ai-may-replace-saas-but-not-for-a-while" target="_blank"><u>blog post</u></a> warning that AI-generated code currently presents “intolerable risks” for many organizations.</p><p>Developers with little or no technical experience often produce code that's unreliable, hard to maintain, or has critical issues.</p><p>Experienced coders, meanwhile, tend to find AI outputs far below the standard they require, while managers responsible for development teams' efforts also report concerns about the quality and maintainability of AI-generated code.</p><p>Obvious safeguards, said the NCSC, include models that write code that is secure by default, and that haven't been developed in such a way as to maliciously introduce issues in code it produces. The way AI is used to review code, both existing human-written code and that which will be written by AI, needs to be examined.</p><p>But there are also more nuanced considerations. </p><p>"How do we use a deterministic architecture (that is, known controls implemented in rules and code, rather than expecting an AI to limit another AI) to limit what code can do even if it is malicious, compromised, or unsafe?" the NCSC wrote.</p><p>"What platforms for hosting AI-generated services (and even human-generated ones) can we design to implement the controls above and protect the organisation and its data even if the code running is of poor quality?"</p><p>There are growing calls for more consideration of how AI can be used to carry out security hygiene such as documentation, test cases, fuzzing and permanently updating threat models for all software.</p><p>Late last year, a survey from Aikido <a href="https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually"><u>found</u></a> that one-in-five CISOs had suffered major incidents because of AI-generated code, with 69% of security leaders, security engineers, and developers across Europe and the US revealing they'd found serious vulnerabilities in AI-written code.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Channel partners are sleepwalking into an AI code generation trap  ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Managed Service Providers (MSPs) are increasingly being asked to do more than shift products. Clients want complete development stacks, and rely on their channel partners to provide a secure, reliable, and fully-featured line-up of systems. In the age of AI-assisted development, that expectation is becoming a liability.</p><p>The speed at which AI code generation tools have been adopted is remarkable. The risk embedded in that adoption is not yet well understood, particularly by the channel partners who are recommending and deploying those tools on behalf of clients.</p><h2 id="buy-efficiency-inherit-vulnerabilities">Buy efficiency, inherit vulnerabilities</h2><p>A <a href="https://cset.georgetown.edu/publication/cybersecurity-risks-of-ai-generated-code/"><u>study by CSET</u></a> found that nearly half of AI-generated code snippets contained security vulnerabilities. That alone should give channel partners reason to pause. The problem compounds when you consider how few organisations are asking the right questions before deploying AI tools: the World Economic Forum found that <a href="https://www.weforum.org/"><u>67% of organisations fail to assess the security of AI tools before deployment</u></a>.</p><p>The AI tools generate flawed code, and most organisations are deploying them without proper validation. For the channel, there creates double exposure: you recommend the stack, and in many cases, manage it too. So if it’s not trustworthy and reliable, you’re left carrying the risk.</p><p>The reasonable assumption has been that, as AI models grow more sophisticated, the quality of their outputs will improve accordingly. That assumption doesn’t hold in practice <a href="https://openai.com/index/o3-o4-mini-system-card/"><u>OpenAI's own reasoning models</u></a> found that hallucination rates more than doubled between o1 and o3, rising from 16% to 33% on factual accuracy benchmarks. The smaller o4-mini model hallucinated at 48%. More capability has consistently led to more errors. </p><p>In code generation, a hallucination is not immediately clear. It looks like a complete, well-structured function that compiles and often passes a surface-level review. Then it fails in production, or introduces a security vulnerability that sits quietly until someone finds it. By then, the damage is often already done.</p><h2 id="ai-risk-what-it-means-for-channel-partners">AI Risk: What it means for channel partners</h2><p>MSPs now operate in a market where clients expect AI to be embedded in the development toolchain, and the partners who can deliver a coherent, integrated AI development stack will win the business.</p><p>But partners who win business without understanding what they are recommending are creating a problem for themselves. When a client's code is compromised because an AI tool produced insecure authentication logic, the conversation about responsibility will ultimately come back to whoever put the stack together.</p><p>This is an avoidable problem, and with the right approach, creates a commercial opportunity. MSPs who get ahead of AI governance can both protect themselves and strengthen their market position. Clients are increasingly aware that AI tools carry risk; most simply don’t know what to do about it. A partner who can articulate that risk clearly and demonstrate a clear way to manage it becomes indispensable.</p><h2 id="building-a-secure-ai-development-stack-what-it-takes">Building a secure AI development stack: what it takes</h2><p>The key is a strong foundation. Before recommending any AI development tool, MSPs should ensure clients have deployed strong pipelines to catch risks early, clear policies that limit exposure, and have trained their teams to work securely with AI.</p><p>Modern Continuous Integration and Continuous Delivery (C/CD) platforms must be a part of any development stack, providing the infrastructure that reliably detects issues before they reach production. These should be supported by strong DevOps practices that map workflows, standardise processes, and bring code generation and integration into one system.</p><p>Shadow AI (use of AI tools without approval or insight) is an immediate threat to this foundation. Development teams routinely adopt tools without procurement or security review. Code written with unapproved tools ends up in production, and the intellectual property generated with those tools may not be fully owned by the client. MSPs managing development environments need tooling that surfaces which AI tools are actually in use, not just what’s approved, but what developers run day to day.</p><p>The pipeline itself also needs to be designed for AI use. Modern CI/CD platforms can apply specific scrutiny to AI-generated code: automated vulnerability scanning calibrated for LLM failure modes, static analysis capable of detecting AI-generated patterns, and mandatory review checkpoints before AI-assisted code reaches production. These are capabilities that already exist; they just need to be configured with AI outputs in mind.</p><p>The crucial point is that AI-generated code tends to look clean, which is precisely what makes it so dangerous. Developer-written code, with its visible imperfections, prompts scrutiny. AI-generated code does not, and teams unconsciously extend the trust it has not earned. Building structured review into the pipeline is not a drag on velocity. It is the only way to deploy AI at speed without accumulating technical and security debt that compounds with every release.</p><h2 id="building-differentiation-through-security">Building differentiation through security </h2><p>MSPs are well placed to turn AI governance and validation into a core service offering. Clients are already aware that AI tools carry risk. What they lack is a partner who can quantify it and help them manage it without slowing things down. </p><p>Partners that provide that clarity will own the client relationship in the future, setting a high standard of trust that no product margin can buy.</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/business/business-strategy/channel-partners-are-sleepwalking-into-an-ai-code-generation-trap</link>
                                                                            <description>
                            <![CDATA[ Channel partners risk security failures by deploying AI code tools without proper validation ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">3SR7Bk4cw2JXtd8z5aHR9d</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/mUyZnUdbkdkCc9yQXwt7cX-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 24 Mar 2026 08:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:55 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Business Strategy]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Business]]></category>
                                                                                                                    <dc:creator><![CDATA[ Barnabás Birmacher ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/UyPTnQeSfoQRMsKgrDBdGQ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/mUyZnUdbkdkCc9yQXwt7cX-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[An abstract image of green code with two blue speech bubbles on top, one reading &#039;AI&#039; and the other showing three dots.]]></media:description>                                                            <media:text><![CDATA[An abstract image of green code with two blue speech bubbles on top, one reading &#039;AI&#039; and the other showing three dots.]]></media:text>
                                <media:title type="plain"><![CDATA[An abstract image of green code with two blue speech bubbles on top, one reading &#039;AI&#039; and the other showing three dots.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/mUyZnUdbkdkCc9yQXwt7cX-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Managed Service Providers (MSPs) are increasingly being asked to do more than shift products. Clients want complete development stacks, and rely on their channel partners to provide a secure, reliable, and fully-featured line-up of systems. In the age of AI-assisted development, that expectation is becoming a liability.</p><p>The speed at which AI code generation tools have been adopted is remarkable. The risk embedded in that adoption is not yet well understood, particularly by the channel partners who are recommending and deploying those tools on behalf of clients.</p><h2 id="buy-efficiency-inherit-vulnerabilities">Buy efficiency, inherit vulnerabilities</h2><p>A <a href="https://cset.georgetown.edu/publication/cybersecurity-risks-of-ai-generated-code/"><u>study by CSET</u></a> found that nearly half of AI-generated code snippets contained security vulnerabilities. That alone should give channel partners reason to pause. The problem compounds when you consider how few organisations are asking the right questions before deploying AI tools: the World Economic Forum found that <a href="https://www.weforum.org/"><u>67% of organisations fail to assess the security of AI tools before deployment</u></a>.</p><p>The AI tools generate flawed code, and most organisations are deploying them without proper validation. For the channel, there creates double exposure: you recommend the stack, and in many cases, manage it too. So if it’s not trustworthy and reliable, you’re left carrying the risk.</p><p>The reasonable assumption has been that, as AI models grow more sophisticated, the quality of their outputs will improve accordingly. That assumption doesn’t hold in practice <a href="https://openai.com/index/o3-o4-mini-system-card/"><u>OpenAI's own reasoning models</u></a> found that hallucination rates more than doubled between o1 and o3, rising from 16% to 33% on factual accuracy benchmarks. The smaller o4-mini model hallucinated at 48%. More capability has consistently led to more errors. </p><p>In code generation, a hallucination is not immediately clear. It looks like a complete, well-structured function that compiles and often passes a surface-level review. Then it fails in production, or introduces a security vulnerability that sits quietly until someone finds it. By then, the damage is often already done.</p><h2 id="ai-risk-what-it-means-for-channel-partners">AI Risk: What it means for channel partners</h2><p>MSPs now operate in a market where clients expect AI to be embedded in the development toolchain, and the partners who can deliver a coherent, integrated AI development stack will win the business.</p><p>But partners who win business without understanding what they are recommending are creating a problem for themselves. When a client's code is compromised because an AI tool produced insecure authentication logic, the conversation about responsibility will ultimately come back to whoever put the stack together.</p><p>This is an avoidable problem, and with the right approach, creates a commercial opportunity. MSPs who get ahead of AI governance can both protect themselves and strengthen their market position. Clients are increasingly aware that AI tools carry risk; most simply don’t know what to do about it. A partner who can articulate that risk clearly and demonstrate a clear way to manage it becomes indispensable.</p><h2 id="building-a-secure-ai-development-stack-what-it-takes">Building a secure AI development stack: what it takes</h2><p>The key is a strong foundation. Before recommending any AI development tool, MSPs should ensure clients have deployed strong pipelines to catch risks early, clear policies that limit exposure, and have trained their teams to work securely with AI.</p><p>Modern Continuous Integration and Continuous Delivery (C/CD) platforms must be a part of any development stack, providing the infrastructure that reliably detects issues before they reach production. These should be supported by strong DevOps practices that map workflows, standardise processes, and bring code generation and integration into one system.</p><p>Shadow AI (use of AI tools without approval or insight) is an immediate threat to this foundation. Development teams routinely adopt tools without procurement or security review. Code written with unapproved tools ends up in production, and the intellectual property generated with those tools may not be fully owned by the client. MSPs managing development environments need tooling that surfaces which AI tools are actually in use, not just what’s approved, but what developers run day to day.</p><p>The pipeline itself also needs to be designed for AI use. Modern CI/CD platforms can apply specific scrutiny to AI-generated code: automated vulnerability scanning calibrated for LLM failure modes, static analysis capable of detecting AI-generated patterns, and mandatory review checkpoints before AI-assisted code reaches production. These are capabilities that already exist; they just need to be configured with AI outputs in mind.</p><p>The crucial point is that AI-generated code tends to look clean, which is precisely what makes it so dangerous. Developer-written code, with its visible imperfections, prompts scrutiny. AI-generated code does not, and teams unconsciously extend the trust it has not earned. Building structured review into the pipeline is not a drag on velocity. It is the only way to deploy AI at speed without accumulating technical and security debt that compounds with every release.</p><h2 id="building-differentiation-through-security">Building differentiation through security </h2><p>MSPs are well placed to turn AI governance and validation into a core service offering. Clients are already aware that AI tools carry risk. What they lack is a partner who can quantify it and help them manage it without slowing things down. </p><p>Partners that provide that clarity will own the client relationship in the future, setting a high standard of trust that no product margin can buy.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Surging third-party risks create software vulnerability headaches for developer teams ]]></title>
                                                                                                <dc:content><![CDATA[ <p>The overwhelming majority of organizations are running software with known, exploitable vulnerabilities, as security risk increases across the software delivery lifecycle.</p><p>Datadog's 2026 <a href="https://www.datadoghq.com/state-of-devsecops/" target="_blank"><u><em>State of DevSecOps </em></u></a>report indicates that 87% of organizations have at least one known exploitable vulnerability in deployed services - a problem that's most visible in Java services, at 59%, with .NET at 47% and Rust at 40%.</p><p>More than four-in-ten (42%) services rely on libraries that are no longer actively maintained. Notably, the median dependency is 278 days behind the latest major version, compared with 215 days behind last year. </p><p>Java and Ruby were 492 days behind and 357 days behind, respectively.</p><p>Services using end-of-life language versions face exploitable vulnerabilities in 50% of cases, Datadog noted, compared with 31% for supported versions.</p><p>Half of organizations adopt new library versions within 24 hours of release, but while this might seem like a good thing, that's not always the case.</p><p>"When factoring in <a href="https://www.itpro.com/strategy/28710/what-is-the-supply-chain-1">supply chain</a> compromises, updating to a new version within a day of release can have a negative impact on the overall security of an application due to the potential to unknowingly install malicious software," the researchers warned.</p><p>Meanwhile, only 4% of organizations pin all public GitHub Actions to a specific version using commit hashes, leaving <a href="https://www.itpro.com/development/32887/what-is-continuous-integration">CI/CD</a> pipelines vulnerable to silent code changes.</p><p>“The way software is built has fundamentally changed, but security practices haven’t kept up,” said Andrew Krug, head of security advocacy at Datadog. </p><p>“<a href="https://www.itpro.com/development/devops/354215/what-is-devsecops-and-why-is-it-important">DevSecOps </a>teams are caught between moving too slowly and moving too fast. Go slow, and outdated software accumulates known vulnerabilities. Go fast, and automation can introduce unvetted code," Krug added.</p><p>"The real challenge, though, isn’t speed - it’s clarity. As environments grow more complex, AI-assisted workflows help ensure top priorities get attention first.”</p><h2 id="alert-fatigue-is-rising">Alert fatigue is rising</h2><p>Researchers warned the volume of alerts is obscuring real risk: while vulnerability alerts continue to rise, most don't represent immediate business risk, with only 18% of vulnerabilities labeled “critical” remaining critical once runtime context is applied.</p><p>“When almost everything is labeled ‘critical’, nothing is,” said Krug. “Teams get paged for noise while threats that pose real risk slip through. Without context, prioritization becomes harder - leading to burnout, slower response times and accumulated risk. Teams need better visibility into what actually requires action.”</p><iframe allow="" height="200px" width="100%" id="" style="" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/" src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/"></iframe><p>Just last week, Veracode released research indicating that <a href="https://www.itpro.com/software/enterprises-still-cant-get-a-handle-on-software-security-debt-and-its-only-going-to-get-worse">82% of organizations are struggling with high levels of security debt</a>, up by 11% compared with last year.</p><p>Of these, 60% have security debt defined as “critical” - representing accumulated vulnerabilities that would be severe enough to cause catastrophic damage to an organization if exploited. </p><p>Third-party libraries and <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> dependencies were behind 66% of the most dangerous, longest-lived vulnerabilities, the researchers said.</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/surging-third-party-risks-create-software-vulnerability-headaches-for-developer-teams</link>
                                                                            <description>
                            <![CDATA[ Security risk is increasing across the software delivery lifecycle as development relies more heavily on third-party components ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">NRYDAZEYQQJ9opUzcnipJ9</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/XaXuXbh2yGMtZCAgBZ8iQY-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 04 Mar 2026 09:03:29 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:21 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/XaXuXbh2yGMtZCAgBZ8iQY-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Blue-colored binary code on a computer screen with pink fiber optic cables touching screen. ]]></media:description>                                                            <media:text><![CDATA[Blue-colored binary code on a computer screen with pink fiber optic cables touching screen. ]]></media:text>
                                <media:title type="plain"><![CDATA[Blue-colored binary code on a computer screen with pink fiber optic cables touching screen. ]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/XaXuXbh2yGMtZCAgBZ8iQY-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The overwhelming majority of organizations are running software with known, exploitable vulnerabilities, as security risk increases across the software delivery lifecycle.</p><p>Datadog's 2026 <a href="https://www.datadoghq.com/state-of-devsecops/" target="_blank"><u><em>State of DevSecOps </em></u></a>report indicates that 87% of organizations have at least one known exploitable vulnerability in deployed services - a problem that's most visible in Java services, at 59%, with .NET at 47% and Rust at 40%.</p><p>More than four-in-ten (42%) services rely on libraries that are no longer actively maintained. Notably, the median dependency is 278 days behind the latest major version, compared with 215 days behind last year. </p><p>Java and Ruby were 492 days behind and 357 days behind, respectively.</p><p>Services using end-of-life language versions face exploitable vulnerabilities in 50% of cases, Datadog noted, compared with 31% for supported versions.</p><p>Half of organizations adopt new library versions within 24 hours of release, but while this might seem like a good thing, that's not always the case.</p><p>"When factoring in <a href="https://www.itpro.com/strategy/28710/what-is-the-supply-chain-1">supply chain</a> compromises, updating to a new version within a day of release can have a negative impact on the overall security of an application due to the potential to unknowingly install malicious software," the researchers warned.</p><p>Meanwhile, only 4% of organizations pin all public GitHub Actions to a specific version using commit hashes, leaving <a href="https://www.itpro.com/development/32887/what-is-continuous-integration">CI/CD</a> pipelines vulnerable to silent code changes.</p><p>“The way software is built has fundamentally changed, but security practices haven’t kept up,” said Andrew Krug, head of security advocacy at Datadog. </p><p>“<a href="https://www.itpro.com/development/devops/354215/what-is-devsecops-and-why-is-it-important">DevSecOps </a>teams are caught between moving too slowly and moving too fast. Go slow, and outdated software accumulates known vulnerabilities. Go fast, and automation can introduce unvetted code," Krug added.</p><p>"The real challenge, though, isn’t speed - it’s clarity. As environments grow more complex, AI-assisted workflows help ensure top priorities get attention first.”</p><h2 id="alert-fatigue-is-rising">Alert fatigue is rising</h2><p>Researchers warned the volume of alerts is obscuring real risk: while vulnerability alerts continue to rise, most don't represent immediate business risk, with only 18% of vulnerabilities labeled “critical” remaining critical once runtime context is applied.</p><p>“When almost everything is labeled ‘critical’, nothing is,” said Krug. “Teams get paged for noise while threats that pose real risk slip through. Without context, prioritization becomes harder - leading to burnout, slower response times and accumulated risk. Teams need better visibility into what actually requires action.”</p><iframe allow="" height="200px" width="100%" id="" style="" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/" src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/"></iframe><p>Just last week, Veracode released research indicating that <a href="https://www.itpro.com/software/enterprises-still-cant-get-a-handle-on-software-security-debt-and-its-only-going-to-get-worse">82% of organizations are struggling with high levels of security debt</a>, up by 11% compared with last year.</p><p>Of these, 60% have security debt defined as “critical” - representing accumulated vulnerabilities that would be severe enough to cause catastrophic damage to an organization if exploited. </p><p>Third-party libraries and <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> dependencies were behind 66% of the most dangerous, longest-lived vulnerabilities, the researchers said.</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Enterprises still can't get a handle on software security debt ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Four-in-five organizations are drowning in <a href="https://www.itpro.com/software/software-security-code-of-practice-ncsc-announcement">software security</a> debt, new research shows, and the backlog is only getting worse.</p><p>More than eight-in-ten (82%) of organizations told Veracode that they're now contending with cumbersome levels of security debt, marking an 11% increase compared to last year. </p><p>Of those, 60% have security debt defined as “critical”, representing accumulated vulnerabilities severe enough to cause catastrophic damage to an organization if exploited. </p><p>Findings from the company's <a href="https://www.veracode.com/resources/analyst-reports/state-of-software-security-2026/?utm_source=veracode&amp;utm_medium=press-release&amp;utm_campaign=2026-soss-report&amp;utm_content=2026-state-of-software-security-report" target="_blank"><u><em>2026 State of Software Security Report</em></u></a> show the backlog of unresolved vulnerabilities is growing faster than teams can eliminate it. </p><p>Moreover, the problem is only made worse by a 36% year-over-year spike in high-risk vulnerabilities, categorized as flaws that are both severe and highly exploitable. </p><p>"The speed of software development has skyrocketed, meaning the pace of flaw creation is outstripping the current capacity for remediation,” said Chris Wysopal, chief security evangelist at Veracode. </p><p>“Despite marginal gains in fix rates, security debt is becoming a much larger issue for many organizations." </p><p>Organizations are discovering more vulnerabilities as their testing programs mature and expand. Meanwhile, the accelerating pace of software releases creates a continuous stream of new code before existing vulnerabilities can be addressed. </p><h2 id="software-security-debt-exacerbated-by-ai">Software security debt exacerbated by AI</h2><p>Notably, Veracode found the growing technical complexity of applications, particularly those incorporating <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated code</a> and extensive third-party dependencies, makes remediation more complex and resource-intensive.</p><p>Researchers said a 20% year-over-year increase in critical <a href="https://www.itpro.com/security/using-ai-to-code-watch-your-security-debt">security debt</a> suggests that the accumulation of risky vulnerabilities older than a year is outpacing remediation capacity - causing an urgent need to rethink how backlogs are managed. </p><p>Third-party libraries and open-source dependencies were behind 66% of the most dangerous, longest-lived vulnerabilities, the researchers said, while AI development is introducing new high-risk vulnerability patterns at scale.</p><p>"Now that <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>has taken software development velocity to an unprecedented level, enterprises must ensure they’re making deliberate, intelligent choices to stem the tide of flaws and minimize their risk," said Wysopal. </p><p>The rise in flaws classed as both “severe” and “highly exploitable” means organizations need to shift from generic severity scoring to prioritization based on real-world attack potential, advised Veracode. </p><p>As such, researchers called for a shift from simple detection toward a more strategic framework of <em>Prioritize, Protect, and Prove</em>. </p><p>This approach enables organizations to prioritize their most valuable systems and applications, such as those holding sensitive data, delivering core services, or impacting overall operations.  </p><p>“We are at an inflection point where running faster on the treadmill of <a href="https://www.itpro.com/security/27713/the-importance-and-benefits-of-effective-patch-management">vulnerability management</a> is no longer a viable strategy. Success requires a deliberate shift,” said Wysopal.</p><p>"Teams must prioritize the 11.3% of flaws that pose real-world danger, protect their critical assets through automated remediation, and prove that their security posture meets the rigorous demands of modern compliance. It is not about fixing everything; it is about managing security debt by minimizing its most consequential risks.” </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/enterprises-still-cant-get-a-handle-on-software-security-debt-and-its-only-going-to-get-worse</link>
                                                                            <description>
                            <![CDATA[ New research shows that the backlog of unresolved vulnerabilities is growing faster than organizations can deal with it ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">mRA4wEYznYXFTjXsxeE4tK</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/83RNMayQZYwRtkjeRbjqDX-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 24 Feb 2026 15:15:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:21 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Workplace Technology]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/83RNMayQZYwRtkjeRbjqDX-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Female developer working in a dimly lit room on a desktop computer while assessing software security debt. ]]></media:description>                                                            <media:text><![CDATA[Female developer working in a dimly lit room on a desktop computer while assessing software security debt. ]]></media:text>
                                <media:title type="plain"><![CDATA[Female developer working in a dimly lit room on a desktop computer while assessing software security debt. ]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/83RNMayQZYwRtkjeRbjqDX-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Four-in-five organizations are drowning in <a href="https://www.itpro.com/software/software-security-code-of-practice-ncsc-announcement">software security</a> debt, new research shows, and the backlog is only getting worse.</p><p>More than eight-in-ten (82%) of organizations told Veracode that they're now contending with cumbersome levels of security debt, marking an 11% increase compared to last year. </p><p>Of those, 60% have security debt defined as “critical”, representing accumulated vulnerabilities severe enough to cause catastrophic damage to an organization if exploited. </p><p>Findings from the company's <a href="https://www.veracode.com/resources/analyst-reports/state-of-software-security-2026/?utm_source=veracode&amp;utm_medium=press-release&amp;utm_campaign=2026-soss-report&amp;utm_content=2026-state-of-software-security-report" target="_blank"><u><em>2026 State of Software Security Report</em></u></a> show the backlog of unresolved vulnerabilities is growing faster than teams can eliminate it. </p><p>Moreover, the problem is only made worse by a 36% year-over-year spike in high-risk vulnerabilities, categorized as flaws that are both severe and highly exploitable. </p><p>"The speed of software development has skyrocketed, meaning the pace of flaw creation is outstripping the current capacity for remediation,” said Chris Wysopal, chief security evangelist at Veracode. </p><p>“Despite marginal gains in fix rates, security debt is becoming a much larger issue for many organizations." </p><p>Organizations are discovering more vulnerabilities as their testing programs mature and expand. Meanwhile, the accelerating pace of software releases creates a continuous stream of new code before existing vulnerabilities can be addressed. </p><h2 id="software-security-debt-exacerbated-by-ai">Software security debt exacerbated by AI</h2><p>Notably, Veracode found the growing technical complexity of applications, particularly those incorporating <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated code</a> and extensive third-party dependencies, makes remediation more complex and resource-intensive.</p><p>Researchers said a 20% year-over-year increase in critical <a href="https://www.itpro.com/security/using-ai-to-code-watch-your-security-debt">security debt</a> suggests that the accumulation of risky vulnerabilities older than a year is outpacing remediation capacity - causing an urgent need to rethink how backlogs are managed. </p><p>Third-party libraries and open-source dependencies were behind 66% of the most dangerous, longest-lived vulnerabilities, the researchers said, while AI development is introducing new high-risk vulnerability patterns at scale.</p><p>"Now that <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>has taken software development velocity to an unprecedented level, enterprises must ensure they’re making deliberate, intelligent choices to stem the tide of flaws and minimize their risk," said Wysopal. </p><p>The rise in flaws classed as both “severe” and “highly exploitable” means organizations need to shift from generic severity scoring to prioritization based on real-world attack potential, advised Veracode. </p><p>As such, researchers called for a shift from simple detection toward a more strategic framework of <em>Prioritize, Protect, and Prove</em>. </p><p>This approach enables organizations to prioritize their most valuable systems and applications, such as those holding sensitive data, delivering core services, or impacting overall operations.  </p><p>“We are at an inflection point where running faster on the treadmill of <a href="https://www.itpro.com/security/27713/the-importance-and-benefits-of-effective-patch-management">vulnerability management</a> is no longer a viable strategy. Success requires a deliberate shift,” said Wysopal.</p><p>"Teams must prioritize the 11.3% of flaws that pose real-world danger, protect their critical assets through automated remediation, and prove that their security posture meets the rigorous demands of modern compliance. It is not about fixing everything; it is about managing security debt by minimizing its most consequential risks.” </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Securing the supply chain:  Why zero trust and recovery readiness are non-negotiable ]]></title>
                                                                                                <dc:content><![CDATA[ <p>A stereotypical view of cybersecurity extends the physical security metaphor, with servers bolted down with chains and only the most privileged employees allowed anywhere near them. However, doing cybersecurity thoroughly now encompasses entire supply chains, with weak links across suppliers, channel partners, and Managed Service Providers (MSPs) causing exploitable vulnerabilities of monumental proportions. </p><p>What’s often misunderstood is that many channel partners and MSPs sit directly in the middle of the modern supply chain. They frequently hold elevated access into multiple customer environments, operate critical components of those environments, and act as extensions of internal IT teams. This makes them unusual actors in the security ecosystem: they are simultaneously prime targets for attackers and frontline defenders for the organizations they support.</p><p>The cyber attacks that plagued numerous UK companies in 2025, including The Co-op, Harrods, M&amp;S, and Jaguar Land Rover, forced many organizations to re-examine their security posture as the perimeters are redrawn so much more broadly. The M&amp;S incident, which rendered online systems inoperable for weeks and led to a £300 million profitability hit, originated via a third-party supplier. And most recently, <a href="https://www.itpro.com/security/data-breaches/salesforce-customers-face-second-third-party-incident-this-year-with-gainsight-breach"><u>Salesforce confirmed</u></a> they have faced two third-party incidents in one year, via its SaaS partner Gainsight. </p><p><a href="https://static.adaptavistassets.com/downloads/adaptavist_crowdstrike_report.pdf"><u>Research</u></a> we conducted before these high-profile incidents indicated that 42% of organizations had concerns about vendors triggering major cyber incidents. Given the recent supply chain breaches we have seen, we suspect that this figure is now underrepresentative. Even organizations that have zero-trust architecture and state-of-the-art disaster recovery plans are still vulnerable to human weaknesses across their whole extended supply chain.</p><p>These examples, among many others, highlight how much more complex the challenge is now: what happens when the breach originates with a partner who has deep, sometimes privileged access into your environment?</p><h2 id="channel-partners-and-msps-are-part-of-the-infrastructure">Channel partners and MSPs are part of the infrastructure</h2><p>For many organizations, channel partners and MSPs are core building blocks of the operational estate. They manage cloud platforms, identity systems, monitoring tools, development pipelines, endpoint fleets, and security controls. In other words, they are part of the infrastructure.</p><p>This interconnectedness means that if an MSP is compromised, attackers may gain horizontal access to the environments of multiple customers at once. <a href="https://en.wikipedia.org/wiki/Kaseya_VSA_ransomware_attack"><u>The Kaseya attack in 2021</u></a> demonstrated this at a global scale, but 2025 has shown it’s now a mainstream, recurring risk.</p><p>As a result, organizations must shift their mindset from “suppliers supporting the business” to “suppliers embedded inside the business architecture.” Visibility, governance, and shared security controls across MSP-managed systems are no longer optional but essential for maximum protection.</p><h2 id="protecting-the-human-layer">Protecting the human layer</h2><p>Recent breaches have been attributed to human vulnerabilities in organizations that supply products and services to others. The M&amp;S incident appears to have been borne out of a social engineering tactic, giving an entry point into the organization that bypassed regular technical defences. These attacks are successful not through sophisticated technical exploitation but by manipulating individuals who already have legitimate access to systems.</p><p>Artificial intelligence (AI) has amplified these risks by scaling up more sophisticated social engineering attacks. AI-powered tools enable attackers to create more convincing phishing emails, generate realistic deepfake communications, and personalise attacks based on information gathered from social media and other public sources. AI has effectively lowered the barrier to entry for cybercriminals and also increased the potential impact of their activities.</p><p>While many organizations have invested heavily in internal cyber-awareness programmes, the new reality is that every supplier and MSP with environment access must be held to the same behavioural and security standards. Regular compliance checks, audits, and zero-trust approaches must be extended to the partner ecosystem. Without continuous validation, the most secure organization may still be exposed through a partner’s weakest link.</p><h2 id="the-importance-of-resilience-and-recovery">The importance of resilience and recovery</h2><p>After the security challenges of 2025, it's naive for anyone to believe that a complete modern security posture will prevent every breach. Beyond prevention, organizations must be able to detect, respond to, and recover from threats, including those triggered within their partner ecosystem.</p><p>This is where visibility becomes critical. Organizations need centralized oversight of MSP-managed systems, identity access, configuration drift, and partner-initiated changes. Hidden dependencies, particularly those controlled by partners, can dramatically extend downtime if they aren’t identified and tested in advance.</p><p>Our research showed big gaps in organizations being prepared to recover, with 84% of them lacking a decent incident response plan, and only 16% finding them effective if they had them. This means that most organizations need to find time and effort to actually test their plans before they're really needed. </p><p>Organizations need to define Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs) for critical systems, and to have their eyes open to systems that might be hidden dependencies, including those run by third parties or their staff. These need to be tested regularly through drills - this helps identify dependencies and other challenges that may not be apparent when things are running normally.</p><p>Critical systems also require offline, immutable backups that cannot be compromised during an attack. Too often, organizations discover after an attack that backups managed or maintained by partners were incomplete, inaccessible, or misconfigured.</p><h2 id="conclusion">Conclusion</h2><p>The events of 2025 show that cyber attacks are increasingly sophisticated and now exploit not only technical vulnerabilities inside an organization but also those embedded throughout its supply chain. MSPs and channel partners, sitting at the centre of this ecosystem, have become both high-value targets and vital protectors.</p><p>Effective cybersecurity now requires that these organizations and their partners give equal attention to prevention and recovery capabilities, with the time taken to get back online having similar importance as the essential preventive measures. </p><p>Those that fully understand and lock down their supply chain from a security perspective, implement strict access controls with zero-trust architecture, and have properly tested recovery plans will have the best chance of surviving the next wave of threats to cybersecurity.</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/securing-the-supply-chain-why-zero-trust-and-recovery-readiness-are-non-negotiable</link>
                                                                            <description>
                            <![CDATA[ To prevent supply chain attacks, suppliers must be embedded in trusted business architecture ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">eXy3QjJKkFye7rubkZF8wE</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/DD7oSG7mL3LVWBrNQQCQu7-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 24 Feb 2026 08:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:03 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Matt Saunders ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/ZFhT6zTPdUeWyitqoQCjfm-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Matt Saunders is an experienced technical operations leader and DevOps architect with a career spanning complex global enterprises, high-growth start-ups, and everything in between. He specializes in helping organizations accelerate the delivery of high-quality software by implementing pragmatic DevOps practices, modern tooling, and collaborative ways of working.&lt;/p&gt;&lt;p&gt;With a background that covers web hosting, financial services, enterprise technology, ISP and networking environments, Matt brings a comprehensive understanding of Internet technologies and large-scale operations. He is known for his ability to translate seamlessly between technical and non-technical teams, ensuring that engineering efforts remain aligned with business goals and deliver measurable value.Matt also leads the London DevOps meetup community (one of the largest DevOps groups in Europe with more than 11,000 members) hosting a highly regarded monthly industry event that connects practitioners, innovators, and thought leaders.&lt;/p&gt;&lt;p&gt;Across his career, Matt has served as an architect, leader, coach, and trainer. He is recognized for his calm, optimistic and pragmatic approach, and for helping teams adopt DevOps and agile methodologies that enable reliable, efficient and low-stress software delivery. He is passionate about mentoring, continuous learning, and fostering high-performing engineering cultures.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/DD7oSG7mL3LVWBrNQQCQu7-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Digital chain concept art]]></media:description>                                                            <media:text><![CDATA[Digital chain concept art]]></media:text>
                                <media:title type="plain"><![CDATA[Digital chain concept art]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/DD7oSG7mL3LVWBrNQQCQu7-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>A stereotypical view of cybersecurity extends the physical security metaphor, with servers bolted down with chains and only the most privileged employees allowed anywhere near them. However, doing cybersecurity thoroughly now encompasses entire supply chains, with weak links across suppliers, channel partners, and Managed Service Providers (MSPs) causing exploitable vulnerabilities of monumental proportions. </p><p>What’s often misunderstood is that many channel partners and MSPs sit directly in the middle of the modern supply chain. They frequently hold elevated access into multiple customer environments, operate critical components of those environments, and act as extensions of internal IT teams. This makes them unusual actors in the security ecosystem: they are simultaneously prime targets for attackers and frontline defenders for the organizations they support.</p><p>The cyber attacks that plagued numerous UK companies in 2025, including The Co-op, Harrods, M&amp;S, and Jaguar Land Rover, forced many organizations to re-examine their security posture as the perimeters are redrawn so much more broadly. The M&amp;S incident, which rendered online systems inoperable for weeks and led to a £300 million profitability hit, originated via a third-party supplier. And most recently, <a href="https://www.itpro.com/security/data-breaches/salesforce-customers-face-second-third-party-incident-this-year-with-gainsight-breach"><u>Salesforce confirmed</u></a> they have faced two third-party incidents in one year, via its SaaS partner Gainsight. </p><p><a href="https://static.adaptavistassets.com/downloads/adaptavist_crowdstrike_report.pdf"><u>Research</u></a> we conducted before these high-profile incidents indicated that 42% of organizations had concerns about vendors triggering major cyber incidents. Given the recent supply chain breaches we have seen, we suspect that this figure is now underrepresentative. Even organizations that have zero-trust architecture and state-of-the-art disaster recovery plans are still vulnerable to human weaknesses across their whole extended supply chain.</p><p>These examples, among many others, highlight how much more complex the challenge is now: what happens when the breach originates with a partner who has deep, sometimes privileged access into your environment?</p><h2 id="channel-partners-and-msps-are-part-of-the-infrastructure">Channel partners and MSPs are part of the infrastructure</h2><p>For many organizations, channel partners and MSPs are core building blocks of the operational estate. They manage cloud platforms, identity systems, monitoring tools, development pipelines, endpoint fleets, and security controls. In other words, they are part of the infrastructure.</p><p>This interconnectedness means that if an MSP is compromised, attackers may gain horizontal access to the environments of multiple customers at once. <a href="https://en.wikipedia.org/wiki/Kaseya_VSA_ransomware_attack"><u>The Kaseya attack in 2021</u></a> demonstrated this at a global scale, but 2025 has shown it’s now a mainstream, recurring risk.</p><p>As a result, organizations must shift their mindset from “suppliers supporting the business” to “suppliers embedded inside the business architecture.” Visibility, governance, and shared security controls across MSP-managed systems are no longer optional but essential for maximum protection.</p><h2 id="protecting-the-human-layer">Protecting the human layer</h2><p>Recent breaches have been attributed to human vulnerabilities in organizations that supply products and services to others. The M&amp;S incident appears to have been borne out of a social engineering tactic, giving an entry point into the organization that bypassed regular technical defences. These attacks are successful not through sophisticated technical exploitation but by manipulating individuals who already have legitimate access to systems.</p><p>Artificial intelligence (AI) has amplified these risks by scaling up more sophisticated social engineering attacks. AI-powered tools enable attackers to create more convincing phishing emails, generate realistic deepfake communications, and personalise attacks based on information gathered from social media and other public sources. AI has effectively lowered the barrier to entry for cybercriminals and also increased the potential impact of their activities.</p><p>While many organizations have invested heavily in internal cyber-awareness programmes, the new reality is that every supplier and MSP with environment access must be held to the same behavioural and security standards. Regular compliance checks, audits, and zero-trust approaches must be extended to the partner ecosystem. Without continuous validation, the most secure organization may still be exposed through a partner’s weakest link.</p><h2 id="the-importance-of-resilience-and-recovery">The importance of resilience and recovery</h2><p>After the security challenges of 2025, it's naive for anyone to believe that a complete modern security posture will prevent every breach. Beyond prevention, organizations must be able to detect, respond to, and recover from threats, including those triggered within their partner ecosystem.</p><p>This is where visibility becomes critical. Organizations need centralized oversight of MSP-managed systems, identity access, configuration drift, and partner-initiated changes. Hidden dependencies, particularly those controlled by partners, can dramatically extend downtime if they aren’t identified and tested in advance.</p><p>Our research showed big gaps in organizations being prepared to recover, with 84% of them lacking a decent incident response plan, and only 16% finding them effective if they had them. This means that most organizations need to find time and effort to actually test their plans before they're really needed. </p><p>Organizations need to define Recovery Time Objectives (RTOs) and Recovery Point Objectives (RPOs) for critical systems, and to have their eyes open to systems that might be hidden dependencies, including those run by third parties or their staff. These need to be tested regularly through drills - this helps identify dependencies and other challenges that may not be apparent when things are running normally.</p><p>Critical systems also require offline, immutable backups that cannot be compromised during an attack. Too often, organizations discover after an attack that backups managed or maintained by partners were incomplete, inaccessible, or misconfigured.</p><h2 id="conclusion">Conclusion</h2><p>The events of 2025 show that cyber attacks are increasingly sophisticated and now exploit not only technical vulnerabilities inside an organization but also those embedded throughout its supply chain. MSPs and channel partners, sitting at the centre of this ecosystem, have become both high-value targets and vital protectors.</p><p>Effective cybersecurity now requires that these organizations and their partners give equal attention to prevention and recovery capabilities, with the time taken to get back online having similar importance as the essential preventive measures. </p><p>Those that fully understand and lock down their supply chain from a security perspective, implement strict access controls with zero-trust architecture, and have properly tested recovery plans will have the best chance of surviving the next wave of threats to cybersecurity.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ AI-generated code is fast becoming the biggest enterprise security risk ]]></title>
                                                                                                <dc:content><![CDATA[ <p>AI has overtaken all other factors in reshaping security priorities, with teams now forced to deal with <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated code</a> that appears correct, professional, and production-ready – but that quietly introduces security risks.</p><p>That’s according to a <a href="https://www.blackduck.com/content/dam/black-duck/en-us/reports/bsimm-report.pdf" target="_blank"><u>new survey from Black Duck</u></a>, which recorded a 12% rise in teams actively risk-ranking where LLM-generated code can and can’t be deployed last year. </p><p>Meanwhile, there was a 10% increase in custom security rules designed specifically to catch AI-generated flaws.  </p><p>“The real risk of AI-generated code isn’t obvious breakage; it’s the illusion of correctness. Code that looks polished can still conceal serious security flaws, and developers are increasingly trusting it,” said Black Duck CEO Jason Schmitt.</p><p>“We’re witnessing a dangerous paradox: developers increasingly trust AI-produced code that lacks the security instincts of seasoned experts."</p><p>It's regulation that's forcing most security investment, researchers found, with the use of <a href="https://www.itpro.com/security/software-security-overhauled-for-the-better-thanks-to-us-legislation">Software Bill of Materials (SBOM)</a> up nearly 30%, and automated infrastructure verification surging by more than 50%. </p><p>Similarly, respondents reported an increase of more than 40% in streamlining responsible vulnerability disclosure, driven by the EU Cyber Resilience Act (CRA) and evolving US government demands. </p><p>"The surge in SBOM adoption reported in BSIMM16 is so critical, since it gives organizations the transparency to understand exactly what’s in their software — whether written by humans, AI, or third parties — and the visibility to respond quickly when vulnerabilities surface," said Schmitt. </p><p>"As regulatory mandates expand, SBOMs are moving beyond compliance — they’re becoming foundational infrastructure for managing risk in an AI-driven development landscape.”</p><h2 id="a-sharp-focus-on-first-and-third-party-code">A sharp focus on first and third-party code</h2><p>Organizations are rapidly standardizing tech stacks, the survey noted. Black Duck found teams are now expanding visibility beyond first-party code as third-party and AI-assisted development explodes. </p><p><a href="https://www.itpro.com/security/33974/our-5-minute-guide-to-security-awareness-training">Security training</a> is also being reinvented, researchers revealed, with multi-day courses now being replaced by just-in-time, on-demand guidance embedded directly into developer workflows in bite-sized chunks. </p><p>The use of open collaboration channels increased 29% year over year, giving teams instant access to security guidance on the fly. </p><h2 id="ai-generated-code-is-in-vogue">AI-generated code is in vogue</h2><p>Recent research from Aikido found that <a href="https://www.itpro.com/software/development/ai-coding-tools-are-finally-delivering-results-for-enterprises-developers-are-saving-so-much-time-theyre-able-to-collaborate-more-focus-on-system-design-and-learn-new-languages">AI coding tools</a> now write 24% of production code globally as enterprises across Europe and US ramp up adoption.</p><p>The trend has been gaining momentum for several years now, with a host of major tech providers such as Google and Microsoft revealing significant portions of source code is now written using the technology. </p><p>However, while this is speeding up production, research shows it also carries huge risks. </p><p>Aikido found that <a href="https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually">AI-generated code is now the cause of one-in-five breaches</a>, with 69% of security leaders, engineers, and developers on both sides of the Atlantic having found serious vulnerabilities. </p><p>These risk factors are further exacerbated by the fact many developers are placing too much faith in the technology when coding. A <a href="https://www.itpro.com/software/development/software-developers-not-checking-ai-generated-code-verification-debt"><u>separate survey from Sonar</u></a> found nearly half of devs fail to check AI-generated code, placing their organization at huge risk. </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/ai-generated-code-is-fast-becoming-the-biggest-enterprise-security-risk-as-teams-struggle-with-the-illusion-of-correctness</link>
                                                                            <description>
                            <![CDATA[ Security teams are scrambling to catch AI-generated flaws that appear correct before disaster strikes ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">tpS2skWBhDwtvLdGKn58Si</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/45XM7VDiKtHZtv8qEvuvW5-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 05 Feb 2026 12:48:13 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:51 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/45XM7VDiKtHZtv8qEvuvW5-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[A visualization of agentic AI layers, shown as blue nodes of code connected by blue strands against a dark background.]]></media:description>                                                            <media:text><![CDATA[A visualization of agentic AI layers, shown as blue nodes of code connected by blue strands against a dark background.]]></media:text>
                                <media:title type="plain"><![CDATA[A visualization of agentic AI layers, shown as blue nodes of code connected by blue strands against a dark background.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/45XM7VDiKtHZtv8qEvuvW5-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>AI has overtaken all other factors in reshaping security priorities, with teams now forced to deal with <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated code</a> that appears correct, professional, and production-ready – but that quietly introduces security risks.</p><p>That’s according to a <a href="https://www.blackduck.com/content/dam/black-duck/en-us/reports/bsimm-report.pdf" target="_blank"><u>new survey from Black Duck</u></a>, which recorded a 12% rise in teams actively risk-ranking where LLM-generated code can and can’t be deployed last year. </p><p>Meanwhile, there was a 10% increase in custom security rules designed specifically to catch AI-generated flaws.  </p><p>“The real risk of AI-generated code isn’t obvious breakage; it’s the illusion of correctness. Code that looks polished can still conceal serious security flaws, and developers are increasingly trusting it,” said Black Duck CEO Jason Schmitt.</p><p>“We’re witnessing a dangerous paradox: developers increasingly trust AI-produced code that lacks the security instincts of seasoned experts."</p><p>It's regulation that's forcing most security investment, researchers found, with the use of <a href="https://www.itpro.com/security/software-security-overhauled-for-the-better-thanks-to-us-legislation">Software Bill of Materials (SBOM)</a> up nearly 30%, and automated infrastructure verification surging by more than 50%. </p><p>Similarly, respondents reported an increase of more than 40% in streamlining responsible vulnerability disclosure, driven by the EU Cyber Resilience Act (CRA) and evolving US government demands. </p><p>"The surge in SBOM adoption reported in BSIMM16 is so critical, since it gives organizations the transparency to understand exactly what’s in their software — whether written by humans, AI, or third parties — and the visibility to respond quickly when vulnerabilities surface," said Schmitt. </p><p>"As regulatory mandates expand, SBOMs are moving beyond compliance — they’re becoming foundational infrastructure for managing risk in an AI-driven development landscape.”</p><h2 id="a-sharp-focus-on-first-and-third-party-code">A sharp focus on first and third-party code</h2><p>Organizations are rapidly standardizing tech stacks, the survey noted. Black Duck found teams are now expanding visibility beyond first-party code as third-party and AI-assisted development explodes. </p><p><a href="https://www.itpro.com/security/33974/our-5-minute-guide-to-security-awareness-training">Security training</a> is also being reinvented, researchers revealed, with multi-day courses now being replaced by just-in-time, on-demand guidance embedded directly into developer workflows in bite-sized chunks. </p><p>The use of open collaboration channels increased 29% year over year, giving teams instant access to security guidance on the fly. </p><h2 id="ai-generated-code-is-in-vogue">AI-generated code is in vogue</h2><p>Recent research from Aikido found that <a href="https://www.itpro.com/software/development/ai-coding-tools-are-finally-delivering-results-for-enterprises-developers-are-saving-so-much-time-theyre-able-to-collaborate-more-focus-on-system-design-and-learn-new-languages">AI coding tools</a> now write 24% of production code globally as enterprises across Europe and US ramp up adoption.</p><p>The trend has been gaining momentum for several years now, with a host of major tech providers such as Google and Microsoft revealing significant portions of source code is now written using the technology. </p><p>However, while this is speeding up production, research shows it also carries huge risks. </p><p>Aikido found that <a href="https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually">AI-generated code is now the cause of one-in-five breaches</a>, with 69% of security leaders, engineers, and developers on both sides of the Atlantic having found serious vulnerabilities. </p><p>These risk factors are further exacerbated by the fact many developers are placing too much faith in the technology when coding. A <a href="https://www.itpro.com/software/development/software-developers-not-checking-ai-generated-code-verification-debt"><u>separate survey from Sonar</u></a> found nearly half of devs fail to check AI-generated code, placing their organization at huge risk. </p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ New industry 'ambassador' scheme looks to shore up software security practices ]]></title>
                                                                                                <dc:content><![CDATA[ <p>The UK government has launched a new scheme to boost adoption of the <a href="https://www.gov.uk/government/publications/software-security-code-of-practice" target="_blank"><em>Software Security Code of Practice</em></a> by appointing a series of industry champions. </p><p>Under the plans, a cohort of ‘Software Security Ambassadors’ will promote the code of practice across various different sectors, showcasing examples of practical implementation and giving feedback to inform future policy improvements.</p><p>The first batch of participating organizations includes the Department for Science, Innovation, and Technology (DSIT) itself, along with the <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do">National Cyber Security Centre (NCSC)</a>. </p><div class="product"><a data-dimension112="09d3756b-f11b-4f40-b164-50861fe20284" data-action="Deal Block" data-label="Make Password Security Your New Year's Resolution" data-dimension48="Make Password Security Your New Year's Resolution" href="https://click.linksynergy.com/deeplink?id=kXQk6%2AivFEQ&amp;mid=42966&amp;u1=itpro-gb-1046892004221913649&amp;murl=https%3A%2F%2Fwww.keepersecurity.com%2Fen_GB%2Fnew-year-resolution.html" target="_blank" rel="nofollow"><figure class="van-image-figure "  ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:310px;"><p class="vanilla-image-block" style="padding-top:52.58%;"><img id="VVXzWjJJrXo7mwL5n5f4mf" name="Keeper Security logo.png" caption="" alt="" src="https://cdn.mos.cms.futurecdn.net/VVXzWjJJrXo7mwL5n5f4mf-1920-80.png" mos="" align="middle" fullscreen="" width="310" height="163" attribution="" endorsement="" credit="" class="" /></p></div></div></figure></a><p><a href="https://click.linksynergy.com/deeplink?id=kXQk6%2AivFEQ&amp;mid=42966&amp;u1=itpro-gb-1046892004221913649&amp;murl=https%3A%2F%2Fwww.keepersecurity.com%2Fen_GB%2Fnew-year-resolution.html" target="_blank" rel="sponsored" data-dimension112="09d3756b-f11b-4f40-b164-50861fe20284" data-action="Deal Block" data-label="Make Password Security Your New Year's Resolution" data-dimension48="Make Password Security Your New Year's Resolution" data-dimension25="">Make Password Security Your New Year's Resolution</a></p><p>Get 50% off Keeper Personal and Family plans, and 30% off Keeper Business Starter today!<a class="view-deal button" href="https://click.linksynergy.com/deeplink?id=kXQk6%2AivFEQ&amp;mid=42966&amp;u1=itpro-gb-1046892004221913649&amp;murl=https%3A%2F%2Fwww.keepersecurity.com%2Fen_GB%2Fnew-year-resolution.html" target="_blank" rel="nofollow" data-dimension112="09d3756b-f11b-4f40-b164-50861fe20284" data-action="Deal Block" data-label="Make Password Security Your New Year's Resolution" data-dimension48="Make Password Security Your New Year's Resolution" data-dimension25="">View Deal</a></p></div><p>Accenture, <a href="https://www.itpro.com/infrastructure/networking/everything-you-need-to-know-about-cisco">Cisco</a>, ISACA, Lloyds Banking Group, Sage, Palo Alto Networks, and others have also backed the scheme. </p><p>"By acting as ambassadors, signatories are committing to a process of transparency, development and continuous improvement. The implementation of this code of practice will take time and, in doing so, may bring to light issues that need to be addressed," DSIT said in a statement confirming the announcement. </p><p>"Signatories and policymakers will learn from these issues as well as the successes and challenges for each organization and, where appropriate, will share information to help develop and strengthen this government policy."  </p><h2 id="what-is-the-software-security-code-of-practice">What is the Software Security Code of Practice?</h2><p>The Software Security Code of Practice was <a href="https://www.itpro.com/software/software-security-code-of-practice-ncsc-announcement"><u>unveiled by the NCSC</u></a> in May last year, setting out a series of voluntary principles defining what good <a href="https://www.itpro.com/software/software-security-flaws-remediation">software security</a> looks like across the entire <a href="https://www.itpro.com/software/development/367842/the-four-major-software-development-lifecycle-models-and-how-they-work">software lifecycle</a>. </p><p>Aimed at technology providers and organizations that develop, sell, or procure software, the code offers best practices for secure design and development, build-environment security, and secure deployment and maintenance.</p><p>The code also emphasizes the importance of transparent communication with customers on potential security risks and vulnerabilities. </p><p>Developed with the NCSC, the code is designed to reflect internationally recognized best practices, such as the US Secure Software Development Framework (SSDF) and the EU’s <a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra">Cyber Resilience Act (CRA)</a>.</p><h2 id="software-security-in-the-spotlight">Software security in the spotlight</h2><p>The launch of the code came in direct response to growing concerns surrounding software security on both sides of the Atlantic. In the US, for example, the <em>Secure by Design Pledge</em> was <a href="https://www.itpro.com/software/software-vendors-are-flocking-to-cisas-secure-by-design-pledge"><u>launched by CISA in 2023</u></a>. </p><p>This voluntary scheme asks software developers and providers to place a stronger emphasis on product security. </p><p>According to figures from the DSIT, more than half (59%) of organizations experienced <a href="https://www.itpro.com/software/software-supply-chain-attacks-are-rife-this-is-what-developers-need-to-watch-out-for">software supply chain attacks</a> in the past year, underlining the growing risks faced by UK enterprises and consumers alike. </p><p>In a separate <a href="https://www.isc2.org/Insights/2025/11/2025-isc2-supply-chain-risk-survey" target="_blank">survey from ISC2</a>, more than half of respondents identified software vulnerabilities in supplier products as the most disruptive <a href="https://www.itpro.com/security/28133/what-is-cyber-security">cybersecurity </a>threat to their organisation’s supply chain.</p><p>ISC2 said it plans to help drive adoption of the code by promoting awareness through educational and thought leadership content, and referencing it in relation to certifications, training, and guidance that support secure software development.</p><p>It will also work with organizations across the software supply chain to encourage practical implementation and require its own partners to incorporate it.</p><p>“Promoting secure software practices that strengthen the resilience of systems underpinning the economy, public services and national infrastructure is central to ISC2’s mission,” said Tara Wisniewski. ISC2 EVP for advocacy and strategic engagement. </p><p>“The code moves software security beyond narrow compliance and elevates it to a board-level resilience priority. As supply chain attacks continue to grow in scale and impact, a shared baseline is essential and through our global community and expertise, ISC2 is committed to helping professionals build the skills needed to put secure-by-design principles into practice.”</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/uk-software-security-ambassadors-ncsc-code-of-practice</link>
                                                                            <description>
                            <![CDATA[ The Software Security Ambassadors scheme aims to boost software supply chains by helping organizations implement the Software Security Code of Practice. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">hhoFwaLxMzvGZkMHzAcDMd</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/9ZT5mU7YeSN7Bg7YHh2LxX-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Mon, 19 Jan 2026 10:47:23 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:58 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Workplace Technology]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/9ZT5mU7YeSN7Bg7YHh2LxX-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Female software developer coding in dark room with screen reflecting on glasses.]]></media:description>                                                            <media:text><![CDATA[Female software developer coding in dark room with screen reflecting on glasses.]]></media:text>
                                <media:title type="plain"><![CDATA[Female software developer coding in dark room with screen reflecting on glasses.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/9ZT5mU7YeSN7Bg7YHh2LxX-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The UK government has launched a new scheme to boost adoption of the <a href="https://www.gov.uk/government/publications/software-security-code-of-practice" target="_blank"><em>Software Security Code of Practice</em></a> by appointing a series of industry champions. </p><p>Under the plans, a cohort of ‘Software Security Ambassadors’ will promote the code of practice across various different sectors, showcasing examples of practical implementation and giving feedback to inform future policy improvements.</p><p>The first batch of participating organizations includes the Department for Science, Innovation, and Technology (DSIT) itself, along with the <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do">National Cyber Security Centre (NCSC)</a>. </p><div class="product"><a data-dimension112="09d3756b-f11b-4f40-b164-50861fe20284" data-action="Deal Block" data-label="Make Password Security Your New Year's Resolution" data-dimension48="Make Password Security Your New Year's Resolution" href="https://click.linksynergy.com/deeplink?id=kXQk6%2AivFEQ&amp;mid=42966&amp;u1=itpro-gb-1046892004221913649&amp;murl=https%3A%2F%2Fwww.keepersecurity.com%2Fen_GB%2Fnew-year-resolution.html" target="_blank" rel="nofollow"><figure class="van-image-figure "  ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:310px;"><p class="vanilla-image-block" style="padding-top:52.58%;"><img id="VVXzWjJJrXo7mwL5n5f4mf" name="Keeper Security logo.png" caption="" alt="" src="https://cdn.mos.cms.futurecdn.net/VVXzWjJJrXo7mwL5n5f4mf-1920-80.png" mos="" align="middle" fullscreen="" width="310" height="163" attribution="" endorsement="" credit="" class="" /></p></div></div></figure></a><p><a href="https://click.linksynergy.com/deeplink?id=kXQk6%2AivFEQ&amp;mid=42966&amp;u1=itpro-gb-1046892004221913649&amp;murl=https%3A%2F%2Fwww.keepersecurity.com%2Fen_GB%2Fnew-year-resolution.html" target="_blank" rel="sponsored" data-dimension112="09d3756b-f11b-4f40-b164-50861fe20284" data-action="Deal Block" data-label="Make Password Security Your New Year's Resolution" data-dimension48="Make Password Security Your New Year's Resolution" data-dimension25="">Make Password Security Your New Year's Resolution</a></p><p>Get 50% off Keeper Personal and Family plans, and 30% off Keeper Business Starter today!<a class="view-deal button" href="https://click.linksynergy.com/deeplink?id=kXQk6%2AivFEQ&amp;mid=42966&amp;u1=itpro-gb-1046892004221913649&amp;murl=https%3A%2F%2Fwww.keepersecurity.com%2Fen_GB%2Fnew-year-resolution.html" target="_blank" rel="nofollow" data-dimension112="09d3756b-f11b-4f40-b164-50861fe20284" data-action="Deal Block" data-label="Make Password Security Your New Year's Resolution" data-dimension48="Make Password Security Your New Year's Resolution" data-dimension25="">View Deal</a></p></div><p>Accenture, <a href="https://www.itpro.com/infrastructure/networking/everything-you-need-to-know-about-cisco">Cisco</a>, ISACA, Lloyds Banking Group, Sage, Palo Alto Networks, and others have also backed the scheme. </p><p>"By acting as ambassadors, signatories are committing to a process of transparency, development and continuous improvement. The implementation of this code of practice will take time and, in doing so, may bring to light issues that need to be addressed," DSIT said in a statement confirming the announcement. </p><p>"Signatories and policymakers will learn from these issues as well as the successes and challenges for each organization and, where appropriate, will share information to help develop and strengthen this government policy."  </p><h2 id="what-is-the-software-security-code-of-practice">What is the Software Security Code of Practice?</h2><p>The Software Security Code of Practice was <a href="https://www.itpro.com/software/software-security-code-of-practice-ncsc-announcement"><u>unveiled by the NCSC</u></a> in May last year, setting out a series of voluntary principles defining what good <a href="https://www.itpro.com/software/software-security-flaws-remediation">software security</a> looks like across the entire <a href="https://www.itpro.com/software/development/367842/the-four-major-software-development-lifecycle-models-and-how-they-work">software lifecycle</a>. </p><p>Aimed at technology providers and organizations that develop, sell, or procure software, the code offers best practices for secure design and development, build-environment security, and secure deployment and maintenance.</p><p>The code also emphasizes the importance of transparent communication with customers on potential security risks and vulnerabilities. </p><p>Developed with the NCSC, the code is designed to reflect internationally recognized best practices, such as the US Secure Software Development Framework (SSDF) and the EU’s <a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra">Cyber Resilience Act (CRA)</a>.</p><h2 id="software-security-in-the-spotlight">Software security in the spotlight</h2><p>The launch of the code came in direct response to growing concerns surrounding software security on both sides of the Atlantic. In the US, for example, the <em>Secure by Design Pledge</em> was <a href="https://www.itpro.com/software/software-vendors-are-flocking-to-cisas-secure-by-design-pledge"><u>launched by CISA in 2023</u></a>. </p><p>This voluntary scheme asks software developers and providers to place a stronger emphasis on product security. </p><p>According to figures from the DSIT, more than half (59%) of organizations experienced <a href="https://www.itpro.com/software/software-supply-chain-attacks-are-rife-this-is-what-developers-need-to-watch-out-for">software supply chain attacks</a> in the past year, underlining the growing risks faced by UK enterprises and consumers alike. </p><p>In a separate <a href="https://www.isc2.org/Insights/2025/11/2025-isc2-supply-chain-risk-survey" target="_blank">survey from ISC2</a>, more than half of respondents identified software vulnerabilities in supplier products as the most disruptive <a href="https://www.itpro.com/security/28133/what-is-cyber-security">cybersecurity </a>threat to their organisation’s supply chain.</p><p>ISC2 said it plans to help drive adoption of the code by promoting awareness through educational and thought leadership content, and referencing it in relation to certifications, training, and guidance that support secure software development.</p><p>It will also work with organizations across the software supply chain to encourage practical implementation and require its own partners to incorporate it.</p><p>“Promoting secure software practices that strengthen the resilience of systems underpinning the economy, public services and national infrastructure is central to ISC2’s mission,” said Tara Wisniewski. ISC2 EVP for advocacy and strategic engagement. </p><p>“The code moves software security beyond narrow compliance and elevates it to a board-level resilience priority. As supply chain attacks continue to grow in scale and impact, a shared baseline is essential and through our global community and expertise, ISC2 is committed to helping professionals build the skills needed to put secure-by-design principles into practice.”</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ AI is creating more software flaws – and they're getting worse ]]></title>
                                                                                                <dc:content><![CDATA[ <p><a href="https://www.itpro.com/strategy/28181/what-is-ai">AI</a> is helping developers write code faster, but it's also leading to more problems, marking the latest study to highlight adoption concerns among <a href="https://www.itpro.com/business-strategy/careers-training/356509/how-to-become-a-software-developer">software developers</a>.  </p><p>In a <a href="https://www.coderabbit.ai/whitepapers/state-of-AI-vs-human-code-generation-report" target="_blank"><u>study </u></a>from CodeRabbit, researchers found AI makes 1.7 more times as many mistakes as human programmers. </p><p>To come to that conclusion, CodeRabbit looked at 470 open source GitHub pull requests, of which 320 had AI input and 150 were human only.</p><p>"The results? Clear, measurable, and consistent with what many developers have been feeling intuitively: AI accelerates output, but it also amplifies certain categories of mistakes," wrote CodeRabbit's director of AI David Loker in a <a href="https://www.coderabbit.ai/blog/state-of-ai-vs-human-code-generation-report" target="_blank"><u>blog post</u></a>.</p><p>He admitted the study wasn't perfect, in part because it was difficult to double-check authorship, but said the findings matched with previous research. Loker pointed to a <a href="https://www.theverge.com/tech/845216/mozilla-ceo-anthony-enzor-demeo" target="_blank"><u>report by Cortex</u></a> that found pull requests per author increased by 20%, but incidents per pull request also went up — by 23.%.</p><p>That matches with <a href="https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually"><u>previous research</u></a> suggesting AI-generated code is now the cause of one-in-five breaches, with <a href="https://www.itpro.com/software/development/developers-say-ai-can-code-better-than-most-humans-but-theres-a-catch"><u>another report</u></a> noting coders' concerns around AI introducing errors to their work.</p><h2 id="more-problems-and-more-critical-flaws">More problems and more critical flaws</h2><p>The CodeRabbit study found 10.83 issues with AI pull requests versus 6.45 for human-only ones, adding that AI pull requests were far more likely to have critical or major issues. </p><p>"Even more striking: high-issue outliers were much more common in AI PRs, creating heavy review workloads," Loker said.</p><p>Logic and correctness was the worst area for AI code, followed by code quality and maintainability and security. Because of that, CodeRabbit advised reviewers to watch out for those types of <a href="https://www.itpro.com/technology/artificial-intelligence/researchers-tested-over-100-leading-ai-models-on-coding-tasks-nearly-half-produced-glaring-security-flaws">errors in AI code</a>.</p><iframe allow="" height="200px" width="100%" id="" style="" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/" src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/"></iframe><p>"These include business logic mistakes, incorrect dependencies, flawed control flow, and misconfigurations," Loker wrote. "Logic errors are among the most expensive to fix and most likely to cause downstream incidents."</p><p>AI code was also spotted omitting null checks, guardrails, and other error checking, which Loker noted are issues that can lead to outages in the real world. </p><p>When it came to security, the most common mistake by AI was improper password handling and insecure object references, Loker noted, with security issues 2.74 times more common in AI code than that written by humans. </p><p>Another major difference between <a href="https://www.itpro.com/technology/artificial-intelligence/can-ai-code-generation-really-replace-human-developers">AI code and human written-code</a> was readability. "AI-produced code often looks consistent but violates local patterns around naming, clarity, and structure," Loker added.</p><p>Beyond those issues, Loker noted flaws in concurrency, formatting, and naming inconsistencies — all of which could not only cause issues with software or apps, but also make it harder for human reviewers to spot problems. </p><h2 id="what-s-happening-and-how-to-fix-it">What's happening, and how to fix it</h2><p>Some of the faults are down to a lack of context, Loker suggested, and in other cases AI is sticking to "generic defaults" rather than company rules, such as with naming patterns or architectural norms. </p><p>Security problems may be down to how models recreate "legacy patterns or outdated practices" by using older code as training data. </p><p>"AI generates surface-level correctness: It produces code that looks right but may skip control-flow protections or misuse dependency ordering," Loker added. </p><p>None of this means AI shouldn't be used in coding, he stressed. Instead, companies should ensure AI has context of business rules, policies or style guides, and be given guidelines for basic security.</p><p>Such efforts would wipe out many of the faults spotted, he said. Similarly, code reviewers should be given a checklist that takes this research into account, so they know what types of errors to watch out for. </p><p>"The future of AI-assisted development isn’t about <a href="https://www.itpro.com/software/development/aws-ceo-matt-garman-just-said-what-everyone-is-thinking-about-ai-replacing-software-developers">replacing developers</a>," he added. "It’s about building systems, workflows, and safety layers that amplify what AI does well while compensating for what it tends to miss."</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/ai-is-creating-more-software-flaws-and-theyre-getting-worse</link>
                                                                            <description>
                            <![CDATA[ A CodeRabbit study compared pull requests with AI and without, finding AI is fast but highly error prone ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">2dxNMZRmEoPNiNyxreKr3</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/4JhLyaj9v5ercjwuih56XQ-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 18 Dec 2025 16:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:52 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                                    <dc:creator><![CDATA[ Nicole Kobie ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/8Y8JDDTQ7XDEk49FoAFP2S-320-70.png ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Nicole Kobie first started writing for ITPro in 2007. As a freelance journalist covering technology and business, Nicole&#039;s work includes  bylines in New Scientist, Wired, PC Pro and many more. &lt;/p&gt;&lt;p&gt;Nicole the author of a book about the history of technology, The Long History of the Future.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/4JhLyaj9v5ercjwuih56XQ-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Female software developer working at a desktop computer in an open plan office space with laptop next to screen.]]></media:description>                                                            <media:text><![CDATA[Female software developer working at a desktop computer in an open plan office space with laptop next to screen.]]></media:text>
                                <media:title type="plain"><![CDATA[Female software developer working at a desktop computer in an open plan office space with laptop next to screen.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/4JhLyaj9v5ercjwuih56XQ-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><a href="https://www.itpro.com/strategy/28181/what-is-ai">AI</a> is helping developers write code faster, but it's also leading to more problems, marking the latest study to highlight adoption concerns among <a href="https://www.itpro.com/business-strategy/careers-training/356509/how-to-become-a-software-developer">software developers</a>.  </p><p>In a <a href="https://www.coderabbit.ai/whitepapers/state-of-AI-vs-human-code-generation-report" target="_blank"><u>study </u></a>from CodeRabbit, researchers found AI makes 1.7 more times as many mistakes as human programmers. </p><p>To come to that conclusion, CodeRabbit looked at 470 open source GitHub pull requests, of which 320 had AI input and 150 were human only.</p><p>"The results? Clear, measurable, and consistent with what many developers have been feeling intuitively: AI accelerates output, but it also amplifies certain categories of mistakes," wrote CodeRabbit's director of AI David Loker in a <a href="https://www.coderabbit.ai/blog/state-of-ai-vs-human-code-generation-report" target="_blank"><u>blog post</u></a>.</p><p>He admitted the study wasn't perfect, in part because it was difficult to double-check authorship, but said the findings matched with previous research. Loker pointed to a <a href="https://www.theverge.com/tech/845216/mozilla-ceo-anthony-enzor-demeo" target="_blank"><u>report by Cortex</u></a> that found pull requests per author increased by 20%, but incidents per pull request also went up — by 23.%.</p><p>That matches with <a href="https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually"><u>previous research</u></a> suggesting AI-generated code is now the cause of one-in-five breaches, with <a href="https://www.itpro.com/software/development/developers-say-ai-can-code-better-than-most-humans-but-theres-a-catch"><u>another report</u></a> noting coders' concerns around AI introducing errors to their work.</p><h2 id="more-problems-and-more-critical-flaws">More problems and more critical flaws</h2><p>The CodeRabbit study found 10.83 issues with AI pull requests versus 6.45 for human-only ones, adding that AI pull requests were far more likely to have critical or major issues. </p><p>"Even more striking: high-issue outliers were much more common in AI PRs, creating heavy review workloads," Loker said.</p><p>Logic and correctness was the worst area for AI code, followed by code quality and maintainability and security. Because of that, CodeRabbit advised reviewers to watch out for those types of <a href="https://www.itpro.com/technology/artificial-intelligence/researchers-tested-over-100-leading-ai-models-on-coding-tasks-nearly-half-produced-glaring-security-flaws">errors in AI code</a>.</p><iframe allow="" height="200px" width="100%" id="" style="" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/" src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/"></iframe><p>"These include business logic mistakes, incorrect dependencies, flawed control flow, and misconfigurations," Loker wrote. "Logic errors are among the most expensive to fix and most likely to cause downstream incidents."</p><p>AI code was also spotted omitting null checks, guardrails, and other error checking, which Loker noted are issues that can lead to outages in the real world. </p><p>When it came to security, the most common mistake by AI was improper password handling and insecure object references, Loker noted, with security issues 2.74 times more common in AI code than that written by humans. </p><p>Another major difference between <a href="https://www.itpro.com/technology/artificial-intelligence/can-ai-code-generation-really-replace-human-developers">AI code and human written-code</a> was readability. "AI-produced code often looks consistent but violates local patterns around naming, clarity, and structure," Loker added.</p><p>Beyond those issues, Loker noted flaws in concurrency, formatting, and naming inconsistencies — all of which could not only cause issues with software or apps, but also make it harder for human reviewers to spot problems. </p><h2 id="what-s-happening-and-how-to-fix-it">What's happening, and how to fix it</h2><p>Some of the faults are down to a lack of context, Loker suggested, and in other cases AI is sticking to "generic defaults" rather than company rules, such as with naming patterns or architectural norms. </p><p>Security problems may be down to how models recreate "legacy patterns or outdated practices" by using older code as training data. </p><p>"AI generates surface-level correctness: It produces code that looks right but may skip control-flow protections or misuse dependency ordering," Loker added. </p><p>None of this means AI shouldn't be used in coding, he stressed. Instead, companies should ensure AI has context of business rules, policies or style guides, and be given guidelines for basic security.</p><p>Such efforts would wipe out many of the faults spotted, he said. Similarly, code reviewers should be given a checklist that takes this research into account, so they know what types of errors to watch out for. </p><p>"The future of AI-assisted development isn’t about <a href="https://www.itpro.com/software/development/aws-ceo-matt-garman-just-said-what-everyone-is-thinking-about-ai-replacing-software-developers">replacing developers</a>," he added. "It’s about building systems, workflows, and safety layers that amplify what AI does well while compensating for what it tends to miss."</p><h3 class="article-body__section" id="section-follow-us-on-social-media"><span>FOLLOW US ON SOCIAL MEDIA</span></h3>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ A concerning number of Log4j downloads are still vulnerable four years on ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Four years on from <a href="https://www.itpro.com/security/zero-day-exploit/361819/what-is-log4shell-log4j-vulnerability">Log4Shell</a>, more than one-in-ten Log4j downloads still contain the vulnerability, according to data from Sonatype.</p><p>Over the last year, 14% of Log4j downloads in the UK were vulnerable, the <a href="https://www.sonatype.com/whitepapers/the-persistence-of-open-source-vulnerabilities" target="_blank"><u>company found</u></a>, with the global figure standing at around 13% despite the availability of safe versions. </p><p>Notably, Sonatype found the problem isn't specific to Log4j, with around 95% of vulnerable <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> components downloaded already having a fixed version available.</p><p>"<a href="https://www.itpro.com/security/cyber-security/368554/how-to-protect-against-endemic-log4j-vulnerabilities">The Log4j vulnerability</a> doesn’t even crack the top few anymore. Sonatype Security Research examined some of the most frequently downloaded avoidable vulnerabilities — collectively they have collectively been downloaded more than 2.94 billion times this year or since their patches were released (whichever is more recent)," said the firm. </p><p>"Every one of those downloads represents unnecessary risk: teams pulling vulnerable versions when fixed ones already exist, and have for years."</p><h2 id="how-the-log4shell-incident-unfolded">How the Log4Shell incident unfolded</h2><p>Log4Shell, a critical zero-day flaw in a widely-used <a href="https://www.itpro.com/software/development/why-java-17-growth-is-exploding">Java library</a>, appeared in December 2021, and was immediately and widely exploited. Nearly <a href="https://www.itpro.com/security/zero-day-exploit/361847/log4shell-zero-day-vulnerability-numbers-revealed">one million attack attempts</a> were launched in the first 72 hours of the vulnerability's disclosure.</p><p>It was described at the time by Check Point Security as "clearly one of the most serious vulnerabilities on the internet in recent years, and the potential for damage is incalculable".</p><p>The incident caused upheaval throughout the security industry, kicking off a new era of software supply chain scrutiny and prompting <a href="https://www.itpro.com/security/software-security-overhauled-for-the-better-thanks-to-us-legislation">software bill of materials</a> mandates in US executive order 14028 and tighter oversight in Europe through the <a href="https://www.itpro.com/business/policy-legislation/370403/what-is-the-network-and-information-security-2-nis2-directive">NIS2 Directive</a> and the <a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra">Cyber Resilience Act (CRA)</a>.</p><p>However, Sonatype said that in 2025 alone, there were nearly 300 million total Log4j downloads, of which 40 million were vulnerable.</p><p>In China, the US, India, Japan, Brazil, Germany, the UK, Canada, South Korea, and France, between 8% and 29% of Log4j downloads still contained Log4Shell. India did particularly badly, with 29%, while the figure was 28% for China and 22% for Japan.</p><h2 id="log4j-complacency-persists">Log4j complacency persists</h2><p>According to Sonatype, the reason behind continued vulnerable Log4j downloads lies in a combination of complacency and the simple fact the incident occurred several years ago. </p><p>Moreover, visibility and oversight - or lack thereof - are also key factors in the trend. </p><p>"Once a library is wired in and everything compiles, it tends to stay that way. Versions get pinned, build files get copied from one service to the next, and no one revisits those choices unless something forces the issue — a breach, a compliance audit, or a production outage," said the firm.</p><p>"Without someone explicitly owning ongoing dependency maintenance, those 'temporary' choices turn into long-lived tech debt. Vulnerable versions of Log4j and other libraries stick around not because anyone chose them recently, but because no one chose to replace them."</p><p>Meanwhile, many vulnerable components — including Log4j in some stacks — are pulled in transitively by other libraries and frameworks, creating an ownership vacuum. </p><p>Component choices are typically optimized for speed and familiarity, rather than time-to-fix history, security posture, or the quality of governance and maintenance. </p><p><a href="https://www.itpro.com/security/adopting-more-security-tools-doesnt-keep-you-safe-it-just-overloads-your-teams-and-creates-greater-risks">Security tooling</a> doesn’t always help, either, thanks particularly to alert fatigue.</p><p>"If you’re not sure where you stand today, start by getting the numbers. Run a scan of your applications to find Log4j and other frequently downloaded vulnerable components, calculate what share of their usage is to vulnerable versions, and benchmark your own 'unnecessary risk rate'," said the firm.</p><p>"That’s the first step toward making sure Log4Shell is remembered as a turning point, not just an anniversary."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/open-source/open-source-security-in-the-spotlight-as-uk-gov-publishes-fresh-guidance">Open source security in the spotlight as UK gov publishes fresh guidance</a></li><li><a href="https://www.itpro.com/software/open-source/open-source-software-attacks-everything-you-need-to-look-out-for">Open source software attacks: Everything you need to look out for</a></li><li><a href="https://www.itpro.com/software/open-source/why-open-source-risks-threaten-all-business-users">Why we need a better understanding of open source software</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/open-source/a-concerning-number-of-log4j-downloads-are-still-vulnerable-four-years-on</link>
                                                                            <description>
                            <![CDATA[ Despite safe Log4j versions having been available for years, many organizations haven't introduced them ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">xhWiBsHGTC9j6Wemp4xav4</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/keTVGxYZ6S7QMNungRToWP-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 12 Dec 2025 08:25:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:16 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Open Source]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Workplace Technology]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/keTVGxYZ6S7QMNungRToWP-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Log4j open source Java library logo pictured on a smartphone with source code in green coloring pictured on screen in background.]]></media:description>                                                            <media:text><![CDATA[Log4j open source Java library logo pictured on a smartphone with source code in green coloring pictured on screen in background.]]></media:text>
                                <media:title type="plain"><![CDATA[Log4j open source Java library logo pictured on a smartphone with source code in green coloring pictured on screen in background.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/keTVGxYZ6S7QMNungRToWP-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Four years on from <a href="https://www.itpro.com/security/zero-day-exploit/361819/what-is-log4shell-log4j-vulnerability">Log4Shell</a>, more than one-in-ten Log4j downloads still contain the vulnerability, according to data from Sonatype.</p><p>Over the last year, 14% of Log4j downloads in the UK were vulnerable, the <a href="https://www.sonatype.com/whitepapers/the-persistence-of-open-source-vulnerabilities" target="_blank"><u>company found</u></a>, with the global figure standing at around 13% despite the availability of safe versions. </p><p>Notably, Sonatype found the problem isn't specific to Log4j, with around 95% of vulnerable <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> components downloaded already having a fixed version available.</p><p>"<a href="https://www.itpro.com/security/cyber-security/368554/how-to-protect-against-endemic-log4j-vulnerabilities">The Log4j vulnerability</a> doesn’t even crack the top few anymore. Sonatype Security Research examined some of the most frequently downloaded avoidable vulnerabilities — collectively they have collectively been downloaded more than 2.94 billion times this year or since their patches were released (whichever is more recent)," said the firm. </p><p>"Every one of those downloads represents unnecessary risk: teams pulling vulnerable versions when fixed ones already exist, and have for years."</p><h2 id="how-the-log4shell-incident-unfolded">How the Log4Shell incident unfolded</h2><p>Log4Shell, a critical zero-day flaw in a widely-used <a href="https://www.itpro.com/software/development/why-java-17-growth-is-exploding">Java library</a>, appeared in December 2021, and was immediately and widely exploited. Nearly <a href="https://www.itpro.com/security/zero-day-exploit/361847/log4shell-zero-day-vulnerability-numbers-revealed">one million attack attempts</a> were launched in the first 72 hours of the vulnerability's disclosure.</p><p>It was described at the time by Check Point Security as "clearly one of the most serious vulnerabilities on the internet in recent years, and the potential for damage is incalculable".</p><p>The incident caused upheaval throughout the security industry, kicking off a new era of software supply chain scrutiny and prompting <a href="https://www.itpro.com/security/software-security-overhauled-for-the-better-thanks-to-us-legislation">software bill of materials</a> mandates in US executive order 14028 and tighter oversight in Europe through the <a href="https://www.itpro.com/business/policy-legislation/370403/what-is-the-network-and-information-security-2-nis2-directive">NIS2 Directive</a> and the <a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra">Cyber Resilience Act (CRA)</a>.</p><p>However, Sonatype said that in 2025 alone, there were nearly 300 million total Log4j downloads, of which 40 million were vulnerable.</p><p>In China, the US, India, Japan, Brazil, Germany, the UK, Canada, South Korea, and France, between 8% and 29% of Log4j downloads still contained Log4Shell. India did particularly badly, with 29%, while the figure was 28% for China and 22% for Japan.</p><h2 id="log4j-complacency-persists">Log4j complacency persists</h2><p>According to Sonatype, the reason behind continued vulnerable Log4j downloads lies in a combination of complacency and the simple fact the incident occurred several years ago. </p><p>Moreover, visibility and oversight - or lack thereof - are also key factors in the trend. </p><p>"Once a library is wired in and everything compiles, it tends to stay that way. Versions get pinned, build files get copied from one service to the next, and no one revisits those choices unless something forces the issue — a breach, a compliance audit, or a production outage," said the firm.</p><p>"Without someone explicitly owning ongoing dependency maintenance, those 'temporary' choices turn into long-lived tech debt. Vulnerable versions of Log4j and other libraries stick around not because anyone chose them recently, but because no one chose to replace them."</p><p>Meanwhile, many vulnerable components — including Log4j in some stacks — are pulled in transitively by other libraries and frameworks, creating an ownership vacuum. </p><p>Component choices are typically optimized for speed and familiarity, rather than time-to-fix history, security posture, or the quality of governance and maintenance. </p><p><a href="https://www.itpro.com/security/adopting-more-security-tools-doesnt-keep-you-safe-it-just-overloads-your-teams-and-creates-greater-risks">Security tooling</a> doesn’t always help, either, thanks particularly to alert fatigue.</p><p>"If you’re not sure where you stand today, start by getting the numbers. Run a scan of your applications to find Log4j and other frequently downloaded vulnerable components, calculate what share of their usage is to vulnerable versions, and benchmark your own 'unnecessary risk rate'," said the firm.</p><p>"That’s the first step toward making sure Log4Shell is remembered as a turning point, not just an anniversary."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/open-source/open-source-security-in-the-spotlight-as-uk-gov-publishes-fresh-guidance">Open source security in the spotlight as UK gov publishes fresh guidance</a></li><li><a href="https://www.itpro.com/software/open-source/open-source-software-attacks-everything-you-need-to-look-out-for">Open source software attacks: Everything you need to look out for</a></li><li><a href="https://www.itpro.com/software/open-source/why-open-source-risks-threaten-all-business-users">Why we need a better understanding of open source software</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ NCSC issues urgent warning over growing AI prompt injection risks ]]></title>
                                                                                                <dc:content><![CDATA[ <p>The <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do">National Cyber Security Centre (NCSC)</a> is warning security teams to be on the lookout for AI prompt injection attacks. </p><p>These involve an attacker creating apparently innocent inputs to <a href="https://www.itpro.com/technology/artificial-intelligence/generative-ai-vs-large-language-models">large language models (LLMs)</a> which take advantage of the model's inability to distinguish between developer-defined prompts and user inputs to cause unintended behaviour.  </p><p>Prompt injection attacks are often seen as just another version of <a href="https://www.itpro.com/hacking/34441/how-does-a-sql-injection-attack-work">SQL injection</a> attacks, <a href="https://www.ncsc.gov.uk/blog-post/prompt-injection-is-not-sql-injection" target="_blank"><u>said</u></a> NCSC technical director for platforms research David C, with data and instructions being handled incorrectly - but this is a mistake.</p><p>In SQL, instructions are something the database engine does and data is something that is stored or used in a query; much the same is true in cross-site scripting and buffer overflows.</p><p>Mitigations for these issues enforce this separation between data and instructions. For example, the use of parameterized queries in SQL means the database engine can never interpret it as an instruction, regardless of the input. The right mitigation solves the data/instruction conflation at its root, David C pointed out.</p><p>"Under the hood of an LLM, there’s no distinction made between ‘data' or ‘instructions';  there is only ever ‘next token’. When you provide an LLM prompt, it doesn’t understand the text it in the way a person does. It is simply predicting the most likely next token from the text so far," he said. </p><p>"As there is no inherent distinction between ‘data’ and ‘instruction’, it’s very possible that prompt injection attacks may never be totally mitigated in the way that SQL injection attacks can be."</p><p>Security teams should stop treating prompt injection as a form of code injection, but instead view it as an exploitation of an ‘inherently confusable deputy’.</p><p>This is where a system can be coerced to perform a function that benefits the attacker, typically where a privileged component is coerced into making a request on behalf of a less-privileged attacker.</p><p>"Crucially, a classical confused deputy vulnerability can be mitigated, whilst I’d argue LLMs are ‘inherently confusable’ as the risk can’t be mitigated," said David C. </p><p>"Rather than hoping we can apply a mitigation that fixes prompt injection, we instead need to approach it by seeking to reduce the risk and the impact. If the system’s security cannot tolerate the remaining risk, it may not be a good use case for LLMs."</p><h2 id="ai-prompt-injection-attacks-are-rising">AI prompt injection attacks are rising</h2><p>Prompt injection attacks have become a recurring talking point over the last three years, with security experts warning about the potential for threat actors to manipulate AI models into producing malicious outputs. </p><p>Pete Luban, field CISO at AttackIQ, said the NCSC advice should be taken seriously by enterprises using the technology. </p><p>However, just because AI prompt injection attacks can't be mitigated in the same way as SQL injection attacks, Luban said this doesn't mean that lessons can't be learned from SQL injection defense.</p><p>"Developers need to build systems around LLMs with the awareness that prompt injection attacks are a threatening class of vulnerability. Since these attacks cannot be handled with a single product or appliance, careful design and operation is paramount to preventing exploitation," he said. </p><p>"Security teams should understand that all known methods of prompt injection prevention can only reduce chances of an attack or breach. Updating and strengthening their overall security posture, including continuously monitoring systems for irregularities and testing against common adversarial tactics, can help systems identify earlier stages of an attack and quickly move to mitigate it."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/business/ai-enabled-cyber-attacks-exacerbated-by-digital-divide-in-uk">AI-enabled cyber attacks exacerbated by digital divide in UK</a></li><li><a href="https://www.itpro.com/security/cyber-attacks/cyber-experts-have-been-warning-about-ai-powered-ddos-attacks-now-theyre-becoming-a-reality">Cyber experts have been warning about AI-powered DDoS attacks – now they’re becoming a reality</a></li><li><a href="https://www.itpro.com/security/generative-ai-attacks-are-accelerating-at-an-alarming-rate">Generative AI attacks are accelerating at an alarming rate</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/ncsc-issues-urgent-warning-over-growing-ai-prompt-injection-risks-heres-what-you-need-to-know</link>
                                                                            <description>
                            <![CDATA[ Many organizations see prompt injection as just another version of SQL injection - but this is a mistake ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">AfGsZaJjoWWekNw7mvLv9k</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/kwyhJmg3ouGdLEZpYEUPxb-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 09 Dec 2025 10:35:58 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:51 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/kwyhJmg3ouGdLEZpYEUPxb-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Malware concept image showing a laptop with skull and crossbones on screen, symbolizing a cyber attack.]]></media:description>                                                            <media:text><![CDATA[Malware concept image showing a laptop with skull and crossbones on screen, symbolizing a cyber attack.]]></media:text>
                                <media:title type="plain"><![CDATA[Malware concept image showing a laptop with skull and crossbones on screen, symbolizing a cyber attack.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/kwyhJmg3ouGdLEZpYEUPxb-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do">National Cyber Security Centre (NCSC)</a> is warning security teams to be on the lookout for AI prompt injection attacks. </p><p>These involve an attacker creating apparently innocent inputs to <a href="https://www.itpro.com/technology/artificial-intelligence/generative-ai-vs-large-language-models">large language models (LLMs)</a> which take advantage of the model's inability to distinguish between developer-defined prompts and user inputs to cause unintended behaviour.  </p><p>Prompt injection attacks are often seen as just another version of <a href="https://www.itpro.com/hacking/34441/how-does-a-sql-injection-attack-work">SQL injection</a> attacks, <a href="https://www.ncsc.gov.uk/blog-post/prompt-injection-is-not-sql-injection" target="_blank"><u>said</u></a> NCSC technical director for platforms research David C, with data and instructions being handled incorrectly - but this is a mistake.</p><p>In SQL, instructions are something the database engine does and data is something that is stored or used in a query; much the same is true in cross-site scripting and buffer overflows.</p><p>Mitigations for these issues enforce this separation between data and instructions. For example, the use of parameterized queries in SQL means the database engine can never interpret it as an instruction, regardless of the input. The right mitigation solves the data/instruction conflation at its root, David C pointed out.</p><p>"Under the hood of an LLM, there’s no distinction made between ‘data' or ‘instructions';  there is only ever ‘next token’. When you provide an LLM prompt, it doesn’t understand the text it in the way a person does. It is simply predicting the most likely next token from the text so far," he said. </p><p>"As there is no inherent distinction between ‘data’ and ‘instruction’, it’s very possible that prompt injection attacks may never be totally mitigated in the way that SQL injection attacks can be."</p><p>Security teams should stop treating prompt injection as a form of code injection, but instead view it as an exploitation of an ‘inherently confusable deputy’.</p><p>This is where a system can be coerced to perform a function that benefits the attacker, typically where a privileged component is coerced into making a request on behalf of a less-privileged attacker.</p><p>"Crucially, a classical confused deputy vulnerability can be mitigated, whilst I’d argue LLMs are ‘inherently confusable’ as the risk can’t be mitigated," said David C. </p><p>"Rather than hoping we can apply a mitigation that fixes prompt injection, we instead need to approach it by seeking to reduce the risk and the impact. If the system’s security cannot tolerate the remaining risk, it may not be a good use case for LLMs."</p><h2 id="ai-prompt-injection-attacks-are-rising">AI prompt injection attacks are rising</h2><p>Prompt injection attacks have become a recurring talking point over the last three years, with security experts warning about the potential for threat actors to manipulate AI models into producing malicious outputs. </p><p>Pete Luban, field CISO at AttackIQ, said the NCSC advice should be taken seriously by enterprises using the technology. </p><p>However, just because AI prompt injection attacks can't be mitigated in the same way as SQL injection attacks, Luban said this doesn't mean that lessons can't be learned from SQL injection defense.</p><p>"Developers need to build systems around LLMs with the awareness that prompt injection attacks are a threatening class of vulnerability. Since these attacks cannot be handled with a single product or appliance, careful design and operation is paramount to preventing exploitation," he said. </p><p>"Security teams should understand that all known methods of prompt injection prevention can only reduce chances of an attack or breach. Updating and strengthening their overall security posture, including continuously monitoring systems for irregularities and testing against common adversarial tactics, can help systems identify earlier stages of an attack and quickly move to mitigate it."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/business/ai-enabled-cyber-attacks-exacerbated-by-digital-divide-in-uk">AI-enabled cyber attacks exacerbated by digital divide in UK</a></li><li><a href="https://www.itpro.com/security/cyber-attacks/cyber-experts-have-been-warning-about-ai-powered-ddos-attacks-now-theyre-becoming-a-reality">Cyber experts have been warning about AI-powered DDoS attacks – now they’re becoming a reality</a></li><li><a href="https://www.itpro.com/security/generative-ai-attacks-are-accelerating-at-an-alarming-rate">Generative AI attacks are accelerating at an alarming rate</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ ‘Slopsquatting’ is a new risk for vibe coding developers – but it can be solved by focusing on the fundamentals ]]></title>
                                                                                                <dc:content><![CDATA[ <p>AI tools offer great potential to clear up time for developers and software engineers – but can also be manipulated to introduce malware and other threats through a new attack vector known as ‘slopsquatting’</p><p>Slopsquatting is an attack method in which hackers exploit common <a href="https://www.itpro.com/technology/artificial-intelligence/ai-hallucinations-what-are-they"><u>AI hallucinations</u></a> to trick engineers into mistakenly installing malicious packages. </p><p>In short, hackers track non-existent packages hallucinated by <a href="https://www.itpro.com/technology/artificial-intelligence/how-ai-coding-is-transforming-the-it-industry-in-2025"><u>AI coding tools</u></a> and then publish malicious packages under these names on public repositories such as <a href="https://www.itpro.com/software/back-from-the-dead-new-revival-hijack-technique-leaves-22000-pypi-projects-vulnerable-to-attacks"><u>PyPI</u></a>. The seemingly legitimate packages are then installed by victims who trust their AI code suggestions.</p><p><em>ITPro </em>spoke to Dustin Kirkland, SVP of Engineering at Chainguard, to learn more about slopsquatting and where it sits in the wider issue of risky AI code.</p><p>“It’s kind of a modern twist on <a href="https://www.itpro.com/business/business-strategy/north-korean-hackers-targeting-developers-open-source-malware-36000#:~:text=That%20includes%20typosquatting,the%20report%20noted."><u>typosquatting</u></a>, we’ve seen that for many years all the way down to simple URLs, you accidentally leave one letter out of ‘Google’ and end up on a malicious site, or something like that,” Kirkland adds.</p><p>The term ‘slopsquatting’ combines ‘typosquatting’ and <a href="https://www.itpro.com/technology/artificial-intelligence/agentic-ai-hype-openai-andrej-karpathy"><u>‘AI slop’</u></a>, a pejorative term for low-effort content generated with AI, Kirkland said </p><p>“For at least ten years, typosquatting has been a problem in the Python and Java universes, where it's quite easy for almost anyone to <a href="https://www.itpro.com/software/development/developers-beware-these-rogue-python-packages-hide-a-nasty-surprise"><u>register a Python package with PIP Python</u></a> and PIP install. </p><p>Kirkland told <em>ITPro</em> that porting this attack methodology into AI comes with risky implications, as developers are increasingly engaged in <a href="https://www.itpro.com/technology/artificial-intelligence/vibe-coding-security-risks-how-to-mitigate"><u>vibe coding</u></a> to produce business-critical code at scale.</p><p>“I would say an old school human coder, especially in the <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> world where I've spent my entire career, every line of code was typically reviewed and approved by a human maintainer.</p><p>“And now the ability of an AI to generate literally gigabytes of code, millions, if not billions of lines of code, starts to put this out of the reach of even some of the most prolific maintainers. </p><p>“And so the scary risk is that these sorts of problems leak into systems that don't get as much human verification.”</p><p>But Kirkland sees potential for <a href="https://www.itpro.com/technology/artificial-intelligence/enterprises-are-worried-about-agentic-ai-security-risks-gartner-says-the-answer-is-just-adding-more-ai-agents"><u>AI assistants to police one another</u></a>, with designated agents taught to identify signs of slopsquatting, typosquatting, and other common attacks using predefined algorithms.</p><p>“[W]hen using something like AI here, one of the real advantages over the human way of doing it is when there is identified a new way of a malicious actor slopsquatting, we can create one algorithm and roll it out comprehensively by updating a single model,” he explained.</p><h2 id="ai-risks-aren-t-top-of-mind-for-leaders">AI risks aren’t top of mind for leaders</h2><p>Chainguard’s <a href="https://www.chainguard.dev/2026-engineering-reality-report" target="_blank"><u><em>2026 Engineering Reality Report</em></u></a> took in responses from 1,200 software engineers and senior technology leaders from across the US, UK, France, and Germany.</p><p>The report also found widespread enthusiasm for using AI tools to mostly or entirely automate tasks in the engineering workflow.</p><p>For example, over two thirds (68%) of respondents said testing, monitoring, and quality assurance had been automated in this way, with a similar figure registered for security patching and vulnerability remediation (67%) as well as code review (65%).</p><p>However, the report also shed light on the core concerns holding software engineers back from full AI adoption. </p><p>The top concern among respondents was the lack of security and privacy associated with AI, with 17% saying as much, while other core concerns included accountability and <a href="https://www.itpro.com/software/development/developers-arent-quite-ready-to-place-their-trust-in-ai-nearly-half-say-they-dont-trust-the-accuracy-of-outputs-and-end-up-wasting-time-debugging-code"><u>trust in code</u></a> and the use of <a href="https://www.itpro.com/technology/artificial-intelligence/shadow-ai-can-be-a-tool-for-ai-innovation-with-the-right-controls-say-gartner-analysts"><u>shadow AI</u></a>.</p><p>Kirkland said these concerns can be eased as firms set out AI usage policies, with Chainguard having rolled its own out at the start of 2025.</p><iframe allow="" height="200px" width="100%" id="" style="" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/" src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/"></iframe><p>This “living document” clearly sets out trusted AI tools employees can use, which reduces operational risk and helps provide oversight for the packages and libraries developers install.</p><p>To prevent slopsquatting in the short term, Kirkland suggested firms could look to methods such as more closely verifying package registries and signatures to prevent those from unknown sources being installed.</p><p>In the long term, Kirkland told <em>ITPro</em> he sees slopsquatting and cybersquatting as a solvable problem. He added that with AI security tools in place, it’s increasingly likely that only the most sophisticated attacks will get through.</p><p>“Just being somewhat contemporary and topical here, when was the last time you heard of an art museum having jewels stolen, right? That's typically, that's typically the story of movies and blockbuster hits and yet, here we are in 2025 and the world's most famous art museum had some of its most famous jewels stolen.”</p><p>In the same way, Kirkland is confident that automated security algorithms that check the popularity, age, and author of packages will ensure that slopsquatting and similar attacks become the exception rather than the rule.</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/development/senior-developers-are-all-in-on-vibe-coding-but-junior-staff-lack-the-experience-to-spot-critical-flaws">Senior developers are all in on vibe coding, but junior staff lack the experience to spot critical flaws</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/vibe-coding-security-risks-how-to-mitigate">Vibe coding security risks and how to mitigate them</a></li><li><a href="https://www.itpro.com/software/development/google-brain-founder-andrew-ng-thinks-everyone-should-learn-programming-with-vibe-coding-tools-industry-experts-say-thats-probably-a-bad-idea">Google Brain founder Andrew Ng thinks everyone should learn programming with ‘vibe coding’ tools</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/slopsquatting-is-a-new-risk-for-vibe-coding-developers-but-it-can-be-solved-by-focusing-on-the-fundamentals</link>
                                                                            <description>
                            <![CDATA[ Malicious packages in public code repositories can be given a sheen of authenticity via AI tools ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">nrfYEC9eQKrXXvr6pftQg3</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/rBugFrvBfGD6iWyyBsYx8j-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 19 Nov 2025 14:30:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:52 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                <author><![CDATA[ rory.bathgate@futurenet.com (Rory Bathgate) ]]></author>                    <dc:creator><![CDATA[ Rory Bathgate ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Vep5JogbPhduK7R6CUWAm6-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Rory Bathgate was the Features and Multimedia Editor at ITPro until 2026, overseeing all in-depth content and case studies. Throughout his time at ITPro, Rory  charted the rise in popularity of generative AI and specifically companies such as Microsoft, OpenAI, and Google. &lt;/p&gt;&lt;p&gt;Alongside this, he delved into increasing calls for ethical and responsible AI as global legislators circle the technology, as well as the latest in mobile networking technology, from 5G mmWave to the 3G sunset and how it will affect businesses.&lt;/p&gt;&lt;p&gt;He  provided coverage from high-profile tech conferences such as Dell Technologies World, SuiteWorld, and VMware Explore Europe. His on-the-ground coverage  included live blogs, extensive daily coverage of the most significant announcements, analysis pieces, and podcast.&lt;/p&gt;&lt;p&gt;Rory was the co-host of the ITPro Podcast alongside Jane McCallion, where he swapped a keyboard for a microphone to discuss the latest learnings in tech.&lt;/p&gt;&lt;p&gt;Rory has an MA in Eighteenth-Century Studies from King’s College London, as well as a BA in English and American Literature from the University of Kent. He joined ITPro in 2022 as a graduate, after four years in student journalism.&lt;/p&gt;&lt;p&gt;In his free time, Rory enjoys photography and video editing, and can often be found at the cinema or reading a good science fiction paperback.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/rBugFrvBfGD6iWyyBsYx8j-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Female software developer using vibe coding tools on a desktop computer alongside a colleague with source code pictured on screens.]]></media:description>                                                            <media:text><![CDATA[Female software developer using vibe coding tools on a desktop computer alongside a colleague with source code pictured on screens.]]></media:text>
                                <media:title type="plain"><![CDATA[Female software developer using vibe coding tools on a desktop computer alongside a colleague with source code pictured on screens.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/rBugFrvBfGD6iWyyBsYx8j-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>AI tools offer great potential to clear up time for developers and software engineers – but can also be manipulated to introduce malware and other threats through a new attack vector known as ‘slopsquatting’</p><p>Slopsquatting is an attack method in which hackers exploit common <a href="https://www.itpro.com/technology/artificial-intelligence/ai-hallucinations-what-are-they"><u>AI hallucinations</u></a> to trick engineers into mistakenly installing malicious packages. </p><p>In short, hackers track non-existent packages hallucinated by <a href="https://www.itpro.com/technology/artificial-intelligence/how-ai-coding-is-transforming-the-it-industry-in-2025"><u>AI coding tools</u></a> and then publish malicious packages under these names on public repositories such as <a href="https://www.itpro.com/software/back-from-the-dead-new-revival-hijack-technique-leaves-22000-pypi-projects-vulnerable-to-attacks"><u>PyPI</u></a>. The seemingly legitimate packages are then installed by victims who trust their AI code suggestions.</p><p><em>ITPro </em>spoke to Dustin Kirkland, SVP of Engineering at Chainguard, to learn more about slopsquatting and where it sits in the wider issue of risky AI code.</p><p>“It’s kind of a modern twist on <a href="https://www.itpro.com/business/business-strategy/north-korean-hackers-targeting-developers-open-source-malware-36000#:~:text=That%20includes%20typosquatting,the%20report%20noted."><u>typosquatting</u></a>, we’ve seen that for many years all the way down to simple URLs, you accidentally leave one letter out of ‘Google’ and end up on a malicious site, or something like that,” Kirkland adds.</p><p>The term ‘slopsquatting’ combines ‘typosquatting’ and <a href="https://www.itpro.com/technology/artificial-intelligence/agentic-ai-hype-openai-andrej-karpathy"><u>‘AI slop’</u></a>, a pejorative term for low-effort content generated with AI, Kirkland said </p><p>“For at least ten years, typosquatting has been a problem in the Python and Java universes, where it's quite easy for almost anyone to <a href="https://www.itpro.com/software/development/developers-beware-these-rogue-python-packages-hide-a-nasty-surprise"><u>register a Python package with PIP Python</u></a> and PIP install. </p><p>Kirkland told <em>ITPro</em> that porting this attack methodology into AI comes with risky implications, as developers are increasingly engaged in <a href="https://www.itpro.com/technology/artificial-intelligence/vibe-coding-security-risks-how-to-mitigate"><u>vibe coding</u></a> to produce business-critical code at scale.</p><p>“I would say an old school human coder, especially in the <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> world where I've spent my entire career, every line of code was typically reviewed and approved by a human maintainer.</p><p>“And now the ability of an AI to generate literally gigabytes of code, millions, if not billions of lines of code, starts to put this out of the reach of even some of the most prolific maintainers. </p><p>“And so the scary risk is that these sorts of problems leak into systems that don't get as much human verification.”</p><p>But Kirkland sees potential for <a href="https://www.itpro.com/technology/artificial-intelligence/enterprises-are-worried-about-agentic-ai-security-risks-gartner-says-the-answer-is-just-adding-more-ai-agents"><u>AI assistants to police one another</u></a>, with designated agents taught to identify signs of slopsquatting, typosquatting, and other common attacks using predefined algorithms.</p><p>“[W]hen using something like AI here, one of the real advantages over the human way of doing it is when there is identified a new way of a malicious actor slopsquatting, we can create one algorithm and roll it out comprehensively by updating a single model,” he explained.</p><h2 id="ai-risks-aren-t-top-of-mind-for-leaders">AI risks aren’t top of mind for leaders</h2><p>Chainguard’s <a href="https://www.chainguard.dev/2026-engineering-reality-report" target="_blank"><u><em>2026 Engineering Reality Report</em></u></a> took in responses from 1,200 software engineers and senior technology leaders from across the US, UK, France, and Germany.</p><p>The report also found widespread enthusiasm for using AI tools to mostly or entirely automate tasks in the engineering workflow.</p><p>For example, over two thirds (68%) of respondents said testing, monitoring, and quality assurance had been automated in this way, with a similar figure registered for security patching and vulnerability remediation (67%) as well as code review (65%).</p><p>However, the report also shed light on the core concerns holding software engineers back from full AI adoption. </p><p>The top concern among respondents was the lack of security and privacy associated with AI, with 17% saying as much, while other core concerns included accountability and <a href="https://www.itpro.com/software/development/developers-arent-quite-ready-to-place-their-trust-in-ai-nearly-half-say-they-dont-trust-the-accuracy-of-outputs-and-end-up-wasting-time-debugging-code"><u>trust in code</u></a> and the use of <a href="https://www.itpro.com/technology/artificial-intelligence/shadow-ai-can-be-a-tool-for-ai-innovation-with-the-right-controls-say-gartner-analysts"><u>shadow AI</u></a>.</p><p>Kirkland said these concerns can be eased as firms set out AI usage policies, with Chainguard having rolled its own out at the start of 2025.</p><iframe allow="" height="200px" width="100%" id="" style="" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/" src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/"></iframe><p>This “living document” clearly sets out trusted AI tools employees can use, which reduces operational risk and helps provide oversight for the packages and libraries developers install.</p><p>To prevent slopsquatting in the short term, Kirkland suggested firms could look to methods such as more closely verifying package registries and signatures to prevent those from unknown sources being installed.</p><p>In the long term, Kirkland told <em>ITPro</em> he sees slopsquatting and cybersquatting as a solvable problem. He added that with AI security tools in place, it’s increasingly likely that only the most sophisticated attacks will get through.</p><p>“Just being somewhat contemporary and topical here, when was the last time you heard of an art museum having jewels stolen, right? That's typically, that's typically the story of movies and blockbuster hits and yet, here we are in 2025 and the world's most famous art museum had some of its most famous jewels stolen.”</p><p>In the same way, Kirkland is confident that automated security algorithms that check the popularity, age, and author of packages will ensure that slopsquatting and similar attacks become the exception rather than the rule.</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/development/senior-developers-are-all-in-on-vibe-coding-but-junior-staff-lack-the-experience-to-spot-critical-flaws">Senior developers are all in on vibe coding, but junior staff lack the experience to spot critical flaws</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/vibe-coding-security-risks-how-to-mitigate">Vibe coding security risks and how to mitigate them</a></li><li><a href="https://www.itpro.com/software/development/google-brain-founder-andrew-ng-thinks-everyone-should-learn-programming-with-vibe-coding-tools-industry-experts-say-thats-probably-a-bad-idea">Google Brain founder Andrew Ng thinks everyone should learn programming with ‘vibe coding’ tools</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Vibe coding security risks and how to mitigate them ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Vibe coding is gaining traction. The <a href="https://www.itpro.com/software/development/vibe-coding-best-ai-models-secure-code-generation"><u>technique</u></a> – which sees a developer describe their project to a large language model (LLM) to generate code – allows programmers to create software and apps with limited training and skills, lowering costs and boosting efficiency. </p><p>OpenAI co-founder and former AI chief at Tesla Andrej Karpathy – who <a href="https://x.com/karpathy/status/1886192184808149383?lang=en" target="_blank"><u>popularized the term</u></a> at the start of 2025 – describes it as "fully giving in to the vibes, embracing exponentials, and forgetting that the code even exists”. </p><p>But vibe coding also opens businesses up to security risks, including the possibility of introducing vulnerabilities into the software being created. In fact, <a href="https://www.itpro.com/technology/artificial-intelligence/researchers-tested-over-100-leading-ai-models-on-coding-tasks-nearly-half-produced-glaring-security-flaws"><u>nearly half of all code generated by AI contains security flaws</u></a>, despite appearing production ready, according to Veracode’s 2025 GenAI Code Security report. </p><p>Veracode tested 100 leading LLMs across 80 curated tasks and found they produced insecure code 45% of the time, with no real improvement across newer or larger models.</p><p>It’s also frighteningly easy to make mistakes: earlier this year, a vibe-coding CEO <a href="https://www.itpro.com/technology/artificial-intelligence/the-replit-vibe-coding-incident-gives-us-a-glimpse-into-why-developers-are-still-wary-of-ai-coding-assistants"><u>managed to delete his entire codebase</u></a> while using Replit’s AI assistant.</p><h2 id="vibe-coding-benefits-versus-risk">Vibe coding: benefits versus risk</h2><p>Vibe coding simplifies app development, but it often bypasses essential security vetting and <a href="https://www.itpro.com/business/policy-and-legislation/compliance-how-the-channel-can-deliver-optimal-enterprise-solutions-tailored-to-evolving-regulations">regulatory compliance</a> checks, says Dr Jeff Schwartzentruber, senior machine learning scientist at eSentire. “Without rigorous preplanning, architectural oversight and experienced project management, vibe coding can introduce vulnerabilities, compliance gaps and substantial <a href="https://www.itpro.com/business/digital-transformation/paying-down-technical-problem-for-businesses">technical debt</a>.”</p><p>Vibe coding lowers the barrier to entry for creating software, but the autonomous nature of AI-generated suggestions introduces security risks, says Louise Fellows, VP, northern Europe at GitLab. <strong>“</strong>AI provides the ‘vibe’ or suggested patterns that developers might accept without critical evaluation or deep comprehension of their underlying security implications. This can result in vulnerabilities in the codebase.”</p><p>At the same time, the AI may not inherently prioritize security best practices, or adhere to specific organizational policies and compliance with regulations such as the <a href="https://www.itpro.com/it-legislation/27814/what-is-gdpr-everything-you-need-to-know"><u>EU general data protection regulation (GDPR)</u></a>.<strong> </strong>“Without <a href="https://www.itpro.com/technology/artificial-intelligence/organizations-face-ticking-timebomb-over-ai-governance">proper governance</a> and continuous security training, <a href="https://www.itpro.com/technology/artificial-intelligence/agentic-ai-carries-huge-implications-for-security-teams-heres-what-leaders-should-know">AI agents may suggest or generate code that includes outdated or vulnerable third-party libraries</a>, lacks essential security controls, or improperly handles sensitive data,” Fellows warns.</p><p>The core problem is that AI <a href="https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually"><u>doesn’t write secure code by default</u></a>. “It just spits out something that works, but under the hood, the logic can be completely wrong, or wide open to attacks,” says Mackenzie Jackson, developer and security advocate at Aikido Security.</p><p>Vibe coding skips too many checks says Camden Woollven, group head of AI product marketing at GRC International Group, who tells <em>ITPro</em> this compounds the issue. “Developers are using AI to write code fast, often without reviewing it properly or even understanding what it’s doing.”</p><p>That leads to vulnerabilities including <a href="https://www.itpro.com/software/development/mcp-servers-security-vulnerabilities"><u>injection flaws</u></a>, poor authorization, missing validation and hardcoded secrets, says Woollven. “If no one’s checking, that code goes live,” she adds.</p><p>Then there’s the <a href="https://www.itpro.com/software/ceos-want-ai-in-everything-but-software-engineers-are-pushing-back-extensive-application-upgrades-are-a-becoming-a-huge-paint-point-for-teams">dependency sprawl</a>. “One prompt can pull in a dozen libraries, some of them insecure or unmaintained,” says Woollven. “If no one’s vetting what the model uses, you’re stacking risk fast. Worse, you end up with code no one fully owns or understands. No documentation, no visibility, no easy way to debug or maintain it. That becomes a long-term liability.”</p><p><a href="https://www.itpro.com/software/development/developers-arent-quite-ready-to-place-their-trust-in-ai-nearly-half-say-they-dont-trust-the-accuracy-of-outputs-and-end-up-wasting-time-debugging-code">Debugging is tough</a>, even when you write the code yourself, says Jackson. “When it’s generated by a machine that’s making thousands of assumptions from a tiny prompt, it’s even harder.”</p><p>He points to issues with platforms such Lovable, where apps built by hobby developers can have <a href="https://mattpalmer.io/posts/CVE-2025-48757/"><u>serious security holes</u></a>. “That’s just a preview of what we’re going to see all over the web as this keeps scaling up.”</p><iframe allow="" height="200px" width="100%" id="" style="" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/" src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/"></iframe><h2 id="secure-vibe-coding-best-practices">Secure vibe coding best practices </h2><p>Despite the risks, vibe coding is already being used by businesses, making it important that firms are on top of the trend and including it in their AI security strategies. The first rule is simple: <a href="https://www.itpro.com/security/agentic-ai-poses-major-challenge-for-security-professionals-says-palo-alto-networks-emea-ciso"><u>Treat AI-generated code as untrusted</u></a>, says Woollven. “Just because it runs doesn’t mean it’s safe.”</p><p>Firms also need to ensure governance measures are in place. “Set clear rules on <a href="https://www.itpro.com/technology/artificial-intelligence/shadow-ai-can-be-a-tool-for-ai-innovation-with-the-right-controls-say-gartner-analysts">where and how AI tools can be used</a>, who’s allowed to take advantage of them, and what kind of review is mandatory,” Woollven advises. “Nothing should ship without sign-off from someone who knows what they’re looking at.”</p><p>Secure vibe coding starts with “strong governance and a human-centric approach”, says Fellows. As part of this, she urges IT leaders to establish clear accountability. “Teams should implement composite identities that directly link AI agent actions to specific human owners. This ensures you always know who's responsible for the code, even when AI suggests it.”</p><p>Over time, firms should prioritize continuous human oversight and automated checks, Fellows adds. “Human review gates must remain in place, alongside automated testing, to catch issues early before they reach production.”</p><p>It’s not enough to know what code is produced, she says. “You also need to monitor its security impact in staging and production environments, associated databases, and any applications it has access to.”</p><p>To boost security in vibe coding, sanitize inputs and use parameterized queries to avoid injection attack, Jackson advises. “Put rate limits in place so someone can’t just hammer your endpoints and never leave secrets such as <a href="https://www.itpro.com/security/12-000-api-keys-and-passwords-were-found-in-a-popular-ai-training-dataset-experts-say-the-issue-is-down-to-poor-identity-management">API keys sitting in your frontend code </a>or in a public repository.”</p><p>Meanwhile, continually check your packages are up to date and therefore secure: “A ton of attacks <a href="https://www.itpro.com/security/patch-management-why-firms-ignore-vulnerabilities-at-their-own-risk">target old vulnerabilities</a>,” Jackson warns.</p><p>As vibe coding takes off, educating employees of the risks will go some way to preventing security issues before they happen. With this in mind, Fellows recommends “<a href="https://www.itpro.com/security/cybersecurity-skills-what-can-be-done">upskilling teams</a> on prompt hygiene and clearly defining when and where vibe coding is appropriate”. </p><p>If you let things get out of control, mistakes are bound to happen. Therefore, if you are going to use vibe coding capabilities, keep the scope small, Woollven says. “Don’t use AI to generate a whole app. Avoid letting it write anything critical like auth, crypto or system-level code – build those parts yourself.”</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/technology/artificial-intelligence/vibe-coding-security-risks-how-to-mitigate</link>
                                                                            <description>
                            <![CDATA[ Vibe coding is increasingly popular, yet it opens firms up to multiple security risks – here’s what businesses need to know. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">viSw7Y2MAjwEhEBnjPWK3n</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/2s4vaz2AeVQcdZC6PXnE9G-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 31 Oct 2025 13:04:02 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:54 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Artificial Intelligence]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Kate O&#039;Flaherty ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/LUULv6n7VJ3BHPnaoLHHdg-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/2s4vaz2AeVQcdZC6PXnE9G-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[A stylized illustration showing a male software engineer wearing a yellow t shirt pressing a large blue button bearing the text &quot;PROMPT&quot; and three stars to show it&#039;s referring to an AI prompt. Beneath, code is beginning to be written, to show vibe coding. These elements are set against a light gray background, with a green speech bubble and large white cog directly behind the aforementioned elements.]]></media:description>                                                            <media:text><![CDATA[A stylized illustration showing a male software engineer wearing a yellow t shirt pressing a large blue button bearing the text &quot;PROMPT&quot; and three stars to show it&#039;s referring to an AI prompt. Beneath, code is beginning to be written, to show vibe coding. These elements are set against a light gray background, with a green speech bubble and large white cog directly behind the aforementioned elements.]]></media:text>
                                <media:title type="plain"><![CDATA[A stylized illustration showing a male software engineer wearing a yellow t shirt pressing a large blue button bearing the text &quot;PROMPT&quot; and three stars to show it&#039;s referring to an AI prompt. Beneath, code is beginning to be written, to show vibe coding. These elements are set against a light gray background, with a green speech bubble and large white cog directly behind the aforementioned elements.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/2s4vaz2AeVQcdZC6PXnE9G-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Vibe coding is gaining traction. The <a href="https://www.itpro.com/software/development/vibe-coding-best-ai-models-secure-code-generation"><u>technique</u></a> – which sees a developer describe their project to a large language model (LLM) to generate code – allows programmers to create software and apps with limited training and skills, lowering costs and boosting efficiency. </p><p>OpenAI co-founder and former AI chief at Tesla Andrej Karpathy – who <a href="https://x.com/karpathy/status/1886192184808149383?lang=en" target="_blank"><u>popularized the term</u></a> at the start of 2025 – describes it as "fully giving in to the vibes, embracing exponentials, and forgetting that the code even exists”. </p><p>But vibe coding also opens businesses up to security risks, including the possibility of introducing vulnerabilities into the software being created. In fact, <a href="https://www.itpro.com/technology/artificial-intelligence/researchers-tested-over-100-leading-ai-models-on-coding-tasks-nearly-half-produced-glaring-security-flaws"><u>nearly half of all code generated by AI contains security flaws</u></a>, despite appearing production ready, according to Veracode’s 2025 GenAI Code Security report. </p><p>Veracode tested 100 leading LLMs across 80 curated tasks and found they produced insecure code 45% of the time, with no real improvement across newer or larger models.</p><p>It’s also frighteningly easy to make mistakes: earlier this year, a vibe-coding CEO <a href="https://www.itpro.com/technology/artificial-intelligence/the-replit-vibe-coding-incident-gives-us-a-glimpse-into-why-developers-are-still-wary-of-ai-coding-assistants"><u>managed to delete his entire codebase</u></a> while using Replit’s AI assistant.</p><h2 id="vibe-coding-benefits-versus-risk">Vibe coding: benefits versus risk</h2><p>Vibe coding simplifies app development, but it often bypasses essential security vetting and <a href="https://www.itpro.com/business/policy-and-legislation/compliance-how-the-channel-can-deliver-optimal-enterprise-solutions-tailored-to-evolving-regulations">regulatory compliance</a> checks, says Dr Jeff Schwartzentruber, senior machine learning scientist at eSentire. “Without rigorous preplanning, architectural oversight and experienced project management, vibe coding can introduce vulnerabilities, compliance gaps and substantial <a href="https://www.itpro.com/business/digital-transformation/paying-down-technical-problem-for-businesses">technical debt</a>.”</p><p>Vibe coding lowers the barrier to entry for creating software, but the autonomous nature of AI-generated suggestions introduces security risks, says Louise Fellows, VP, northern Europe at GitLab. <strong>“</strong>AI provides the ‘vibe’ or suggested patterns that developers might accept without critical evaluation or deep comprehension of their underlying security implications. This can result in vulnerabilities in the codebase.”</p><p>At the same time, the AI may not inherently prioritize security best practices, or adhere to specific organizational policies and compliance with regulations such as the <a href="https://www.itpro.com/it-legislation/27814/what-is-gdpr-everything-you-need-to-know"><u>EU general data protection regulation (GDPR)</u></a>.<strong> </strong>“Without <a href="https://www.itpro.com/technology/artificial-intelligence/organizations-face-ticking-timebomb-over-ai-governance">proper governance</a> and continuous security training, <a href="https://www.itpro.com/technology/artificial-intelligence/agentic-ai-carries-huge-implications-for-security-teams-heres-what-leaders-should-know">AI agents may suggest or generate code that includes outdated or vulnerable third-party libraries</a>, lacks essential security controls, or improperly handles sensitive data,” Fellows warns.</p><p>The core problem is that AI <a href="https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually"><u>doesn’t write secure code by default</u></a>. “It just spits out something that works, but under the hood, the logic can be completely wrong, or wide open to attacks,” says Mackenzie Jackson, developer and security advocate at Aikido Security.</p><p>Vibe coding skips too many checks says Camden Woollven, group head of AI product marketing at GRC International Group, who tells <em>ITPro</em> this compounds the issue. “Developers are using AI to write code fast, often without reviewing it properly or even understanding what it’s doing.”</p><p>That leads to vulnerabilities including <a href="https://www.itpro.com/software/development/mcp-servers-security-vulnerabilities"><u>injection flaws</u></a>, poor authorization, missing validation and hardcoded secrets, says Woollven. “If no one’s checking, that code goes live,” she adds.</p><p>Then there’s the <a href="https://www.itpro.com/software/ceos-want-ai-in-everything-but-software-engineers-are-pushing-back-extensive-application-upgrades-are-a-becoming-a-huge-paint-point-for-teams">dependency sprawl</a>. “One prompt can pull in a dozen libraries, some of them insecure or unmaintained,” says Woollven. “If no one’s vetting what the model uses, you’re stacking risk fast. Worse, you end up with code no one fully owns or understands. No documentation, no visibility, no easy way to debug or maintain it. That becomes a long-term liability.”</p><p><a href="https://www.itpro.com/software/development/developers-arent-quite-ready-to-place-their-trust-in-ai-nearly-half-say-they-dont-trust-the-accuracy-of-outputs-and-end-up-wasting-time-debugging-code">Debugging is tough</a>, even when you write the code yourself, says Jackson. “When it’s generated by a machine that’s making thousands of assumptions from a tiny prompt, it’s even harder.”</p><p>He points to issues with platforms such Lovable, where apps built by hobby developers can have <a href="https://mattpalmer.io/posts/CVE-2025-48757/"><u>serious security holes</u></a>. “That’s just a preview of what we’re going to see all over the web as this keeps scaling up.”</p><iframe allow="" height="200px" width="100%" id="" style="" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/" src="https://player.captivate.fm/episode/20d5b431-d29a-41dc-9ba0-4802a06f2284/"></iframe><h2 id="secure-vibe-coding-best-practices">Secure vibe coding best practices </h2><p>Despite the risks, vibe coding is already being used by businesses, making it important that firms are on top of the trend and including it in their AI security strategies. The first rule is simple: <a href="https://www.itpro.com/security/agentic-ai-poses-major-challenge-for-security-professionals-says-palo-alto-networks-emea-ciso"><u>Treat AI-generated code as untrusted</u></a>, says Woollven. “Just because it runs doesn’t mean it’s safe.”</p><p>Firms also need to ensure governance measures are in place. “Set clear rules on <a href="https://www.itpro.com/technology/artificial-intelligence/shadow-ai-can-be-a-tool-for-ai-innovation-with-the-right-controls-say-gartner-analysts">where and how AI tools can be used</a>, who’s allowed to take advantage of them, and what kind of review is mandatory,” Woollven advises. “Nothing should ship without sign-off from someone who knows what they’re looking at.”</p><p>Secure vibe coding starts with “strong governance and a human-centric approach”, says Fellows. As part of this, she urges IT leaders to establish clear accountability. “Teams should implement composite identities that directly link AI agent actions to specific human owners. This ensures you always know who's responsible for the code, even when AI suggests it.”</p><p>Over time, firms should prioritize continuous human oversight and automated checks, Fellows adds. “Human review gates must remain in place, alongside automated testing, to catch issues early before they reach production.”</p><p>It’s not enough to know what code is produced, she says. “You also need to monitor its security impact in staging and production environments, associated databases, and any applications it has access to.”</p><p>To boost security in vibe coding, sanitize inputs and use parameterized queries to avoid injection attack, Jackson advises. “Put rate limits in place so someone can’t just hammer your endpoints and never leave secrets such as <a href="https://www.itpro.com/security/12-000-api-keys-and-passwords-were-found-in-a-popular-ai-training-dataset-experts-say-the-issue-is-down-to-poor-identity-management">API keys sitting in your frontend code </a>or in a public repository.”</p><p>Meanwhile, continually check your packages are up to date and therefore secure: “A ton of attacks <a href="https://www.itpro.com/security/patch-management-why-firms-ignore-vulnerabilities-at-their-own-risk">target old vulnerabilities</a>,” Jackson warns.</p><p>As vibe coding takes off, educating employees of the risks will go some way to preventing security issues before they happen. With this in mind, Fellows recommends “<a href="https://www.itpro.com/security/cybersecurity-skills-what-can-be-done">upskilling teams</a> on prompt hygiene and clearly defining when and where vibe coding is appropriate”. </p><p>If you let things get out of control, mistakes are bound to happen. Therefore, if you are going to use vibe coding capabilities, keep the scope small, Woollven says. “Don’t use AI to generate a whole app. Avoid letting it write anything critical like auth, crypto or system-level code – build those parts yourself.”</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ AI-generated code now behind one-in-five breaches ]]></title>
                                                                                                <dc:content><![CDATA[ <p><a href="https://www.itpro.com/software/development/ai-coding-tools-arent-the-solution-to-the-unfolding-developer-crisis-teams-think-they-can-boost-productivity-and-delivery-times-but-end-up-bogged-down-by-manual-remediation-and-unsafe-code">AI coding tools</a> are creating serious security risks in production, with one-in-five CISOs saying they've suffered major incidents because of <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated code</a>.</p><p>AI coding tools now write 24% of production code – 21% in Europe and 29% in the US – according to a new <a href="https://www.aikido.dev/state-of-ai-security-development-2026" target="_blank"><u>report</u></a> from Aikido. But it's risky, with 69% of security leaders, security engineers, and developers across Europe and the US revealing they'd found serious vulnerabilities in AI-written code.</p><p>US-based respondents were among the worst hit by AI-related flaws, with 43% of organizations reporting serious incidents, compared with just 20% in Europe. </p><p>This, the study noted, appears to be down to better prevention and oversight. For example, EU-based firms reported more “near misses” with AI-generated code than their US counterparts, potentially highlighting more robust testing practices. </p><p>Adding more tools to address the issue isn’t helping, Aikido found. Indeed, <a href="https://www.itpro.com/security/adopting-more-security-tools-doesnt-keep-you-safe-it-just-overloads-your-teams-and-creates-greater-risks">organizations with more security tools report more incidents</a>, with more overhead and slower remediation. </p><p>Nearly two-thirds (64%) of those with just one or two tools had an incident, the figure was 90% for those with between six and nine tools. </p><h2 id="all-in-one-ai-coding-tools-are-helping-bridge-gaps">All-in-one AI coding tools are helping bridge gaps</h2><p>Notably, teams using tools designed for both developers and security teams were more than twice as likely to report zero incidents than those using tools made for only one specific group.</p><p>“Giving developers the right security tool that works with existing tools and workflows allows teams to implement security best practices and improve their posture,” commented Walid Mahmoud, <a href="https://www.itpro.com/development/devops/354215/what-is-devsecops-and-why-is-it-important">DevSecOps </a>lead at the UK Cabinet Office.</p><p>Teams using separate AppSec and CloudSec tools were 50% more likely to face incidents, and 93% of those with separate tools reported integration headaches such as duplicate alerts or inconsistent data.</p><h2 id="the-security-blame-game-is-heating-up">The security blame game is heating up</h2><p>The blame for incidents caused by AI code is now becoming a serious point of contention within enterprises, the report noted. For example, 53% of respondents blamed security teams for failing to address issues, while 45% blamed developers who failed to spot issues before pushing to production. </p><p>Meanwhile, 42% pointed toward whoever merged it. This blame game is expected to continue escalating, according to Aikido. Half of developers reckoned they’d be blamed if the AI code they wrote introduced a vulnerability, even more than the security team itself.</p><p>“There's clearly a lack of clarity among respondents over where accountability should sit for good risk management,” commented Andy Boura, CISO at Rothesay.</p><p>Despite concerns across the board, enterprises are expected to continue driving ahead with adoption of AI coding tools, the study noted. Nine-in-ten said they expect <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>to take over <a href="https://www.itpro.com/penetration-testing/33981/what-is-penetration-testing">penetration testing</a> within the next five years, for example</p><p>Meanwhile, 96% believe AI will write secure, reliable, code at some point, with the biggest proportion (44%) thinking it will happen in the next three-to-five years. </p><p>Only 21% think this will be achieved without human oversight, however, underlining the importance of keeping humans in the loop. </p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/development/think-ai-coding-tools-are-speeding-up-work-think-again-theyre-actually-slowing-developers-down">Think AI coding tools are speeding up work? Think again – they’re actually slowing developers down</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/how-ai-coding-is-transforming-the-it-industry-in-2025">How AI coding is transforming the IT industry in 2025</a></li><li><a href="https://www.itpro.com/software/development/ai-coding-tools-software-development-regional-popularity">AI coding tools are booming – and developers in this one country are by far the most frequent users</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/ai-generated-code-is-now-the-cause-of-one-in-five-breaches-but-developers-and-security-leaders-alike-are-convinced-the-technology-will-come-good-eventually</link>
                                                                            <description>
                            <![CDATA[ AI coding tools now write 24% of production code globally, but it's risky and causing issues for developers and security practitioners alike. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">BJyUaCbykBUPx25vExFApF</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/pXaDHxpCwz8PrGomizBmrT-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 22 Oct 2025 11:02:57 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:52 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/pXaDHxpCwz8PrGomizBmrT-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Software developer using AI coding tools on a laptop computer with source code pictured on screen and desktop monitor in background.]]></media:description>                                                            <media:text><![CDATA[Software developer using AI coding tools on a laptop computer with source code pictured on screen and desktop monitor in background.]]></media:text>
                                <media:title type="plain"><![CDATA[Software developer using AI coding tools on a laptop computer with source code pictured on screen and desktop monitor in background.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/pXaDHxpCwz8PrGomizBmrT-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><a href="https://www.itpro.com/software/development/ai-coding-tools-arent-the-solution-to-the-unfolding-developer-crisis-teams-think-they-can-boost-productivity-and-delivery-times-but-end-up-bogged-down-by-manual-remediation-and-unsafe-code">AI coding tools</a> are creating serious security risks in production, with one-in-five CISOs saying they've suffered major incidents because of <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated code</a>.</p><p>AI coding tools now write 24% of production code – 21% in Europe and 29% in the US – according to a new <a href="https://www.aikido.dev/state-of-ai-security-development-2026" target="_blank"><u>report</u></a> from Aikido. But it's risky, with 69% of security leaders, security engineers, and developers across Europe and the US revealing they'd found serious vulnerabilities in AI-written code.</p><p>US-based respondents were among the worst hit by AI-related flaws, with 43% of organizations reporting serious incidents, compared with just 20% in Europe. </p><p>This, the study noted, appears to be down to better prevention and oversight. For example, EU-based firms reported more “near misses” with AI-generated code than their US counterparts, potentially highlighting more robust testing practices. </p><p>Adding more tools to address the issue isn’t helping, Aikido found. Indeed, <a href="https://www.itpro.com/security/adopting-more-security-tools-doesnt-keep-you-safe-it-just-overloads-your-teams-and-creates-greater-risks">organizations with more security tools report more incidents</a>, with more overhead and slower remediation. </p><p>Nearly two-thirds (64%) of those with just one or two tools had an incident, the figure was 90% for those with between six and nine tools. </p><h2 id="all-in-one-ai-coding-tools-are-helping-bridge-gaps">All-in-one AI coding tools are helping bridge gaps</h2><p>Notably, teams using tools designed for both developers and security teams were more than twice as likely to report zero incidents than those using tools made for only one specific group.</p><p>“Giving developers the right security tool that works with existing tools and workflows allows teams to implement security best practices and improve their posture,” commented Walid Mahmoud, <a href="https://www.itpro.com/development/devops/354215/what-is-devsecops-and-why-is-it-important">DevSecOps </a>lead at the UK Cabinet Office.</p><p>Teams using separate AppSec and CloudSec tools were 50% more likely to face incidents, and 93% of those with separate tools reported integration headaches such as duplicate alerts or inconsistent data.</p><h2 id="the-security-blame-game-is-heating-up">The security blame game is heating up</h2><p>The blame for incidents caused by AI code is now becoming a serious point of contention within enterprises, the report noted. For example, 53% of respondents blamed security teams for failing to address issues, while 45% blamed developers who failed to spot issues before pushing to production. </p><p>Meanwhile, 42% pointed toward whoever merged it. This blame game is expected to continue escalating, according to Aikido. Half of developers reckoned they’d be blamed if the AI code they wrote introduced a vulnerability, even more than the security team itself.</p><p>“There's clearly a lack of clarity among respondents over where accountability should sit for good risk management,” commented Andy Boura, CISO at Rothesay.</p><p>Despite concerns across the board, enterprises are expected to continue driving ahead with adoption of AI coding tools, the study noted. Nine-in-ten said they expect <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>to take over <a href="https://www.itpro.com/penetration-testing/33981/what-is-penetration-testing">penetration testing</a> within the next five years, for example</p><p>Meanwhile, 96% believe AI will write secure, reliable, code at some point, with the biggest proportion (44%) thinking it will happen in the next three-to-five years. </p><p>Only 21% think this will be achieved without human oversight, however, underlining the importance of keeping humans in the loop. </p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/development/think-ai-coding-tools-are-speeding-up-work-think-again-theyre-actually-slowing-developers-down">Think AI coding tools are speeding up work? Think again – they’re actually slowing developers down</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/how-ai-coding-is-transforming-the-it-industry-in-2025">How AI coding is transforming the IT industry in 2025</a></li><li><a href="https://www.itpro.com/software/development/ai-coding-tools-software-development-regional-popularity">AI coding tools are booming – and developers in this one country are by far the most frequent users</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Data at risk: helping your customers close gaps in their supply chain ]]></title>
                                                                                                <dc:content><![CDATA[ <p>You can’t outsource accountability, but many organizations are doing just that, often without even realizing it. This is especially the case when it comes to data. </p><p>As businesses rely more heavily on third-party suppliers to store, move, and manage their data, the risk of something going wrong multiplies. Whether that’s compliance, the ability to restore lost data, or susceptibility to cyber attack.</p><p>But even though we’re continuously reminded that data is our most valuable asset, most companies still lack visibility into how their suppliers handle sensitive information. Just 14% of UK businesses actively review supplier-related risks, according to the UK government's <a href="https://www.gov.uk/government/statistics/cyber-security-breaches-survey-2025"><u>2025 Cyber Security Breaches Survey</u></a>.</p><p>That’s a problem. But it’s also an opportunity for the channel to step in, take the lead, and help customers close governance gaps before they turn into costly incidents.</p><h2 id="the-risks-rising-threats-and-low-visibility">The risks: rising threats and low visibility</h2><p>Most organizations can’t function without sharing data with third parties. Whether it’s for customer support, logistics, marketing, or cloud storage, data inevitably flows outside the company.</p><p>But even when internal controls are strong, suppliers may not meet the same standard. Giving external partners access to data increases their organization's potential attack surface, and with it the likelihood of a breach or data loss. </p><p>Helping your customers to recognise that reality, and showing them how to monitor and verify the security posture of their suppliers, will strengthen their resilience. It also positions you as a trusted advisor in a space where the risks are real and the stakes are high.</p><h2 id="a-wake-up-call">A wake-up call</h2><p>Although the UK is no longer part of the European Union, when UK organizations work with European data, they must comply with EU rules that govern it. This is true for GDPR, NIS2, and the EU Data Act. And the penalties for not complying can be weighty.</p><p>Along with the current geo-political climate, this means that where data is stored, who can access it, and how it’s being governed have become more important. If they haven’t already, UK companies need to evaluate their data residency. This includes the data in their supply chain.</p><p>Without clear governance, your customers’ data could be processed or stored across borders by a third party without their knowledge. This puts compliance and trust at risk.</p><p>By guiding your customers through a clear assessment of their data landscape, including where data is stored, who has access, and how it’s governed, you can help them build a more secure, compliant supply chain. </p><h2 id="why-backup-alone-isn-t-enough-for-data-storage">Why backup alone isn’t enough for data storage</h2><p>One of the most critical, and often overlooked, third-party suppliers is the data storage vendor.</p><p>In the past, you might have simply asked whether your customers understood their vendor’s backup protocols: How quickly could they recover from an outage or a cyber attack?</p><p>But that’s only part of the story now. Backup protects against data loss, not misuse, exposure, or unauthorized access. And in today’s regulatory and threat landscape, that’s simply not enough.</p><p>Your customers need to know that their storage vendors have robust governance in place, with clearly defined retention rules, immutable backups, detailed access logs, and auditable processes.</p><p>Helping them ask the right questions now could prevent painful consequences later.</p><h2 id="key-questions-for-your-vendors">Key questions for your vendors</h2><p>You are in the perfect position to help your customers get to grips with third-party access to their data - so that they feel confident their data is protected, compliant, and well-governed. </p><p>Often, all it takes is one conversation to check in, make sure they understand the risks, and guide them towards stronger data resilience.</p><p>Try asking them:</p><ol start="1"><li><strong>Where is customer data stored? </strong>Encourage customers to look beyond the term “cloud” and ask their vendors exactly which regions or jurisdictions their data is stored in. This affects which laws apply and whether that data could be accessed or requested by foreign governments or regulatory bodies.</li><li><strong>Who can access customer data? </strong>Help your customers understand which suppliers have access to their data. Which staff members can access, under what circumstances, and how that access is controlled. Are strong identity and access management protocols in place? Is access logged and monitored?</li><li><strong>What compliance frameworks are supported? </strong>Suppliers should support the relevant data protection and industry-specific compliance frameworks, like GDPR, ISO 27001, or HIPAA. Ask if these certifications are regularly reviewed and audited.</li><li><strong>How are retention, immutability, and auditing handled? </strong>Backup is only part of the picture. Your customers also need to know their data can’t be tampered with, altered, or deleted without proper controls. And that there's a clear audit trail if something goes wrong.</li><li><strong>Can customers easily see and manage data flows across suppliers? </strong>With more suppliers in the chain, visibility is key. Do your customers have the tools to track how their data moves between systems and partners, and the power to restrict or revoke access if needed?</li></ol><h2 id="a-trusted-advisor">A trusted advisor</h2><p>By asking these questions, you're not just helping your customers protect their data; you're helping them build trust with their own stakeholders. In a climate where digital accountability matters more than ever, organizations that demonstrate care and control over their data will stand out. </p><p>By guiding these conversations, you strengthen your own position as a trusted advisor. Someone who goes beyond the sale to support long-term resilience, compliance, and customer confidence.</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/data-at-risk-helping-your-customers-close-gaps-in-their-supply-chain</link>
                                                                            <description>
                            <![CDATA[ Most UK businesses lack visibility into third‑party supplier data governance, exposing themselves to compliance and cyber risks… ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">rk8fCJZjFu5kSiJ6Vyx5Qe</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/gjcd7Vr5oYycasRyGGDdD4-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 14 Oct 2025 07:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:02 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Dan Middleton ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/K5fUKDSdPMaK5zt3otKgRj-320-70.png ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/gjcd7Vr5oYycasRyGGDdD4-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Digital chain with one link lit up in light blue on digital background]]></media:description>                                                            <media:text><![CDATA[Digital chain with one link lit up in light blue on digital background]]></media:text>
                                <media:title type="plain"><![CDATA[Digital chain with one link lit up in light blue on digital background]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/gjcd7Vr5oYycasRyGGDdD4-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>You can’t outsource accountability, but many organizations are doing just that, often without even realizing it. This is especially the case when it comes to data. </p><p>As businesses rely more heavily on third-party suppliers to store, move, and manage their data, the risk of something going wrong multiplies. Whether that’s compliance, the ability to restore lost data, or susceptibility to cyber attack.</p><p>But even though we’re continuously reminded that data is our most valuable asset, most companies still lack visibility into how their suppliers handle sensitive information. Just 14% of UK businesses actively review supplier-related risks, according to the UK government's <a href="https://www.gov.uk/government/statistics/cyber-security-breaches-survey-2025"><u>2025 Cyber Security Breaches Survey</u></a>.</p><p>That’s a problem. But it’s also an opportunity for the channel to step in, take the lead, and help customers close governance gaps before they turn into costly incidents.</p><h2 id="the-risks-rising-threats-and-low-visibility">The risks: rising threats and low visibility</h2><p>Most organizations can’t function without sharing data with third parties. Whether it’s for customer support, logistics, marketing, or cloud storage, data inevitably flows outside the company.</p><p>But even when internal controls are strong, suppliers may not meet the same standard. Giving external partners access to data increases their organization's potential attack surface, and with it the likelihood of a breach or data loss. </p><p>Helping your customers to recognise that reality, and showing them how to monitor and verify the security posture of their suppliers, will strengthen their resilience. It also positions you as a trusted advisor in a space where the risks are real and the stakes are high.</p><h2 id="a-wake-up-call">A wake-up call</h2><p>Although the UK is no longer part of the European Union, when UK organizations work with European data, they must comply with EU rules that govern it. This is true for GDPR, NIS2, and the EU Data Act. And the penalties for not complying can be weighty.</p><p>Along with the current geo-political climate, this means that where data is stored, who can access it, and how it’s being governed have become more important. If they haven’t already, UK companies need to evaluate their data residency. This includes the data in their supply chain.</p><p>Without clear governance, your customers’ data could be processed or stored across borders by a third party without their knowledge. This puts compliance and trust at risk.</p><p>By guiding your customers through a clear assessment of their data landscape, including where data is stored, who has access, and how it’s governed, you can help them build a more secure, compliant supply chain. </p><h2 id="why-backup-alone-isn-t-enough-for-data-storage">Why backup alone isn’t enough for data storage</h2><p>One of the most critical, and often overlooked, third-party suppliers is the data storage vendor.</p><p>In the past, you might have simply asked whether your customers understood their vendor’s backup protocols: How quickly could they recover from an outage or a cyber attack?</p><p>But that’s only part of the story now. Backup protects against data loss, not misuse, exposure, or unauthorized access. And in today’s regulatory and threat landscape, that’s simply not enough.</p><p>Your customers need to know that their storage vendors have robust governance in place, with clearly defined retention rules, immutable backups, detailed access logs, and auditable processes.</p><p>Helping them ask the right questions now could prevent painful consequences later.</p><h2 id="key-questions-for-your-vendors">Key questions for your vendors</h2><p>You are in the perfect position to help your customers get to grips with third-party access to their data - so that they feel confident their data is protected, compliant, and well-governed. </p><p>Often, all it takes is one conversation to check in, make sure they understand the risks, and guide them towards stronger data resilience.</p><p>Try asking them:</p><ol start="1"><li><strong>Where is customer data stored? </strong>Encourage customers to look beyond the term “cloud” and ask their vendors exactly which regions or jurisdictions their data is stored in. This affects which laws apply and whether that data could be accessed or requested by foreign governments or regulatory bodies.</li><li><strong>Who can access customer data? </strong>Help your customers understand which suppliers have access to their data. Which staff members can access, under what circumstances, and how that access is controlled. Are strong identity and access management protocols in place? Is access logged and monitored?</li><li><strong>What compliance frameworks are supported? </strong>Suppliers should support the relevant data protection and industry-specific compliance frameworks, like GDPR, ISO 27001, or HIPAA. Ask if these certifications are regularly reviewed and audited.</li><li><strong>How are retention, immutability, and auditing handled? </strong>Backup is only part of the picture. Your customers also need to know their data can’t be tampered with, altered, or deleted without proper controls. And that there's a clear audit trail if something goes wrong.</li><li><strong>Can customers easily see and manage data flows across suppliers? </strong>With more suppliers in the chain, visibility is key. Do your customers have the tools to track how their data moves between systems and partners, and the power to restrict or revoke access if needed?</li></ol><h2 id="a-trusted-advisor">A trusted advisor</h2><p>By asking these questions, you're not just helping your customers protect their data; you're helping them build trust with their own stakeholders. In a climate where digital accountability matters more than ever, organizations that demonstrate care and control over their data will stand out. </p><p>By guiding these conversations, you strengthen your own position as a trusted advisor. Someone who goes beyond the sale to support long-term resilience, compliance, and customer confidence.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Using AI to code? Watch your security debt ]]></title>
                                                                                                <dc:content><![CDATA[ <p>AI is helping to speed up code deployment, but security isn't keeping up. </p><p>That's one of the key findings from a report by security firm Black Duck, with 81% of 1,000 security professionals surveyed saying application security testing is now slowing down development and delivery. </p><p>The report comes as AI is starting to have an impact on coding and development, with 84% of developers <a href="https://www.itpro.com/software/development/developers-arent-quite-ready-to-place-their-trust-in-ai-nearly-half-say-they-dont-trust-the-accuracy-of-outputs-and-end-up-wasting-time-debugging-code">surveyed by Stack Overflow</a> over the summer saying they've used the technology in the last year or plan to imminently, even though trust in the end product remains an issue. Indeed, a <a href="https://www.itpro.com/technology/artificial-intelligence/security-leaders-are-increasingly-worried-about-ai-generated-code">survey of security leaders</a> last year found that the vast majority – some 92% of those polled – were concerned that <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated</a> code could cause a security incident in their organization. </p><p>The <a href="https://www.blackduck.com/resources/analyst-reports/state-of-devsecops.html?cmp=pr-sig&amp;utm_medium=referral">Black Duck research</a> found nearly 60% of those polled are deploying code every day – if not more frequently – but security is getting in the way of that AI-accelerated speed. </p><p>That's because 46% of those asked still rely on manual processes with security, with 81% of professionals saying that application security slows down the development process – and that can lead to <a href="https://www.itpro.com/business/public-sector/public-sector-organizations-are-drowning-in-security-debt">security debt</a>, with security problems left piling up unaddressed. </p><p>The report noted that companies have successfully built "high-velocity development pipelines," thanks to AI as well as other coding tools, but automation of security lags behind. </p><p>"This automation gap means many businesses are simply unaware of their vulnerabilities, with 61.64% of</p><p>organizations testing less than 60% of their own applications," the report noted. "The result is that you're accumulating a massive security debt with every single release."</p><h2 id="ai-vs-workflows">AI vs workflows</h2><p>Because of that, developers said that improving development workflow integration is a top priority for 27% of those polled. </p><p>"The findings paint a clear picture: the old ways of doing application security aren't working, and speed without integrated security creates risk for companies," said Jason Schmitt, CEO of Black Duck. "To navigate this new world, development teams must shift from a reactive, tool-centric model to a proactive, platform-based strategy that integrates security directly into developer workflows to achieve true scale application security."</p><p>The challenges are exacerbated by 71% of respondents saying that security alerts are noise, with too many false positives and duplicate findings from multiple tools eating into any benefits, known as tool sprawl. </p><h2 id="risk-vs-reward-for-ai-coding">Risk vs reward for AI coding</h2><p>More generally, two-thirds of respondents said AI helps them write more secure code, but 57% agreed it can also introduce new risks. </p><p>"This report nails the core dilemma facing modern DevSecOps: the tradeoff between velocity and visibility," said Mayur Upadhyaya, CEO at APIContext. "We're seeing a shift away from adding more tools toward simplifying and integrating the ones teams already have."</p><p>Upadhyaya added: "As AI becomes both a productivity multiplier and an attack vector, governance must evolve, but so must observability. If you can't baseline normal behavior and detect deviation in real time, you're playing catch-up. And in AI-native pipelines, catch-up is too late."</p><p>Of course, security debt is a problem even without AI. A <a href="https://www.itpro.com/software/software-security-flaws-remediation">report by Veracode</a> earlier this year showed remediation times for security flaws had grown by 47% over the last five years, from an average 171 days to fix a vulnerability in 2020 to 252 days in 2025. </p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/using-ai-to-code-watch-your-security-debt</link>
                                                                            <description>
                            <![CDATA[ Black Duck research shows faster development may be causing risks for companies ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">g3rvbpP9ki4xD58nh7XRQ8</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/TeTemFzsXKP9wv3C8GriNJ-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 09 Oct 2025 12:08:03 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:51 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Nicole Kobie ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/8Y8JDDTQ7XDEk49FoAFP2S-320-70.png ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Nicole Kobie first started writing for ITPro in 2007. As a freelance journalist covering technology and business, Nicole&#039;s work includes  bylines in New Scientist, Wired, PC Pro and many more. &lt;/p&gt;&lt;p&gt;Nicole the author of a book about the history of technology, The Long History of the Future.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/TeTemFzsXKP9wv3C8GriNJ-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Open source vulnerabilities concept image showing HTML code on a computer screen.]]></media:description>                                                            <media:text><![CDATA[Open source vulnerabilities concept image showing HTML code on a computer screen.]]></media:text>
                                <media:title type="plain"><![CDATA[Open source vulnerabilities concept image showing HTML code on a computer screen.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/TeTemFzsXKP9wv3C8GriNJ-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>AI is helping to speed up code deployment, but security isn't keeping up. </p><p>That's one of the key findings from a report by security firm Black Duck, with 81% of 1,000 security professionals surveyed saying application security testing is now slowing down development and delivery. </p><p>The report comes as AI is starting to have an impact on coding and development, with 84% of developers <a href="https://www.itpro.com/software/development/developers-arent-quite-ready-to-place-their-trust-in-ai-nearly-half-say-they-dont-trust-the-accuracy-of-outputs-and-end-up-wasting-time-debugging-code">surveyed by Stack Overflow</a> over the summer saying they've used the technology in the last year or plan to imminently, even though trust in the end product remains an issue. Indeed, a <a href="https://www.itpro.com/technology/artificial-intelligence/security-leaders-are-increasingly-worried-about-ai-generated-code">survey of security leaders</a> last year found that the vast majority – some 92% of those polled – were concerned that <a href="https://www.itpro.com/technology/artificial-intelligence/ai-generated-code-risks-what-cisos-need-to-know">AI-generated</a> code could cause a security incident in their organization. </p><p>The <a href="https://www.blackduck.com/resources/analyst-reports/state-of-devsecops.html?cmp=pr-sig&amp;utm_medium=referral">Black Duck research</a> found nearly 60% of those polled are deploying code every day – if not more frequently – but security is getting in the way of that AI-accelerated speed. </p><p>That's because 46% of those asked still rely on manual processes with security, with 81% of professionals saying that application security slows down the development process – and that can lead to <a href="https://www.itpro.com/business/public-sector/public-sector-organizations-are-drowning-in-security-debt">security debt</a>, with security problems left piling up unaddressed. </p><p>The report noted that companies have successfully built "high-velocity development pipelines," thanks to AI as well as other coding tools, but automation of security lags behind. </p><p>"This automation gap means many businesses are simply unaware of their vulnerabilities, with 61.64% of</p><p>organizations testing less than 60% of their own applications," the report noted. "The result is that you're accumulating a massive security debt with every single release."</p><h2 id="ai-vs-workflows">AI vs workflows</h2><p>Because of that, developers said that improving development workflow integration is a top priority for 27% of those polled. </p><p>"The findings paint a clear picture: the old ways of doing application security aren't working, and speed without integrated security creates risk for companies," said Jason Schmitt, CEO of Black Duck. "To navigate this new world, development teams must shift from a reactive, tool-centric model to a proactive, platform-based strategy that integrates security directly into developer workflows to achieve true scale application security."</p><p>The challenges are exacerbated by 71% of respondents saying that security alerts are noise, with too many false positives and duplicate findings from multiple tools eating into any benefits, known as tool sprawl. </p><h2 id="risk-vs-reward-for-ai-coding">Risk vs reward for AI coding</h2><p>More generally, two-thirds of respondents said AI helps them write more secure code, but 57% agreed it can also introduce new risks. </p><p>"This report nails the core dilemma facing modern DevSecOps: the tradeoff between velocity and visibility," said Mayur Upadhyaya, CEO at APIContext. "We're seeing a shift away from adding more tools toward simplifying and integrating the ones teams already have."</p><p>Upadhyaya added: "As AI becomes both a productivity multiplier and an attack vector, governance must evolve, but so must observability. If you can't baseline normal behavior and detect deviation in real time, you're playing catch-up. And in AI-native pipelines, catch-up is too late."</p><p>Of course, security debt is a problem even without AI. A <a href="https://www.itpro.com/software/software-security-flaws-remediation">report by Veracode</a> earlier this year showed remediation times for security flaws had grown by 47% over the last five years, from an average 171 days to fix a vulnerability in 2020 to 252 days in 2025. </p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Organizations around the world are unprepared for the threat from bad bots – and UK businesses are some of the worst performers  ]]></title>
                                                                                                <dc:content><![CDATA[ <p>The UK is one of the world's worst performers when it comes to protecting against bots – though most countries are pretty poor.</p><p>That's according to <a href="https://datadome.co/resources/bot-security-report/">DataDome</a>, which states that only 1.8% of large UK domains are fully protected against <a href="https://www.itpro.com/technology/2025-bad-bot-report">bots</a>, compared with a Europe-wide average of 2.5% and a global average of 2.8%. Bigger organizations are no better than smaller ones, with only 2% of domains with more than 30 million monthly visits fully protected.</p><p>And it's an increasing issue. <a href="https://www.itpro.com/security/ai-is-helping-bad-bots-take-over-the-internet">AI-driven bot traffic</a> is becoming the norm, said DataDome, with AI bot and crawler traffic having risen from 2.6% of verified bot traffic in January this year to more than 10.1% by August. The company said it detected nearly 1.7 billion requests from OpenAI crawlers alone in a single month – scraping web content, draining server resources, and exposing proprietary data.</p><div class="product"><a data-dimension112="718493d7-cb3c-40d4-b2fe-69e41048377d" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow"><figure class="van-image-figure "  ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:310px;"><p class="vanilla-image-block" style="padding-top:52.58%;"><img id="VVXzWjJJrXo7mwL5n5f4mf" name="Keeper Security logo.png" caption="" alt="" src="https://cdn.mos.cms.futurecdn.net/VVXzWjJJrXo7mwL5n5f4mf-1920-80.png" mos="" align="middle" fullscreen="" width="310" height="163" attribution="" endorsement="" credit="" class="" /></p></div></div></figure></a><p><a href="https://www.keepersecurity.com/en_GB/affiliate/business/" data-dimension112="718493d7-cb3c-40d4-b2fe-69e41048377d" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25=""><strong>30% off Keeper Security's Business Starter and Business plans</strong></a></p><p>Keeper Security is trusted and valued by thousands of businesses and millions of employees. Why not join them and protect your most important assets while taking advantage of this special offer?<a class="view-deal button" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow" data-dimension112="718493d7-cb3c-40d4-b2fe-69e41048377d" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25="">View Deal</a></p></div><p>Earlier this year, the <a href="https://www.itpro.com/tag/national-cyber-security-centre">National Cyber Security Centre (NCSC)</a> warned of a developing digital divide between systems keeping pace with AI-enabled threats and those that are more vulnerable.</p><p>"Our data on low bot protection rates provides concrete evidence that this is already happening, proving that many UK businesses are ill-equipped for the next wave of AI-driven cyberattacks," said Jérôme Segura, VP of threat research at DataDome. </p><p>"This gap is not accidental, but is rooted in systemic national issues: an economy dominated by resource-strapped small and medium-sized enterprises, a persistent and critical <a href="https://www.itpro.com/security/cybersecurity-skills-what-can-be-done">cybersecurity skills gap</a>, and a business culture that frequently underinvests in security."  </p><p>Businesses aren't doing a great job of countering the problem, the researchers said. Legacy defenses are failing fast, with only 2.8% of websites fully protected in 2025, down from 8.4% in 2024. </p><p>While nearly nine-in-ten domains disallow GPTBot in their robots.txt files, AI-powered crawlers and browsers ignore these directives, rendering static blocking strategies obsolete. Meanwhile, anti-fingerprinting bots were only blocked by around 7% of websites, and fake Chrome and curl bots were detected just 21% of the time.</p><p>The weakest protection was seen in the government, non-profit, and telecoms sectors, while travel and hospitality, gambling, and real estate were the best-performing. </p><p>Threat actors, said DataDome, are increasingly blending basic automation with more advanced tactics such as leveraging agentic AI tools that simulate human behavior, bypass Captchas, manipulate TLS fingerprints, and adapt in real time.</p><p>"AI agents are rewriting the rules of online engagement," said Segura. "Traditional defenses, built to spot static automation, are collapsing under this complexity. Businesses can't tell if the AI traffic they're seeing is good or bad, which leaves them both exposed to fraud and blind to opportunity. What's needed is adaptive, intent-based protection that can make sense of this AI-driven chaos in real time."</p><p>Earlier this year, research from Imperva revealed that bot traffic now accounts for more than half of all web traffic, with malicious bots now making up 37% of all internet traffic.</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/technology/2025-bad-bot-report">2025 bad bot report</a></li><li><a href="https://www.itpro.com/security/ai-is-helping-bad-bots-take-over-the-internet">AI is helping bad bots take over the internet </a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/organizations-around-the-world-are-unprepared-for-the-threat-from-bad-bots-and-uk-businesses-are-some-of-the-worst-performers</link>
                                                                            <description>
                            <![CDATA[ As AI-driven bot traffic booms, legacy defenses are failing fast ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">vsAPYdv48NETajidjigrgJ</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/GrdMjCeAr9EuWXYXepictH-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 30 Sep 2025 13:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:49 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/GrdMjCeAr9EuWXYXepictH-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[A finger pointing to a red bot with alerts]]></media:description>                                                            <media:text><![CDATA[A finger pointing to a red bot with alerts]]></media:text>
                                <media:title type="plain"><![CDATA[A finger pointing to a red bot with alerts]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/GrdMjCeAr9EuWXYXepictH-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The UK is one of the world's worst performers when it comes to protecting against bots – though most countries are pretty poor.</p><p>That's according to <a href="https://datadome.co/resources/bot-security-report/">DataDome</a>, which states that only 1.8% of large UK domains are fully protected against <a href="https://www.itpro.com/technology/2025-bad-bot-report">bots</a>, compared with a Europe-wide average of 2.5% and a global average of 2.8%. Bigger organizations are no better than smaller ones, with only 2% of domains with more than 30 million monthly visits fully protected.</p><p>And it's an increasing issue. <a href="https://www.itpro.com/security/ai-is-helping-bad-bots-take-over-the-internet">AI-driven bot traffic</a> is becoming the norm, said DataDome, with AI bot and crawler traffic having risen from 2.6% of verified bot traffic in January this year to more than 10.1% by August. The company said it detected nearly 1.7 billion requests from OpenAI crawlers alone in a single month – scraping web content, draining server resources, and exposing proprietary data.</p><div class="product"><a data-dimension112="718493d7-cb3c-40d4-b2fe-69e41048377d" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow"><figure class="van-image-figure "  ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:310px;"><p class="vanilla-image-block" style="padding-top:52.58%;"><img id="VVXzWjJJrXo7mwL5n5f4mf" name="Keeper Security logo.png" caption="" alt="" src="https://cdn.mos.cms.futurecdn.net/VVXzWjJJrXo7mwL5n5f4mf-1920-80.png" mos="" align="middle" fullscreen="" width="310" height="163" attribution="" endorsement="" credit="" class="" /></p></div></div></figure></a><p><a href="https://www.keepersecurity.com/en_GB/affiliate/business/" data-dimension112="718493d7-cb3c-40d4-b2fe-69e41048377d" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25=""><strong>30% off Keeper Security's Business Starter and Business plans</strong></a></p><p>Keeper Security is trusted and valued by thousands of businesses and millions of employees. Why not join them and protect your most important assets while taking advantage of this special offer?<a class="view-deal button" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow" data-dimension112="718493d7-cb3c-40d4-b2fe-69e41048377d" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25="">View Deal</a></p></div><p>Earlier this year, the <a href="https://www.itpro.com/tag/national-cyber-security-centre">National Cyber Security Centre (NCSC)</a> warned of a developing digital divide between systems keeping pace with AI-enabled threats and those that are more vulnerable.</p><p>"Our data on low bot protection rates provides concrete evidence that this is already happening, proving that many UK businesses are ill-equipped for the next wave of AI-driven cyberattacks," said Jérôme Segura, VP of threat research at DataDome. </p><p>"This gap is not accidental, but is rooted in systemic national issues: an economy dominated by resource-strapped small and medium-sized enterprises, a persistent and critical <a href="https://www.itpro.com/security/cybersecurity-skills-what-can-be-done">cybersecurity skills gap</a>, and a business culture that frequently underinvests in security."  </p><p>Businesses aren't doing a great job of countering the problem, the researchers said. Legacy defenses are failing fast, with only 2.8% of websites fully protected in 2025, down from 8.4% in 2024. </p><p>While nearly nine-in-ten domains disallow GPTBot in their robots.txt files, AI-powered crawlers and browsers ignore these directives, rendering static blocking strategies obsolete. Meanwhile, anti-fingerprinting bots were only blocked by around 7% of websites, and fake Chrome and curl bots were detected just 21% of the time.</p><p>The weakest protection was seen in the government, non-profit, and telecoms sectors, while travel and hospitality, gambling, and real estate were the best-performing. </p><p>Threat actors, said DataDome, are increasingly blending basic automation with more advanced tactics such as leveraging agentic AI tools that simulate human behavior, bypass Captchas, manipulate TLS fingerprints, and adapt in real time.</p><p>"AI agents are rewriting the rules of online engagement," said Segura. "Traditional defenses, built to spot static automation, are collapsing under this complexity. Businesses can't tell if the AI traffic they're seeing is good or bad, which leaves them both exposed to fraud and blind to opportunity. What's needed is adaptive, intent-based protection that can make sense of this AI-driven chaos in real time."</p><p>Earlier this year, research from Imperva revealed that bot traffic now accounts for more than half of all web traffic, with malicious bots now making up 37% of all internet traffic.</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/technology/2025-bad-bot-report">2025 bad bot report</a></li><li><a href="https://www.itpro.com/security/ai-is-helping-bad-bots-take-over-the-internet">AI is helping bad bots take over the internet </a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Mobile app security is a huge blind spot for developer teams ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Organizations are overconfident about their mobile app security practices, according to new research, and it’s putting enterprises and consumers alike at risk. </p><p>While 93% of organizations <a href="https://www.guardsquare.com/report/overconfidence-exposes-mobile-app-security-gaps" target="_blank"><u>told researchers</u></a> they were confident in their capabilities, and 97% that they had up-to-date policies outlining mobile app security policies, 62% were breached in the past year, with an average of nine incidents each. </p><p>Just over half (52%) fell victim to a malware attack, 45% suffered data breaches or leaks, and 37% experienced unauthorized access to data. The same number suffered <a href="https://www.itpro.com/security/cyber-attacks/credential-theft-has-surged-160-percent-in-2025">credential theft</a>. </p><div class="product"><a data-dimension112="59d5bd14-ee2e-49ae-93fe-61859c5d87e2" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow"><figure class="van-image-figure "  ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:310px;"><p class="vanilla-image-block" style="padding-top:52.58%;"><img id="VVXzWjJJrXo7mwL5n5f4mf" name="Keeper Security logo.png" caption="" alt="" src="https://cdn.mos.cms.futurecdn.net/VVXzWjJJrXo7mwL5n5f4mf-1920-80.png" mos="" align="middle" fullscreen="" width="310" height="163" attribution="" endorsement="" credit="" class="" /></p></div></div></figure></a><p><a href="https://www.keepersecurity.com/en_GB/affiliate/business/" data-dimension112="59d5bd14-ee2e-49ae-93fe-61859c5d87e2" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25=""><strong>30% off Keeper Security's Business Starter and Business plans</strong></a></p><p>Keeper Security is trusted and valued by thousands of businesses and millions of employees. Why not join them and protect your most important assets while taking advantage of this special offer?<a class="view-deal button" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow" data-dimension112="59d5bd14-ee2e-49ae-93fe-61859c5d87e2" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25="">View Deal</a></p></div><p>Much of the problem derives from pressure to accelerate release cycles, with 74% saying mobile app teams are increasingly pushed on time-to-market. Similarly, 71% of organizations admit this has compromised mobile app security.</p><p>“The data is clear, and the perceived trade-off between speed and security is a false choice that is costing organizations,” said Roel Caers, CEO of Guardsquare. </p><p>“When developers are under immense pressure to release new features, and security is seen as a roadblock, they are forced to sacrifice protection for time-to-market. This reactive, fire-fighting approach is unsustainable. What’s needed is a proactive, integrated strategy where security is an enabler, not a hindrance.”</p><p>Other security challenges included balancing security with app performance, cited by 47%, ensuring compliance (44%) and providing a seamless user experience (42%).</p><h2 id="mobile-app-security-is-improving">Mobile app security is improving</h2><p>On the positive side, most respondents reported that they were currently using some core mobile app security capabilities such as data encryption (69%), mobile application security testing (63%) and threat monitoring (59%). </p><p>However, the report found low adoption of proactive defenses, with almost 70% of organizations failing to use obfuscation to protect their mobile apps, and 60% lacking Runtime Application Self-Protection (RASP). </p><p>This, the study warned, is leaving their apps vulnerable to both static and dynamic analysis. Nearly four-in-ten said they relied entirely on DIY security solutions or OS-level protections.</p><p>Meanwhile, the impacts of security incidents extend beyond the average reported cost. More than half of respondents (54%) reported application downtime, with 48% experiencing data leakage and 41% suffering a loss of <a href="https://www.itpro.com/data-leakage/26529/data-breaches-have-destroyed-customers-trust-in-companies">consumer trust</a>.</p><p>Worryingly, 85% of survey respondents agreed that a security incident is often the catalyst for a security purchase, with 58% of respondents citing security incidents, 47% partner or client requirements and 30% a failed <a href="https://www.itpro.com/penetration-testing/33981/what-is-penetration-testing">penetration test</a> or audit.</p><p>Researchers said means far too many organizations are taking action too late.</p><p>“As organizations face pressure to develop feature-rich applications that can be easily used from any device, attackers often target vulnerabilities in mobile applications,” said Melinda Marks, practice director, <a href="https://www.itpro.com/security/28133/what-is-cyber-security">cybersecurity</a>, for Enterprise Strategy Group. </p><p>“To stay ahead of threats and attacks, security teams need to take a proactive approach to mobile application security with the right tools."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/security/cyber-attacks/salesloft-drift-hackers-had-access-to-company-github-account-for-months-before-attacks">Salesloft Drift hackers had access to company GitHub account for months before attacks</a></li><li><a href="https://www.itpro.com/security/cyber-attacks/jaguar-land-rover-u-turns-on-cyber-attack-containment-claims-admits-some-data-has-been-affected">Jaguar Land Rover u-turns on cyber attack containment claims</a></li><li><a href="https://www.itpro.com/security/cyber-attacks/fbi-warns-indiscriminate-salt-typhoon-hacking-campaign-has-hit-organizations-in-more-than-80-countries">FBI warns 'indiscriminate' Salt Typhoon hacking campaign has hit organizations in more than 80 countries</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/mobile-app-security-is-a-huge-blind-spot-for-developer-teams-93-percent-are-confident-their-applications-are-secure-but-62-percent-reported-breaches-last-year</link>
                                                                            <description>
                            <![CDATA[ Organizations are overconfident about their mobile app security practices, according to new research, and it’s putting enterprises and consumers alike at risk. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">breJhos62Lw2LAhouQzTHk</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/MtUfTszvJDvG59aRcikytH-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 12 Sep 2025 09:11:51 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:06 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/MtUfTszvJDvG59aRcikytH-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Mobile app security concept image showing a person&#039;s hand illuminated by a smartphone screen on a dark street.]]></media:description>                                                            <media:text><![CDATA[Mobile app security concept image showing a person&#039;s hand illuminated by a smartphone screen on a dark street.]]></media:text>
                                <media:title type="plain"><![CDATA[Mobile app security concept image showing a person&#039;s hand illuminated by a smartphone screen on a dark street.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/MtUfTszvJDvG59aRcikytH-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Organizations are overconfident about their mobile app security practices, according to new research, and it’s putting enterprises and consumers alike at risk. </p><p>While 93% of organizations <a href="https://www.guardsquare.com/report/overconfidence-exposes-mobile-app-security-gaps" target="_blank"><u>told researchers</u></a> they were confident in their capabilities, and 97% that they had up-to-date policies outlining mobile app security policies, 62% were breached in the past year, with an average of nine incidents each. </p><p>Just over half (52%) fell victim to a malware attack, 45% suffered data breaches or leaks, and 37% experienced unauthorized access to data. The same number suffered <a href="https://www.itpro.com/security/cyber-attacks/credential-theft-has-surged-160-percent-in-2025">credential theft</a>. </p><div class="product"><a data-dimension112="59d5bd14-ee2e-49ae-93fe-61859c5d87e2" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow"><figure class="van-image-figure "  ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:310px;"><p class="vanilla-image-block" style="padding-top:52.58%;"><img id="VVXzWjJJrXo7mwL5n5f4mf" name="Keeper Security logo.png" caption="" alt="" src="https://cdn.mos.cms.futurecdn.net/VVXzWjJJrXo7mwL5n5f4mf-1920-80.png" mos="" align="middle" fullscreen="" width="310" height="163" attribution="" endorsement="" credit="" class="" /></p></div></div></figure></a><p><a href="https://www.keepersecurity.com/en_GB/affiliate/business/" data-dimension112="59d5bd14-ee2e-49ae-93fe-61859c5d87e2" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25=""><strong>30% off Keeper Security's Business Starter and Business plans</strong></a></p><p>Keeper Security is trusted and valued by thousands of businesses and millions of employees. Why not join them and protect your most important assets while taking advantage of this special offer?<a class="view-deal button" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow" data-dimension112="59d5bd14-ee2e-49ae-93fe-61859c5d87e2" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25="">View Deal</a></p></div><p>Much of the problem derives from pressure to accelerate release cycles, with 74% saying mobile app teams are increasingly pushed on time-to-market. Similarly, 71% of organizations admit this has compromised mobile app security.</p><p>“The data is clear, and the perceived trade-off between speed and security is a false choice that is costing organizations,” said Roel Caers, CEO of Guardsquare. </p><p>“When developers are under immense pressure to release new features, and security is seen as a roadblock, they are forced to sacrifice protection for time-to-market. This reactive, fire-fighting approach is unsustainable. What’s needed is a proactive, integrated strategy where security is an enabler, not a hindrance.”</p><p>Other security challenges included balancing security with app performance, cited by 47%, ensuring compliance (44%) and providing a seamless user experience (42%).</p><h2 id="mobile-app-security-is-improving">Mobile app security is improving</h2><p>On the positive side, most respondents reported that they were currently using some core mobile app security capabilities such as data encryption (69%), mobile application security testing (63%) and threat monitoring (59%). </p><p>However, the report found low adoption of proactive defenses, with almost 70% of organizations failing to use obfuscation to protect their mobile apps, and 60% lacking Runtime Application Self-Protection (RASP). </p><p>This, the study warned, is leaving their apps vulnerable to both static and dynamic analysis. Nearly four-in-ten said they relied entirely on DIY security solutions or OS-level protections.</p><p>Meanwhile, the impacts of security incidents extend beyond the average reported cost. More than half of respondents (54%) reported application downtime, with 48% experiencing data leakage and 41% suffering a loss of <a href="https://www.itpro.com/data-leakage/26529/data-breaches-have-destroyed-customers-trust-in-companies">consumer trust</a>.</p><p>Worryingly, 85% of survey respondents agreed that a security incident is often the catalyst for a security purchase, with 58% of respondents citing security incidents, 47% partner or client requirements and 30% a failed <a href="https://www.itpro.com/penetration-testing/33981/what-is-penetration-testing">penetration test</a> or audit.</p><p>Researchers said means far too many organizations are taking action too late.</p><p>“As organizations face pressure to develop feature-rich applications that can be easily used from any device, attackers often target vulnerabilities in mobile applications,” said Melinda Marks, practice director, <a href="https://www.itpro.com/security/28133/what-is-cyber-security">cybersecurity</a>, for Enterprise Strategy Group. </p><p>“To stay ahead of threats and attacks, security teams need to take a proactive approach to mobile application security with the right tools."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/security/cyber-attacks/salesloft-drift-hackers-had-access-to-company-github-account-for-months-before-attacks">Salesloft Drift hackers had access to company GitHub account for months before attacks</a></li><li><a href="https://www.itpro.com/security/cyber-attacks/jaguar-land-rover-u-turns-on-cyber-attack-containment-claims-admits-some-data-has-been-affected">Jaguar Land Rover u-turns on cyber attack containment claims</a></li><li><a href="https://www.itpro.com/security/cyber-attacks/fbi-warns-indiscriminate-salt-typhoon-hacking-campaign-has-hit-organizations-in-more-than-80-countries">FBI warns 'indiscriminate' Salt Typhoon hacking campaign has hit organizations in more than 80 countries</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ 74% of companies admit insecure code caused a security breach ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Nearly three-quarters of organizations have suffered at least one security breach or incident in the last year that can be blamed on insecure coding practices. </p><p><a href="https://www.secureflag.com/resources/resource-details#secure-coding-training-in-uk-enterprises-c-suite-survey-key-findings" target="_blank"><u>Analysis from SecureFlag</u></a> found 74% of organizations have suffered an incident as a result of dodgy code, with nearly half of those hit by multiple breaches. </p><p>The report comes as <a href="https://www.itpro.com/software/development/vibe-coding-best-ai-models-secure-code-generation"><u>AI is beginning to take over some coding duties</u></a> from developers. Debate remains over whether that code is secure. Some say <a href="https://www.itpro.com/software/development/developers-say-ai-can-code-better-than-most-humans-but-theres-a-catch"><u>AI can code better than human developers</u></a>, but <a href="https://www.itpro.com/software/developers-relying-on-github-copilot-could-be-creating-dangerously-flawed-code"><u>research</u></a> has suggested insecure code could be easily replicated by <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI</a>. </p><p>Andrea Scaduto, CEO and co-founder of SecureFlag, said the study highlights the risks faced by enterprises rushing to automate aspects of software development. </p><p>"This should be a wake-up call for every business that develops software,” she said. “It’s frankly shocking that in 2025 so many breaches are still happening because of avoidable coding flaws.” </p><p>It wasn't all bad news, however. The report revealed that companies are ramping up developer security training as a result of lingering issues. Nearly half (44%) said they offer training updates on a quarterly basis, while 29% offer fresh training schemes monthly. </p><p>The report said this shows enterprises are conscious of the risks associated with insecure code and are taking proactive steps to mitigate risks. Indeed, nine-in-ten said they were formally assessing their development teams' secure coding skills. </p><p>The most common training format is video-based tutorials (46%) followed by eLearning platforms (42%). Classes, both in-person and virtual, were also popular for four-in-ten companies, as were interactive labs and hands-on environments. </p><p>A third of companies surveyed said they run hacking games such as "capture the flag".</p><h2 id="roi-for-developer-security-training">ROI for developer security training</h2><p>Challenges remain, however. According to SecureFlag, respondents said measuring return on investment (ROI) remained a hurdle (40%), followed by a lack of useful content, not enough time, low engagement from employees, and insufficient budget — as well as lack of leadership support. </p><p>"Even though most executives believe in the value of training, they struggle to prove in concrete terms how these programs reduce risk or justify their cost, a clear sign that quantifying the impact of secure coding initiatives remains elusive," the report noted. </p><p>"Overall, the data highlights that proving ROI to stakeholders and allocating sufficient time and content resources are the prevailing hurdles to overcome, even more so than money or buy-in."</p><p>Though they may lack the hard data to prove a ROI, nine-in-ten of those surveyed believe that secure coding has reduced the number of security bugs in development, and view training as a solid move to prevent such incidents. </p><p>"Breaches stemming from coding mistakes are preventable – but only if companies invest in proper training," said Emilio Pinna, SecureFlag’s CTO and co-founder. "It’s far cheaper to train a developer than to clean up after a breach."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/want-developers-to-build-secure-software-you-need-to-ditch-these-two-programming-languages">Want developers to build secure software? You need to ditch these two programming languages</a></li><li><a href="https://www.itpro.com/software/software-security-code-of-practice-ncsc-announcement">The NCSC wants developers to get serious on software security</a></li><li><a href="https://www.itpro.com/software/development/software-security-shift-left-developer-overload">Shifting left might improve software security, but developers are becoming overwhelmed</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/74-percent-of-companies-admit-insecure-code-caused-a-security-breach</link>
                                                                            <description>
                            <![CDATA[ A large number of data breaches are linked to insecure code, prompting calls for better training ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">hEapLPGNtngmpVkaaBCCSV</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/pfftm3kbsf6RpxZ6fmMoPf-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 26 Aug 2025 10:30:17 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:19 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Nicole Kobie ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/8Y8JDDTQ7XDEk49FoAFP2S-320-70.png ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Nicole Kobie first started writing for ITPro in 2007. As a freelance journalist covering technology and business, Nicole&#039;s work includes  bylines in New Scientist, Wired, PC Pro and many more. &lt;/p&gt;&lt;p&gt;Nicole the author of a book about the history of technology, The Long History of the Future.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/pfftm3kbsf6RpxZ6fmMoPf-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Software security concept image showing binary code snippets with some highlighted on a digital interface. ]]></media:description>                                                            <media:text><![CDATA[Software security concept image showing binary code snippets with some highlighted on a digital interface. ]]></media:text>
                                <media:title type="plain"><![CDATA[Software security concept image showing binary code snippets with some highlighted on a digital interface. ]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/pfftm3kbsf6RpxZ6fmMoPf-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Nearly three-quarters of organizations have suffered at least one security breach or incident in the last year that can be blamed on insecure coding practices. </p><p><a href="https://www.secureflag.com/resources/resource-details#secure-coding-training-in-uk-enterprises-c-suite-survey-key-findings" target="_blank"><u>Analysis from SecureFlag</u></a> found 74% of organizations have suffered an incident as a result of dodgy code, with nearly half of those hit by multiple breaches. </p><p>The report comes as <a href="https://www.itpro.com/software/development/vibe-coding-best-ai-models-secure-code-generation"><u>AI is beginning to take over some coding duties</u></a> from developers. Debate remains over whether that code is secure. Some say <a href="https://www.itpro.com/software/development/developers-say-ai-can-code-better-than-most-humans-but-theres-a-catch"><u>AI can code better than human developers</u></a>, but <a href="https://www.itpro.com/software/developers-relying-on-github-copilot-could-be-creating-dangerously-flawed-code"><u>research</u></a> has suggested insecure code could be easily replicated by <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI</a>. </p><p>Andrea Scaduto, CEO and co-founder of SecureFlag, said the study highlights the risks faced by enterprises rushing to automate aspects of software development. </p><p>"This should be a wake-up call for every business that develops software,” she said. “It’s frankly shocking that in 2025 so many breaches are still happening because of avoidable coding flaws.” </p><p>It wasn't all bad news, however. The report revealed that companies are ramping up developer security training as a result of lingering issues. Nearly half (44%) said they offer training updates on a quarterly basis, while 29% offer fresh training schemes monthly. </p><p>The report said this shows enterprises are conscious of the risks associated with insecure code and are taking proactive steps to mitigate risks. Indeed, nine-in-ten said they were formally assessing their development teams' secure coding skills. </p><p>The most common training format is video-based tutorials (46%) followed by eLearning platforms (42%). Classes, both in-person and virtual, were also popular for four-in-ten companies, as were interactive labs and hands-on environments. </p><p>A third of companies surveyed said they run hacking games such as "capture the flag".</p><h2 id="roi-for-developer-security-training">ROI for developer security training</h2><p>Challenges remain, however. According to SecureFlag, respondents said measuring return on investment (ROI) remained a hurdle (40%), followed by a lack of useful content, not enough time, low engagement from employees, and insufficient budget — as well as lack of leadership support. </p><p>"Even though most executives believe in the value of training, they struggle to prove in concrete terms how these programs reduce risk or justify their cost, a clear sign that quantifying the impact of secure coding initiatives remains elusive," the report noted. </p><p>"Overall, the data highlights that proving ROI to stakeholders and allocating sufficient time and content resources are the prevailing hurdles to overcome, even more so than money or buy-in."</p><p>Though they may lack the hard data to prove a ROI, nine-in-ten of those surveyed believe that secure coding has reduced the number of security bugs in development, and view training as a solid move to prevent such incidents. </p><p>"Breaches stemming from coding mistakes are preventable – but only if companies invest in proper training," said Emilio Pinna, SecureFlag’s CTO and co-founder. "It’s far cheaper to train a developer than to clean up after a breach."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/want-developers-to-build-secure-software-you-need-to-ditch-these-two-programming-languages">Want developers to build secure software? You need to ditch these two programming languages</a></li><li><a href="https://www.itpro.com/software/software-security-code-of-practice-ncsc-announcement">The NCSC wants developers to get serious on software security</a></li><li><a href="https://www.itpro.com/software/development/software-security-shift-left-developer-overload">Shifting left might improve software security, but developers are becoming overwhelmed</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ LevelBlue and Akamai are teaming up to launch a managed web application and API protection service ]]></title>
                                                                                                <dc:content><![CDATA[ <p>LevelBlue has announced a new strategic partnership with <a href="https://www.itpro.com/security/28133/what-is-cyber-security">cybersecurity </a>vendor Akamai to provide new managed web application and <a href="https://www.itpro.com/security/api-attacks-are-spiraling-out-of-control">API protection</a> services.</p><p>The new Managed Web Application and API Protection (WAAP) service aims to deliver flexible web app and API protection to help organizations consolidate, simplify, and scale their security.</p><p>Powered by Akamai’s App &amp; API Protector technology, the offering combines next-gen web application firewall (WAF), distributed-denial-of-service (DDoS) mitigation, bot protection, and foundational API security capabilities, backed by LevelBlue’s WAAP Operations team.</p><p>In an announcement, LevelBlue president, Sundhar Annamalai, said the service offers a solution to the complexity, silos, and rising costs of the modern web app and API security landscape.</p><p>“LevelBlue offers an alternative: proven services that consolidate and simplify protections with predictable investment,” he added. “By combining LevelBlue’s operational expertise with Akamai’s proven technology, organizations can stay ahead of evolving threats and create cyber resilience for critical digital capabilities.” </p><h2 id="what-the-partnership-means-for-customers">What the partnership means for customers</h2><p>Available in two tiers, Essential and Advanced, LevelBlue Managed WAAP combines AI-driven threat detection with global threat intelligence to catch anomalies, adapt to new attack vectors, and stay ahead of threats.</p><p>Organizations also benefit from automatic app and API prioritization, automated policy management to drive efficiency and reduce false positives, as well as around-the-clock access to WAAP specialists for support, monitoring, and advisory assistance.</p><p>The release comes as businesses continue to ramp up their use of web apps and APIs as part of their digital-first strategies. </p><p>According to research from Enterprise Strategy Group, the average number of web apps per organization is expected to rise from 145 to over 200 in the next two years, while those with over half their apps using APIs will shoot up from 32% to 80%</p><p>This sharp increase in ecosystem complexity brings fresh security challenges, particularly around app and API deployments and scaling, compounded further by industry staff constraints and skills gaps.</p><p>Rupesh Chokshi, senior vice president and general manager of Akamai’s Application Security Portfolio, said the company saw more than 311 billion web app attacks in 2024 alone. </p><p>“As AI accelerates, threats are harder to spot, and security is tougher to control,” he explained. </p><p>“<a href="https://www.itpro.com/cloud/cloud-computing/akamai-has-high-hopes-for-its-new-gecko-edge-cloud-service-but-can-it-target-competition-with-hyperscalers">Akamai </a>and LevelBlue’s partnership gives customers access to a trusted, reliable team that combines industry-leading technology with the deep operational expertise of one of the world’s largest MSSPs.</p><p>“It’s a powerful combination with a flexible solution that can fast-track organizations to resilient protection and compliance."</p><h3 class="article-body__section" id="section-more-from-channelpro"><span>MORE FROM CHANNELPRO</span></h3><ul><li><a href="https://www.itpro.com/security/ransomware/msps-beware-these-two-ransomware-groups-are-ramping-up-attacks-and-have-claimed-hundreds-of-victims">MSPs beware – these two ransomware groups are ramping up attacks </a></li><li><a href="https://www.itpro.com/security/firewalls/sonicwall-launches-new-firewalls-as-part-of-generation-8-refresh">SonicWall launches new firewalls as part of Generation 8 refresh</a></li><li><a href="https://www.itpro.com/business/business-strategy/we-are-helping-organizations-strengthen-their-overall-security-postures-fortinet-hits-major-milestone-as-partner-program-surpasses-400-partners">Fortinet hits major milestone as partner program surpasses 400 partners</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/levelblue-and-akamai-are-teaming-up-to-launch-a-managed-web-application-and-api-protection-service</link>
                                                                            <description>
                            <![CDATA[ The new Managed WAAP offering aims to help organizations secure their rapidly expanding web app and API ecosystems ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">irRMPb6UaNC5Am3kyR95wK</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/87BSyCjjR5QVShx4NmwLPF-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 15 Aug 2025 11:45:58 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:02 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                <author><![CDATA[ itpro@futurenet.com (Daniel Todd) ]]></author>                    <dc:creator><![CDATA[ Daniel Todd ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/SRyC34qeLpNDj3dJtsVDhT-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/87BSyCjjR5QVShx4NmwLPF-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[SaaS security concept imaging showing centralized cloud symbol with orange coloring connecting to different data points. ]]></media:description>                                                            <media:text><![CDATA[SaaS security concept imaging showing centralized cloud symbol with orange coloring connecting to different data points. ]]></media:text>
                                <media:title type="plain"><![CDATA[SaaS security concept imaging showing centralized cloud symbol with orange coloring connecting to different data points. ]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/87BSyCjjR5QVShx4NmwLPF-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>LevelBlue has announced a new strategic partnership with <a href="https://www.itpro.com/security/28133/what-is-cyber-security">cybersecurity </a>vendor Akamai to provide new managed web application and <a href="https://www.itpro.com/security/api-attacks-are-spiraling-out-of-control">API protection</a> services.</p><p>The new Managed Web Application and API Protection (WAAP) service aims to deliver flexible web app and API protection to help organizations consolidate, simplify, and scale their security.</p><p>Powered by Akamai’s App &amp; API Protector technology, the offering combines next-gen web application firewall (WAF), distributed-denial-of-service (DDoS) mitigation, bot protection, and foundational API security capabilities, backed by LevelBlue’s WAAP Operations team.</p><p>In an announcement, LevelBlue president, Sundhar Annamalai, said the service offers a solution to the complexity, silos, and rising costs of the modern web app and API security landscape.</p><p>“LevelBlue offers an alternative: proven services that consolidate and simplify protections with predictable investment,” he added. “By combining LevelBlue’s operational expertise with Akamai’s proven technology, organizations can stay ahead of evolving threats and create cyber resilience for critical digital capabilities.” </p><h2 id="what-the-partnership-means-for-customers">What the partnership means for customers</h2><p>Available in two tiers, Essential and Advanced, LevelBlue Managed WAAP combines AI-driven threat detection with global threat intelligence to catch anomalies, adapt to new attack vectors, and stay ahead of threats.</p><p>Organizations also benefit from automatic app and API prioritization, automated policy management to drive efficiency and reduce false positives, as well as around-the-clock access to WAAP specialists for support, monitoring, and advisory assistance.</p><p>The release comes as businesses continue to ramp up their use of web apps and APIs as part of their digital-first strategies. </p><p>According to research from Enterprise Strategy Group, the average number of web apps per organization is expected to rise from 145 to over 200 in the next two years, while those with over half their apps using APIs will shoot up from 32% to 80%</p><p>This sharp increase in ecosystem complexity brings fresh security challenges, particularly around app and API deployments and scaling, compounded further by industry staff constraints and skills gaps.</p><p>Rupesh Chokshi, senior vice president and general manager of Akamai’s Application Security Portfolio, said the company saw more than 311 billion web app attacks in 2024 alone. </p><p>“As AI accelerates, threats are harder to spot, and security is tougher to control,” he explained. </p><p>“<a href="https://www.itpro.com/cloud/cloud-computing/akamai-has-high-hopes-for-its-new-gecko-edge-cloud-service-but-can-it-target-competition-with-hyperscalers">Akamai </a>and LevelBlue’s partnership gives customers access to a trusted, reliable team that combines industry-leading technology with the deep operational expertise of one of the world’s largest MSSPs.</p><p>“It’s a powerful combination with a flexible solution that can fast-track organizations to resilient protection and compliance."</p><h3 class="article-body__section" id="section-more-from-channelpro"><span>MORE FROM CHANNELPRO</span></h3><ul><li><a href="https://www.itpro.com/security/ransomware/msps-beware-these-two-ransomware-groups-are-ramping-up-attacks-and-have-claimed-hundreds-of-victims">MSPs beware – these two ransomware groups are ramping up attacks </a></li><li><a href="https://www.itpro.com/security/firewalls/sonicwall-launches-new-firewalls-as-part-of-generation-8-refresh">SonicWall launches new firewalls as part of Generation 8 refresh</a></li><li><a href="https://www.itpro.com/business/business-strategy/we-are-helping-organizations-strengthen-their-overall-security-postures-fortinet-hits-major-milestone-as-partner-program-surpasses-400-partners">Fortinet hits major milestone as partner program surpasses 400 partners</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Perplexity hits back at Cloudflare amid claims of website 'stealth crawling' to dodge AI blocks ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Cloudflare has accused Perplexity of failing to honour requests from websites to opt out of content scraping by AI companies. </p><p>Last month, the web infrastructure company <a href="https://www.itpro.com/technology/artificial-intelligence/cloudflare-says-ai-companies-have-been-scraping-content-without-limits-now-its-letting-website-owners-block-crawlers-by-default"><u>announced a system to block AI companies</u></a> from accessing websites without permission or compensation. The move came as part of a push back against AI companies hoovering up the entire internet to use as training data — a tactic that has sparked lawsuits. </p><p>Cloudflare's system lets online publishers and other website owners block AI crawlers from seeing their content, with future plans to only allow those who have paid to scrape. </p><p>Several weeks into the blocking system, Cloudflare has reported that AI company Perplexity is using evasive techniques to access that content regardless. In a <a href="https://blog.cloudflare.com/perplexity-is-using-stealth-undeclared-crawlers-to-evade-website-no-crawl-directives/"><u>blog post</u></a> this week, the firm said Perplexity changes how it presents itself to a website when it spots a block. </p><p>"Although Perplexity initially crawls from their declared user agent, when they are presented with a network block, they appear to obscure their crawling identity in an attempt to circumvent the website’s preferences," the post noted. </p><p><em>ITPro </em>contacted Perplexity for a statement, but had received no response at time of publication. A spokesperson for the firm told <a href="https://techcrunch.com/2025/08/04/perplexity-accused-of-scraping-websites-that-explicitly-blocked-ai-scraping/" target="_blank"><u><em>TechCrunch</em></u></a><em> </em>that the Cloudflare research was a "sales pitch" for the blocking product and said that the bot discussed "isn't even ours." </p><p>In a separate statement to <a href="https://www.theverge.com/news/718319/perplexity-stealth-crawling-cloudflare-ai-bots-report" target="_blank"><u><em>The Verge</em></u></a>, the company said Cloudflare's report was a "publicity stunt" and that there were "a lot of misunderstandings in the blog post". </p><p>It's not the first time Perplexity has been accused of letting its bots crawl where they're not wanted. Reports from <a href="https://www.wired.com/story/aws-perplexity-bot-scraping-investigation/"><u>Wired</u></a> spotted such behavior last year while <a href="https://www.niemanlab.org/reading/forbes-threatens-perplexity-ai-with-legal-action-over-copyright-infringement/"><u>Forbes</u></a>, the <a href="https://techcrunch.com/2024/10/15/new-york-times-sends-perplexity-cease-and-desist-letter-demands-it-stops-using-its-content-in-ai-summaries/"><u>New York Times</u></a>, and the <a href="https://www.ft.com/content/b743d401-dc5d-44b8-9987-825a4ffcf4ca"><u>BBC</u></a> accused the company of scraping and reproducing their content without permission.</p><p>Perplexity has denied the accusations. </p><h2 id="what-cloudflare-claims">What Cloudflare claims</h2><p>Cloudflare said it saw "continued evidence" that Perplexity's user agent is changing their user agent and the source where it's coming from to hide this activity, and even ignoring or failing to view the "robot.txt" files — these are a list of instructions for bots telling them what to access and not, used for search crawlers and now AI agents. </p><p>After hearing complaints from customers who had tried to block AI crawlers, Cloudflare set up a series of experiments using brand-new test websites that were not publicly accessible, with a robots.txt file directing "respectful bots from accessing any part of a website." </p><p>Cloudflare then asked Perplexity AI questions about the domains, and found it was able to access detailed information from the restricted test sites. </p><p>"This response was unexpected, as we had taken all necessary precautions to prevent this data from being retrievable by their crawlers," the post noted. </p><p>Cloudflare said Perplexity is not only using a declared user agent, but also a generic browser that impersonates Chrome on macOS when the declared agent is blocked. </p><p>For comparison, Cloudflare ran similar tests with OpenAI's ChatGPT, finding it fetched the robots.txt file and stopped crawling when told not to access a page; when there were no instructions in the robots.txt file but there was a block page, ChatGPT again stopped crawling. </p><p>"Both of these demonstrate the appropriate response to website owner preferences," Cloudflare said. </p><h2 id="danger-to-the-internet">Danger to the internet?</h2><p>Cloudflare said that this behavior risks the network of trust that holds up the internet. </p><p>"There are clear preferences that crawlers should be transparent, serve a clear purpose, perform a specific activity, and, most importantly, follow website directives and preferences," the post said. </p><p>The company added that it would now block the AI company from websites using its service. </p><p>"Based on Perplexity’s observed behavior, which is incompatible with those preferences, we have de-listed them as a verified bot and added heuristics to our managed rules that block this stealth crawling," the post added. </p><p>Calling on AI companies to behave better, Cloudflare said "well-intentioned crawlers acting in good faith" should be transparent and identify the agent honestly, and not attempt to dodge detection by sites attempting to block such access. </p><p>For sites that do allow access, AI crawlers should behave fairly and not flood sites with too much traffic or scrape sensitive data, and serve a "clear purpose" — such as checking a price or powering a voice assistant.</p><p>Cloudflare also suggested AI companies use separate web crawlers for each activity, letting website owners more easily allow some crawler activity but not others. "Don’t force site owners to make an all-or-nothing decision," the post said. </p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/technology/artificial-intelligence/a-threat-to-googles-dominance-the-ai-browser-wars-have-begun-here-are-the-top-contenders-vying-for-the-crown">A threat to Google’s dominance? The AI browser wars have begun – here are the top contenders vying for the crown</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/perplexity-labs-ai-automation-tools">Sick and tired of spreadsheets? Perplexity’s new tools can help with that</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/perplexity-ai-a-startup-that-just-raised-dollar736-million-from-nvidia-and-databricks-wants-to-take-on-googles-search-engine-dominance">Perplexity AI, a startup that just raised $73.6 million from Nvidia and Databricks, wants to take on Google's search engine</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/privacy/perplexity-hits-back-at-cloudflare-amid-claims-of-website-stealth-crawling-to-dodge-ai-blocks</link>
                                                                            <description>
                            <![CDATA[ Perplexity has hit back at claims by Cloudflare that it's been stealthily crawling websites, suggesting recent research was a "sales pitch" for a new blocking product. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">vFQj9Y9afqoHddNfyQfn7A</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/fQWXQDcyzua2pePWLh4PUZ-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 06 Aug 2025 08:21:39 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 14:56:37 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Nicole Kobie ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/8Y8JDDTQ7XDEk49FoAFP2S-320-70.png ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Nicole Kobie first started writing for ITPro in 2007. As a freelance journalist covering technology and business, Nicole&#039;s work includes  bylines in New Scientist, Wired, PC Pro and many more. &lt;/p&gt;&lt;p&gt;Nicole the author of a book about the history of technology, The Long History of the Future.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/fQWXQDcyzua2pePWLh4PUZ-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Logo of Perplexity AI, developer of the Perplexity Labs, Deep Research, and AI-powered browser tools, pictured on a smartphone screen.]]></media:description>                                                            <media:text><![CDATA[Logo of Perplexity AI, developer of the Perplexity Labs, Deep Research, and AI-powered browser tools, pictured on a smartphone screen.]]></media:text>
                                <media:title type="plain"><![CDATA[Logo of Perplexity AI, developer of the Perplexity Labs, Deep Research, and AI-powered browser tools, pictured on a smartphone screen.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/fQWXQDcyzua2pePWLh4PUZ-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Cloudflare has accused Perplexity of failing to honour requests from websites to opt out of content scraping by AI companies. </p><p>Last month, the web infrastructure company <a href="https://www.itpro.com/technology/artificial-intelligence/cloudflare-says-ai-companies-have-been-scraping-content-without-limits-now-its-letting-website-owners-block-crawlers-by-default"><u>announced a system to block AI companies</u></a> from accessing websites without permission or compensation. The move came as part of a push back against AI companies hoovering up the entire internet to use as training data — a tactic that has sparked lawsuits. </p><p>Cloudflare's system lets online publishers and other website owners block AI crawlers from seeing their content, with future plans to only allow those who have paid to scrape. </p><p>Several weeks into the blocking system, Cloudflare has reported that AI company Perplexity is using evasive techniques to access that content regardless. In a <a href="https://blog.cloudflare.com/perplexity-is-using-stealth-undeclared-crawlers-to-evade-website-no-crawl-directives/"><u>blog post</u></a> this week, the firm said Perplexity changes how it presents itself to a website when it spots a block. </p><p>"Although Perplexity initially crawls from their declared user agent, when they are presented with a network block, they appear to obscure their crawling identity in an attempt to circumvent the website’s preferences," the post noted. </p><p><em>ITPro </em>contacted Perplexity for a statement, but had received no response at time of publication. A spokesperson for the firm told <a href="https://techcrunch.com/2025/08/04/perplexity-accused-of-scraping-websites-that-explicitly-blocked-ai-scraping/" target="_blank"><u><em>TechCrunch</em></u></a><em> </em>that the Cloudflare research was a "sales pitch" for the blocking product and said that the bot discussed "isn't even ours." </p><p>In a separate statement to <a href="https://www.theverge.com/news/718319/perplexity-stealth-crawling-cloudflare-ai-bots-report" target="_blank"><u><em>The Verge</em></u></a>, the company said Cloudflare's report was a "publicity stunt" and that there were "a lot of misunderstandings in the blog post". </p><p>It's not the first time Perplexity has been accused of letting its bots crawl where they're not wanted. Reports from <a href="https://www.wired.com/story/aws-perplexity-bot-scraping-investigation/"><u>Wired</u></a> spotted such behavior last year while <a href="https://www.niemanlab.org/reading/forbes-threatens-perplexity-ai-with-legal-action-over-copyright-infringement/"><u>Forbes</u></a>, the <a href="https://techcrunch.com/2024/10/15/new-york-times-sends-perplexity-cease-and-desist-letter-demands-it-stops-using-its-content-in-ai-summaries/"><u>New York Times</u></a>, and the <a href="https://www.ft.com/content/b743d401-dc5d-44b8-9987-825a4ffcf4ca"><u>BBC</u></a> accused the company of scraping and reproducing their content without permission.</p><p>Perplexity has denied the accusations. </p><h2 id="what-cloudflare-claims">What Cloudflare claims</h2><p>Cloudflare said it saw "continued evidence" that Perplexity's user agent is changing their user agent and the source where it's coming from to hide this activity, and even ignoring or failing to view the "robot.txt" files — these are a list of instructions for bots telling them what to access and not, used for search crawlers and now AI agents. </p><p>After hearing complaints from customers who had tried to block AI crawlers, Cloudflare set up a series of experiments using brand-new test websites that were not publicly accessible, with a robots.txt file directing "respectful bots from accessing any part of a website." </p><p>Cloudflare then asked Perplexity AI questions about the domains, and found it was able to access detailed information from the restricted test sites. </p><p>"This response was unexpected, as we had taken all necessary precautions to prevent this data from being retrievable by their crawlers," the post noted. </p><p>Cloudflare said Perplexity is not only using a declared user agent, but also a generic browser that impersonates Chrome on macOS when the declared agent is blocked. </p><p>For comparison, Cloudflare ran similar tests with OpenAI's ChatGPT, finding it fetched the robots.txt file and stopped crawling when told not to access a page; when there were no instructions in the robots.txt file but there was a block page, ChatGPT again stopped crawling. </p><p>"Both of these demonstrate the appropriate response to website owner preferences," Cloudflare said. </p><h2 id="danger-to-the-internet">Danger to the internet?</h2><p>Cloudflare said that this behavior risks the network of trust that holds up the internet. </p><p>"There are clear preferences that crawlers should be transparent, serve a clear purpose, perform a specific activity, and, most importantly, follow website directives and preferences," the post said. </p><p>The company added that it would now block the AI company from websites using its service. </p><p>"Based on Perplexity’s observed behavior, which is incompatible with those preferences, we have de-listed them as a verified bot and added heuristics to our managed rules that block this stealth crawling," the post added. </p><p>Calling on AI companies to behave better, Cloudflare said "well-intentioned crawlers acting in good faith" should be transparent and identify the agent honestly, and not attempt to dodge detection by sites attempting to block such access. </p><p>For sites that do allow access, AI crawlers should behave fairly and not flood sites with too much traffic or scrape sensitive data, and serve a "clear purpose" — such as checking a price or powering a voice assistant.</p><p>Cloudflare also suggested AI companies use separate web crawlers for each activity, letting website owners more easily allow some crawler activity but not others. "Don’t force site owners to make an all-or-nothing decision," the post said. </p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/technology/artificial-intelligence/a-threat-to-googles-dominance-the-ai-browser-wars-have-begun-here-are-the-top-contenders-vying-for-the-crown">A threat to Google’s dominance? The AI browser wars have begun – here are the top contenders vying for the crown</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/perplexity-labs-ai-automation-tools">Sick and tired of spreadsheets? Perplexity’s new tools can help with that</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/perplexity-ai-a-startup-that-just-raised-dollar736-million-from-nvidia-and-databricks-wants-to-take-on-googles-search-engine-dominance">Perplexity AI, a startup that just raised $73.6 million from Nvidia and Databricks, wants to take on Google's search engine</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Researchers tested over 100 leading AI models on coding tasks — nearly half produced glaring security flaws ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Just 55% of code generated with AI is free of known cybersecurity vulnerabilities, according to new research from Veracode. </p><p>To test the capability of AI models to generate safe code, Veracode took existing functions and replaced part of the code with a comment describing what the finished code should look like. </p><p>In 45% of results, generated code contained known security flaws, with no significant difference in outcome between small models and the largest available.</p><div class="product"><a data-dimension112="3332482e-1e8e-4fdc-ac60-12ce28450b99" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow"><figure class="van-image-figure "  ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:310px;"><p class="vanilla-image-block" style="padding-top:52.58%;"><img id="VVXzWjJJrXo7mwL5n5f4mf" name="Keeper Security logo.png" caption="" alt="" src="https://cdn.mos.cms.futurecdn.net/VVXzWjJJrXo7mwL5n5f4mf-1920-80.png" mos="" align="middle" fullscreen="" width="310" height="163" attribution="" endorsement="" credit="" class="" /></p></div></div></figure></a><p><a href="https://www.keepersecurity.com/en_GB/affiliate/business/" data-dimension112="3332482e-1e8e-4fdc-ac60-12ce28450b99" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25=""><strong>30% off Keeper Security's Business Starter and Business plans</strong></a></p><p>Keeper Security is trusted and valued by thousands of businesses and millions of employees. Why not join them and protect your most important assets while taking advantage of this special offer?<a class="view-deal button" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow" data-dimension112="3332482e-1e8e-4fdc-ac60-12ce28450b99" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25="">View Deal</a></p></div><p>The findings underline a major potential risk attached to <a href="https://www.itpro.com/software/development/vibe-coding-best-ai-models-secure-code-generation"><u>‘vibe coding’</u></a>, in which software developers rely heavily on large language model (LLM) output to quickly generate code for use in software.</p><p>Researchers put over 100 LLMs across a variety of vendors, sizes, and intended applications – including models specifically intended for coding as well as general purpose models – through 80 distinct coding tasks.</p><p>Veracode said researchers intentionally used sections that could be coded in a number of different ‘correct’ ways, as well as in at least one way that would include a known software vulnerability or ‘Common Weakness Enumeration’ (CWE).</p><p>These CWEs included flaws that hackers could use for <a href="https://www.itpro.com/hacking/34441/how-does-a-sql-injection-attack-work"><u>SQL injection</u></a>, <a href="https://www.itpro.com/cross-site-scripting-xss/34411/what-is-cross-site-scripting-xss"><u>cross-site scripting (XSS)</u></a>, cracking <a href="https://www.itpro.com/security/innovation-at-work/24460/what-is-data-encryption"><u>cryptographic algorithms</u></a>, and log injection attacks. Each featured vulnerability is in the Open Worldwide Application Security Project (OWASP) list of top ten vulnerabilities.</p><p>Models showed inconsistent performance across different vulnerability types, achieving security pass rates of 85.6% and 80.4% when it came to avoiding inclusion of the cryptographic algorithm and SQL injection vulnerabilities.</p><p>In contrast, models fared extremely poorly with avoiding the XSS and log injection vulnerabilities, achieving an average 13.5% and 12% respectively. </p><p>Researchers noted that the tested LLMs are getting better still at avoiding the SQL injection and cryptographic algorithm flaws over time, while seemingly getting worse at avoiding the XSS and log injection vulnerabilities.</p><p>Overall, Veracode noted that the security improvements of the tested LLMs have flatlined.</p><p>The authors of the report noted that it is possible to phrase AI code prompts in a more security-conscious way, but that this is far from standard practice. With this in mind, they intentionally short prompts, to examine how models react when given minimal context.</p><p>But they also warned that even if firms take a more security-aware approach to code generation, LLMs are still prone to errors such as which variables require sanitization, a necessary step for preventing code injection attacks.</p><p>“Even with a large context window, it is unclear whether models can perform the detailed interprocedural dataflow analysis required to determine this information precisely,” they wrote.</p><p>LLMs were tested across a range of programming languages: Python, C#, JavaScript, and Java. Overall, the researchers found LLMs the worst at generating Java safely, achieving an average score of 28.5% in this <a href="https://www.itpro.com/software/development/its-far-from-showing-its-age-java-mightve-just-turned-30-but-its-still-going-strong-and-here-to-stay"><u>widely-used language</u></a>.</p><h2 id="ai-generated-code-remains-a-concern-but-adoption-is-still-rising">AI-generated code remains a concern, but adoption is still rising</h2><p>AI tools are now widely used for generating code, with <a href="https://www.itpro.com/software/development/developers-arent-quite-ready-to-place-their-trust-in-ai-nearly-half-say-they-dont-trust-the-accuracy-of-outputs-and-end-up-wasting-time-debugging-code"><u>84% of software developers</u></a> using AI to produce code more quickly according to recent Stack Overflow findings. </p><p>But the same report underlined continued distrust among developers in the quality of <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>code, with three-quarters (75.3%) reporting that they do not trust AI outputs and 61.7% stating they have security concerns over the use of AI code.</p><p>Despite these worries, big tech continues to embrace AI code, with Alphabet CEO Sundar Pichai having revealed last year that <a href="https://www.itpro.com/technology/artificial-intelligence/sundar-pichai-says-more-than-25-percent-of-googles-code-is-now-generated-by-ai-and-its-a-big-hint-at-the-future-of-software-development"><u>25% of Google’s internal code</u></a> is now AI-generated and Microsoft CEO Satya Nadella <a href="https://www.itpro.com/software/development/developers-will-need-to-adapt-microsoft-ceo-satya-nadella-joins-googles-sundar-pichai-in-revealing-the-scale-of-ai-generated-code-at-the-tech-giants-and-its-a-stark-warning-for-software-developers"><u>recently revealing up to 20-30% of his firm’s code was written by AI</u></a>.</p><p>Nadella noted that while Microsoft has been quick to adopt AI-generated Python code, C++ has proven harder to adopt. Kevin Scott, CTO at Microsoft, has been bullish on overcoming these hurdles with his prediction that 95% of code will be AI-generated by 2030, as reported by <em>Business Insider</em>.</p><p>Security teams and developers will have to carefully weigh up findings such as Veracode’s against the potential benefits to their bottom line of using AI to alter and add to their codebase.</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/development/ai-coding-tools-software-development-regional-popularity">AI coding tools are booming – and developers in this one country are by far the most frequent users</a></li><li><a href="https://www.itpro.com/software/development/ai-coding-tools-are-finally-delivering-results-for-enterprises-developers-are-saving-so-much-time-theyre-able-to-collaborate-more-focus-on-system-design-and-learn-new-languages">AI coding tools are finally delivering results for enterprises</a></li><li><a href="https://www.itpro.com/software/development/think-ai-coding-tools-are-speeding-up-work-think-again-theyre-actually-slowing-developers-down">Think AI coding tools are speeding up work? Think again – they’re actually slowing developers down</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/technology/artificial-intelligence/researchers-tested-over-100-leading-ai-models-on-coding-tasks-nearly-half-produced-glaring-security-flaws</link>
                                                                            <description>
                            <![CDATA[ AI models large and small were found to introduce cross-site scripting errors and seriously struggle with secure Java generation ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">TE29RBeTEhbXQCoRiqjRyd</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/9ZT5mU7YeSN7Bg7YHh2LxX-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 30 Jul 2025 12:22:19 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:53 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Artificial Intelligence]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                <author><![CDATA[ rory.bathgate@futurenet.com (Rory Bathgate) ]]></author>                    <dc:creator><![CDATA[ Rory Bathgate ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Vep5JogbPhduK7R6CUWAm6-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Rory Bathgate was the Features and Multimedia Editor at ITPro until 2026, overseeing all in-depth content and case studies. Throughout his time at ITPro, Rory  charted the rise in popularity of generative AI and specifically companies such as Microsoft, OpenAI, and Google. &lt;/p&gt;&lt;p&gt;Alongside this, he delved into increasing calls for ethical and responsible AI as global legislators circle the technology, as well as the latest in mobile networking technology, from 5G mmWave to the 3G sunset and how it will affect businesses.&lt;/p&gt;&lt;p&gt;He  provided coverage from high-profile tech conferences such as Dell Technologies World, SuiteWorld, and VMware Explore Europe. His on-the-ground coverage  included live blogs, extensive daily coverage of the most significant announcements, analysis pieces, and podcast.&lt;/p&gt;&lt;p&gt;Rory was the co-host of the ITPro Podcast alongside Jane McCallion, where he swapped a keyboard for a microphone to discuss the latest learnings in tech.&lt;/p&gt;&lt;p&gt;Rory has an MA in Eighteenth-Century Studies from King’s College London, as well as a BA in English and American Literature from the University of Kent. He joined ITPro in 2022 as a graduate, after four years in student journalism.&lt;/p&gt;&lt;p&gt;In his free time, Rory enjoys photography and video editing, and can often be found at the cinema or reading a good science fiction paperback.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/9ZT5mU7YeSN7Bg7YHh2LxX-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Female software developer coding in dark room with screen reflecting on glasses.]]></media:description>                                                            <media:text><![CDATA[Female software developer coding in dark room with screen reflecting on glasses.]]></media:text>
                                <media:title type="plain"><![CDATA[Female software developer coding in dark room with screen reflecting on glasses.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/9ZT5mU7YeSN7Bg7YHh2LxX-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Just 55% of code generated with AI is free of known cybersecurity vulnerabilities, according to new research from Veracode. </p><p>To test the capability of AI models to generate safe code, Veracode took existing functions and replaced part of the code with a comment describing what the finished code should look like. </p><p>In 45% of results, generated code contained known security flaws, with no significant difference in outcome between small models and the largest available.</p><div class="product"><a data-dimension112="3332482e-1e8e-4fdc-ac60-12ce28450b99" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow"><figure class="van-image-figure "  ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:310px;"><p class="vanilla-image-block" style="padding-top:52.58%;"><img id="VVXzWjJJrXo7mwL5n5f4mf" name="Keeper Security logo.png" caption="" alt="" src="https://cdn.mos.cms.futurecdn.net/VVXzWjJJrXo7mwL5n5f4mf-1920-80.png" mos="" align="middle" fullscreen="" width="310" height="163" attribution="" endorsement="" credit="" class="" /></p></div></div></figure></a><p><a href="https://www.keepersecurity.com/en_GB/affiliate/business/" data-dimension112="3332482e-1e8e-4fdc-ac60-12ce28450b99" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25=""><strong>30% off Keeper Security's Business Starter and Business plans</strong></a></p><p>Keeper Security is trusted and valued by thousands of businesses and millions of employees. Why not join them and protect your most important assets while taking advantage of this special offer?<a class="view-deal button" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow" data-dimension112="3332482e-1e8e-4fdc-ac60-12ce28450b99" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25="">View Deal</a></p></div><p>The findings underline a major potential risk attached to <a href="https://www.itpro.com/software/development/vibe-coding-best-ai-models-secure-code-generation"><u>‘vibe coding’</u></a>, in which software developers rely heavily on large language model (LLM) output to quickly generate code for use in software.</p><p>Researchers put over 100 LLMs across a variety of vendors, sizes, and intended applications – including models specifically intended for coding as well as general purpose models – through 80 distinct coding tasks.</p><p>Veracode said researchers intentionally used sections that could be coded in a number of different ‘correct’ ways, as well as in at least one way that would include a known software vulnerability or ‘Common Weakness Enumeration’ (CWE).</p><p>These CWEs included flaws that hackers could use for <a href="https://www.itpro.com/hacking/34441/how-does-a-sql-injection-attack-work"><u>SQL injection</u></a>, <a href="https://www.itpro.com/cross-site-scripting-xss/34411/what-is-cross-site-scripting-xss"><u>cross-site scripting (XSS)</u></a>, cracking <a href="https://www.itpro.com/security/innovation-at-work/24460/what-is-data-encryption"><u>cryptographic algorithms</u></a>, and log injection attacks. Each featured vulnerability is in the Open Worldwide Application Security Project (OWASP) list of top ten vulnerabilities.</p><p>Models showed inconsistent performance across different vulnerability types, achieving security pass rates of 85.6% and 80.4% when it came to avoiding inclusion of the cryptographic algorithm and SQL injection vulnerabilities.</p><p>In contrast, models fared extremely poorly with avoiding the XSS and log injection vulnerabilities, achieving an average 13.5% and 12% respectively. </p><p>Researchers noted that the tested LLMs are getting better still at avoiding the SQL injection and cryptographic algorithm flaws over time, while seemingly getting worse at avoiding the XSS and log injection vulnerabilities.</p><p>Overall, Veracode noted that the security improvements of the tested LLMs have flatlined.</p><p>The authors of the report noted that it is possible to phrase AI code prompts in a more security-conscious way, but that this is far from standard practice. With this in mind, they intentionally short prompts, to examine how models react when given minimal context.</p><p>But they also warned that even if firms take a more security-aware approach to code generation, LLMs are still prone to errors such as which variables require sanitization, a necessary step for preventing code injection attacks.</p><p>“Even with a large context window, it is unclear whether models can perform the detailed interprocedural dataflow analysis required to determine this information precisely,” they wrote.</p><p>LLMs were tested across a range of programming languages: Python, C#, JavaScript, and Java. Overall, the researchers found LLMs the worst at generating Java safely, achieving an average score of 28.5% in this <a href="https://www.itpro.com/software/development/its-far-from-showing-its-age-java-mightve-just-turned-30-but-its-still-going-strong-and-here-to-stay"><u>widely-used language</u></a>.</p><h2 id="ai-generated-code-remains-a-concern-but-adoption-is-still-rising">AI-generated code remains a concern, but adoption is still rising</h2><p>AI tools are now widely used for generating code, with <a href="https://www.itpro.com/software/development/developers-arent-quite-ready-to-place-their-trust-in-ai-nearly-half-say-they-dont-trust-the-accuracy-of-outputs-and-end-up-wasting-time-debugging-code"><u>84% of software developers</u></a> using AI to produce code more quickly according to recent Stack Overflow findings. </p><p>But the same report underlined continued distrust among developers in the quality of <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>code, with three-quarters (75.3%) reporting that they do not trust AI outputs and 61.7% stating they have security concerns over the use of AI code.</p><p>Despite these worries, big tech continues to embrace AI code, with Alphabet CEO Sundar Pichai having revealed last year that <a href="https://www.itpro.com/technology/artificial-intelligence/sundar-pichai-says-more-than-25-percent-of-googles-code-is-now-generated-by-ai-and-its-a-big-hint-at-the-future-of-software-development"><u>25% of Google’s internal code</u></a> is now AI-generated and Microsoft CEO Satya Nadella <a href="https://www.itpro.com/software/development/developers-will-need-to-adapt-microsoft-ceo-satya-nadella-joins-googles-sundar-pichai-in-revealing-the-scale-of-ai-generated-code-at-the-tech-giants-and-its-a-stark-warning-for-software-developers"><u>recently revealing up to 20-30% of his firm’s code was written by AI</u></a>.</p><p>Nadella noted that while Microsoft has been quick to adopt AI-generated Python code, C++ has proven harder to adopt. Kevin Scott, CTO at Microsoft, has been bullish on overcoming these hurdles with his prediction that 95% of code will be AI-generated by 2030, as reported by <em>Business Insider</em>.</p><p>Security teams and developers will have to carefully weigh up findings such as Veracode’s against the potential benefits to their bottom line of using AI to alter and add to their codebase.</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/development/ai-coding-tools-software-development-regional-popularity">AI coding tools are booming – and developers in this one country are by far the most frequent users</a></li><li><a href="https://www.itpro.com/software/development/ai-coding-tools-are-finally-delivering-results-for-enterprises-developers-are-saving-so-much-time-theyre-able-to-collaborate-more-focus-on-system-design-and-learn-new-languages">AI coding tools are finally delivering results for enterprises</a></li><li><a href="https://www.itpro.com/software/development/think-ai-coding-tools-are-speeding-up-work-think-again-theyre-actually-slowing-developers-down">Think AI coding tools are speeding up work? Think again – they’re actually slowing developers down</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Enterprises need to sharpen up on software supply chain security ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Organizations are in the dark about their software supply chain visibility, despite 40% of CEOs saying it's their biggest security risk.</p><p>A new <a href="https://levelblue.com/resource-center/levelblue-research/2025-data-accelerator-software-supply-chain-cybersecurity" target="_blank"><u>report from LevelBlue</u></a> has found that only 23% of organizations are confident that they have very high visibility of their software supply chain, with 49% lacking the visibility to fully understand – or even identify – the risks. </p><p>This, the study noted, has huge consequences for enterprises, with 80% of those with low visibility having suffered a security breach in the past 12 months - vastly more than the 6% of those on the opposite end of the scale. </p><div class="product"><a data-dimension112="b55851a0-6cb2-425d-9407-194f24f705d9" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow"><figure class="van-image-figure "  ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:310px;"><p class="vanilla-image-block" style="padding-top:52.58%;"><img id="VVXzWjJJrXo7mwL5n5f4mf" name="Keeper Security logo.png" caption="" alt="" src="https://cdn.mos.cms.futurecdn.net/VVXzWjJJrXo7mwL5n5f4mf-1920-80.png" mos="" align="middle" fullscreen="" width="310" height="163" attribution="" endorsement="" credit="" class="" /></p></div></div></figure></a><p><a href="https://www.keepersecurity.com/en_GB/affiliate/business/" data-dimension112="b55851a0-6cb2-425d-9407-194f24f705d9" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25=""><strong>30% off Keeper Security's Business Starter and Business plans</strong></a></p><p>Keeper Security is trusted and valued by thousands of businesses and millions of employees. Why not join them and protect your most important assets while taking advantage of this special offer?<a class="view-deal button" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow" data-dimension112="b55851a0-6cb2-425d-9407-194f24f705d9" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25="">View Deal</a></p></div><p>Meanwhile, 80% of organizations with low visibility view critical factors like custom code, commercial off-the-shelf software, and API integrations as very risky or somewhat risky.</p><p>Theresa Lanowitz, chief evangelist at LevelBlue, said the study highlights the “immediate need” for organizations to prioritize improvements to <a href="https://www.itpro.com/software/software-supply-chain-attacks-are-rife-this-is-what-developers-need-to-watch-out-for">software supply chain security</a>.</p><p>"In an era of increasing AI disruption and evolving threats from nation-states and cyber criminal groups, the ability to withstand and recover from cyber attacks is directly tied to a clear understanding of an organisation's software ecosystem,” Lanowitz said.</p><h2 id="focus-on-software-supply-chain-security-is-growing">Focus on software supply chain security is growing</h2><p>Media attention has bumped cybersecurity up on the C-suite agenda, with organizations saying that <a href="https://www.itpro.com/security/insurance-sector-urged-to-sharpen-up-third-party-risk-management-as-attacks-surge">third-party risk management</a> is one of the biggest threats they face. </p><p>Yet despite this, only a quarter plan to prioritize engaging with software suppliers about security credentials in the next 12 months.</p><p>CEOs are more concerned about the risks of the software supply chain than other C-suite executives - 40% said it was the biggest security risk their organisation faces today, compared with 29% of CIOs and 27% of CTOs.</p><p>North America appears to be more prepared for software supply chain attacks, with 57% of  organizations saying they are ready for the threat, compared to just 44% in APAC, 51% in Europe and 50% in Latin America.</p><h2 id="europe-leads-the-way-on-investment">Europe leads the way on investment</h2><p>According to LevelBlue, European organizations lead the way on proactive investment in this regard. The study found more than two-thirds (67%) of enterprises in the region are investing in enhanced software supply chain security capabilities. </p><p>Establishing visibility across the supply chain isn't easy, requiring the cooperation of all up-stream suppliers and a consensus on standard methods and formats for communicating software components. </p><p>Crucially, new standards and regulations are emerging that will place pressure on organizations to sharpen up their capabilities. </p><p>The EU<a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra"> Cyber Resilience Act (CRA)</a>, for example, includes a Software Bill of Materials (SBOM) provision for impacted software, while in the US the FDA requires all network-connected medical devices to include SBOMs as part of the approval process.</p><p>Similarly, the US government is <a href="https://www.itpro.com/security/software-security-overhauled-for-the-better-thanks-to-us-legislation">mandating that software vendors contracted with federal agencies provide SBOMs</a>.</p><p>Mike McGuire, senior software manager at Black Duck, said that regardless of whether an organization is operating in a regulated environment, improvements to broader supply chain visibility are paramount. </p><p>“This means making standardized SBOMs a hard requirement of their vendors and software producers," McGuire said. </p><p>"Software producers should see this shifting landscape not as introducing additional burdens, but rather as an opportunity to leverage security and transparency as leverage over their less diligent competitors."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/software-security-flaws-remediation">Software security debt is spiraling out of control </a></li><li><a href="https://www.itpro.com/software/want-developers-to-build-secure-software-you-need-to-ditch-these-two-programming-languages">Want developers to build secure software? You need to ditch these two programming languages</a></li><li><a href="https://www.itpro.com/software/software-security-code-of-practice-ncsc-announcement">The NCSC wants developers to get serious on software security</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/enterprises-need-to-sharpen-up-on-software-supply-chain-security</link>
                                                                            <description>
                            <![CDATA[ A new report from LevelBlue shows many enterprises are failing on software supply chain security, despite growing risks. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">qX3vqSMUuqRAGs5SkXVwD</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/EibGSnXsYyx7jBFwACwsQQ-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 10 Jul 2025 11:50:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:21 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Workplace Technology]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/EibGSnXsYyx7jBFwACwsQQ-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Software supply chain security concept image showing glowing data points all connected to three sources overlaid on a digital interface.]]></media:description>                                                            <media:text><![CDATA[Software supply chain security concept image showing glowing data points all connected to three sources overlaid on a digital interface.]]></media:text>
                                <media:title type="plain"><![CDATA[Software supply chain security concept image showing glowing data points all connected to three sources overlaid on a digital interface.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/EibGSnXsYyx7jBFwACwsQQ-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Organizations are in the dark about their software supply chain visibility, despite 40% of CEOs saying it's their biggest security risk.</p><p>A new <a href="https://levelblue.com/resource-center/levelblue-research/2025-data-accelerator-software-supply-chain-cybersecurity" target="_blank"><u>report from LevelBlue</u></a> has found that only 23% of organizations are confident that they have very high visibility of their software supply chain, with 49% lacking the visibility to fully understand – or even identify – the risks. </p><p>This, the study noted, has huge consequences for enterprises, with 80% of those with low visibility having suffered a security breach in the past 12 months - vastly more than the 6% of those on the opposite end of the scale. </p><div class="product"><a data-dimension112="b55851a0-6cb2-425d-9407-194f24f705d9" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow"><figure class="van-image-figure "  ><div class='image-full-width-wrapper'><div class='image-widthsetter' style="max-width:310px;"><p class="vanilla-image-block" style="padding-top:52.58%;"><img id="VVXzWjJJrXo7mwL5n5f4mf" name="Keeper Security logo.png" caption="" alt="" src="https://cdn.mos.cms.futurecdn.net/VVXzWjJJrXo7mwL5n5f4mf-1920-80.png" mos="" align="middle" fullscreen="" width="310" height="163" attribution="" endorsement="" credit="" class="" /></p></div></div></figure></a><p><a href="https://www.keepersecurity.com/en_GB/affiliate/business/" data-dimension112="b55851a0-6cb2-425d-9407-194f24f705d9" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25=""><strong>30% off Keeper Security's Business Starter and Business plans</strong></a></p><p>Keeper Security is trusted and valued by thousands of businesses and millions of employees. Why not join them and protect your most important assets while taking advantage of this special offer?<a class="view-deal button" href="https://www.keepersecurity.com/en_GB/affiliate/business/" target="_blank" rel="nofollow" data-dimension112="b55851a0-6cb2-425d-9407-194f24f705d9" data-action="Deal Block" data-label="30% off Keeper Security's Business Starter and Business plans" data-dimension48="30% off Keeper Security's Business Starter and Business plans" data-dimension25="">View Deal</a></p></div><p>Meanwhile, 80% of organizations with low visibility view critical factors like custom code, commercial off-the-shelf software, and API integrations as very risky or somewhat risky.</p><p>Theresa Lanowitz, chief evangelist at LevelBlue, said the study highlights the “immediate need” for organizations to prioritize improvements to <a href="https://www.itpro.com/software/software-supply-chain-attacks-are-rife-this-is-what-developers-need-to-watch-out-for">software supply chain security</a>.</p><p>"In an era of increasing AI disruption and evolving threats from nation-states and cyber criminal groups, the ability to withstand and recover from cyber attacks is directly tied to a clear understanding of an organisation's software ecosystem,” Lanowitz said.</p><h2 id="focus-on-software-supply-chain-security-is-growing">Focus on software supply chain security is growing</h2><p>Media attention has bumped cybersecurity up on the C-suite agenda, with organizations saying that <a href="https://www.itpro.com/security/insurance-sector-urged-to-sharpen-up-third-party-risk-management-as-attacks-surge">third-party risk management</a> is one of the biggest threats they face. </p><p>Yet despite this, only a quarter plan to prioritize engaging with software suppliers about security credentials in the next 12 months.</p><p>CEOs are more concerned about the risks of the software supply chain than other C-suite executives - 40% said it was the biggest security risk their organisation faces today, compared with 29% of CIOs and 27% of CTOs.</p><p>North America appears to be more prepared for software supply chain attacks, with 57% of  organizations saying they are ready for the threat, compared to just 44% in APAC, 51% in Europe and 50% in Latin America.</p><h2 id="europe-leads-the-way-on-investment">Europe leads the way on investment</h2><p>According to LevelBlue, European organizations lead the way on proactive investment in this regard. The study found more than two-thirds (67%) of enterprises in the region are investing in enhanced software supply chain security capabilities. </p><p>Establishing visibility across the supply chain isn't easy, requiring the cooperation of all up-stream suppliers and a consensus on standard methods and formats for communicating software components. </p><p>Crucially, new standards and regulations are emerging that will place pressure on organizations to sharpen up their capabilities. </p><p>The EU<a href="https://www.itpro.com/business/policy-and-legislation/what-is-the-eus-cyber-resilience-act-cra"> Cyber Resilience Act (CRA)</a>, for example, includes a Software Bill of Materials (SBOM) provision for impacted software, while in the US the FDA requires all network-connected medical devices to include SBOMs as part of the approval process.</p><p>Similarly, the US government is <a href="https://www.itpro.com/security/software-security-overhauled-for-the-better-thanks-to-us-legislation">mandating that software vendors contracted with federal agencies provide SBOMs</a>.</p><p>Mike McGuire, senior software manager at Black Duck, said that regardless of whether an organization is operating in a regulated environment, improvements to broader supply chain visibility are paramount. </p><p>“This means making standardized SBOMs a hard requirement of their vendors and software producers," McGuire said. </p><p>"Software producers should see this shifting landscape not as introducing additional burdens, but rather as an opportunity to leverage security and transparency as leverage over their less diligent competitors."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/software-security-flaws-remediation">Software security debt is spiraling out of control </a></li><li><a href="https://www.itpro.com/software/want-developers-to-build-secure-software-you-need-to-ditch-these-two-programming-languages">Want developers to build secure software? You need to ditch these two programming languages</a></li><li><a href="https://www.itpro.com/software/software-security-code-of-practice-ncsc-announcement">The NCSC wants developers to get serious on software security</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Cloudflare is cracking down on AI web scrapers ]]></title>
                                                                                                <dc:content><![CDATA[ <p><a href="https://www.itpro.com/cloud/32096/everything-you-need-to-know-about-cloudflare">Cloudflare </a>has announced new capabilities aimed at blocking <a href="https://www.itpro.com/technology/artificial-intelligence/openai-quietly-unveils-gptbot-dedicated-web-crawler">AI crawlers</a> from accessing content without permission or compensation. </p><p>Available by default from today (1st July), the web infrastructure firm will allow website owners to choose if they want AI crawlers to access content. </p><p>Meanwhile, the company's "pay-per-crawl" feature, which is currently in private preview for select customers, will allow publishers to set prices that bots are forced to pay before scraping content. </p><p>The move will also see <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>companies required to “clearly state their purpose” and disclose whether crawlers are used for training, inference, or search purposes. </p><p>This, Cloudflare said, will “help website owners decide which crawlers to allow”. </p><p>“If the internet is going to survive the age of AI, we need to give publishers the control they deserve and build a new economic model that works for everyone - creators, consumers, tomorrow’s AI founders, and the future of the web itself,” said <a href="https://www.itpro.com/business/careers-and-training/cloudflare-employees-viral-dismissal-video-offers-a-stark-glimpse-into-the-human-cost-of-layoffs">Matthew Prince</a>, co-founder and CEO of Cloudflare.</p><p>“Original content is what makes the Internet one of the greatest inventions in the last century, and it's essential that creators continue making it.”</p><p>Prince noted that AI crawlers have been “scraping content without limits” and the company aims to “put the power back in the hands of creators while still helping AI companies innovate.”</p><p>“This is about safeguarding the future of a free and vibrant Internet with a new model that works for everyone,” he added. </p><h2 id="how-cloudflare-plans-to-tackle-ai-crawlers">How Cloudflare plans to tackle AI crawlers</h2><p>Cloudflare has made previous moves to tackle the issue of AI crawlers, having introduced the option to block AI crawlers in September 2024. The company said more than one million customers have chosen this option since launch. </p><p>This latest attempt is “taking the next step” to enforce a permission-based model, the company noted, with AI companies now required to obtain "explicit permission” from a website before scraping content. </p><p>Every new domain will now be asked if they want to allow AI crawlers upon sign-up, the company added. </p><p>“This significant shift means that every new domain starts with the default of control and eliminates the need for webpage owners to manually configure their settings to opt out,” Cloudflare said in a statement. </p><p>“Customers can easily check their settings and enable crawling at any time if they want their content to be freely accessed.”</p><h2 id="publishers-have-welcomed-the-move">Publishers have welcomed the move</h2><p>The move by Cloudflare comes amidst long-running disputes between media organizations and AI companies over the use of crawlers to scrape data from the web for training purposes. </p><p>A host of <a href="https://www.itpro.com/technology/artificial-intelligence/more-authors-join-chatgpt-training-data-copyright-lawsuit"><u>high-profile lawsuits</u></a> have been filed against major industry providers, including OpenAI, contesting the practice. </p><p>An array of publishers have welcomed the move, including Conde Nast, The Atlantic, the Associated Press, and ADWEEK.</p><p>Roger Lynch, CEO of Condé Nast, described the new approach as a “game-changer for publishers” that will “set a new standard for how content is respected online”. </p><p>“When AI companies can no longer take anything, they want for free, it opens the door to sustainable innovation built on permission and partnership,” Lynch said. </p><p>“This is a critical step toward creating a fair value exchange on the Internet that protects creators, supports quality journalism and holds AI companies accountable.”</p><p>Steve Huffman, co-founder and CEO of Reddit, echoed Lynch’s comments. The social media platform <a href="https://www.theguardian.com/technology/2025/jun/04/reddit-lawsuit-ai-startup-anthropic-data">recently filed a lawsuit against AI giant Anthropic</a>, claiming the company has illegally scraped user comments to train its Claude AI mode. </p><p>“AI companies, search engines, researchers, and anyone else crawling sites have to be who they say they are. And any platform on the web should have a say in who is taking their content for what,” Huffman, said. </p><p>“The whole ecosystem of creators, platforms, web users and crawlers will be better when crawling is more transparent and controlled, and Cloudflare’s efforts are a step in the right direction for everyone.”</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/technology/artificial-intelligence/government-consults-on-controversial-ai-training-rules">Government consults on controversial AI training rules</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/openai-woos-uk-government-amid-consultation-on-ai-training-and-copyright">OpenAI woos UK government amid consultation on AI training and copyright</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/content-creators-wary-of-uks-ai-copyright-consultation">Content creators wary of UK's AI copyright consultation</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/technology/artificial-intelligence/cloudflare-says-ai-companies-have-been-scraping-content-without-limits-now-its-letting-website-owners-block-crawlers-by-default</link>
                                                                            <description>
                            <![CDATA[ Cloudflare CEO Matthew Prince said AI companies have been "scraping content without limits" - now the company is cracking down. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">2gYLysp6r8Jkw5ErLB2cuK</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/H5ZaXEc5rxyKDkKAhYUdt8-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 01 Jul 2025 13:31:44 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:53 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Artificial Intelligence]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                <author><![CDATA[ ross.kelly@futurenet.com (Ross Kelly) ]]></author>                    <dc:creator><![CDATA[ Ross Kelly ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Y5vrV2V98Np6jHAGmAtCd3-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Ross Kelly is ITPro&#039;s News &amp;amp; Analysis Editor, with a keen interest in cyber security, business leadership and emerging technologies.&lt;/p&gt;
&lt;p&gt;He graduated from Edinburgh Napier University in 2016 with a BA (Hons) in Journalism, and joined ITPro in 2022 after four years working in technology conference research.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In his spare time, Ross enjoys cycling, walking and is an avid reader of history and non-fiction.&lt;/p&gt;
&lt;p&gt;You can contact Ross at ross.kelly@futurenet.com or on &lt;a href=&quot;https://twitter.com/rosswritesetc&quot;&gt;Twitter&lt;/a&gt; and &lt;a href=&quot;https://www.linkedin.com/in/ross-kelly-18a54411a/&quot;&gt;LinkedIn&lt;/a&gt;.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/H5ZaXEc5rxyKDkKAhYUdt8-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Cloudflare co-founder and CEO, Matthew Prince, pictured during the Fortune Brainstorm AI conference in San Francisco, California, US, on Monday, Dec. 11, 2023]]></media:description>                                                            <media:text><![CDATA[Cloudflare co-founder and CEO, Matthew Prince, pictured during the Fortune Brainstorm AI conference in San Francisco, California, US, on Monday, Dec. 11, 2023]]></media:text>
                                <media:title type="plain"><![CDATA[Cloudflare co-founder and CEO, Matthew Prince, pictured during the Fortune Brainstorm AI conference in San Francisco, California, US, on Monday, Dec. 11, 2023]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/H5ZaXEc5rxyKDkKAhYUdt8-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p><a href="https://www.itpro.com/cloud/32096/everything-you-need-to-know-about-cloudflare">Cloudflare </a>has announced new capabilities aimed at blocking <a href="https://www.itpro.com/technology/artificial-intelligence/openai-quietly-unveils-gptbot-dedicated-web-crawler">AI crawlers</a> from accessing content without permission or compensation. </p><p>Available by default from today (1st July), the web infrastructure firm will allow website owners to choose if they want AI crawlers to access content. </p><p>Meanwhile, the company's "pay-per-crawl" feature, which is currently in private preview for select customers, will allow publishers to set prices that bots are forced to pay before scraping content. </p><p>The move will also see <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>companies required to “clearly state their purpose” and disclose whether crawlers are used for training, inference, or search purposes. </p><p>This, Cloudflare said, will “help website owners decide which crawlers to allow”. </p><p>“If the internet is going to survive the age of AI, we need to give publishers the control they deserve and build a new economic model that works for everyone - creators, consumers, tomorrow’s AI founders, and the future of the web itself,” said <a href="https://www.itpro.com/business/careers-and-training/cloudflare-employees-viral-dismissal-video-offers-a-stark-glimpse-into-the-human-cost-of-layoffs">Matthew Prince</a>, co-founder and CEO of Cloudflare.</p><p>“Original content is what makes the Internet one of the greatest inventions in the last century, and it's essential that creators continue making it.”</p><p>Prince noted that AI crawlers have been “scraping content without limits” and the company aims to “put the power back in the hands of creators while still helping AI companies innovate.”</p><p>“This is about safeguarding the future of a free and vibrant Internet with a new model that works for everyone,” he added. </p><h2 id="how-cloudflare-plans-to-tackle-ai-crawlers">How Cloudflare plans to tackle AI crawlers</h2><p>Cloudflare has made previous moves to tackle the issue of AI crawlers, having introduced the option to block AI crawlers in September 2024. The company said more than one million customers have chosen this option since launch. </p><p>This latest attempt is “taking the next step” to enforce a permission-based model, the company noted, with AI companies now required to obtain "explicit permission” from a website before scraping content. </p><p>Every new domain will now be asked if they want to allow AI crawlers upon sign-up, the company added. </p><p>“This significant shift means that every new domain starts with the default of control and eliminates the need for webpage owners to manually configure their settings to opt out,” Cloudflare said in a statement. </p><p>“Customers can easily check their settings and enable crawling at any time if they want their content to be freely accessed.”</p><h2 id="publishers-have-welcomed-the-move">Publishers have welcomed the move</h2><p>The move by Cloudflare comes amidst long-running disputes between media organizations and AI companies over the use of crawlers to scrape data from the web for training purposes. </p><p>A host of <a href="https://www.itpro.com/technology/artificial-intelligence/more-authors-join-chatgpt-training-data-copyright-lawsuit"><u>high-profile lawsuits</u></a> have been filed against major industry providers, including OpenAI, contesting the practice. </p><p>An array of publishers have welcomed the move, including Conde Nast, The Atlantic, the Associated Press, and ADWEEK.</p><p>Roger Lynch, CEO of Condé Nast, described the new approach as a “game-changer for publishers” that will “set a new standard for how content is respected online”. </p><p>“When AI companies can no longer take anything, they want for free, it opens the door to sustainable innovation built on permission and partnership,” Lynch said. </p><p>“This is a critical step toward creating a fair value exchange on the Internet that protects creators, supports quality journalism and holds AI companies accountable.”</p><p>Steve Huffman, co-founder and CEO of Reddit, echoed Lynch’s comments. The social media platform <a href="https://www.theguardian.com/technology/2025/jun/04/reddit-lawsuit-ai-startup-anthropic-data">recently filed a lawsuit against AI giant Anthropic</a>, claiming the company has illegally scraped user comments to train its Claude AI mode. </p><p>“AI companies, search engines, researchers, and anyone else crawling sites have to be who they say they are. And any platform on the web should have a say in who is taking their content for what,” Huffman, said. </p><p>“The whole ecosystem of creators, platforms, web users and crawlers will be better when crawling is more transparent and controlled, and Cloudflare’s efforts are a step in the right direction for everyone.”</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/technology/artificial-intelligence/government-consults-on-controversial-ai-training-rules">Government consults on controversial AI training rules</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/openai-woos-uk-government-amid-consultation-on-ai-training-and-copyright">OpenAI woos UK government amid consultation on AI training and copyright</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/content-creators-wary-of-uks-ai-copyright-consultation">Content creators wary of UK's AI copyright consultation</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Want to build more secure software? Follow these key memory safe language tips from CISA ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Are you still patching buffer overflows? It's time to switch to a memory safe language (MSL) — and security agencies have released a report with plenty of advice to help make the switch. </p><p>Memory safety vulnerabilities are flaws caused by software incorrectly using memory — such as buffer overflows, use-after-free allocations, and other memory bugs — and they've long been a weakness in software, despite <a href="https://www.itpro.com/software/want-developers-to-build-secure-software-you-need-to-ditch-these-two-programming-languages"><u>new languages</u></a> such as Rust, <a href="https://www.itpro.com/business-strategy/careers-training/356640/how-to-become-a-python-software-developer">Python</a> and Java designed to avoid such issues. </p><p>The massive <a href="https://www.itpro.com/security/22101/heartbleed-bug-everything-you-need-to-know"><u>Heartbleed</u></a> attack back in 2014 was pinned on such issues, as was the BadAlloc hack in 2021. </p><p>Because of that, the US National Security Agency (NSA) and <a href="https://www.itpro.com/security/what-is-cisa">Cybersecurity and Infrastructure Security Agency (CISA)</a> pulled together a <a href="https://www.cisa.gov/resources-tools/resources/memory-safe-languages-reducing-vulnerabilities-modern-software-development" target="_blank"><u>report</u></a> on the best way to deal with such flaws — calling for developers to switch to MSLs where possible. </p><p>"Achieving better memory safety demands language-level protections, library support, robust tooling, and developer training," the report noted. </p><p>"While decades of experience with non-MSLs have shown that secure coding standards and analysis tools can mitigate many risks, they cannot fully eliminate memory safety vulnerabilities inherent to these languages as effectively as the safeguards used in MSL."</p><p>Emilio Pinna, director at SecureFlag, has welcomed the publication of the guidance, but noted it’s been a long time coming. Moreover, enterprise willingness to make the shift hasn’t exactly helped the situation.</p><p>"It’s 2025, and yet, we’re still patching buffer overflows like it’s 1995. The newly released CISA and NSA report on Memory Safe Languages is a much-needed wake-up call (again) for the industry,” he said. “After decades of shipping software riddled with memory safety bugs, it’s clear: the problem isn’t new, we’re just stubborn."</p><p>According to the report, two-thirds of CVEs for iOS 12 were caused by memory safety issues, and the researchers pointed to Google data that showed three-quarters of in-the-wild exploits used memory safety vulnerabilities. </p><p>Meanwhile, Microsoft data showed that 70% of CVEs related to its own solutions were attributed to memory safety in 2016, though that's since fallen to 50%. </p><p>"That’s not a bug, that’s a systemic design flaw in how we write code," added Pinna. "And yes, that means the C++ codebase your team inherited might just be a beautifully commented landmine. Young developers today are stuck fighting the vulnerabilities their coding ancestors thought they could 'just be careful' around."</p><h2 id="time-to-make-the-switch-to-memory-safe-languages">Time to make the switch to memory safe languages</h2><p>CISA advice has long been advising to shift to MSLs, which are any language designed with security by design mechanisms that prevent bugs such as memory management and bounds checking. </p><p>However, the agencies admit in the report that it's not always possible to do so, such as with legacy systems and working with existing codebases and third-party libraries. </p><p>"Reducing <a href="https://www.itpro.com/software/inside-googles-promising-and-pragmatic-approach-to-fixing-software-developments-memory-safety-problem">memory safety vulnerabilities</a> requires understanding when MSLs are appropriate, knowing how to adopt them effectively, and recognizing where non-MSLs remain practical necessities," the report adds. </p><p>Pinna added that rewriting systems wouldn't be cheap or easy, but said there are costs associated with fighting zero-day flaws, too.</p><p>"The push toward Memory Safe Languages (MSLs) like Rust, <a href="https://www.itpro.com/software/development/fast-modern-safe-and-a-joy-to-write-why-apple-is-banging-the-drum-on-swift-as-the-successor-to-c">Swift</a>, and modern iterations of Go or even Java is a necessity now more than ever. You don’t get brownie points for reinventing the wheel with manual memory management anymore," he said. </p><p>"As the CISA/NSA guidance makes clear, we’re at a crossroads: keep clinging to legacy languages with known safety issues, or modernize for the future."</p><h2 id="what-can-be-done">What can be done? </h2><p>So what can be done on this front? First and foremost, companies should prioritize the adoption of MSLs in new projects where possible and consider incremental adoption for existing code</p><p>Similarly, writing new components and features in MSLs for high risk areas, such as networking facing services, is also advised. One key to making the shift is ensuring robust APIs to allow communication between MSL and non-MSL components of systems. </p><p>This, researchers said, will ensure security while maintaining interoperability. </p><p>When developers must use languages that aren't deemed memory safe by default, they should ensure they understand the risks, with the report calling for better training on memory safe flaws and "secure coding" mitigations in training courses and university programs. </p><p>Thomas Richards, infrastructure security practice director at Black Duck, echoed Pinna’s comments, adding that the shift away from unsafe programming languages is an “excellent step toward reducing certain classes of software vulnerabilities”. </p><p>This won’t be a silver bullet to help prevent vulnerabilities in the future, however. </p><p>"This should not be taken as assuming all code written in MSLs is fully secure; they still have insecure coding practices that could create other vulnerabilities,” he warned. </p><p>“Developers should always be aware of secure coding guidelines for the specific language they are using to reduce the risk of vulnerabilities in their code and ensure uncompromised trust in their software."</p><p>Beyond that, the report calls for companies to actively include MSL expertise in job requirements. "This action will signal demand for these skills that is felt not only throughout the job market, but also in studies and in future funding of academic and certification programs," the report noted. </p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/most-open-source-projects-fail-to-use-memory-safe-programming-languages-and-cisa-says-that-needs-to-change">Most open source projects fail to use memory-safe programming languages</a></li><li><a href="https://www.itpro.com/software/us-lawmakers-are-pushing-for-a-shift-to-memory-safe-programming-languages-but-will-it-improve-software-security">US lawmakers are pushing for a shift to memory safe programming languages, but will it improve software security?</a></li><li><a href="https://www.itpro.com/development/programming-languages/369499/move-away-from-memory-unsafe-languages-c">Move away from memory-unsafe languages like C and C++, NSA urges</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/memory-safe-language-tips-cisa-development</link>
                                                                            <description>
                            <![CDATA[ CISA has been pushing for a shift to memory safe languages - now it's published guidance on how developers can make the switch. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">5DyVprqXDY2yE92P3oWGe3</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/zKyttTsgksBLRYnZ42xrWS-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 26 Jun 2025 11:48:52 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:21 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Workplace Technology]]></category>
                                                                                                                    <dc:creator><![CDATA[ Nicole Kobie ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/8Y8JDDTQ7XDEk49FoAFP2S-320-70.png ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Nicole Kobie first started writing for ITPro in 2007. As a freelance journalist covering technology and business, Nicole&#039;s work includes  bylines in New Scientist, Wired, PC Pro and many more. &lt;/p&gt;&lt;p&gt;Nicole the author of a book about the history of technology, The Long History of the Future.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/zKyttTsgksBLRYnZ42xrWS-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Male and female software developers in dimly lit room discussing memory safe languages while pointing at a vertically aligned desktop monitor.]]></media:description>                                                            <media:text><![CDATA[Male and female software developers in dimly lit room discussing memory safe languages while pointing at a vertically aligned desktop monitor.]]></media:text>
                                <media:title type="plain"><![CDATA[Male and female software developers in dimly lit room discussing memory safe languages while pointing at a vertically aligned desktop monitor.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/zKyttTsgksBLRYnZ42xrWS-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Are you still patching buffer overflows? It's time to switch to a memory safe language (MSL) — and security agencies have released a report with plenty of advice to help make the switch. </p><p>Memory safety vulnerabilities are flaws caused by software incorrectly using memory — such as buffer overflows, use-after-free allocations, and other memory bugs — and they've long been a weakness in software, despite <a href="https://www.itpro.com/software/want-developers-to-build-secure-software-you-need-to-ditch-these-two-programming-languages"><u>new languages</u></a> such as Rust, <a href="https://www.itpro.com/business-strategy/careers-training/356640/how-to-become-a-python-software-developer">Python</a> and Java designed to avoid such issues. </p><p>The massive <a href="https://www.itpro.com/security/22101/heartbleed-bug-everything-you-need-to-know"><u>Heartbleed</u></a> attack back in 2014 was pinned on such issues, as was the BadAlloc hack in 2021. </p><p>Because of that, the US National Security Agency (NSA) and <a href="https://www.itpro.com/security/what-is-cisa">Cybersecurity and Infrastructure Security Agency (CISA)</a> pulled together a <a href="https://www.cisa.gov/resources-tools/resources/memory-safe-languages-reducing-vulnerabilities-modern-software-development" target="_blank"><u>report</u></a> on the best way to deal with such flaws — calling for developers to switch to MSLs where possible. </p><p>"Achieving better memory safety demands language-level protections, library support, robust tooling, and developer training," the report noted. </p><p>"While decades of experience with non-MSLs have shown that secure coding standards and analysis tools can mitigate many risks, they cannot fully eliminate memory safety vulnerabilities inherent to these languages as effectively as the safeguards used in MSL."</p><p>Emilio Pinna, director at SecureFlag, has welcomed the publication of the guidance, but noted it’s been a long time coming. Moreover, enterprise willingness to make the shift hasn’t exactly helped the situation.</p><p>"It’s 2025, and yet, we’re still patching buffer overflows like it’s 1995. The newly released CISA and NSA report on Memory Safe Languages is a much-needed wake-up call (again) for the industry,” he said. “After decades of shipping software riddled with memory safety bugs, it’s clear: the problem isn’t new, we’re just stubborn."</p><p>According to the report, two-thirds of CVEs for iOS 12 were caused by memory safety issues, and the researchers pointed to Google data that showed three-quarters of in-the-wild exploits used memory safety vulnerabilities. </p><p>Meanwhile, Microsoft data showed that 70% of CVEs related to its own solutions were attributed to memory safety in 2016, though that's since fallen to 50%. </p><p>"That’s not a bug, that’s a systemic design flaw in how we write code," added Pinna. "And yes, that means the C++ codebase your team inherited might just be a beautifully commented landmine. Young developers today are stuck fighting the vulnerabilities their coding ancestors thought they could 'just be careful' around."</p><h2 id="time-to-make-the-switch-to-memory-safe-languages">Time to make the switch to memory safe languages</h2><p>CISA advice has long been advising to shift to MSLs, which are any language designed with security by design mechanisms that prevent bugs such as memory management and bounds checking. </p><p>However, the agencies admit in the report that it's not always possible to do so, such as with legacy systems and working with existing codebases and third-party libraries. </p><p>"Reducing <a href="https://www.itpro.com/software/inside-googles-promising-and-pragmatic-approach-to-fixing-software-developments-memory-safety-problem">memory safety vulnerabilities</a> requires understanding when MSLs are appropriate, knowing how to adopt them effectively, and recognizing where non-MSLs remain practical necessities," the report adds. </p><p>Pinna added that rewriting systems wouldn't be cheap or easy, but said there are costs associated with fighting zero-day flaws, too.</p><p>"The push toward Memory Safe Languages (MSLs) like Rust, <a href="https://www.itpro.com/software/development/fast-modern-safe-and-a-joy-to-write-why-apple-is-banging-the-drum-on-swift-as-the-successor-to-c">Swift</a>, and modern iterations of Go or even Java is a necessity now more than ever. You don’t get brownie points for reinventing the wheel with manual memory management anymore," he said. </p><p>"As the CISA/NSA guidance makes clear, we’re at a crossroads: keep clinging to legacy languages with known safety issues, or modernize for the future."</p><h2 id="what-can-be-done">What can be done? </h2><p>So what can be done on this front? First and foremost, companies should prioritize the adoption of MSLs in new projects where possible and consider incremental adoption for existing code</p><p>Similarly, writing new components and features in MSLs for high risk areas, such as networking facing services, is also advised. One key to making the shift is ensuring robust APIs to allow communication between MSL and non-MSL components of systems. </p><p>This, researchers said, will ensure security while maintaining interoperability. </p><p>When developers must use languages that aren't deemed memory safe by default, they should ensure they understand the risks, with the report calling for better training on memory safe flaws and "secure coding" mitigations in training courses and university programs. </p><p>Thomas Richards, infrastructure security practice director at Black Duck, echoed Pinna’s comments, adding that the shift away from unsafe programming languages is an “excellent step toward reducing certain classes of software vulnerabilities”. </p><p>This won’t be a silver bullet to help prevent vulnerabilities in the future, however. </p><p>"This should not be taken as assuming all code written in MSLs is fully secure; they still have insecure coding practices that could create other vulnerabilities,” he warned. </p><p>“Developers should always be aware of secure coding guidelines for the specific language they are using to reduce the risk of vulnerabilities in their code and ensure uncompromised trust in their software."</p><p>Beyond that, the report calls for companies to actively include MSL expertise in job requirements. "This action will signal demand for these skills that is felt not only throughout the job market, but also in studies and in future funding of academic and certification programs," the report noted. </p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/most-open-source-projects-fail-to-use-memory-safe-programming-languages-and-cisa-says-that-needs-to-change">Most open source projects fail to use memory-safe programming languages</a></li><li><a href="https://www.itpro.com/software/us-lawmakers-are-pushing-for-a-shift-to-memory-safe-programming-languages-but-will-it-improve-software-security">US lawmakers are pushing for a shift to memory safe programming languages, but will it improve software security?</a></li><li><a href="https://www.itpro.com/development/programming-languages/369499/move-away-from-memory-unsafe-languages-c">Move away from memory-unsafe languages like C and C++, NSA urges</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Application security risk: How leaders can protect their businesses ]]></title>
                                                                                                <dc:content><![CDATA[ <p>The increasingly complex nature of software combined with pressure to develop and rollout new features quickly makes application security a growing challenge. </p><p>Application development infrastructure is full of significant security risks, according to <a href="https://www.itpro.com/security/developers-cant-get-a-handle-on-application-security-risks"><u>research</u></a> by Legit Security. The issue is widespread – the researchers found high or <a href="https://www.itpro.com/security/these-three-critical-sectors-are-riddled-with-high-risk-vulnerabilities"><u>critical risks</u></a> in the developer environments of every company it examined.</p><p>And there isn’t a simple fix. Legit said application security is no longer simply about spotting flaws in source code, because the attack surface for applications has grown and diversified.</p><p>So what can businesses do to assess their own application security risks and mitigate them effectively?</p><h2 id="tying-application-security-risk-to-software-complexity">Tying application security risk to software complexity</h2><p>Application security is set against an increasingly risky backdrop. Software development has become complex with the adoption of <a href="https://www.itpro.com/strategy/28878/what-are-microservices"><u>microservices</u></a>, <a href="https://www.itpro.com/cloud/31389/what-is-edge-computing"><u>edge computing</u></a> and distributed systems across hybrid clouds, says Kelvin Lim, senior director, head of security engineering at Black Duck. </p><p>This “significantly expands the attack surface”, making it more challenging to secure every component, he says.</p><p>Adding to this, businesses often put pressure on developers to deliver new features and functionality, which can lead to “a prioritization of speed over security”, says Bharat Mistry, field CTO at Trend Micro. “This focus on rapid deployment can result in inadequate testing and oversight of newly-introduced code,” he says.</p><p>At the same time, without the right controls in place, applications can be exposed to SQL and prompt injection attacks, or “a host of authentication and access control failures that leave sensitive data easily accessible to cybercriminals”, says Ann Maya, EMEA CTO at Boomi. She cites the example of last year’s <a href="https://www.itpro.com/security/cyber-attacks/15-million-trello-users-have-been-exposed-in-a-data-breach-heres-what-you-need-to-know"><u>Trello breach</u></a>. “This saw a threat actor exploit an <a href="http://google.com/search?q=site%3Aitpro.com+API+endpoint&amp;rlz=1C5GCEM_enGB1166GB1166&amp;oq=site%3Aitpro.com+API+endpoint&amp;gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIGCAEQRRg60gEIMTQ3MGowajeoAgCwAgA&amp;sourceid=chrome&amp;ie=UTF-8"><u>open API endpoint</u></a> and gain unauthorized access to information on 15 million registered users.”</p><p>Application security problems can lead to supply chain incidents, which are now “a significant source of breaches”, says Jeff Watkins, chief technology officer at CreateFuture. “The problem with application security issues is they are often incredibly insidious – especially in the case of a <a href="https://www.itpro.com/security/supply-chain-attacks-are-still-plaguing-enterprises-heres-why"><u>supply chain attack</u></a> – and can require extensive rollout activities to remediate.”</p><p>Mistry cites the example of the <a href="https://www.itpro.com/security/these-tech-firms-downplayed-the-impact-of-the-solarwinds-hack-now-theyve-been-fined-by-the-sec"><u>SolarWinds attack</u></a>, which saw adversaries exploit weaknesses in the application to gain unauthorized access to sensitive information. “This highlighted how vulnerabilities in software supply chains can trigger massive data breaches affecting thousands of organizations”, he says.</p><p>Another infamous case is the <a href="http://google.com/search?q=site%3Aitpro.com+log4j&amp;rlz=1C5GCEM_enGB1166GB1166&amp;oq=site%3Aitpro.com+log4j&amp;gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIGCAEQRRg7MgYIAhBFGDrSAQgxOTkyajBqN6gCALACAA&amp;sourceid=chrome&amp;ie=UTF-8"><u>Log4j</u></a> vulnerability, or Log4Shell, a critical security flaw discovered in December 2021 within the widely-used <a href="https://www.itpro.com/software/development/its-far-from-showing-its-age-java-mightve-just-turned-30-but-its-still-going-strong-and-here-to-stay"><u>Java</u></a> logging library. “This flaw allowed attackers to execute remote code by taking advantage of the library’s logging function,” says Mistry. “The discovery of Log4j sent shockwaves through the cybersecurity community, leading to widespread panic as organizations scrambled to assess their exposure and implement patches.”</p><h2 id="ai-and-application-security-risk">AI and application security risk</h2><p>An additional factor adding complexity to application security is the use of AI for writing software, as well as the technology’s inclusion in live systems. According to Legit’s application security report, 46% of firms are using AI models in source code in a risky way. In fact, many security teams are unaware where AI is in use within their organizations, a phenomenon known as <a href="https://www.itpro.com/software/development/shadow-ai-is-creeping-its-way-into-software-development-more-than-half-of-developers-admit-to-using-unauthorized-ai-tools-at-work-and-its-putting-companies-at-risk"><u>shadow AI</u></a>.</p><p>The use of AI has resulted in new categories of risk to consider, says Watkins. “Existing advice to protect against <a href="https://www.itpro.com/technology/artificial-intelligence/ai-threats-the-importance-of-a-concrete-strategy-in-fighting-novel-attacks"><u>attacks on AI systems</u></a> is often inaccurate or absent, and some kinds of AI interface are technically impossible to secure, due to their non-deterministic nature.”</p><p>Yet AI can’t be ignored, given its growing role in software coding. <a href="https://www.itpro.com/technology/artificial-intelligence-ai/369959/what-is-generative-ai"><u>Generative AI</u></a> is accelerating code creation and by 2028, <a href="https://www.gartner.com/en/newsroom/press-releases/2024-04-11-gartner-says-75-percent-of-enterprise-software-engineers-will-use-ai-code-assistants-by-2028"><u>Gartner predicts</u></a> 75% of enterprise software engineers will use AI code assistants. </p><p>This surge in AI-generated code could result in even more pressure on security teams, since it will require them to “scrutinize even greater volumes of potentially vulnerable software”, John Smith, EMEA CTO at Veracode warns. </p><p>It’s not all bad, though, as AI could also be used as a countermeasure, providing better application security tooling to organizations. It is especially useful when monitoring generative interactions that would be difficult to secure using traditional tooling, Watkins says.</p><iframe allow="" height="200px" width="100%" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/2fa90d58-bc3c-4ca0-8bcb-e4bb4fcc1297/" src="https://player.captivate.fm/episode/2fa90d58-bc3c-4ca0-8bcb-e4bb4fcc1297/"></iframe><h2 id="application-security-risk-strategy">Application security risk strategy</h2><p>It might seem complex, but it’s possible to manage the risks surrounding application security by combining a few tools, policies and techniques.</p><p>Firstly, secure your development environments, says Watkins. “Be sure that a single attacker can’t create a huge blast radius in your organization by applying the <a href="https://en.wikipedia.org/wiki/Principle_of_least_privilege"><u>least privilege principle</u></a>.”</p><p>To boost application security within the business, embracing a “shift-left security approach” in the development process is “essential”, says Mistry. “This entails incorporating security practices early in the software development lifecycle through developer training in secure coding and integrating security tools into the <a href="https://www.itpro.com/business/digital-transformation/cicd-comes-into-focus-as-enterprises-ramp-up-application-modernization-efforts"><u>CI/CD</u></a> pipeline.”</p><p>Additionally, implementing supply chain governance via a <a href="https://www.itpro.com/security/software-inventories-may-give-hackers-clearer-route-for-attacks"><u>software bill of materials (SBOM)</u></a> helps track components and vulnerabilities, ensuring transparency and security in third-party and open-source components, Mistry adds.</p><p>Watkins also advises a “<a href="https://www.itpro.com/development/devops/354215/what-is-devsecops-and-why-is-it-important"><u>DevSecOps</u></a>” approach and continuous security integration, using software composition analysis, static application security testing and dynamic application security testing tooling alongside strict <a href="https://www.itpro.com/software/saas-dependency-is-causing-serious-problems-for-tech-leaders"><u>dependency management</u></a> and container scanning. “This will ensure your code and the code in your supply chain is secure.”</p><p>Watkins highlights the importance of, “getting serious” on secrets management. “Even if your code is secrets free, Legit’s report noted that 36% of those surveyed had secrets posted elsewhere, such as logs, tickets, and documents.”</p><p>Meanwhile, organizations can consider a centralized <a href="https://www.gov.uk/guidance/defining-an-api-management-strategy"><u>API management strategy</u></a> that considers all their integration, automation, data and security requirements, says Maya.</p><p>There are also specific measures that help to mitigate API security risks, Maya says. “First, a system must be in place to detect all APIs attached to a gateway and identify <a href="https://www.itpro.com/development/web-development/368248/what-is-metadata"><u>metadata</u></a>, such as usage, to root out ‘zombie APIs’ or 'shadow APIs' flying under IT’s radar. Then, organizations must ensure they can check quality and security as APIs are introduced into an environment.”</p><p>Other best practices include strong API authentication and authorization controls, validating and sanitizing input data, and using security logging and monitoring to secure the data flow, says Maya. “Regular testing, <a href="https://www.itpro.com/security/patch-management-why-firms-ignore-vulnerabilities-at-their-own-risk">patch management</a> and software updates for APIs are also essential to maintain systems’ overall security and mitigate application security risk.”</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/application-security-risk-how-leaders-can-protect-their-businesses</link>
                                                                            <description>
                            <![CDATA[ Application security risk is higher than ever, as new services and expanding attack surfaces put pressure on cyber leaders ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">YVTm3iK5BbMSiFyQA8Ud9</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/Wwr4YasQDqgeQ9Rw5UHjKL-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 13 Jun 2025 10:06:13 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:20 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Kate O&#039;Flaherty ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/LUULv6n7VJ3BHPnaoLHHdg-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/Wwr4YasQDqgeQ9Rw5UHjKL-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[An abstract CGI visualization of a shield shape on a semi-transparent, multicolored surface resembling a computer processor, to represent application security.]]></media:description>                                                            <media:text><![CDATA[An abstract CGI visualization of a shield shape on a semi-transparent, multicolored surface resembling a computer processor, to represent application security.]]></media:text>
                                <media:title type="plain"><![CDATA[An abstract CGI visualization of a shield shape on a semi-transparent, multicolored surface resembling a computer processor, to represent application security.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/Wwr4YasQDqgeQ9Rw5UHjKL-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The increasingly complex nature of software combined with pressure to develop and rollout new features quickly makes application security a growing challenge. </p><p>Application development infrastructure is full of significant security risks, according to <a href="https://www.itpro.com/security/developers-cant-get-a-handle-on-application-security-risks"><u>research</u></a> by Legit Security. The issue is widespread – the researchers found high or <a href="https://www.itpro.com/security/these-three-critical-sectors-are-riddled-with-high-risk-vulnerabilities"><u>critical risks</u></a> in the developer environments of every company it examined.</p><p>And there isn’t a simple fix. Legit said application security is no longer simply about spotting flaws in source code, because the attack surface for applications has grown and diversified.</p><p>So what can businesses do to assess their own application security risks and mitigate them effectively?</p><h2 id="tying-application-security-risk-to-software-complexity">Tying application security risk to software complexity</h2><p>Application security is set against an increasingly risky backdrop. Software development has become complex with the adoption of <a href="https://www.itpro.com/strategy/28878/what-are-microservices"><u>microservices</u></a>, <a href="https://www.itpro.com/cloud/31389/what-is-edge-computing"><u>edge computing</u></a> and distributed systems across hybrid clouds, says Kelvin Lim, senior director, head of security engineering at Black Duck. </p><p>This “significantly expands the attack surface”, making it more challenging to secure every component, he says.</p><p>Adding to this, businesses often put pressure on developers to deliver new features and functionality, which can lead to “a prioritization of speed over security”, says Bharat Mistry, field CTO at Trend Micro. “This focus on rapid deployment can result in inadequate testing and oversight of newly-introduced code,” he says.</p><p>At the same time, without the right controls in place, applications can be exposed to SQL and prompt injection attacks, or “a host of authentication and access control failures that leave sensitive data easily accessible to cybercriminals”, says Ann Maya, EMEA CTO at Boomi. She cites the example of last year’s <a href="https://www.itpro.com/security/cyber-attacks/15-million-trello-users-have-been-exposed-in-a-data-breach-heres-what-you-need-to-know"><u>Trello breach</u></a>. “This saw a threat actor exploit an <a href="http://google.com/search?q=site%3Aitpro.com+API+endpoint&amp;rlz=1C5GCEM_enGB1166GB1166&amp;oq=site%3Aitpro.com+API+endpoint&amp;gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIGCAEQRRg60gEIMTQ3MGowajeoAgCwAgA&amp;sourceid=chrome&amp;ie=UTF-8"><u>open API endpoint</u></a> and gain unauthorized access to information on 15 million registered users.”</p><p>Application security problems can lead to supply chain incidents, which are now “a significant source of breaches”, says Jeff Watkins, chief technology officer at CreateFuture. “The problem with application security issues is they are often incredibly insidious – especially in the case of a <a href="https://www.itpro.com/security/supply-chain-attacks-are-still-plaguing-enterprises-heres-why"><u>supply chain attack</u></a> – and can require extensive rollout activities to remediate.”</p><p>Mistry cites the example of the <a href="https://www.itpro.com/security/these-tech-firms-downplayed-the-impact-of-the-solarwinds-hack-now-theyve-been-fined-by-the-sec"><u>SolarWinds attack</u></a>, which saw adversaries exploit weaknesses in the application to gain unauthorized access to sensitive information. “This highlighted how vulnerabilities in software supply chains can trigger massive data breaches affecting thousands of organizations”, he says.</p><p>Another infamous case is the <a href="http://google.com/search?q=site%3Aitpro.com+log4j&amp;rlz=1C5GCEM_enGB1166GB1166&amp;oq=site%3Aitpro.com+log4j&amp;gs_lcrp=EgZjaHJvbWUyBggAEEUYOTIGCAEQRRg7MgYIAhBFGDrSAQgxOTkyajBqN6gCALACAA&amp;sourceid=chrome&amp;ie=UTF-8"><u>Log4j</u></a> vulnerability, or Log4Shell, a critical security flaw discovered in December 2021 within the widely-used <a href="https://www.itpro.com/software/development/its-far-from-showing-its-age-java-mightve-just-turned-30-but-its-still-going-strong-and-here-to-stay"><u>Java</u></a> logging library. “This flaw allowed attackers to execute remote code by taking advantage of the library’s logging function,” says Mistry. “The discovery of Log4j sent shockwaves through the cybersecurity community, leading to widespread panic as organizations scrambled to assess their exposure and implement patches.”</p><h2 id="ai-and-application-security-risk">AI and application security risk</h2><p>An additional factor adding complexity to application security is the use of AI for writing software, as well as the technology’s inclusion in live systems. According to Legit’s application security report, 46% of firms are using AI models in source code in a risky way. In fact, many security teams are unaware where AI is in use within their organizations, a phenomenon known as <a href="https://www.itpro.com/software/development/shadow-ai-is-creeping-its-way-into-software-development-more-than-half-of-developers-admit-to-using-unauthorized-ai-tools-at-work-and-its-putting-companies-at-risk"><u>shadow AI</u></a>.</p><p>The use of AI has resulted in new categories of risk to consider, says Watkins. “Existing advice to protect against <a href="https://www.itpro.com/technology/artificial-intelligence/ai-threats-the-importance-of-a-concrete-strategy-in-fighting-novel-attacks"><u>attacks on AI systems</u></a> is often inaccurate or absent, and some kinds of AI interface are technically impossible to secure, due to their non-deterministic nature.”</p><p>Yet AI can’t be ignored, given its growing role in software coding. <a href="https://www.itpro.com/technology/artificial-intelligence-ai/369959/what-is-generative-ai"><u>Generative AI</u></a> is accelerating code creation and by 2028, <a href="https://www.gartner.com/en/newsroom/press-releases/2024-04-11-gartner-says-75-percent-of-enterprise-software-engineers-will-use-ai-code-assistants-by-2028"><u>Gartner predicts</u></a> 75% of enterprise software engineers will use AI code assistants. </p><p>This surge in AI-generated code could result in even more pressure on security teams, since it will require them to “scrutinize even greater volumes of potentially vulnerable software”, John Smith, EMEA CTO at Veracode warns. </p><p>It’s not all bad, though, as AI could also be used as a countermeasure, providing better application security tooling to organizations. It is especially useful when monitoring generative interactions that would be difficult to secure using traditional tooling, Watkins says.</p><iframe allow="" height="200px" width="100%" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/2fa90d58-bc3c-4ca0-8bcb-e4bb4fcc1297/" src="https://player.captivate.fm/episode/2fa90d58-bc3c-4ca0-8bcb-e4bb4fcc1297/"></iframe><h2 id="application-security-risk-strategy">Application security risk strategy</h2><p>It might seem complex, but it’s possible to manage the risks surrounding application security by combining a few tools, policies and techniques.</p><p>Firstly, secure your development environments, says Watkins. “Be sure that a single attacker can’t create a huge blast radius in your organization by applying the <a href="https://en.wikipedia.org/wiki/Principle_of_least_privilege"><u>least privilege principle</u></a>.”</p><p>To boost application security within the business, embracing a “shift-left security approach” in the development process is “essential”, says Mistry. “This entails incorporating security practices early in the software development lifecycle through developer training in secure coding and integrating security tools into the <a href="https://www.itpro.com/business/digital-transformation/cicd-comes-into-focus-as-enterprises-ramp-up-application-modernization-efforts"><u>CI/CD</u></a> pipeline.”</p><p>Additionally, implementing supply chain governance via a <a href="https://www.itpro.com/security/software-inventories-may-give-hackers-clearer-route-for-attacks"><u>software bill of materials (SBOM)</u></a> helps track components and vulnerabilities, ensuring transparency and security in third-party and open-source components, Mistry adds.</p><p>Watkins also advises a “<a href="https://www.itpro.com/development/devops/354215/what-is-devsecops-and-why-is-it-important"><u>DevSecOps</u></a>” approach and continuous security integration, using software composition analysis, static application security testing and dynamic application security testing tooling alongside strict <a href="https://www.itpro.com/software/saas-dependency-is-causing-serious-problems-for-tech-leaders"><u>dependency management</u></a> and container scanning. “This will ensure your code and the code in your supply chain is secure.”</p><p>Watkins highlights the importance of, “getting serious” on secrets management. “Even if your code is secrets free, Legit’s report noted that 36% of those surveyed had secrets posted elsewhere, such as logs, tickets, and documents.”</p><p>Meanwhile, organizations can consider a centralized <a href="https://www.gov.uk/guidance/defining-an-api-management-strategy"><u>API management strategy</u></a> that considers all their integration, automation, data and security requirements, says Maya.</p><p>There are also specific measures that help to mitigate API security risks, Maya says. “First, a system must be in place to detect all APIs attached to a gateway and identify <a href="https://www.itpro.com/development/web-development/368248/what-is-metadata"><u>metadata</u></a>, such as usage, to root out ‘zombie APIs’ or 'shadow APIs' flying under IT’s radar. Then, organizations must ensure they can check quality and security as APIs are introduced into an environment.”</p><p>Other best practices include strong API authentication and authorization controls, validating and sanitizing input data, and using security logging and monitoring to secure the data flow, says Maya. “Regular testing, <a href="https://www.itpro.com/security/patch-management-why-firms-ignore-vulnerabilities-at-their-own-risk">patch management</a> and software updates for APIs are also essential to maintain systems’ overall security and mitigate application security risk.”</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Shifting left might improve software security, but developers are becoming overwhelmed ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Nearly half of enterprises are trying to "shift left" in a bid to shore up software security, but developers are reporting significant issues with the strategy. </p><p>False positives, the faster pace of development thanks to AI, and challenges integrating tools are hampering progress.</p><p>That's according to<a href="https://www.pynt.io/resources-hub/guides-and-reports/shift-left-adoption-benchmark-report-2025"><u> research by AI security firm Pynt</u></a> that focused on the adoption of shift left  practices — referring to a strategy of spotting flaws and security issues earlier in the software development cycle when they're easier to fix.</p><p>The survey of 250 security professionals found 47% of organizations had implemented a shift left approach to software development, with a further 27% working to do so. </p><p>But a quarter of developers felt overwhelmed by the volume of vulnerabilities, and more than a third saw false positives as the main challenge to implementing a successful shift-left strategy, followed by integration issues and vulnerability overload. </p><p>The study raises serious questions over whether this approach to software development is actually reducing overall risks, or merely increasing complexity, according to Pynt chief executive Tzvika Shneider.</p><p>"Everyone talks about shifting left, but few are seeing the security gains they expected," said Shneider. "Most organizations have tools in place, but they still struggle with noise, process friction, and developer resistance."</p><p>"<a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>accelerates how software is developed and shipped, forcing security to keep pace, Shneider added.</p><p>The research also found that the vast majority of companies that had shifted left had turned to <a href="https://www.itpro.com/software/amazons-codewhisperer-updates-could-be-a-game-changer-for-shifting-left"><u>software tools to help the process</u></a>, but 31% said that integrating those tools within development workflows continued to be a major barrier. </p><p>The most popular tools are Static Application Security Testing (SAST), Software Composition Analysis (SCA) and Dynamic Application Security Testing (DAST), with each used by about a third of respondents. </p><h2 id="software-security-priorities-are-causing-friction">Software security priorities are causing friction</h2><p>Two-thirds of respondents said they prefer to fix bugs in app code rather than with rules in post-production, highlighting friction between developers and security teams. The former prioritize feature development and see security as a burden, while the latter wants to see flaws fixed rapidly.</p><p>"Shift right is easier since it doesn’t require extensive coordination between multiple teams, whereas Shift Left demands a collaborative effort across development, security, and testing teams,” the report noted.</p><p>"Shift Left was meant to improve security, but many organizations are finding that execution challenges are holding them back," added Shneider. "Security leaders must rethink their approach to reduce friction between security and development teams while maintaining effective risk management."</p><p>Pynt said that automation in security testing could help, and called for improved collaboration between security and development teams, including integrating security into testing phases. </p><p>Europeans are ahead adopting shift left practices, the survey found, with Germany and the UK both at 52%. Developer teams in the US, however, aren't quite up to scratch in this regard, researchers found, with just 42% of enterprises having adopted the approach.</p><p>The report follows earlier research that <a href="https://www.itpro.com/cloud/cloud-security/enterprise-ai-is-surging-but-is-security-keeping-up"><u>suggests enterprise security teams</u></a> are struggling to keep up with the adoption of AI tools. Similar research found showing the rise in AI coding tools may actually be slowing down development thanks to the <a href="https://www.itpro.com/software/development/devsecops-teams-are-ramping-up-the-use-of-ai-coding-tools-but-theyve-got-serious-concerns-ai-generated-code-is-causing-major-security-headaches-and-slowing-down-development-processes"><u>security headaches it causes</u></a>.  </p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/development/anthropic-claude-opus-4-software-development">Anthropic’s new AI model could be a game changer for developers</a></li><li><a href="https://www.itpro.com/software/development/developers-will-need-to-adapt-microsoft-ceo-satya-nadella-joins-googles-sundar-pichai-in-revealing-the-scale-of-ai-generated-code-at-the-tech-giants-and-its-a-stark-warning-for-software-developers">30% of Microsoft's code is now AI-generated, and that's bad news for devs</a></li><li><a href="https://www.itpro.com/software/development/its-far-from-showing-its-age-java-mightve-just-turned-30-but-its-still-going-strong-and-here-to-stay">Java might’ve just turned 30, but it’s still going strong and here to stay</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/software-security-shift-left-developer-overload</link>
                                                                            <description>
                            <![CDATA[ Developers are becoming overwhelmed amid the 'shift left' in development practices, new research shows. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">EUT7wUMzfHPvc2bN2ePQqR</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/7YH4hNrEoL7oEoygVyJuZi-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 29 May 2025 11:50:45 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:10 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                                    <dc:creator><![CDATA[ Nicole Kobie ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/8Y8JDDTQ7XDEk49FoAFP2S-320-70.png ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Nicole Kobie first started writing for ITPro in 2007. As a freelance journalist covering technology and business, Nicole&#039;s work includes  bylines in New Scientist, Wired, PC Pro and many more. &lt;/p&gt;&lt;p&gt;Nicole the author of a book about the history of technology, The Long History of the Future.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/7YH4hNrEoL7oEoygVyJuZi-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Software security concept image showing female developer working on a desktop computer with screen reflected in glasses.]]></media:description>                                                            <media:text><![CDATA[Software security concept image showing female developer working on a desktop computer with screen reflected in glasses.]]></media:text>
                                <media:title type="plain"><![CDATA[Software security concept image showing female developer working on a desktop computer with screen reflected in glasses.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/7YH4hNrEoL7oEoygVyJuZi-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Nearly half of enterprises are trying to "shift left" in a bid to shore up software security, but developers are reporting significant issues with the strategy. </p><p>False positives, the faster pace of development thanks to AI, and challenges integrating tools are hampering progress.</p><p>That's according to<a href="https://www.pynt.io/resources-hub/guides-and-reports/shift-left-adoption-benchmark-report-2025"><u> research by AI security firm Pynt</u></a> that focused on the adoption of shift left  practices — referring to a strategy of spotting flaws and security issues earlier in the software development cycle when they're easier to fix.</p><p>The survey of 250 security professionals found 47% of organizations had implemented a shift left approach to software development, with a further 27% working to do so. </p><p>But a quarter of developers felt overwhelmed by the volume of vulnerabilities, and more than a third saw false positives as the main challenge to implementing a successful shift-left strategy, followed by integration issues and vulnerability overload. </p><p>The study raises serious questions over whether this approach to software development is actually reducing overall risks, or merely increasing complexity, according to Pynt chief executive Tzvika Shneider.</p><p>"Everyone talks about shifting left, but few are seeing the security gains they expected," said Shneider. "Most organizations have tools in place, but they still struggle with noise, process friction, and developer resistance."</p><p>"<a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>accelerates how software is developed and shipped, forcing security to keep pace, Shneider added.</p><p>The research also found that the vast majority of companies that had shifted left had turned to <a href="https://www.itpro.com/software/amazons-codewhisperer-updates-could-be-a-game-changer-for-shifting-left"><u>software tools to help the process</u></a>, but 31% said that integrating those tools within development workflows continued to be a major barrier. </p><p>The most popular tools are Static Application Security Testing (SAST), Software Composition Analysis (SCA) and Dynamic Application Security Testing (DAST), with each used by about a third of respondents. </p><h2 id="software-security-priorities-are-causing-friction">Software security priorities are causing friction</h2><p>Two-thirds of respondents said they prefer to fix bugs in app code rather than with rules in post-production, highlighting friction between developers and security teams. The former prioritize feature development and see security as a burden, while the latter wants to see flaws fixed rapidly.</p><p>"Shift right is easier since it doesn’t require extensive coordination between multiple teams, whereas Shift Left demands a collaborative effort across development, security, and testing teams,” the report noted.</p><p>"Shift Left was meant to improve security, but many organizations are finding that execution challenges are holding them back," added Shneider. "Security leaders must rethink their approach to reduce friction between security and development teams while maintaining effective risk management."</p><p>Pynt said that automation in security testing could help, and called for improved collaboration between security and development teams, including integrating security into testing phases. </p><p>Europeans are ahead adopting shift left practices, the survey found, with Germany and the UK both at 52%. Developer teams in the US, however, aren't quite up to scratch in this regard, researchers found, with just 42% of enterprises having adopted the approach.</p><p>The report follows earlier research that <a href="https://www.itpro.com/cloud/cloud-security/enterprise-ai-is-surging-but-is-security-keeping-up"><u>suggests enterprise security teams</u></a> are struggling to keep up with the adoption of AI tools. Similar research found showing the rise in AI coding tools may actually be slowing down development thanks to the <a href="https://www.itpro.com/software/development/devsecops-teams-are-ramping-up-the-use-of-ai-coding-tools-but-theyve-got-serious-concerns-ai-generated-code-is-causing-major-security-headaches-and-slowing-down-development-processes"><u>security headaches it causes</u></a>.  </p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/development/anthropic-claude-opus-4-software-development">Anthropic’s new AI model could be a game changer for developers</a></li><li><a href="https://www.itpro.com/software/development/developers-will-need-to-adapt-microsoft-ceo-satya-nadella-joins-googles-sundar-pichai-in-revealing-the-scale-of-ai-generated-code-at-the-tech-giants-and-its-a-stark-warning-for-software-developers">30% of Microsoft's code is now AI-generated, and that's bad news for devs</a></li><li><a href="https://www.itpro.com/software/development/its-far-from-showing-its-age-java-mightve-just-turned-30-but-its-still-going-strong-and-here-to-stay">Java might’ve just turned 30, but it’s still going strong and here to stay</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ CISOs take the back seat as dev teams claim responsibility for application security ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Application security is becoming an increasingly important factor in the purchasing decisions of software companies, with responsibility shifting towards development teams.  </p><p>According to findings from Checkmarx' <a href="https://checkmarx.com/cisos-guide-to-steering-appsec-in-the-era-of-devsecops/"><u>annual report</u></a>, 49% of chief information security officers (CISOs) from a range of industries and regions said buyers regularly factor it in, with a quarter saying that application security is always a factor in those decisions. </p><p>This is predominantly the case in Europe, where regulatory frameworks like DORA led 58% of respondents to say that security is always a factor, compared with a third in the Asia Pacific region and only 8% in North America.</p><p>In nearly half of software-based product companies, security oversight has moved outside the CISO’s office entirely, the study found. </p><p>Engineering teams are increasingly responsible for ensuring secure, scalable delivery, while development teams are taking over AppSec decisions and budgets to embed security earlier and more efficiently in the development process.</p><p>"We’re witnessing a pivotal change: AppSec is now a competitive differentiator, a budget priority and a boardroom issue," said Checkmarx chief product officer Jonathan Rende. </p><p>"As development teams take greater ownership, CISOs must focus on governance, strategy and collaboration to keep security outcomes on track."</p><p>However, the report warned this shift in responsibility is leading to gaps in security coverage, with uneven protection across applications and fragmented tooling leading to blind spots.</p><p>Only four-in-ten business operations run on secured applications, and seven-in-ten organizations said that at least half of their applications lack robust security measures.</p><p>The good news is that AppSec budgets are growing, with 78% of respondents saying their budget rose last year, and four-in-ten saying the increase was ‘significant’. More than seven-in-ten reckoned their budget would increase this year, with a quarter saying the increase would be significant.</p><p>Budget increases were most frequently seen in Europe, where 56% of respondents reported significant growth, compared with roughly a third in both North America and the Asia Pacific region.</p><h2 id="communication-barriers-are-causing-problems">Communication barriers are causing problems</h2><p>Despite positive signs with regard to budget growth and responsibility, the study did uncover problems with the way security is communicated at the executive level. </p><p>While 62% of CISOs report AppSec metrics to their board, most said they focus entirely on vulnerability counts, with only a quarter linking those risks to business outcomes like brand reputation or regulatory exposure. </p><p>Nearly one-in-five said they don't report on application security risks at all.</p><p>As a result, the report said CISOs need to try and redefine their role through governance, rather than direct control, and foster a culture of shared responsibility by incorporating developer feedback to redefine processes.</p><p>"As <a href="https://www.itpro.com/security">security </a>responsibility migrates toward development teams, so does the funding," said Rende. "That’s why <a href="https://www.itpro.com/careers/28228/ciso-job-description-what-does-a-ciso-do">CISOs </a>today need to lead with influence, creating guardrails, not roadblocks."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/security/vulnerability-patching-ai-application-security">Businesses are taking their eye off the ball with vulnerability patching</a></li><li><a href="https://www.itpro.com/software/development/developers-are-struggling-to-build-generative-ai-applications-heres-why">Developers are at their wits end trying to build generative AI applications</a></li><li>INSERT STORY LINK</li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/cisos-take-the-back-seat-as-dev-teams-claim-responsibility-for-application-security</link>
                                                                            <description>
                            <![CDATA[ Development and engineering teams are steering security and budget strategies ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">MCdUqH4CjGif4cziP5EwQj</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/VprAJFzXyeBAnDYJQ5QGWb-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Wed, 14 May 2025 11:43:50 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:09 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/VprAJFzXyeBAnDYJQ5QGWb-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Software developers discussing the use of AI coding tools and low-code practices in an open plan office space, with two female developers and one male developer pictured. ]]></media:description>                                                            <media:text><![CDATA[Software developers discussing the use of AI coding tools and low-code practices in an open plan office space, with two female developers and one male developer pictured. ]]></media:text>
                                <media:title type="plain"><![CDATA[Software developers discussing the use of AI coding tools and low-code practices in an open plan office space, with two female developers and one male developer pictured. ]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/VprAJFzXyeBAnDYJQ5QGWb-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Application security is becoming an increasingly important factor in the purchasing decisions of software companies, with responsibility shifting towards development teams.  </p><p>According to findings from Checkmarx' <a href="https://checkmarx.com/cisos-guide-to-steering-appsec-in-the-era-of-devsecops/"><u>annual report</u></a>, 49% of chief information security officers (CISOs) from a range of industries and regions said buyers regularly factor it in, with a quarter saying that application security is always a factor in those decisions. </p><p>This is predominantly the case in Europe, where regulatory frameworks like DORA led 58% of respondents to say that security is always a factor, compared with a third in the Asia Pacific region and only 8% in North America.</p><p>In nearly half of software-based product companies, security oversight has moved outside the CISO’s office entirely, the study found. </p><p>Engineering teams are increasingly responsible for ensuring secure, scalable delivery, while development teams are taking over AppSec decisions and budgets to embed security earlier and more efficiently in the development process.</p><p>"We’re witnessing a pivotal change: AppSec is now a competitive differentiator, a budget priority and a boardroom issue," said Checkmarx chief product officer Jonathan Rende. </p><p>"As development teams take greater ownership, CISOs must focus on governance, strategy and collaboration to keep security outcomes on track."</p><p>However, the report warned this shift in responsibility is leading to gaps in security coverage, with uneven protection across applications and fragmented tooling leading to blind spots.</p><p>Only four-in-ten business operations run on secured applications, and seven-in-ten organizations said that at least half of their applications lack robust security measures.</p><p>The good news is that AppSec budgets are growing, with 78% of respondents saying their budget rose last year, and four-in-ten saying the increase was ‘significant’. More than seven-in-ten reckoned their budget would increase this year, with a quarter saying the increase would be significant.</p><p>Budget increases were most frequently seen in Europe, where 56% of respondents reported significant growth, compared with roughly a third in both North America and the Asia Pacific region.</p><h2 id="communication-barriers-are-causing-problems">Communication barriers are causing problems</h2><p>Despite positive signs with regard to budget growth and responsibility, the study did uncover problems with the way security is communicated at the executive level. </p><p>While 62% of CISOs report AppSec metrics to their board, most said they focus entirely on vulnerability counts, with only a quarter linking those risks to business outcomes like brand reputation or regulatory exposure. </p><p>Nearly one-in-five said they don't report on application security risks at all.</p><p>As a result, the report said CISOs need to try and redefine their role through governance, rather than direct control, and foster a culture of shared responsibility by incorporating developer feedback to redefine processes.</p><p>"As <a href="https://www.itpro.com/security">security </a>responsibility migrates toward development teams, so does the funding," said Rende. "That’s why <a href="https://www.itpro.com/careers/28228/ciso-job-description-what-does-a-ciso-do">CISOs </a>today need to lead with influence, creating guardrails, not roadblocks."</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/security/vulnerability-patching-ai-application-security">Businesses are taking their eye off the ball with vulnerability patching</a></li><li><a href="https://www.itpro.com/software/development/developers-are-struggling-to-build-generative-ai-applications-heres-why">Developers are at their wits end trying to build generative AI applications</a></li><li>INSERT STORY LINK</li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ The NCSC wants developers to get serious on software security ]]></title>
                                                                                                <dc:content><![CDATA[ <p>The <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do">NCSC’s </a>new <em>Software Security Code of Practice</em> is a “clear call to developers” to beef up secure by design practices, according to a senior <a href="https://www.itpro.com/security/28133/what-is-cyber-security">cybersecurity </a>expert. </p><p>James Neilson, SVP International at OPSWAT, said the new rules introduced by the security agency will play a key role in encouraging organizations to <a href="https://www.itpro.com/software/want-developers-to-build-secure-software-you-need-to-ditch-these-two-programming-languages">build more secure software</a> solutions. </p><p>“This new code is a welcome move,” he said. “It isn’t just a checklist — it’s a call to get serious about end-to-end security. A software supply chain is only as strong as its weakest link.”</p><p>The new code of practice has been introduced following a review conducted by the agency last year. At the time, the NCSC said technology markets “do not incentivize organizations to develop software that is ‘secure by default’.”</p><p>“Understandably, organizations will prioritize growth and profit rather than the security and resilience of their products and services,” the NCSC said in a <a href="https://www.ncsc.gov.uk/blog-post/software-code-of-practice-building-a-secure-digital-future" target="_blank"><u>blog post</u></a> unveiling the code. </p><p>“When the importance of cybersecurity is recognized, we know from research that software developers are not necessarily security experts, and may find it hard to efficiently build software that is secure using tools that are often inaccessible and complicated.”</p><p>While the new code of practice is voluntary, the NCSC nonetheless believes it will provide a clear “market baseline” for software security. What this means is that software developers and suppliers are now expected to adhere to a minimum set of standards to ensure products are resilient to growing security threats. </p><h2 id="what-the-software-security-code-of-practice-covers">What the Software Security Code of Practice covers</h2><p>The new code of practice contains 14 core principles, split across four themes, <a href="https://assets.publishing.service.gov.uk/media/681a156fdf188ba858873aac/Software_Security_Code_of_Practice_Web_Accessible.pdf" target="_blank"><u>according to the NCSC</u></a>. Organizations adhering to the code will be required to appoint a ‘Senior Responsible Owner’, who will hold a senior leadership role, to ensure these principles are met. </p><p>The four key themes outlined in the code include: </p><ul><li>Secure design and development</li><li>Build environment security</li><li>Secure deployment and maintenance</li><li>Communication with customers</li></ul><p>A particular focus has been placed on the ‘secure design and development’ theme, which applies predominantly to software vendors and encourages them to follow an established secure development framework. </p><p>The Senior Responsible Owner will also be required to assess the risks associated with software developed at their respective organization, as well as any risks linked to the ingestion and maintenance of third-party components throughout the development lifecycle”.</p><p>Elsewhere, the ‘secure deployment and maintenance’ theme seeks to bolster software and application security “throughout its lifetime”. </p><p>This requires vendors to distribute software to customers that is secure at the point of sale and to publish an “effective vulnerability disclosure process” to ensure customers are made aware of any security risks. </p><p>All told, the agency believes these rules will have a positive downstream effect, improving <a href="https://www.itpro.com/software/software-supply-chain-attacks-are-rife-this-is-what-developers-need-to-watch-out-for">supply chain security</a> and preventing costly remediation processes for developers. </p><p>“The Code provides a framework to help organizations measure their progress, identify improvements, and provide tangible evidence of their commitment to security,” the NCSC said in its blog post. </p><p>“It includes practical guidance to make clear to vendors what is required to ‘bake’ cybersecurity into all stages of the development life cycle. Doing this addresses cybersecurity problems at the root cause and prevents costly redesigns later on.”</p><h2 id="what-about-open-source-software">What about open source software?</h2><p>Notably, the NCSC said <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> developers and maintainers are “not considered the primary audience” with respect to the new code of practice. </p><p>“This Code of Practice is most relevant to the sale and distribution of proprietary software as the Code aims to set out the responsibilities of software vendors in the context of business-to-business commercial relationships,” the agency said. </p><p>The NCSC added that <a href="https://www.itpro.com/software/open-source/cisa-wants-closer-ties-with-open-source-developers-to-stop-the-next-log4shell">open source developers</a> and maintainers bear “no formal commitment” with regard to the security of their supply chain or the maintenance of their code. </p><p>In other words, responsibility for managing any risks associated with open source code rests on the end-user or proprietary developer using this in their software. </p><p>Regardless, Neilson noted that the new code of practice will prompt organizations to consider the potential risks here, which again will ultimately bolster broader supply chain security. </p><p>“Software developers often use third-party components, including open source software, to speed up development and add features,” he said. “However, these may contain known or newly discovered vulnerabilities, or even ones introduced maliciously.”</p><p>“By securing their software supply chains — scanning for hidden threats, validating SBOMs, securing build environments, and ensuring that what is delivered is exactly what was intended — vendors can build greater resilience and trust into their software.”</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/software-security-flaws-remediation">Software security debt is spiraling out of control</a></li><li><a href="https://www.itpro.com/software/us-lawmakers-are-pushing-for-a-shift-to-memory-safe-programming-languages-but-will-it-improve-software-security">US lawmakers are pushing for a shift to memory safe programming languages, but will it improve software security?</a></li><li><a href="https://www.itpro.com/software/the-ncscs-cto-just-said-what-is-thinking-about-software-security">NCSC CTO says what everyone is thinking about software security</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/software-security-code-of-practice-ncsc-announcement</link>
                                                                            <description>
                            <![CDATA[ The NCSC's new Software Security Code of Practice has been welcomed by cyber professionals as a positive step toward bolstering software supply chain security. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">8TW5GhCixgmGzpzFRjgi4E</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/8pfqtuhJxbbJcWfiXUbNba-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 09 May 2025 06:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:57 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Workplace Technology]]></category>
                                                                                                <author><![CDATA[ ross.kelly@futurenet.com (Ross Kelly) ]]></author>                    <dc:creator><![CDATA[ Ross Kelly ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Y5vrV2V98Np6jHAGmAtCd3-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Ross Kelly is ITPro&#039;s News &amp;amp; Analysis Editor, with a keen interest in cyber security, business leadership and emerging technologies.&lt;/p&gt;
&lt;p&gt;He graduated from Edinburgh Napier University in 2016 with a BA (Hons) in Journalism, and joined ITPro in 2022 after four years working in technology conference research.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In his spare time, Ross enjoys cycling, walking and is an avid reader of history and non-fiction.&lt;/p&gt;
&lt;p&gt;You can contact Ross at ross.kelly@futurenet.com or on &lt;a href=&quot;https://twitter.com/rosswritesetc&quot;&gt;Twitter&lt;/a&gt; and &lt;a href=&quot;https://www.linkedin.com/in/ross-kelly-18a54411a/&quot;&gt;LinkedIn&lt;/a&gt;.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/8pfqtuhJxbbJcWfiXUbNba-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Software security concept image showing male developer coding on a laptop while working at a desk, with two monitors placed on desk. ]]></media:description>                                                            <media:text><![CDATA[Software security concept image showing male developer coding on a laptop while working at a desk, with two monitors placed on desk. ]]></media:text>
                                <media:title type="plain"><![CDATA[Software security concept image showing male developer coding on a laptop while working at a desk, with two monitors placed on desk. ]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/8pfqtuhJxbbJcWfiXUbNba-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The <a href="https://www.itpro.com/security/what-is-the-national-cyber-security-centre-ncsc-and-what-does-it-do">NCSC’s </a>new <em>Software Security Code of Practice</em> is a “clear call to developers” to beef up secure by design practices, according to a senior <a href="https://www.itpro.com/security/28133/what-is-cyber-security">cybersecurity </a>expert. </p><p>James Neilson, SVP International at OPSWAT, said the new rules introduced by the security agency will play a key role in encouraging organizations to <a href="https://www.itpro.com/software/want-developers-to-build-secure-software-you-need-to-ditch-these-two-programming-languages">build more secure software</a> solutions. </p><p>“This new code is a welcome move,” he said. “It isn’t just a checklist — it’s a call to get serious about end-to-end security. A software supply chain is only as strong as its weakest link.”</p><p>The new code of practice has been introduced following a review conducted by the agency last year. At the time, the NCSC said technology markets “do not incentivize organizations to develop software that is ‘secure by default’.”</p><p>“Understandably, organizations will prioritize growth and profit rather than the security and resilience of their products and services,” the NCSC said in a <a href="https://www.ncsc.gov.uk/blog-post/software-code-of-practice-building-a-secure-digital-future" target="_blank"><u>blog post</u></a> unveiling the code. </p><p>“When the importance of cybersecurity is recognized, we know from research that software developers are not necessarily security experts, and may find it hard to efficiently build software that is secure using tools that are often inaccessible and complicated.”</p><p>While the new code of practice is voluntary, the NCSC nonetheless believes it will provide a clear “market baseline” for software security. What this means is that software developers and suppliers are now expected to adhere to a minimum set of standards to ensure products are resilient to growing security threats. </p><h2 id="what-the-software-security-code-of-practice-covers">What the Software Security Code of Practice covers</h2><p>The new code of practice contains 14 core principles, split across four themes, <a href="https://assets.publishing.service.gov.uk/media/681a156fdf188ba858873aac/Software_Security_Code_of_Practice_Web_Accessible.pdf" target="_blank"><u>according to the NCSC</u></a>. Organizations adhering to the code will be required to appoint a ‘Senior Responsible Owner’, who will hold a senior leadership role, to ensure these principles are met. </p><p>The four key themes outlined in the code include: </p><ul><li>Secure design and development</li><li>Build environment security</li><li>Secure deployment and maintenance</li><li>Communication with customers</li></ul><p>A particular focus has been placed on the ‘secure design and development’ theme, which applies predominantly to software vendors and encourages them to follow an established secure development framework. </p><p>The Senior Responsible Owner will also be required to assess the risks associated with software developed at their respective organization, as well as any risks linked to the ingestion and maintenance of third-party components throughout the development lifecycle”.</p><p>Elsewhere, the ‘secure deployment and maintenance’ theme seeks to bolster software and application security “throughout its lifetime”. </p><p>This requires vendors to distribute software to customers that is secure at the point of sale and to publish an “effective vulnerability disclosure process” to ensure customers are made aware of any security risks. </p><p>All told, the agency believes these rules will have a positive downstream effect, improving <a href="https://www.itpro.com/software/software-supply-chain-attacks-are-rife-this-is-what-developers-need-to-watch-out-for">supply chain security</a> and preventing costly remediation processes for developers. </p><p>“The Code provides a framework to help organizations measure their progress, identify improvements, and provide tangible evidence of their commitment to security,” the NCSC said in its blog post. </p><p>“It includes practical guidance to make clear to vendors what is required to ‘bake’ cybersecurity into all stages of the development life cycle. Doing this addresses cybersecurity problems at the root cause and prevents costly redesigns later on.”</p><h2 id="what-about-open-source-software">What about open source software?</h2><p>Notably, the NCSC said <a href="https://www.itpro.com/software/28109/what-is-open-source">open source</a> developers and maintainers are “not considered the primary audience” with respect to the new code of practice. </p><p>“This Code of Practice is most relevant to the sale and distribution of proprietary software as the Code aims to set out the responsibilities of software vendors in the context of business-to-business commercial relationships,” the agency said. </p><p>The NCSC added that <a href="https://www.itpro.com/software/open-source/cisa-wants-closer-ties-with-open-source-developers-to-stop-the-next-log4shell">open source developers</a> and maintainers bear “no formal commitment” with regard to the security of their supply chain or the maintenance of their code. </p><p>In other words, responsibility for managing any risks associated with open source code rests on the end-user or proprietary developer using this in their software. </p><p>Regardless, Neilson noted that the new code of practice will prompt organizations to consider the potential risks here, which again will ultimately bolster broader supply chain security. </p><p>“Software developers often use third-party components, including open source software, to speed up development and add features,” he said. “However, these may contain known or newly discovered vulnerabilities, or even ones introduced maliciously.”</p><p>“By securing their software supply chains — scanning for hidden threats, validating SBOMs, securing build environments, and ensuring that what is delivered is exactly what was intended — vendors can build greater resilience and trust into their software.”</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/software/software-security-flaws-remediation">Software security debt is spiraling out of control</a></li><li><a href="https://www.itpro.com/software/us-lawmakers-are-pushing-for-a-shift-to-memory-safe-programming-languages-but-will-it-improve-software-security">US lawmakers are pushing for a shift to memory safe programming languages, but will it improve software security?</a></li><li><a href="https://www.itpro.com/software/the-ncscs-cto-just-said-what-is-thinking-about-software-security">NCSC CTO says what everyone is thinking about software security</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Criminals target APIs as web attacks skyrocket globally  ]]></title>
                                                                                                <dc:content><![CDATA[ <p>The number of web attacks around the world is surging, with APIs emerging as the primary target. </p><p>In total, there were 311 billion web attacks in 2024, up 33% on the year before. Europe, the Middle East and Africa accounted for 62 billion of these attacks - up 16% year-on-year. </p><p>More than 230 billion web attacks targeted commerce organizations, making it the most impacted industry, with nearly three times as many attacks as the second most attacked sector, high technology.</p><p>According to Akamai's <a href="https://www.akamai.com/lp/soti/app-api-ai-security-report-2025" target="_blank"><u><em>State of Apps and API Security 2025</em></u></a> report, more than a third of web attacks targeted APIs, with 150 billion API attacks from January 2023 through December 2024. </p><p>The report noted that <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>is expanding attack surfaces and introducing new security challenges, thanks to the integration of AI-driven tools with core platforms via APIs. </p><p>Most AI-powered APIs are externally accessible and many rely on inadequate authentication mechanisms - something criminals are taking advantage of.</p><p>"AI is transforming web and API security, enhancing threat detection but also creating new challenges," said Rupesh Chokshi, senior vice president and general manager of Akamai’s Application Security Portfolio.</p><p>The research also revealed a dramatic rise in Layer 7 (application-layer) <a href="https://www.itpro.com/security/28026/what-is-a-ddos-attack">distributed denial-of-service (DDoS) attacks</a> against web applications and APIs. </p><p>Quarterly attack volumes nearly doubled year-over-year between the first quarter of 2023 and the end of 2024 - indeed, there were 1.1 trillion in December 2024 alone. </p><p>This growth, Akamai said, is due to the growing sophistication of bot-driven attacks, the persistence of HTTPS flooding as a primary attack vector, and the prevalence of Layer 7 DDoS attacks targeting the high technology industry.</p><p>Here, the most affected industry was the high technology sector, with seven trillion Layer 7 DDoS attacks between January 2023 and December 2024.</p><p>Other findings of the report included a rise of 32% in Open Worldwide Application Security Project (OWASP) API Security top 10–related incidents, with authentication and authorization flaws exposing sensitive data and functionality.</p><p>Security alerts related to the <a href="https://www.itpro.com/security/confusion-and-frustration-mitre-cve-oversight-ends-federal-contract-expiry">MITRE </a>security framework were also up by 30%, as attackers move to advanced techniques such as automation and AI to exploit APIs.</p><p>Similarly, shadow and zombie APIs - outdated interfaces that remain active because of incomplete decommissioning, staff turnover, or other reasons - are often missed in inventories, making them particularly vulnerable.</p><p>Indeed, the research indicated that one-third of malicious API transactions target <a href="https://www.itpro.com/security/cyber-attacks/api-and-bot-attacks-are-costing-businesses-billions">shadow APIs</a>.</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/security/data-breaches/cyber-attacks-against-uk-firms-dropped-by-10-percent-last-year-but-experts-say-dont-get-complacent">Cyber attacks against UK firms dropped by 10% last year, but experts say don't get complacent</a></li><li><a href="https://www.itpro.com/security/is-the-ciso-role-in-crisis">Bigger salaries, more burnout: Is the CISO role in crisis?</a></li><li><a href="https://www.itpro.com/security/vulnerability-patching-ai-application-security">Businesses are taking their eye off the ball with vulnerability patching</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/criminals-target-apis-as-web-attacks-skyrocket-globally</link>
                                                                            <description>
                            <![CDATA[ More than a third of web attacks target APIs as AI expands attack surfaces and brings new security challenges ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">foYtS5u5QddFaBPjZHXT25</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/Xvan8EtXzQ9JDibnCMs3CX-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 25 Apr 2025 02:00:00 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:20 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Emma Woollacott ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/aWfskavxoVSMDy6cDWtYmJ-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/Xvan8EtXzQ9JDibnCMs3CX-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Laptop with warning symbol in red denoting a cyber attack or compromised device.]]></media:description>                                                            <media:text><![CDATA[Laptop with warning symbol in red denoting a cyber attack or compromised device.]]></media:text>
                                <media:title type="plain"><![CDATA[Laptop with warning symbol in red denoting a cyber attack or compromised device.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/Xvan8EtXzQ9JDibnCMs3CX-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>The number of web attacks around the world is surging, with APIs emerging as the primary target. </p><p>In total, there were 311 billion web attacks in 2024, up 33% on the year before. Europe, the Middle East and Africa accounted for 62 billion of these attacks - up 16% year-on-year. </p><p>More than 230 billion web attacks targeted commerce organizations, making it the most impacted industry, with nearly three times as many attacks as the second most attacked sector, high technology.</p><p>According to Akamai's <a href="https://www.akamai.com/lp/soti/app-api-ai-security-report-2025" target="_blank"><u><em>State of Apps and API Security 2025</em></u></a> report, more than a third of web attacks targeted APIs, with 150 billion API attacks from January 2023 through December 2024. </p><p>The report noted that <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>is expanding attack surfaces and introducing new security challenges, thanks to the integration of AI-driven tools with core platforms via APIs. </p><p>Most AI-powered APIs are externally accessible and many rely on inadequate authentication mechanisms - something criminals are taking advantage of.</p><p>"AI is transforming web and API security, enhancing threat detection but also creating new challenges," said Rupesh Chokshi, senior vice president and general manager of Akamai’s Application Security Portfolio.</p><p>The research also revealed a dramatic rise in Layer 7 (application-layer) <a href="https://www.itpro.com/security/28026/what-is-a-ddos-attack">distributed denial-of-service (DDoS) attacks</a> against web applications and APIs. </p><p>Quarterly attack volumes nearly doubled year-over-year between the first quarter of 2023 and the end of 2024 - indeed, there were 1.1 trillion in December 2024 alone. </p><p>This growth, Akamai said, is due to the growing sophistication of bot-driven attacks, the persistence of HTTPS flooding as a primary attack vector, and the prevalence of Layer 7 DDoS attacks targeting the high technology industry.</p><p>Here, the most affected industry was the high technology sector, with seven trillion Layer 7 DDoS attacks between January 2023 and December 2024.</p><p>Other findings of the report included a rise of 32% in Open Worldwide Application Security Project (OWASP) API Security top 10–related incidents, with authentication and authorization flaws exposing sensitive data and functionality.</p><p>Security alerts related to the <a href="https://www.itpro.com/security/confusion-and-frustration-mitre-cve-oversight-ends-federal-contract-expiry">MITRE </a>security framework were also up by 30%, as attackers move to advanced techniques such as automation and AI to exploit APIs.</p><p>Similarly, shadow and zombie APIs - outdated interfaces that remain active because of incomplete decommissioning, staff turnover, or other reasons - are often missed in inventories, making them particularly vulnerable.</p><p>Indeed, the research indicated that one-third of malicious API transactions target <a href="https://www.itpro.com/security/cyber-attacks/api-and-bot-attacks-are-costing-businesses-billions">shadow APIs</a>.</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/security/data-breaches/cyber-attacks-against-uk-firms-dropped-by-10-percent-last-year-but-experts-say-dont-get-complacent">Cyber attacks against UK firms dropped by 10% last year, but experts say don't get complacent</a></li><li><a href="https://www.itpro.com/security/is-the-ciso-role-in-crisis">Bigger salaries, more burnout: Is the CISO role in crisis?</a></li><li><a href="https://www.itpro.com/security/vulnerability-patching-ai-application-security">Businesses are taking their eye off the ball with vulnerability patching</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ AI is helping bad bots take over the internet  ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Automated bot traffic has surpassed human online activity for the first time in a decade, according to research from Imperva, accounting for 51% of all web traffic. </p><p>The <a href="https://www.imperva.com/resources/resource-library/reports/2025-bad-bot-report/">2025 Bad Bot Report</a> found that automated threats continue to rise, with malicious bots now making up 37% of all internet traffic. </p><p>Attackers are able to create more advanced and evasive bots with AI. But more concerning is the way it lowers the barrier for newer or less skilled hackers to create low-quality bots, resulting in an increase in simple attacks, according to the report.</p><p>This is the 12th annual <a href="https://www.itpro.com/security/bad-bots-are-on-the-rise-as-almost-half-of-all-internet-traffic-is-now-automated">Bad Bot Report from Imperva</a>. It's based on insights from its Threat Research and Security Analyst Services teams with data collected from across the firm's global network. That includes the blocking of 13 trillion bad bot requests across thousands of domains and industries, according to Imperva.  </p><p>"The surge in AI-driven bot creation has serious implications for businesses worldwide," said Tim Chang, general manager of Application Security at Imperva's parent company, Thales. "As automated traffic accounts for more than half of all web activity, organizations face heightened risks from bad bots, which are becoming more prolific every day."</p><p>Chang added that the 2025 report sheds light on the evolving tactics and techniques being used by threat actors. The advanced evasion methods that can be created with AI are now widely available, resulting in a rapidly changing threat environment for business. As a result, Chang urged them to evolve their own strategies. </p><p>"It's crucial to adopt an adaptive and proactive approach, leveraging sophisticated bot detection tools and comprehensive cybersecurity management solutions to build a resilient defense against the ever-shifting landscape of bot-related threats," Chang said.</p><p>Advanced AI tools, such as ChatGPT, ByteSpider Bot, ClaudeBot, <a href="https://www.itpro.com/technology/artificial-intelligence/google-jumps-on-the-agentic-ai-bandwagon">Google Gemini</a>, Perplexity AI, and Cohere AI, are transforming user interactions. What's more, they're providing new methods of attack for would-be and professional hackers.</p><p>The ByteSpider Bot alone is responsible for 54% of all AI-enabled attacks, according to Impervia. AppleBot was attributed to 26%, ClaudeBot 13%, and the ChatGPT User Bot accounted for 6%, according to the Imperva Threat Research team.</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/ai-is-helping-bad-bots-take-over-the-internet</link>
                                                                            <description>
                            <![CDATA[ Automated bot traffic has surpassed human activity for the first time in a decade, according to Imperva ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">koMNUGxNgChfWBpyQiyFSU</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/q4FaYNBFPVDL9KEg5LUYZM-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Tue, 15 Apr 2025 09:31:46 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:49 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                <author><![CDATA[ itpro@futurenet.com (Bobby Hellard) ]]></author>                    <dc:creator><![CDATA[ Bobby Hellard ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/bsR2tHSyVKUoyXZF5pNsDA-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Bobby Hellard&amp;nbsp;is&amp;nbsp;ITPro&#039;s Reviews Editor and has worked on&amp;nbsp;CloudPro and ChannelPro since 2018. In his time at ITPro, Bobby has covered stories for all the major technology companies, such as Apple, Microsoft, Amazon and Facebook, and regularly attends industry-leading events such as AWS Re:Invent and Google Cloud Next.&lt;/p&gt;
&lt;p&gt;Bobby mainly covers hardware reviews, but you will also recognize him as the face of many of our video reviews of laptops and smartphones.&lt;/p&gt;
&lt;p&gt;He has been a journalist for ten years, originally covering sports, before moving into business technology with ITPro. He has bylines in The Independent, Vice and The Business Briefing. Contact him at &lt;a href=&quot;mailto:bobby.hellard@futurenet.com&quot;&gt;bobby.hellard@futurenet.com&lt;/a&gt; or find him on Twitter: &lt;a href=&quot;https://twitter.com/bobbyhellard&quot;&gt;@bobbyhellard&lt;/a&gt;&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/q4FaYNBFPVDL9KEg5LUYZM-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Lines of code with a skull silhouette]]></media:description>                                                            <media:text><![CDATA[Lines of code with a skull silhouette]]></media:text>
                                <media:title type="plain"><![CDATA[Lines of code with a skull silhouette]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/q4FaYNBFPVDL9KEg5LUYZM-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Automated bot traffic has surpassed human online activity for the first time in a decade, according to research from Imperva, accounting for 51% of all web traffic. </p><p>The <a href="https://www.imperva.com/resources/resource-library/reports/2025-bad-bot-report/">2025 Bad Bot Report</a> found that automated threats continue to rise, with malicious bots now making up 37% of all internet traffic. </p><p>Attackers are able to create more advanced and evasive bots with AI. But more concerning is the way it lowers the barrier for newer or less skilled hackers to create low-quality bots, resulting in an increase in simple attacks, according to the report.</p><p>This is the 12th annual <a href="https://www.itpro.com/security/bad-bots-are-on-the-rise-as-almost-half-of-all-internet-traffic-is-now-automated">Bad Bot Report from Imperva</a>. It's based on insights from its Threat Research and Security Analyst Services teams with data collected from across the firm's global network. That includes the blocking of 13 trillion bad bot requests across thousands of domains and industries, according to Imperva.  </p><p>"The surge in AI-driven bot creation has serious implications for businesses worldwide," said Tim Chang, general manager of Application Security at Imperva's parent company, Thales. "As automated traffic accounts for more than half of all web activity, organizations face heightened risks from bad bots, which are becoming more prolific every day."</p><p>Chang added that the 2025 report sheds light on the evolving tactics and techniques being used by threat actors. The advanced evasion methods that can be created with AI are now widely available, resulting in a rapidly changing threat environment for business. As a result, Chang urged them to evolve their own strategies. </p><p>"It's crucial to adopt an adaptive and proactive approach, leveraging sophisticated bot detection tools and comprehensive cybersecurity management solutions to build a resilient defense against the ever-shifting landscape of bot-related threats," Chang said.</p><p>Advanced AI tools, such as ChatGPT, ByteSpider Bot, ClaudeBot, <a href="https://www.itpro.com/technology/artificial-intelligence/google-jumps-on-the-agentic-ai-bandwagon">Google Gemini</a>, Perplexity AI, and Cohere AI, are transforming user interactions. What's more, they're providing new methods of attack for would-be and professional hackers.</p><p>The ByteSpider Bot alone is responsible for 54% of all AI-enabled attacks, according to Impervia. AppleBot was attributed to 26%, ClaudeBot 13%, and the ChatGPT User Bot accounted for 6%, according to the Imperva Threat Research team.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Security experts issue warning over the rise of 'gray bot' AI web scrapers ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Security firm Barracuda has called for organizations to factor <a href="https://www.itpro.com/technology/artificial-intelligence-ai/369959/what-is-generative-ai">AI</a> bots that scrape data from public websites into their security strategies, labelling them not as good or <a href="https://www.itpro.com/security/bad-bots-are-on-the-rise-as-almost-half-of-all-internet-traffic-is-now-automated"><u>bad bots</u></a>, but “gray bots”.</p><p>Defining these three categories of bot, senior principal software engineer for application security engineering at Barracuda Rahul Gupta <a href="https://blog.barracuda.com/2025/04/02/threat-spotlight-gray-bots-gen-ai-scraper-bots-targeting-web-apps"><u>said</u></a>: “There are good bots – such as search engine crawler bots, SEO bots, and customer service bots – and bad bots, designed for malicious or harmful online activities like breaching accounts to steal personal data or commit fraud.</p><p>“In the space between them you will find what Barracuda calls ‘gray bots.’ … Gray bots are blurring the boundaries of legitimate activity. They are not overtly malicious, but their approach can be questionable. Some are highly aggressive.”</p><p>Examples of gray bots given by Gupta include web scraper bots, automated content aggregators for news, travel offers, and so on, and generative AI scraper bots.</p><p>The activity of this third category was specifically highlighted by Gupta, with web applications receiving millions of requests from bots such as Anthropic’s ClaudeBot and TikTok’s Bytespider bot.</p><p>“ClaudeBot is the most active Gen AI gray bot in our dataset by a considerable margin,” said Gupta. “ClaudeBot’s relentless requests are likely to impact many of its targeted web applications.</p><p>According to Barracuda's analysis, one web application received an average of 323,300  AI scraper bot requests a day over the course of 30 days. </p><p>Another received 500,000 requests in a single day. A third received approximately 40,800 requests over the course of a day, with an average request rate of 17,000 per hour.</p><p>Gupta said this level of consistency was “unexpected”. </p><p>“It is generally assumed, and often the case, that gray bot traffic comes in waves, hitting a website for a few minutes to an hour or so before falling back,” he said, although he added that “constant bombardment or unexpected, ad hoc traffic surges [both] present challenges for web applications”.</p><p>This level of activity can disrupt operations and degrade the performance of web application traffic, Gupta said, as well as gathering up “vast volumes of proprietary or commercial data”.</p><p>There can also be more indirect impacts, such as distorting web traffic figures making it harder to take data driven decisions, Barracuda claimed.</p><h2 id="defensive-measures">Defensive measures</h2><p>There are multiple reasons why organizations may wish to protect themselves from AI webscrapers, ranging from protecting their IP and copyright to data privacy concerns, as well as performance degradation.</p><p>Those in the creative industries in particular are increasingly worried about their data being used to train generative AI models without their permission, but it’s a dilemma that affects other businesses too.</p><p><a href="https://www.itpro.com/technology/artificial-intelligence/generative-ai-training-in-the-crosshairs-as-ico-set-to-examine-legality-of-personal-data-use"><u>In January 2024</u></a>, the UK’s Information Commissioner’s Office (ICO) said it would examine web scraping by generative AI bots as part of its investigation into the collection and processing of personal data by LLMs owned by companies like OpenAI and Anthropic.</p><p>"The impact of generative AI can be transformative for society if it's developed and deployed responsibly," said the ICO's executive director for regulatory risk, Stephen Almond, at the time.</p><p>"This call for views will help the ICO provide industry with certainty regarding its obligations and safeguard people's information rights and freedoms," he added.</p><p>For his part, Gupta recommended: “To ensure your web applications are protected against the impact of gray bots, consider implementing bot protection capable of detecting and blocking generative AI scraper bot activity.”</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/security/bad-bots-are-on-the-rise-as-almost-half-of-all-internet-traffic-is-now-automated">Bad bots are on the rise as almost half of all internet traffic is now automated</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/protecting-your-business-from-ai-web-scraping">How to protect your business from AI web scraping</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/openai-quietly-unveils-gptbot-dedicated-web-crawler">OpenAI quietly unveils GPTBot dedicated web crawler</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/security-experts-issue-warning-over-the-rise-of-gray-bot-ai-web-scrapers</link>
                                                                            <description>
                            <![CDATA[ While not malicious, the bots can overwhelm web applications in a way similar to bad actors ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">SeCaUxmVe4rgnWkKBCzrug</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/nyVbXBTHTVEeREU2f2im4B-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Thu, 03 Apr 2025 12:29:23 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:49 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                <author><![CDATA[ jane.mccallion@futurenet.com (Jane McCallion) ]]></author>                    <dc:creator><![CDATA[ Jane McCallion ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Wq9nnLr7TNkY8gyBRb7YsA-320-70.jpeg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Jane is managing editor at ITPro and ChannelPro. She started out with the brands as a staff writer specializing in cloud computing before going on to become senior writer and reports editor, managing the content and creation of ITPro’s quarterly whitepapers. During this time, she broadened her expertise to include cybersecurity, data centers and enterprise IT infrastructure. In 2016, she became features editor, managing a pool of freelance and internal writers, while continuing to specialize in enterprise IT infrastructure, data centers, and business strategy.&lt;/p&gt;&lt;p&gt;In October 2021, she became the sites’ deputy editor, before moving to the role of managing editor in June 2024. Although she now has a more strategic role,  she is still a specialist in enterprise IT infrastructure, business strategy, and cybersecurity.&lt;/p&gt;&lt;p&gt;Jane holds an MA in journalism from Goldsmiths, University of London, and a BA in Applied Languages from the University of Portsmouth. She is fluent in French and Spanish, and has written features in both languages.&lt;/p&gt;&lt;p&gt;Prior to joining ITPro, Jane was a freelance business journalist writing as both Jane McCallion and Jane Bordenave for titles such as European CEO, World Finance, and Business Excellence Magazine.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/nyVbXBTHTVEeREU2f2im4B-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[AI web scraper bot concept image showing a robotic hand touching and interfacing with flowing data lines.]]></media:description>                                                            <media:text><![CDATA[AI web scraper bot concept image showing a robotic hand touching and interfacing with flowing data lines.]]></media:text>
                                <media:title type="plain"><![CDATA[AI web scraper bot concept image showing a robotic hand touching and interfacing with flowing data lines.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/nyVbXBTHTVEeREU2f2im4B-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Security firm Barracuda has called for organizations to factor <a href="https://www.itpro.com/technology/artificial-intelligence-ai/369959/what-is-generative-ai">AI</a> bots that scrape data from public websites into their security strategies, labelling them not as good or <a href="https://www.itpro.com/security/bad-bots-are-on-the-rise-as-almost-half-of-all-internet-traffic-is-now-automated"><u>bad bots</u></a>, but “gray bots”.</p><p>Defining these three categories of bot, senior principal software engineer for application security engineering at Barracuda Rahul Gupta <a href="https://blog.barracuda.com/2025/04/02/threat-spotlight-gray-bots-gen-ai-scraper-bots-targeting-web-apps"><u>said</u></a>: “There are good bots – such as search engine crawler bots, SEO bots, and customer service bots – and bad bots, designed for malicious or harmful online activities like breaching accounts to steal personal data or commit fraud.</p><p>“In the space between them you will find what Barracuda calls ‘gray bots.’ … Gray bots are blurring the boundaries of legitimate activity. They are not overtly malicious, but their approach can be questionable. Some are highly aggressive.”</p><p>Examples of gray bots given by Gupta include web scraper bots, automated content aggregators for news, travel offers, and so on, and generative AI scraper bots.</p><p>The activity of this third category was specifically highlighted by Gupta, with web applications receiving millions of requests from bots such as Anthropic’s ClaudeBot and TikTok’s Bytespider bot.</p><p>“ClaudeBot is the most active Gen AI gray bot in our dataset by a considerable margin,” said Gupta. “ClaudeBot’s relentless requests are likely to impact many of its targeted web applications.</p><p>According to Barracuda's analysis, one web application received an average of 323,300  AI scraper bot requests a day over the course of 30 days. </p><p>Another received 500,000 requests in a single day. A third received approximately 40,800 requests over the course of a day, with an average request rate of 17,000 per hour.</p><p>Gupta said this level of consistency was “unexpected”. </p><p>“It is generally assumed, and often the case, that gray bot traffic comes in waves, hitting a website for a few minutes to an hour or so before falling back,” he said, although he added that “constant bombardment or unexpected, ad hoc traffic surges [both] present challenges for web applications”.</p><p>This level of activity can disrupt operations and degrade the performance of web application traffic, Gupta said, as well as gathering up “vast volumes of proprietary or commercial data”.</p><p>There can also be more indirect impacts, such as distorting web traffic figures making it harder to take data driven decisions, Barracuda claimed.</p><h2 id="defensive-measures">Defensive measures</h2><p>There are multiple reasons why organizations may wish to protect themselves from AI webscrapers, ranging from protecting their IP and copyright to data privacy concerns, as well as performance degradation.</p><p>Those in the creative industries in particular are increasingly worried about their data being used to train generative AI models without their permission, but it’s a dilemma that affects other businesses too.</p><p><a href="https://www.itpro.com/technology/artificial-intelligence/generative-ai-training-in-the-crosshairs-as-ico-set-to-examine-legality-of-personal-data-use"><u>In January 2024</u></a>, the UK’s Information Commissioner’s Office (ICO) said it would examine web scraping by generative AI bots as part of its investigation into the collection and processing of personal data by LLMs owned by companies like OpenAI and Anthropic.</p><p>"The impact of generative AI can be transformative for society if it's developed and deployed responsibly," said the ICO's executive director for regulatory risk, Stephen Almond, at the time.</p><p>"This call for views will help the ICO provide industry with certainty regarding its obligations and safeguard people's information rights and freedoms," he added.</p><p>For his part, Gupta recommended: “To ensure your web applications are protected against the impact of gray bots, consider implementing bot protection capable of detecting and blocking generative AI scraper bot activity.”</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/security/bad-bots-are-on-the-rise-as-almost-half-of-all-internet-traffic-is-now-automated">Bad bots are on the rise as almost half of all internet traffic is now automated</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/protecting-your-business-from-ai-web-scraping">How to protect your business from AI web scraping</a></li><li><a href="https://www.itpro.com/technology/artificial-intelligence/openai-quietly-unveils-gptbot-dedicated-web-crawler">OpenAI quietly unveils GPTBot dedicated web crawler</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ What are business logic vulnerabilities? ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Cybersecurity often focuses on traditional threats like <a href="https://www.itpro.com/software/fbi-and-cisa-say-its-time-to-delete-sql-injection-flaws-for-good"><u>SQL injection</u></a>, <a href="https://www.itpro.com/malware/28076/what-is-malware">malware</a>, and <a href="https://www.itpro.com/security/cyber-attacks/phishing-tactics-the-top-attacks-trends-in-year"><u>phishing attacks</u></a>, but a more insidious risk is quietly undermining the security of many companies —business logic vulnerabilities.</p><p>Business logic vulnerabilities pose a serious yet often overlooked threat to modern businesses. Unlike traditional security vulnerabilities, such as SQL injection or <a href="https://www.itpro.com/cross-site-scripting-xss/34411/what-is-cross-site-scripting-xss">cross-site scripting (XSS)</a>, which exploit technical weaknesses, business logic vulnerabilities arise from flaws in how an application or system processes data. </p><p>The risks posed by business logic vulnerabilities are immense. Attackers can exploit them to manipulate pricing models, bypass authentication, or even gain unauthorized access to restricted areas of an application. Because these vulnerabilities are unique to each business system, they are notoriously difficult to detect, making them a significant concern for cybersecurity teams.</p><p>Sascha Giese, tech evangelist at SolarWinds, explains to <em>ITPro</em> that business logic is at the core of how organizations process data. </p><p>“A simple example would be a ‘buy two, get one free’ offer. When you add two items to your cart, the system adjusts the price automatically. But today, business logic can get a lot more advanced,” he says. </p><p>“A system might monitor stock levels and raise prices when demand is high or even apply complex rules like adjusting prices based on a customer’s location or purchasing power.” While these processes are designed to optimize business operations, they also introduce vulnerabilities. Attackers can exploit these logical pathways to gain financial advantages, steal data, or disrupt services.</p><h2 id="a-different-kind-of-security-risk">A different kind of security risk</h2><p>Business logic vulnerabilities stand apart from traditional <a href="https://www.itpro.com/security/cyber-attacks/global-cyber-attacks-jumped-44-percent-last-year"><u>cybersecurity threats</u></a> because they do not exploit <a href="https://www.itpro.com/security/hackers-are-deliberately-poisoning-ai-systems-to-make-them-malfunction-and-theres-no-way-to-defend-against-it"><u>system defences' weaknesses</u></a>. Instead, they manipulate how a system is supposed to work. </p><p>Ray Kelly, a fellow at Black Duck, points out that business logic vulnerabilities require careful planning and a deeper understanding of a system’s inner workings. “Unlike threats such as SQL injection or cross-site scripting, which can be quickly and easily tested, business logic flaws often require multiple steps or manual processes to exploit,” Kelly says. “<a href="https://www.itpro.com/security/cyber-crime/hackers-are-using-a-new-ai-chatbot-to-wage-cyber-attacks-ghostgpt-lets-users-write-malicious-code-create-malware-and-curate-phishing-emails-and-it-costs-just-usd50-to-use"><u>Hackers</u></a> tend to favor low-hanging fruit – attacks that require minimal effort – making common vulnerabilities like SQL injection more attractive targets. In contrast, exploiting business logic flaws takes more time but can be highly rewarding.”</p><p>One example is seat spinning, where cybercriminals repeatedly hold and release airline seats to block availability and resell them for profit. These are not traditional hacks but rather an exploitation of the business model itself.</p><h2 id="why-are-business-logic-flaws-so-hard-to-spot">Why are business logic flaws so hard to spot?</h2><p>Unlike <a href="https://www.itpro.com/security/openai-bug-bounty-program-payout"><u>software bugs</u></a> that can be detected with automated tools, business logic flaws require <a href="https://www.itpro.com/software/development/the-worlds-first-ai-software-engineer-isnt-living-up-to-expectations-cognition-ais-devin-assistant-was-touted-as-a-game-changer-for-developers-but-so-far-its-fumbling-tasks-and-struggling-to-compete-with-human-workers"><u>human intuition</u></a> and creative problem-solving to uncover. </p><p>James Sherlow, systems engineering director at Cequence Security, notes that business logic abuse is unique to each application, making it difficult to apply universal security measures. “Whereas SQL and XSS can be protected by a web application firewall (WAF), for example, business logic abuse will be completely different for each application. There is not one test or signature that can be used,” Sherlow explains. “This is why these attacks need to be detected using behavioral analysis rather than traditional security testing.”</p><p>Dirk Schrader, VP of security research at Netwrix, also points out. “Automated pen-testing, even those that use an AI-based approach, has limited capabilities as it usually replicates what has been done before,” he explains to ITPro. “This is when the creativity of a human pen-tester makes a huge difference.” Since these vulnerabilities often don’t produce error messages or alerts, they go unnoticed until an attacker successfully exploits them.</p><h2 id="how-businesses-can-prevent-business-logic-vulnerabilities">How businesses can prevent business logic vulnerabilities</h2><p>Addressing business logic vulnerabilities requires a fundamental shift in a business's cybersecurity strategy. Instead of relying merely on automated security tools, organizations must integrate <a href="https://www.itpro.com/security/ransomware/building-ransomware-resilience-to-avoid-paying-out">threat modeling</a>, human-driven testing, and real-time <a href="https://www.itpro.com/security/uks-new-cyber-monitoring-centre-wants-to-create-a-digital-richter-scale-for-cyber-attacks">threat monitoring</a> into their security framework.</p><h3 class="article-body__section" id="section-1-implementing-threat-modeling"><span>1. Implementing threat modeling</span></h3><p>Rather than focusing on traditional security risks, threat modeling analyzes how an attacker might manipulate a system’s workflows. According to Sherlow, the success of threat modeling depends on company-wide collaboration, not just the security team. “The key component here is that this needs to be embedded in company culture and not owned by the security team alone,” he advocates. “Security needs to come together with <a href="https://www.itpro.com/security/developers-cant-get-a-handle-on-application-security-risks"><u>developers</u></a>, business owners, product managers, and other areas of the business to build in processes to model potential threats.”</p><h3 class="article-body__section" id="section-2-manual-penetration-testing"><span>2. Manual penetration testing</span></h3><p>Since automated tools struggle to detect business logic vulnerabilities, manual <a href="https://www.itpro.com/penetration-testing/33981/what-is-penetration-testing">penetration testing</a> remains crucial. <a href="https://www.itpro.com/security/hacking/two-thirds-of-ethical-hackers-using-generative-ai-in-bug-hunting"><u>Ethical hackers</u></a> and security analysts must test applications as if they were attackers, looking for ways to exploit business logic flaws.</p><p>Danny Jenkins, CEO and co-founder at ThreatLocker stresses that AI cannot fully replace human analysis in identifying these vulnerabilities. "Automated testing is not great at testing for business logic vulnerabilities, so they usually have to be caught by a human," Jenkins says. "Security teams can overcome some of these challenges by ensuring proper code review and giving developers the time they need to consider potential risks as they develop."</p><h3 class="article-body__section" id="section-3-adopting-a-zero-trust-approach"><span>3. Adopting a zero trust approach</span></h3><p>A <a href="https://www.itpro.com/security/network-security/358282/what-is-zero-trust"><u>zero trust security model</u></a> assumes that no system or user should be automatically trusted, even those within the organization. Dominik Birgelen, CEO of Oneclick AG, explains that zero trust architecture (ZTA) can help reduce the risk of business logic abuse. </p><p>“Zero Trust enforces continuous identity verification and context-aware access controls, ensuring users and devices are validated based on real-time risk assessments,” Birgelen explains. By applying strict access controls, session monitoring, and behavioral anomaly detection, businesses can limit an attacker’s ability to exploit logical weaknesses.</p><h3 class="article-body__section" id="section-4-monitoring-for-behavioral-anomalies"><span>4. Monitoring for behavioral anomalies</span></h3><p>Since business logic vulnerabilities often involve unexpected user behavior, real-time monitoring can help detect suspicious activity before it causes damage. <a href="https://www.itpro.com/security/cyber-crime/agentic-ai-cybersecurity-risks">AI-driven security tools</a> can analyze normal user behavior and flag anomalies—such as a sudden increase in purchase attempts, repeated coupon code use, or unusual login patterns.</p><p>Cequence Security’s Sherlow emphasizes that detection must go beyond simple IP blocking to avoid false positives. “Defeating malicious actors is not only about blocking them but also breaking their business model,” he says. Security teams must use behavioral fingerprinting to track suspicious users without accidentally blocking legitimate customers.</p><iframe allow="" height="200px" width="100%" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/a696c78c-0d94-4bc0-b1cf-106e70c68480/" src="https://player.captivate.fm/episode/a696c78c-0d94-4bc0-b1cf-106e70c68480/"></iframe><p>Business logic vulnerabilities present a unique and growing threat that many organizations are ill-prepared to handle. Unlike traditional security flaws, these vulnerabilities arise from design weaknesses rather than technical exploits, making them more complex to detect and even more challenging for businesses to prevent.</p><p>As businesses continue to develop complex digital applications, attackers will look for new ways to <a href="https://www.itpro.com/technology/artificial-intelligence/ai-threats-the-importance-of-a-concrete-strategy-in-fighting-novel-attacks"><u>manipulate their logic</u></a>. The only way to stay ahead is by embracing proactive security strategies—including threat modeling, manual testing, Zero Trust security, and real-time behavioral monitoring. Organizations that fail to address these vulnerabilities risk financial losses, data breaches, and reputational damage.</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/cyber-attacks/what-are-business-logic-vulnerabilities</link>
                                                                            <description>
                            <![CDATA[ Business logic vulnerabilities let attackers exploit design flaws in software, bypassing security controls to manipulate pricing, authentication, and more ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">jv4qMScdG5x2K3qRGQxSeC</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/VGzkXrzhdDXaUHzZM6tc5L-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Mon, 31 Mar 2025 22:00:26 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:20 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Cyber Attacks]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Cyber Resilience]]></category>
                                                                                                                    <dc:creator><![CDATA[ David Howell ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/RyCMPNysW5pydbG6t9n8Kh-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ null ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/VGzkXrzhdDXaUHzZM6tc5L-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[A CGI image of cubes rippling at slightly varying heights, each marked with a &#039;1&#039;, a &#039;0&#039;, or the image of an orange padlock to represent data security. It is lit in blue and purple light.]]></media:description>                                                            <media:text><![CDATA[A CGI image of cubes rippling at slightly varying heights, each marked with a &#039;1&#039;, a &#039;0&#039;, or the image of an orange padlock to represent data security. It is lit in blue and purple light.]]></media:text>
                                <media:title type="plain"><![CDATA[A CGI image of cubes rippling at slightly varying heights, each marked with a &#039;1&#039;, a &#039;0&#039;, or the image of an orange padlock to represent data security. It is lit in blue and purple light.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/VGzkXrzhdDXaUHzZM6tc5L-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Cybersecurity often focuses on traditional threats like <a href="https://www.itpro.com/software/fbi-and-cisa-say-its-time-to-delete-sql-injection-flaws-for-good"><u>SQL injection</u></a>, <a href="https://www.itpro.com/malware/28076/what-is-malware">malware</a>, and <a href="https://www.itpro.com/security/cyber-attacks/phishing-tactics-the-top-attacks-trends-in-year"><u>phishing attacks</u></a>, but a more insidious risk is quietly undermining the security of many companies —business logic vulnerabilities.</p><p>Business logic vulnerabilities pose a serious yet often overlooked threat to modern businesses. Unlike traditional security vulnerabilities, such as SQL injection or <a href="https://www.itpro.com/cross-site-scripting-xss/34411/what-is-cross-site-scripting-xss">cross-site scripting (XSS)</a>, which exploit technical weaknesses, business logic vulnerabilities arise from flaws in how an application or system processes data. </p><p>The risks posed by business logic vulnerabilities are immense. Attackers can exploit them to manipulate pricing models, bypass authentication, or even gain unauthorized access to restricted areas of an application. Because these vulnerabilities are unique to each business system, they are notoriously difficult to detect, making them a significant concern for cybersecurity teams.</p><p>Sascha Giese, tech evangelist at SolarWinds, explains to <em>ITPro</em> that business logic is at the core of how organizations process data. </p><p>“A simple example would be a ‘buy two, get one free’ offer. When you add two items to your cart, the system adjusts the price automatically. But today, business logic can get a lot more advanced,” he says. </p><p>“A system might monitor stock levels and raise prices when demand is high or even apply complex rules like adjusting prices based on a customer’s location or purchasing power.” While these processes are designed to optimize business operations, they also introduce vulnerabilities. Attackers can exploit these logical pathways to gain financial advantages, steal data, or disrupt services.</p><h2 id="a-different-kind-of-security-risk">A different kind of security risk</h2><p>Business logic vulnerabilities stand apart from traditional <a href="https://www.itpro.com/security/cyber-attacks/global-cyber-attacks-jumped-44-percent-last-year"><u>cybersecurity threats</u></a> because they do not exploit <a href="https://www.itpro.com/security/hackers-are-deliberately-poisoning-ai-systems-to-make-them-malfunction-and-theres-no-way-to-defend-against-it"><u>system defences' weaknesses</u></a>. Instead, they manipulate how a system is supposed to work. </p><p>Ray Kelly, a fellow at Black Duck, points out that business logic vulnerabilities require careful planning and a deeper understanding of a system’s inner workings. “Unlike threats such as SQL injection or cross-site scripting, which can be quickly and easily tested, business logic flaws often require multiple steps or manual processes to exploit,” Kelly says. “<a href="https://www.itpro.com/security/cyber-crime/hackers-are-using-a-new-ai-chatbot-to-wage-cyber-attacks-ghostgpt-lets-users-write-malicious-code-create-malware-and-curate-phishing-emails-and-it-costs-just-usd50-to-use"><u>Hackers</u></a> tend to favor low-hanging fruit – attacks that require minimal effort – making common vulnerabilities like SQL injection more attractive targets. In contrast, exploiting business logic flaws takes more time but can be highly rewarding.”</p><p>One example is seat spinning, where cybercriminals repeatedly hold and release airline seats to block availability and resell them for profit. These are not traditional hacks but rather an exploitation of the business model itself.</p><h2 id="why-are-business-logic-flaws-so-hard-to-spot">Why are business logic flaws so hard to spot?</h2><p>Unlike <a href="https://www.itpro.com/security/openai-bug-bounty-program-payout"><u>software bugs</u></a> that can be detected with automated tools, business logic flaws require <a href="https://www.itpro.com/software/development/the-worlds-first-ai-software-engineer-isnt-living-up-to-expectations-cognition-ais-devin-assistant-was-touted-as-a-game-changer-for-developers-but-so-far-its-fumbling-tasks-and-struggling-to-compete-with-human-workers"><u>human intuition</u></a> and creative problem-solving to uncover. </p><p>James Sherlow, systems engineering director at Cequence Security, notes that business logic abuse is unique to each application, making it difficult to apply universal security measures. “Whereas SQL and XSS can be protected by a web application firewall (WAF), for example, business logic abuse will be completely different for each application. There is not one test or signature that can be used,” Sherlow explains. “This is why these attacks need to be detected using behavioral analysis rather than traditional security testing.”</p><p>Dirk Schrader, VP of security research at Netwrix, also points out. “Automated pen-testing, even those that use an AI-based approach, has limited capabilities as it usually replicates what has been done before,” he explains to ITPro. “This is when the creativity of a human pen-tester makes a huge difference.” Since these vulnerabilities often don’t produce error messages or alerts, they go unnoticed until an attacker successfully exploits them.</p><h2 id="how-businesses-can-prevent-business-logic-vulnerabilities">How businesses can prevent business logic vulnerabilities</h2><p>Addressing business logic vulnerabilities requires a fundamental shift in a business's cybersecurity strategy. Instead of relying merely on automated security tools, organizations must integrate <a href="https://www.itpro.com/security/ransomware/building-ransomware-resilience-to-avoid-paying-out">threat modeling</a>, human-driven testing, and real-time <a href="https://www.itpro.com/security/uks-new-cyber-monitoring-centre-wants-to-create-a-digital-richter-scale-for-cyber-attacks">threat monitoring</a> into their security framework.</p><h3 class="article-body__section" id="section-1-implementing-threat-modeling"><span>1. Implementing threat modeling</span></h3><p>Rather than focusing on traditional security risks, threat modeling analyzes how an attacker might manipulate a system’s workflows. According to Sherlow, the success of threat modeling depends on company-wide collaboration, not just the security team. “The key component here is that this needs to be embedded in company culture and not owned by the security team alone,” he advocates. “Security needs to come together with <a href="https://www.itpro.com/security/developers-cant-get-a-handle-on-application-security-risks"><u>developers</u></a>, business owners, product managers, and other areas of the business to build in processes to model potential threats.”</p><h3 class="article-body__section" id="section-2-manual-penetration-testing"><span>2. Manual penetration testing</span></h3><p>Since automated tools struggle to detect business logic vulnerabilities, manual <a href="https://www.itpro.com/penetration-testing/33981/what-is-penetration-testing">penetration testing</a> remains crucial. <a href="https://www.itpro.com/security/hacking/two-thirds-of-ethical-hackers-using-generative-ai-in-bug-hunting"><u>Ethical hackers</u></a> and security analysts must test applications as if they were attackers, looking for ways to exploit business logic flaws.</p><p>Danny Jenkins, CEO and co-founder at ThreatLocker stresses that AI cannot fully replace human analysis in identifying these vulnerabilities. "Automated testing is not great at testing for business logic vulnerabilities, so they usually have to be caught by a human," Jenkins says. "Security teams can overcome some of these challenges by ensuring proper code review and giving developers the time they need to consider potential risks as they develop."</p><h3 class="article-body__section" id="section-3-adopting-a-zero-trust-approach"><span>3. Adopting a zero trust approach</span></h3><p>A <a href="https://www.itpro.com/security/network-security/358282/what-is-zero-trust"><u>zero trust security model</u></a> assumes that no system or user should be automatically trusted, even those within the organization. Dominik Birgelen, CEO of Oneclick AG, explains that zero trust architecture (ZTA) can help reduce the risk of business logic abuse. </p><p>“Zero Trust enforces continuous identity verification and context-aware access controls, ensuring users and devices are validated based on real-time risk assessments,” Birgelen explains. By applying strict access controls, session monitoring, and behavioral anomaly detection, businesses can limit an attacker’s ability to exploit logical weaknesses.</p><h3 class="article-body__section" id="section-4-monitoring-for-behavioral-anomalies"><span>4. Monitoring for behavioral anomalies</span></h3><p>Since business logic vulnerabilities often involve unexpected user behavior, real-time monitoring can help detect suspicious activity before it causes damage. <a href="https://www.itpro.com/security/cyber-crime/agentic-ai-cybersecurity-risks">AI-driven security tools</a> can analyze normal user behavior and flag anomalies—such as a sudden increase in purchase attempts, repeated coupon code use, or unusual login patterns.</p><p>Cequence Security’s Sherlow emphasizes that detection must go beyond simple IP blocking to avoid false positives. “Defeating malicious actors is not only about blocking them but also breaking their business model,” he says. Security teams must use behavioral fingerprinting to track suspicious users without accidentally blocking legitimate customers.</p><iframe allow="" height="200px" width="100%" class="position-center" data-lazy-priority="low" data-lazy-src="https://player.captivate.fm/episode/a696c78c-0d94-4bc0-b1cf-106e70c68480/" src="https://player.captivate.fm/episode/a696c78c-0d94-4bc0-b1cf-106e70c68480/"></iframe><p>Business logic vulnerabilities present a unique and growing threat that many organizations are ill-prepared to handle. Unlike traditional security flaws, these vulnerabilities arise from design weaknesses rather than technical exploits, making them more complex to detect and even more challenging for businesses to prevent.</p><p>As businesses continue to develop complex digital applications, attackers will look for new ways to <a href="https://www.itpro.com/technology/artificial-intelligence/ai-threats-the-importance-of-a-concrete-strategy-in-fighting-novel-attacks"><u>manipulate their logic</u></a>. The only way to stay ahead is by embracing proactive security strategies—including threat modeling, manual testing, Zero Trust security, and real-time behavioral monitoring. Organizations that fail to address these vulnerabilities risk financial losses, data breaches, and reputational damage.</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Red teaming comes to the fore as devs tackle AI application flaws ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Only a third of organizations employ adequate testing practices in AI <a href="https://www.itpro.com/security/developers-cant-get-a-handle-on-application-security-risks">application development</a>, according to new research, prompting calls for increased red teaming to reduce risks. </p><p>Analysis from Applause found 70% of developers are currently developing <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>applications and features, with over half (55%) highlighting <a href="https://www.itpro.com/technology/artificial-intelligence/the-pros-and-cons-of-chatbots-for-customer-service">chatbots </a>and customer support tools as their primary focus at present. </p><p>Yet despite an acceleration in <a href="https://www.itpro.com/software/development/developers-are-struggling-to-build-generative-ai-applications-heres-why">AI application development</a>, a concerning number of organizations are overlooking quality assurance (QA) efforts during the <a href="https://www.itpro.com/software/development/367842/the-four-major-software-development-lifecycle-models-and-how-they-work">software development lifecycle</a>. </p><p>The study warned this trend is having an adverse impact on both quality and long-term return on investment (ROI). </p><p>“The results of our annual AI survey underscore the need to raise the bar on how we test and roll out new <a href="https://www.itpro.com/technology/artificial-intelligence-ai/369959/what-is-generative-ai">generative AI</a> models and applications,” said Chris Sheehan, EVP of high tech &amp; AI at Applause.</p><h2 id="ai-application-development-needs-a-human-touch">AI application development needs a human touch</h2><p>A key talking point of the Applause study centered around human involvement in the development lifecycle. With developers ramping up the use of generative AI tools in their daily workflows, the need for a ‘human touch’ has become critical to identify and remediate a range of issues. </p><p>These include issues such as inaccuracy, bias, and toxicity, the study noted. </p><p>Researchers found the top QA-related activities that involve human testing include prompt and response grading (61%), accessibility testing (54%), and UX testing (57%). </p><p>Applause added that humans are also crucial in training industry-specific or ‘niche’ models, particularly with the rise of agentic AI applications that interact directly with end-users. </p><p>Notably, the study found that only one-third (33%) of organizations currently employ red team testing in application development processes. Red teaming refers to adversarial testing practices - commonly used in <a href="https://www.itpro.com/security/28133/what-is-cyber-security">cybersecurity </a>- to identify potential weak points in platforms or applications.</p><p>Researchers called for a heightened focus on red teaming in AI application development, noting that this could play a key role in highlighting the aforementioned issues such as model bias or inaccuracy. </p><h2 id="application-flaws-persist">Application flaws persist</h2><p>The study from Applause found that customer-related issues are becoming a frequent problem for enterprises. Nearly two-thirds of customers using generative Ai in 2025 reported encountering some sort of issue. </p><p>Over a third (35%) encountered biased responses, hallucinations (32%), and offensive responses (17%). </p><p>Hallucinations have been a persistent problem in AI development for some time now. </p><p>While the situation has improved markedly since the early days of the generative AI boom, the issue is still causing a degree of uncertainty among enterprise IT leaders. </p><p>In a study by KPMG in August 2024, <a href="https://www.itpro.com/technology/artificial-intelligence/ai-hallucinations-accuracy-still-top-concerns-for-uk-tech-leaders-as-adoption-continues"><u>six-in-ten tech leaders specifically highlighted hallucinations as a key concern</u></a> with adopting or building generative AI tools and applications. </p><p>Sheehan noted that positive changes are being made by development teams, however. Many enterprises surveyed by the firm are “already ahead of the curve” and are integrating AI testing measures into the development lifecycle at an earlier stage. </p><p>This includes more robust model training methods which employ “diverse, high quality” datasets. Some enterprises are also warming to red teaming practices, he added. </p><p>“While every <a href="https://www.itpro.com/technology/artificial-intelligence/nearly-half-of-execs-believe-generative-ai-will-boost-financial-performance-in-2024">generative AI use case</a> requires a custom approach to quality, human intelligence can be applied to many parts of the development process including model data, model evaluation and comprehensive testing in the real world. </p><p>“As AI seeps into every part of our existence, we need to ensure these solutions provide the exceptional experiences users demand while mitigating the risks that are inherent to the technology.”</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/security/developers-spend-17-hours-security-dont-consider-it-a-top-priority">Developers spend 17 hours a week on security — but don't consider it a top priority</a></li><li><a href="https://www.itpro.com/software/development/java-developer-productivity-challenges">Java developers are facing serious productivity issues</a></li><li><a href="https://www.itpro.com/software/want-developers-to-build-secure-software-you-need-to-ditch-these-two-programming-languages">Want developers to build secure software? You need to ditch these two programming languages</a></li></ul> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/software/development/red-teaming-comes-to-the-fore-as-devs-tackle-ai-application-flaws</link>
                                                                            <description>
                            <![CDATA[ Only a third of organizations employ adequate testing practices in AI application development, according to new research, prompting calls for increased red teaming to reduce risks. ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">CJY6ykDqJp9ePeAfV5GW5A</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/ziHSXhVq4XRsdLBsncM874-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Mon, 31 Mar 2025 10:26:02 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:07:49 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Development]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                    <category><![CDATA[Software]]></category>
                                                                                                <author><![CDATA[ ross.kelly@futurenet.com (Ross Kelly) ]]></author>                    <dc:creator><![CDATA[ Ross Kelly ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/Y5vrV2V98Np6jHAGmAtCd3-320-70.jpg ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Ross Kelly is ITPro&#039;s News &amp;amp; Analysis Editor, with a keen interest in cyber security, business leadership and emerging technologies.&lt;/p&gt;
&lt;p&gt;He graduated from Edinburgh Napier University in 2016 with a BA (Hons) in Journalism, and joined ITPro in 2022 after four years working in technology conference research.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;In his spare time, Ross enjoys cycling, walking and is an avid reader of history and non-fiction.&lt;/p&gt;
&lt;p&gt;You can contact Ross at ross.kelly@futurenet.com or on &lt;a href=&quot;https://twitter.com/rosswritesetc&quot;&gt;Twitter&lt;/a&gt; and &lt;a href=&quot;https://www.linkedin.com/in/ross-kelly-18a54411a/&quot;&gt;LinkedIn&lt;/a&gt;.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/ziHSXhVq4XRsdLBsncM874-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Female developer carrying out software security flaw remediation tasks on desktop computer in dimly-lit room with two monitors.]]></media:description>                                                            <media:text><![CDATA[Female developer carrying out software security flaw remediation tasks on desktop computer in dimly-lit room with two monitors.]]></media:text>
                                <media:title type="plain"><![CDATA[Female developer carrying out software security flaw remediation tasks on desktop computer in dimly-lit room with two monitors.]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/ziHSXhVq4XRsdLBsncM874-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Only a third of organizations employ adequate testing practices in AI <a href="https://www.itpro.com/security/developers-cant-get-a-handle-on-application-security-risks">application development</a>, according to new research, prompting calls for increased red teaming to reduce risks. </p><p>Analysis from Applause found 70% of developers are currently developing <a href="https://www.itpro.com/strategy/28181/what-is-ai">AI </a>applications and features, with over half (55%) highlighting <a href="https://www.itpro.com/technology/artificial-intelligence/the-pros-and-cons-of-chatbots-for-customer-service">chatbots </a>and customer support tools as their primary focus at present. </p><p>Yet despite an acceleration in <a href="https://www.itpro.com/software/development/developers-are-struggling-to-build-generative-ai-applications-heres-why">AI application development</a>, a concerning number of organizations are overlooking quality assurance (QA) efforts during the <a href="https://www.itpro.com/software/development/367842/the-four-major-software-development-lifecycle-models-and-how-they-work">software development lifecycle</a>. </p><p>The study warned this trend is having an adverse impact on both quality and long-term return on investment (ROI). </p><p>“The results of our annual AI survey underscore the need to raise the bar on how we test and roll out new <a href="https://www.itpro.com/technology/artificial-intelligence-ai/369959/what-is-generative-ai">generative AI</a> models and applications,” said Chris Sheehan, EVP of high tech &amp; AI at Applause.</p><h2 id="ai-application-development-needs-a-human-touch">AI application development needs a human touch</h2><p>A key talking point of the Applause study centered around human involvement in the development lifecycle. With developers ramping up the use of generative AI tools in their daily workflows, the need for a ‘human touch’ has become critical to identify and remediate a range of issues. </p><p>These include issues such as inaccuracy, bias, and toxicity, the study noted. </p><p>Researchers found the top QA-related activities that involve human testing include prompt and response grading (61%), accessibility testing (54%), and UX testing (57%). </p><p>Applause added that humans are also crucial in training industry-specific or ‘niche’ models, particularly with the rise of agentic AI applications that interact directly with end-users. </p><p>Notably, the study found that only one-third (33%) of organizations currently employ red team testing in application development processes. Red teaming refers to adversarial testing practices - commonly used in <a href="https://www.itpro.com/security/28133/what-is-cyber-security">cybersecurity </a>- to identify potential weak points in platforms or applications.</p><p>Researchers called for a heightened focus on red teaming in AI application development, noting that this could play a key role in highlighting the aforementioned issues such as model bias or inaccuracy. </p><h2 id="application-flaws-persist">Application flaws persist</h2><p>The study from Applause found that customer-related issues are becoming a frequent problem for enterprises. Nearly two-thirds of customers using generative Ai in 2025 reported encountering some sort of issue. </p><p>Over a third (35%) encountered biased responses, hallucinations (32%), and offensive responses (17%). </p><p>Hallucinations have been a persistent problem in AI development for some time now. </p><p>While the situation has improved markedly since the early days of the generative AI boom, the issue is still causing a degree of uncertainty among enterprise IT leaders. </p><p>In a study by KPMG in August 2024, <a href="https://www.itpro.com/technology/artificial-intelligence/ai-hallucinations-accuracy-still-top-concerns-for-uk-tech-leaders-as-adoption-continues"><u>six-in-ten tech leaders specifically highlighted hallucinations as a key concern</u></a> with adopting or building generative AI tools and applications. </p><p>Sheehan noted that positive changes are being made by development teams, however. Many enterprises surveyed by the firm are “already ahead of the curve” and are integrating AI testing measures into the development lifecycle at an earlier stage. </p><p>This includes more robust model training methods which employ “diverse, high quality” datasets. Some enterprises are also warming to red teaming practices, he added. </p><p>“While every <a href="https://www.itpro.com/technology/artificial-intelligence/nearly-half-of-execs-believe-generative-ai-will-boost-financial-performance-in-2024">generative AI use case</a> requires a custom approach to quality, human intelligence can be applied to many parts of the development process including model data, model evaluation and comprehensive testing in the real world. </p><p>“As AI seeps into every part of our existence, we need to ensure these solutions provide the exceptional experiences users demand while mitigating the risks that are inherent to the technology.”</p><h3 class="article-body__section" id="section-more-from-itpro"><span>MORE FROM ITPRO</span></h3><ul><li><a href="https://www.itpro.com/security/developers-spend-17-hours-security-dont-consider-it-a-top-priority">Developers spend 17 hours a week on security — but don't consider it a top priority</a></li><li><a href="https://www.itpro.com/software/development/java-developer-productivity-challenges">Java developers are facing serious productivity issues</a></li><li><a href="https://www.itpro.com/software/want-developers-to-build-secure-software-you-need-to-ditch-these-two-programming-languages">Want developers to build secure software? You need to ditch these two programming languages</a></li></ul>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
                                <item>
                                                            <title><![CDATA[ Developers spend 17 hours a week on security — but don't consider it a top priority  ]]></title>
                                                                                                <dc:content><![CDATA[ <p>Three quarters of developers spend more than 17 hours a week on security-related tasks — and one in four spends more than 25 hours each week. </p><p>That's according to a survey of 1,500 development heads, platform engineers and software engineers by security firm Checkmarx. </p><p>Despite <a href="https://www.itpro.com/software/development/software-developers-are-spending-more-time-every-week-fixing-security-issues-and-its-costing-companies-a-fortune">security's heavy impact on workloads for developers</a>, just 21% said that security is their top priority when coding — suggesting that perhaps spending more time up front could help avoid time spent on remediation down the line.</p><p>Just 42% of those surveyed said they understand the vulnerability tickets they're sent half of the time, though the majority (92.5%) of respondents rated the effectiveness of their security trainin as medium or high.</p><p>The Checkmarx report follows <a href="https://www.itpro.com/software/development/software-developers-are-spending-more-time-every-week-fixing-security-issues-and-its-costing-companies-a-fortune" target="_blank"><u>similar research from JFrog</u></a>, that found half of developers spend 19% of their weekly hours on security-related tasks — often outside normal working hours and costing companies as much as $28,000 per developer per year. </p><h2 id="the-road-to-devsecops">The road to DevSecOps</h2><p>The report examined how well development teams and security teams work together, in particular shifting from <a href="https://www.itpro.com/devops/28097/what-is-devops">DevOps</a> to more mature stages of <a href="https://www.itpro.com/software/development/devsecops-teams-are-ramping-up-the-use-of-ai-coding-tools-but-theyve-got-serious-concerns-ai-generated-code-is-causing-major-security-headaches-and-slowing-down-development-processes">development, security and operations (DevSecOps)</a>. Only 30% of companies are currently moving beyond "focusing only on the developer experience to building more sophisticated processes" — though 45% are now measuring code security. </p><p>"The massive increase in the number of development teams and DevOps pipelines within large organizations shows how critical it is for DevOps and security teams to build a shared culture for successful collaboration," said Martin Lindsay, Vice President of Regional Marketing at Checkmarx. </p><p>"With the ultimate goal of delivering high-performing code – which, by definition is secure code – these two teams are finding that improving the developer experience with application security is just the first step and that security must find a way to match the pace of agile development," Lindsay added.</p><h2 id="four-stages-to-better-security">Four stages to better security</h2><p>According to Checkmark, there are four stages to DevSecOps. The first is merely reactive about security, in which application security is "bolted on" to development and can slow development, while the second sees security teams working to pass flaws to developers, but without support or guidance.</p><p>Moving to a developer experience focused system, security tools are embedded into the development environment. In a mature DevSecOps system, security and development teams work closely together and agree on policies with goals well aligned. </p><p>The report said: "With overall market maturity in its early stages, the Checkmarx study reveals that there is not yet wide adherence to established best practices for operation and measurement of effective DevSecOps. While organizations have made forward strides, there is still more progress to be made."</p> ]]></dc:content>
                                                                                                                                            <link>https://www.itpro.com/security/developers-spend-17-hours-security-dont-consider-it-a-top-priority</link>
                                                                            <description>
                            <![CDATA[ More work on DevSecOps has been identified as a top priority for developer teams ]]>
                                                                                                            </description>
                                                                                                                                <guid isPermaLink="false">wqsroxVKAHFMkHsrxwu4HR</guid>
                                                                                                <enclosure url="https://cdn.mos.cms.futurecdn.net/rgaPWLxQbAAfySPkjMRnFW-1920-80.jpg" type="image/jpeg" length="0"></enclosure>
                                                                        <pubDate>Fri, 28 Mar 2025 11:06:48 +0000</pubDate>                                                                                                                                <updated>Thu, 19 Nov 2026 13:08:09 +0000</updated>
                                                                                                                                            <category><![CDATA[Application Security (DevSecOps)]]></category>
                                                    <category><![CDATA[Security]]></category>
                                                    <category><![CDATA[Cybersecurity]]></category>
                                                                                                                    <dc:creator><![CDATA[ Nicole Kobie ]]></dc:creator>                                                                                    <dc:source><![CDATA[ https://cdn.mos.cms.futurecdn.net/8Y8JDDTQ7XDEk49FoAFP2S-320-70.png ]]></dc:source>
                                                                <dc:description><![CDATA[ &lt;p&gt;Nicole Kobie first started writing for ITPro in 2007. As a freelance journalist covering technology and business, Nicole&#039;s work includes  bylines in New Scientist, Wired, PC Pro and many more. &lt;/p&gt;&lt;p&gt;Nicole the author of a book about the history of technology, The Long History of the Future.&lt;/p&gt; ]]></dc:description>
                                                                                                                                <cf:isSponsored>false</cf:isSponsored>
                <cf:hasAffiliateLinks>false</cf:hasAffiliateLinks>
                <cf:isPaid>false</cf:isPaid>
                                                                                                                                                                                    <media:content type="image/jpeg" url="https://cdn.mos.cms.futurecdn.net/rgaPWLxQbAAfySPkjMRnFW-1920-80.jpg">
                                                            <media:credit><![CDATA[Getty Images]]></media:credit>
                                                                                                                                                                                                                                    <media:description><![CDATA[Female software developer using AI coding tools on a desktop computer with light from screen reflecting in spectacles. ]]></media:description>                                                            <media:text><![CDATA[Female software developer using AI coding tools on a desktop computer with light from screen reflecting in spectacles. ]]></media:text>
                                <media:title type="plain"><![CDATA[Female software developer using AI coding tools on a desktop computer with light from screen reflecting in spectacles. ]]></media:title>
                                                    </media:content>
                                                    <media:thumbnail url="https://cdn.mos.cms.futurecdn.net/rgaPWLxQbAAfySPkjMRnFW-1920-80.jpg" />
                                                                                                                                                                    <content:encoded >
                            <![CDATA[
                            <article>
                                <p>Three quarters of developers spend more than 17 hours a week on security-related tasks — and one in four spends more than 25 hours each week. </p><p>That's according to a survey of 1,500 development heads, platform engineers and software engineers by security firm Checkmarx. </p><p>Despite <a href="https://www.itpro.com/software/development/software-developers-are-spending-more-time-every-week-fixing-security-issues-and-its-costing-companies-a-fortune">security's heavy impact on workloads for developers</a>, just 21% said that security is their top priority when coding — suggesting that perhaps spending more time up front could help avoid time spent on remediation down the line.</p><p>Just 42% of those surveyed said they understand the vulnerability tickets they're sent half of the time, though the majority (92.5%) of respondents rated the effectiveness of their security trainin as medium or high.</p><p>The Checkmarx report follows <a href="https://www.itpro.com/software/development/software-developers-are-spending-more-time-every-week-fixing-security-issues-and-its-costing-companies-a-fortune" target="_blank"><u>similar research from JFrog</u></a>, that found half of developers spend 19% of their weekly hours on security-related tasks — often outside normal working hours and costing companies as much as $28,000 per developer per year. </p><h2 id="the-road-to-devsecops">The road to DevSecOps</h2><p>The report examined how well development teams and security teams work together, in particular shifting from <a href="https://www.itpro.com/devops/28097/what-is-devops">DevOps</a> to more mature stages of <a href="https://www.itpro.com/software/development/devsecops-teams-are-ramping-up-the-use-of-ai-coding-tools-but-theyve-got-serious-concerns-ai-generated-code-is-causing-major-security-headaches-and-slowing-down-development-processes">development, security and operations (DevSecOps)</a>. Only 30% of companies are currently moving beyond "focusing only on the developer experience to building more sophisticated processes" — though 45% are now measuring code security. </p><p>"The massive increase in the number of development teams and DevOps pipelines within large organizations shows how critical it is for DevOps and security teams to build a shared culture for successful collaboration," said Martin Lindsay, Vice President of Regional Marketing at Checkmarx. </p><p>"With the ultimate goal of delivering high-performing code – which, by definition is secure code – these two teams are finding that improving the developer experience with application security is just the first step and that security must find a way to match the pace of agile development," Lindsay added.</p><h2 id="four-stages-to-better-security">Four stages to better security</h2><p>According to Checkmark, there are four stages to DevSecOps. The first is merely reactive about security, in which application security is "bolted on" to development and can slow development, while the second sees security teams working to pass flaws to developers, but without support or guidance.</p><p>Moving to a developer experience focused system, security tools are embedded into the development environment. In a mature DevSecOps system, security and development teams work closely together and agree on policies with goals well aligned. </p><p>The report said: "With overall market maturity in its early stages, the Checkmarx study reveals that there is not yet wide adherence to established best practices for operation and measurement of effective DevSecOps. While organizations have made forward strides, there is still more progress to be made."</p>
                                                            </article>
                            ]]>
                        </content:encoded>
                                                </item>
            </channel>
</rss>