Have I Been Pwned has added the Suno data breach to its database, reporting that the AI music platform’s breach affected 55.3 million accounts.
The newly reported total substantially expands the known scale of the incident. According to Have I Been Pwned, the compromised information included email addresses, phone numbers and, in tens of thousands of Stripe-related records, names, physical addresses, purchase details and partial payment card information.
Have I Been Pwned can be found here: Have I Been Pwned: Check if your email address has been exposed in a data breach
The Suno breach can be found here: Have I Been Pwned: Suno Data Breach
Seemant Sehgal, Founder & CEO, BreachLock had this comment:
“When the disclosed scope of a breach grows this significantly in such a short period, it suggests that either the initial investigation was rushed or the organization lacked adequate visibility into its environment.
“The scale and variety of the exposed data raise serious questions about internal segmentation, security monitoring and incident readiness. Regulators and customers will spend less time focused on the 55.3 million figure than on what Suno knew, when it knew it and how it responded. Organizations that cannot establish what was accessed, when and from where within the first 72 hours will find their disclosure decisions harder to defend than the breach itself.”
Steven Swift, Managing Director, Suzu Labs follows with this::
“Customers have considerable breach fatigue after being notified repeatedly that their names, addresses, email addresses and other personal information have been exposed. At this point, individuals should assume that much of their personal information has already been compromised.
“The AI component is not necessarily the central issue here. There has been no public evidence directly attributing Suno’s security posture to its use of AI-generated code. However, rapidly growing AI companies may rely heavily on AI-assisted development, which can introduce security weaknesses when code is deployed without proper review and testing.
“Most breaches result from organizations failing to follow established security practices. Companies using AI in their applications, automation and infrastructure need a comprehensive security baseline and regular testing to confirm that their controls work. That should include at least annual penetration testing of hosted applications, services, internal networks and devices.
“Testing alone is not enough. Organizations also need to remediate the vulnerabilities that testing identifies. Too many companies conduct annual penetration tests only to receive the same findings year after year.”
Organizations need to consider that being pwned is the worst thing that can happen to them. If they do that, maybe then they will start to take information security seriously.
Introducing Harness Agent DLC: New Capabilities for the AI Agent Development Lifecycle
Posted in Commentary with tags Harness on July 22, 2026 by itnerdHarness today announced it is extending its platform to cover the full AI Agent Development Lifecycle (DLC), giving enterprises a single set of pipelines and controls to build, test, deploy, and run agents the same way they already ship everything else.
Every enterprise is building AI agents, but most can’t get them past internal pilots or proofs of concept. According to Gartner®, “Only 8% of organizations have agentic AI in production.” The software delivery lifecycle enterprises’ trust for shipping application code hasn’t extended to agents yet, trapping the ROI of internal AI investments. Real innovation arrives once a company can run an agent live with the same trust and confidence it has in the rest of its software.
Why AI agents break the traditional software delivery lifecycle
Traditional software works because it’s predictable. Application code is deterministic. Run the same test against the same code twice, and it produces the same result both times.
Agents don’t work that way: an agent’s underlying language model decides how to complete a task, and the same agent, given the same input, can choose a different tool or take a different action from one run to the next. A test that passes once offers no guarantee it will pass the next time. Incidents stop being reproducible on demand, which means the standard playbook for catching and fixing bugs doesn’t transfer either.
The stakes rise with the size of the business. A rogue agent can expose customer data, violate a compliance policy, or take an action nobody approved. Enterprises need a way to answer for what their agents are doing, and the traditional software delivery lifecycle was never built to give them one.
New Harness Agent DLC products and capabilities
Agent DLC closes the gap between building an agent and delivering it safely to production. Today’s launch includes five new products and capabilities spanning testing, deployment, operations, and governance:
In addition, existing Harness products already extend to agents without requiring any changes: Continuous Integration builds them like any other service, Artifact Registry tracks their versions and dependencies, AI Test Automation validates their responses in plain English criteria, and AI Cost Management extends spend visibility to every agent and model.
Securing the Agent DLC
Agents choose their own approach and path to get there, so their behavior is hard to predict and just as hard to secure. They expand their own attack surface by connecting to tools and APIs, spawning sub-agents, and inheriting trust from every model they touch. Static scans were never designed for this kind of risk. Harness is launching new security capabilities to close that gap.
Shift-left: constrain what agents can do before they ship.
Shield-right: enforce policy and maintain visibility once they’re live.
Together, these capabilities give Agent DLC a single audit trail from development to production.
Built on the Harness platform
Harness built context and intelligence directly into the platform with the Software Delivery Knowledge Graph, which captures and connects data from every stage of the delivery lifecycle, now spanning both applications and agents. Organizations relying on siloed tools don’t have that same connected view.
In June 2026, Harness introduced Autonomous Worker Agents, a platform for building and safely running AI agents inside software delivery pipelines. Worker Agents run as governed steps within those pipelines, covered by the same controls Harness already applies to every deployment.
Agent DLC extends that same context and governance across the full agent lifecycle. The pipelines, policies, approvals, and evidence that already apply to an organization’s code now apply to its agents too, so eval gates, deployment approvals, and security checks run as stages within a single pipeline, from the moment an agent is created through everything it does afterward.
Availability
Harness Agent DLC capabilities are rolling out now to Harness customers. For a full breakdown of what’s included at each stage of the lifecycle, visit this blog page.
Leave a comment »