Federal Reserve warns AI-powered cyberattacks and rogue agents threaten financial stability

Posted in Commentary with tags , on November 16, 2026 by itnerd

The Federal Reserve’s latest Financial Stability Report identifies AI-enabled cyberattacks and autonomous AI systems as emerging threats to the U.S. financial system.

In a survey of financial market participants, 87% identified AI as a significant risk, citing concerns including sophisticated cyberattacks, damage caused by advanced AI models and disruptions to critical financial infrastructure.

Speaking Monday, Federal Reserve Governor Michael Barr warned that AI agents have already demonstrated an ability to cross security boundaries and exploit vulnerabilities previously considered too difficult to attack. He also highlighted concerns about rogue agents operating outside human instructions and AI-powered attackers accelerating the discovery and exploitation of security weaknesses.

Barr noted that major banks are already encountering AI agents attempting to act on customer accounts without being able to verify authorization or consent. He warned that autonomous agents could also accelerate financial transactions during periods of market stress, potentially overwhelming existing safeguards.

Seemant Sehgal, Founder & CEO, BreachLock

“What Barr described is something security practitioners have been calling out for months. AI agents are crossing authorization boundaries because the providers shipping them haven’t built the operational discipline to govern how they’re used, nor has it been widely prioritized outside of specialized cybersecurity companies. Banks can’t verify authenticity, consent, or alignment with customer instructions because the agents calling them have no identity layer, no authorization gate, and no accountability for who they’re acting on behalf of. That’s a design problem on the AI provider side, and banks shouldn’t be the only ones expected to solve it.

“This is the retail banking version of the same problem the FBI named in the ARTEX advisory three days earlier. You can’t react your way out of agentic risk at any level of the financial system. The four major US banks that restricted third-party AI agents in October are responding to exactly this. Restrictions buy time. They don’t fix the underlying issue. Until AI providers build authentication, consent, and scope enforcement into the agents they ship, banks will keep detecting the consequences after the fact.”

ㅤ

Darin Fredde, Senior Director and Offensive Security Evangelist, Ridge Security

“We have been asking some version of this question for a while: what authority are we giving AI agents, and what evidence proves they stay within it? Once an agent can move money, that question becomes rather less academic. “Trust me, the customer said it was fine” is not a banking control, even when delivered by a very articulate chatbot. Barr’s account of banks encountering agents whose customer authorization they cannot verify gets to the heart of the problem. Identifying an agent, establishing whom it represents and confirming permission for a particular transaction are separate requirements. A successful login should not become a blank check for everything an agent decides would be helpful.

“My recommendation is to enforce those boundaries outside the model. Give agents narrowly defined permissions, bind consent to specific actions, and make access revocable. Higher-impact actions should require stronger verification. Then test whether those controls stop an agent that misunderstands instructions, encounters malicious content, or finds an unexpected route to its goal.

“There is also a harder problem: individually authorized actions can still produce a dangerous collective outcome. If many agents respond to the same signal by moving funds at once, every transaction could follow its customer’s instructions while the combined effect intensifies financial stress. Institutions should test that possibility alongside unauthorized access. AI also gives defenders an opportunity to find and validate weaknesses sooner. We should use it. But finding a vulnerability, fixing it and proving the fix works are three different accomplishments. The Fed’s warning adds urgency to a familiar security discipline: define authority, enforce limits, and verify outcomes. A more capable agent makes that discipline more valuable.”

ㅤ

John Strand, Owner, Black Hills Information Security

“Follow the money. When major financial institutions start raising concerns about cybersecurity, that tells us two things.

“First, the threat is real. The impact of agentic AI automation and AI-driven attacks is becoming a serious conversation among CEOs, CFOs, and boards of directors. This is no longer just a technical discussion inside security teams.

“Second, never let a good crisis go to waste.

“For years, security teams have struggled to get the funding they need. And I’m not just talking about buying more technology or throwing AI at the problem. I’m talking about hiring people, training them, and giving defensive teams the resources they need to protect their organizations.

“If you’re leading a security team, you should be putting these stories in front of your executives and using them to drive conversations about funding, staffing, and training.

“Because here’s the problem. Defense always lags behind offense. You can’t just write a check and suddenly have an effective security program. It takes months to hire people, train them, integrate technologies, and build the processes needed to respond.

“And with AI accelerating the speed of attacks, that gap is only going to become more dangerous.

“The right time to start preparing isn’t after an attack. It’s right now.”

ㅤ

Ryan McCurdy, Vice President of Marketing, Liquibase

“Governor Barr’s warning is that we’re seeing AI agents cross security boundaries even when they aren’t acting maliciously. An agent can have legitimate access, be given a legitimate objective, and still take an action nobody authorized.

“This becomes concerning in financial services, where a mistake involving a critical system can have consequences well beyond an individual application. As AI agents take on more responsibility across software development and IT operations, enterprises need to rethink how they enforce control.

“AI agents operate probabilistically, making decisions that aren’t always predictable. That’s one thing when generating code. It’s another when an agent is making changes to a production database or interacting with critical financial infrastructure. You can’t afford to guess.

“That’s why enterprises need deterministic controls around probabilistic systems. It’s not enough to verify an agent’s identity or give it permission to access a system. Independent policies need to govern what it’s actually allowed to change, block dangerous operations, require approvals where necessary, and maintain audit evidence of what happened.

“The same enterprise standards need to apply whether a database change comes from a developer, an automated pipeline, or an AI agent.”

Financial Services have had their two minute warning. We saw this happen to virtual currency companies like Binance. And take my word that Financial Services companies are next.

How is AI going to impact Black Friday and Cyber-Monday – Good or Bad?

Posted in Commentary with tags , on November 16, 2026 by itnerd

Folks across the tech industry have probably been reaching out to me about how Black Friday and Cyber Monday put retailers to the test when it comes to downtime and cyberattacks.

But this year, there’s a new wrinkle. AI is changing who’s doing the shopping. And, the biggest challenge for retailers may not only be their websites, but also the databases and infrastructure (storage, networking, you name it) behind them.

Here are some interesting stats:

  • AI shopping is taking off. YouGov’s October 2026 research found that 34% of likely Black Friday and Cyber Monday shoppers plan to use AI, more than double last year’s 16%.
  • Accuracy is already a concern. The same YouGov research found that 56% of AI shoppers are concerned about inaccurate or outdated information. That puts a spotlight on the importance of reliable, up-to-date retail data.
  • AI agents are moving closer to checkout. HUMAN Security’s 2026 research found that in 2025, 8.8% of observed agentic AI activity occurred on account pages and 2.3% on checkout pages. AI isn’t just searching for products anymore.

Don Boxley, CEO and Co-Founder of DH2i, had this to say about why retailers need to start thinking beyond website traffic and take a closer look at the databases, infrastructure, and security behind the checkout button.

“For quite some time, Black Friday has been a stress test for most retailers. But this year, there’s a new shopper in the mix: AI. Now consumers can let AI do all the legwork. From comparing prices and checking inventory, to refreshing pages to grab that must-have gift. That’s pretty convenient, right? But, what does that mean for those behind the scenes? Think about it… Every one of those requests depends on databases delivering accurate, up-to-date information. But now, retailers have all this additional automated activity to contend with, on top of the usual holiday hubbub.

Here’s what worries me… For years, retailers have worked on updating and making sure their websites can handle the crowds. But what good is a website that loads perfectly and looks great if the database behind it can’t confirm inventory or process an order? Just because a server is running doesn’t mean the database is healthy, or even available for that matter. Retailers still need to make sure their databases can handle the demand, remain available when something goes wrong, and recover quickly when there’s a failure.

And, let’s not forget about security. Not every AI agent is a bad actor. Many/most are legitimate shoppers trying to spend money. That’s a very good thing. However, other AI ‘visitors’ may be looking for vulnerabilities or ways into systems they have no business accessing. Retailers can’t just shut the door on automated traffic, but they can’t give everyone the keys to the kingdom, either. They need to protect their critical infrastructure and make sure every connection has access to only what it needs.

So, the big question this Black Friday isn’t just whether retailers can handle the crowds and increase in AI-driven traffic. It’s whether the databases and infrastructure behind the checkout button can keep up, stay up, and keep the bad guys out.”

Richard Copeland, CEO of Leaseweb USA had this to add:

“We are seeing both extremes in the market… Retailers that began thinking about and planning for how AI was going to affect their business around this time last year and those that felt it was a tomorrow problem. For those that haven’t already planned and deployed the right strategy, Black Friday and Cyber Monday will likely be a nightmare. They will need to deal with surging online traffic, AI shopping bots, and increasingly sophisticated AI-driven cyberattacks. Keeping their websites and even onsite shopping experiences fast, secure, and available will likely be no walk in the park. We all know what every second of downtime or a security breach means… not only lost customers and revenue, but frustrated employees, and potential legal regulations and compliance issues.

The key advice here is, don’t put all your eggs in one basket.” Retailers can no longer afford to rely entirely on on-prem infrastructure or the public cloud. Neither alone gives them all the flexibility, control, security, and scalability they need to handle unpredictable traffic spikes, AI-driven shopping, and growing cyber threats. A hybrid approach lets them put workloads where they make the most sense. If your entire business depends on one infrastructure environment staying up, you have a bigger problem than Black Friday traffic. You have a business continuity problem. If you have taken the smart step to go hybrid, and your provider can’t provide a better strategy then simply selling you more capacity, it’s time to start talking to someone who can.”

Attackers Use Autonomous AI And Target Semiconductor, Defense, Civil Society Sectors

Posted in Commentary on November 16, 2026 by itnerd

Unit 42 researchers revealed on November 12, 2026, that Chinese-speaking attackers used an open-source AI penetration testing framework called Cairn to autonomously conduct 25 operations against at least 19 organizations. The attackers weaponized Cairn by pairing it with Chinese AI models Zhipu GLM and DeepSeek. The attackers supplied a target and a goal, then Cairn planned, executed and recorded results on its own.

These attacks achieved unauthorized access or data retrieval at 10 of the targeted organizations. They accessed dozens of valid credentials, exposed massive amounts of personal data (exceeding 1 Mil records at one organization), retrieved military and government identities, created persistent admin accounts in a production system, and modified a live industry standards-ballot document.

Darin Fredde, Senior Director and Offensive Security Evangelist, Ridge Security

“In attacker does not need your AI to misbehave. They can bring their own. Cairn is one example in a growing ecosystem of publicly available AI security tools. The same capabilities that help an organization uncover an exposed application can help an intruder pursue it. My concern is that treating the availability of these tools as the problem could leave legitimate defenders with fewer ways to test themselves, while determined attackers modify what is already available.

“We should preserve proactive defense. Organizations need opportunities to discover how their systems fail before someone else does. But access to a powerful testing tool also creates responsibilities: define its scope, constrain its privileges, and protect the information it collects. A penetration test can accumulate credentials, sensitive records, and a detailed map of an organization’s weaknesses. Its dashboard and evidence store become sensitive assets themselves. Attackers have no obligation to preserve those protections.

“In the campaign Unit 42 describes, operators used a modified framework and fabricated authorization claims that the models accepted. An authorization file written by the attacker is hardly permission from the victim. That is why responsible-use language and model guardrails cannot carry the entire security burden. They can help, but organizations need controls that continue to enforce boundaries when someone ignores the instructions, changes the model, or modifies the tool. The urgency comes from what happens after discovery. A weakness that once required an operator’s sustained attention can now become part of an automated search for access. Defenders should use that same opportunity to test exposed systems, fix exploitable paths, and verify that the fixes hold.

“I would resist broad restrictions that weaken legitimate testing without a demonstrated reduction in abuse. Give defenders the ability to investigate aggressively and require evidence that their tools respect scope and protect what they discover. Meanwhile, build enterprise defenses on the assumption that an attacker’s agent will keep trying, regardless of what its acceptable-use policy says.”

Waseem Ahmed, Head of Engineering, Secure.com

“This is a real shift. With tools like Cairn, one operator gives AI agents a one-line goal, and they handle recon, scanning, and exploit attempts. In one campaign Reuters reported, a researcher estimated the AI cost at roughly $50 per successful hack. Unit 42 says autonomous AI raises the volume and coverage of attacks, not their complexity, so the weaknesses are old ones.

The agents use normal tools, so watch behaviour, not files: bursts of scans and logins at machine speed, and access that hops between systems. Unit 42 links a separate Cairn campaign, with moderate confidence, to China-nexus intelligence collection. It targeted at least 19 organisations, including chip makers, defense and policy groups and civil society, and breached 10.

“When we aimed an AI pentest pipeline at three live systems over one weekend, it found 21 flaws, seven of them critical. That was on systems we own. Test yourself with AI first, fix fast, then test again.”

The fact that this was written up means that this is a “today” problem and should be treated as such.

150 million Kik profile images exposed in an open database

Posted in Commentary with tags on November 16, 2026 by itnerd

cCbersecurity researcher Jeremiah Fowler found a database sitting open online, with no password or encryption, holding more than 150 million images tied to the Kik messaging app. The files were split into thumbnails and originals, suggesting about 75 million unique profile pictures, including images of children and teens.

This is a serious exposure for an app whose parent company is already under investigation by Connecticut’s Attorney General over alleged lax age assurance and content moderation, practices child safety advocates have called a “predator’s paradise.”

You can find the full report here: https://www.expressvpn.com/research/kik-data-exposed

Microsoft Releases Their Root Cause Analysis In Regards To The Great Outage Of Last Week

Posted in Commentary with tags on November 16, 2026 by itnerd

In reference to the great Microsoft outage from last week, a Microsoft executive laid out the cause of the issue via a very lengthy Twitter/X post. You can read the post here.

My take on this is as follows.

  • I find it completely inconceivable that Microsoft of all companies could screw up on this scale and in this manner.
  • Related to the above I have problems believing that this isn’t connected to Microsoft laying off a ton of people.

But I might be looking at this from a very cynical point of view. Thus your opinion may differ. Please leave a comment below and share your thoughts. In the meantime you might want to consider diversifying your tech stack away from Microsoft. Just a thought.

Expert warns Microsoft’s new remote lock feature could let hackers disable hundreds of corporate device

Posted in Commentary with tags on November 16, 2026 by itnerd

Microsoft is testing a new feature that allows IT administrators to remotely lock compromised or stolen Windows devices without deleting their data. However, Cybernews information security researcher Rasa Jurgutyte warns that the same feature could become a tool for attackers.

According to Jurgutyte, there are several situations in which the feature could cause more harm than good:

The feature also doesn’t necessarily prevent data theft. If BitLocker encryption isn’t enabled, attackers with physical access may still be able to retrieve files.

The warnings come after the Stryker cyberattack, in which hackers claimed to have stolen 50 terabytes of data following a compromise of the company’s Microsoft environment.

Read the full story here: https://cybernews.com/security/microsoft-remote-lock-bitlocker-reminder/

AI-native CRM Dreamteam raises $53M to challenge incumbents with AI coworkers who actually get work done

Posted in Commentary with tags on November 16, 2026 by itnerd

For over two decades, CRMs like Salesforce and HubSpot have depended on sales teams remembering to manually enter conversational data. Dreamteam is built around the opposite idea: that, in the era of AI, CRMs should extract signals from sales conversations automatically and actually do the work to move deals forward.

Today, Dreamteam announced it has raised $53M from Accel, Together Fund, and Premji Invest to scale their AI-native CRM that understands the full context behind a customer relationship, reasons over that information, and takes action through specialized AI teammates.

Why this matters today

Legacy CRM architecture is built around structured fields and rigid hand-coded workflows, but the information AI needs to reason well is often semantic: whether a prospect sounds hesitant on price, a competitor was referenced on a call, or a board is suddenly scrutinizing costs. Any trained salesperson can make sense of those signals immediately. A legacy CRM with only a few manually updated fields can’t provide the full picture. Layering more tools fragments the customer story across systems, while the unspoken context behind decisions often goes uncaptured.

Most CRMs on the market add to the workload of sales teams that are already short on time. AI can lift that load, handling everything from operational tasks like account research, meeting prep and email drafting to strategic work like sales forecasting and win-loss analysis.

How Dreamteam works

At the heart of Dreamteam is the Company Brain, a living memory of a business built from customer conversations, emails, meetings, and workflows. It connects the dots across every interaction, capturing buyer intent, objections, competitor mentions, stakeholder dynamics, and more.

Four specialized AI coworkers turn intelligence into action:

  • Rachel, the research assistant, enriches every account and contact, with various tools.
  • Sally, the sales assistant, handles your pre-meeting prep, drafts follow-up emails and manages tasks.
  • Raj, the RevOps partner, monitors pipelines, flags deal risks and improves forecasting.
  • Alex, the CRM administrator, sets up and keeps the system running without manual overhead.

Each AI co-worker is skilled in a specific job and is ready to start work without teams having to build and train their own agents. Upstream, sales leaders stay in control and get immediate answers to questions legacy CRMs are a blind to, like which deals are stalling and why.

Customer traction

Dreamteam was co-created in close partnership with a select group of fast-growing, AI-forward GTM teams that helped shape the product. This collaborative approach ensured Dreamteam is grounded in real-world sales workflows from day one while factoring in the evolution of sales processes for the AI era.

Today, hundreds of companies across diverse industries, including AI, online media, healthcare, manufacturing, and consulting, use Dreamteam. Patrick Doyle, CEO of DMS Health says “I truly believe this is so far ahead of everything any other CRM is doing, that it would revolutionise our sales.”.

At invideo, Head of Enterprise GTM, Dhruv Dewan started off with a small group to pilot and expanded quickly to the entire sales team, with Dreamteam reviewing customer interactions each morning and surfacing insights, which were never possible before. For Plex, Inc., Co-Founder and CPO Scott Olechowski says Dreamteam’s combination of simplicity and powerful AI capabilities “hits the sweet spot,” calling its ability to work with existing AI tools like Claude, “a game changer.”

The big picture

Dreamteam was founded by Anand Venkatraman, Ramesh Parthasarathy, and Senthil Kanthaswamy, former senior executives at Freshworks who helped scale the company from its early startup days through its IPO. With over 25 years of experience each building and selling B2B software, the founders saw firsthand how traditional CRMs lose valuable customer context, leaving teams with stale pipelines and unreliable forecasts.

Having built AI applications since the GPT-2 era and scaled them to tens of thousands of businesses worldwide, the founders recognized a pivotal shift when AI reasoning made it possible for software to understand context and execute work. They saw an opportunity to reimagine CRM from the ground up, rather than simply layering AI onto existing systems.

Finite State to Reveal Results of Six-Month, AI-Driven Firmware Security Research at Hardwear.io 2026

Posted in Commentary with tags on November 16, 2026 by itnerd

Finite State today announced that Roland Lindsey, Chief Product Security Engineer, will present findings from six months of intensive firmware security research at Hardwear.io Netherlands 2026, taking place November 19–20 at the Amsterdam Marriott Hotel.

The 90-minute technical session, “140+ Detonations: What Six Months of LLM-Driven Firmware Teardowns Actually Proved,” will examine how large language models (LLMs), automated code analysis, adversarial validation, and dynamic testing can be combined to identify and verify exploitable vulnerabilities in connected devices.

Over six months, Lindsey and the research team analyzed 35 firmware images spanning embedded Linux routers, industrial controllers, automotive electronic control units (ECUs), and bare-metal real-time operating system (RTOS) devices. Across the broader research team, more than 50 firmware images were examined.

Using an LLM-driven analysis pipeline, the research identified 802 potential remote code execution (RCE) vulnerabilities involving command and code injection that survived initial triage. However, only 68 were subsequently demonstrated through reproducible proofs of vulnerability against the shipped binaries. Including successfully exploited memory-corruption vulnerabilities, the total number of demonstrated exploits exceeded 140.

The findings underscore a fundamental challenge facing manufacturers and security researchers: Identifying a potentially exploitable vulnerability is not the same as proving that an attacker can exploit it.

As AI makes automated vulnerability discovery faster and more accessible, distinguishing actionable security risks from false positives and unproven findings is becoming increasingly important.

Lindsey’s presentation will examine the research methodology, including automated firmware unpacking, decompilation, parallel AI-assisted vulnerability hunting, adversarial validation, and dynamic exploit verification under emulation.

Key takeaways:

  • A reusable teardown pipeline you can run yourself — unpack → decompile → fan-out hunt → adversarial triage → dynamic proof — not a vendor black box.
  • Why proving beats flagging, and how to tell them apart — the discipline that separates “reachable, sink confirmed” from a detonated root shell, and the guards that stop a model over-claiming its own exploit.
  • The negative results, so you skip the dead ends — what we were sure would help (e.g. reachability hints) and measurably didn’t.
  • An honest cost/quality picture — where the false positives actually live, what a teardown costs, and the bug classes automation still misses.

The negative results, so you skip the dead ends — what we were sure would help (e.g. reachability hints) and measurably didn’t.

An honest cost/quality picture — where the false positives actually live, what a teardown costs, and the bug classes automation still misses.

The session will also address unexpected findings and limitations, including:

  • Why verification matters: The substantial difference between vulnerabilities flagged during analysis and those demonstrated through reproducible exploitation.
  • The value of adversarial AI validation: How challenging and attempting to disprove initial findings can improve the reliability of automated vulnerability discovery.
  • Unexpected limitations: Why techniques such as reachability hints, initially expected to improve results, failed to provide measurable benefits in this research.
  • Practical barriers to exploitation: The challenges posed by emulation environments, complex execution conditions, and hardware architectures lacking established testing tools.
  • Real-world costs and limitations: The resources required for firmware analysis and the vulnerability classes that automated techniques still fail to detect.

The value of adversarial AI validation: How challenging and attempting to disprove initial findings can improve the reliability of automated vulnerability discovery.

Unexpected limitations: Why techniques such as reachability hints, initially expected to improve results, failed to provide measurable benefits in this research.

Practical barriers to exploitation: The challenges posed by emulation environments, complex execution conditions, and hardware architectures lacking established testing tools.

Attendees will gain a reproducible methodology for conducting AI-assisted firmware security assessments, along with practical guidance for distinguishing credible vulnerability findings from demonstrated security risks.

Presentation Details

  • Session: 140+ Detonations: What Six Months of LLM-Driven Firmware Teardowns Actually Proved
  • Speaker: Roland Lindsey, Chief Product Security Engineer, Finite State
  • Date: Thursday, November 19, 2026
  • Time: 1:30–3:00 p.m. CET
  • Location: Amsterdam Marriott Hotel, Amsterdam, Netherlands

Event: Hardwear.io Netherlands 2026

Event website: https://hardwear.io/nl-2026/

Anthropic’s IPO: the biggest test yet for AI?

Posted in Commentary with tags on November 16, 2026 by itnerd

Anthropic is due to go public later this week, in what could be the biggest test yet of how public investors value AI. Jyoti Bansal, CEO of Harness has some thoughts as to what this means: ,

“Anthropic’s IPO will be one of the biggest tests yet of how public investors value AI. Some have questioned whether it’s too early, but going public usually comes down to two things; how ready the business is, and how ready the market is. When both line up, companies tend to go. From what’s been disclosed publicly, Anthropic’s revenue has grown quickly, and its losses have been narrowing; so the timing looks right.

Much of that readiness comes from Anthropic’s focus on enterprise sales. That’s the kind of revenue public investors tend to value: recurring, tied to usage, and connected to real workflows. Enterprise workloads that sit in production tend to stay there, which makes the revenue easier to forecast.

More broadly, the IPO is also a sign that enterprise AI has definitively moved past the experimental stage. A couple of years ago the open question was whether AI works at all. Now enterprises are asking how to run it at scale, keep it safe, and show the return. Investment is likely to keep growing, since the appetite for building new things has been close to endless in every previous technology cycle. A public Anthropic will be a meaningful vote of confidence for the wider AI ecosystem.”

I guess we’ll see later this week what Anthropic gets. Becaue its a more than safe bet that OpenAI will try to get more.

Detectify launches Agentic Tooling to bring verifiable evidence to AI-led security investigations

Posted in Commentary with tags on November 16, 2026 by itnerd

Detectify, the Swedish application security platform built and trusted by hackers, today announced Agentic Tooling. It lets organizations’ own AI agents, running in their own environments, proactively investigate suspected vulnerabilities and test whether they can be exploited in running applications. A new Security Ledger lets security teams verify agents’ findings against objective evidence, ensuring informed decisions rather than relying solely on probabilistic conclusions.

The tools address a growing gap in DevSecOps. Engineering teams have built software factories that move code from commit to production in minutes. AI now writes a growing share of that code, and vulnerabilities move through the same pipelines at the same speed, which turns those software factories into vulnerability factories.

Detectify customers report that roughly 80% of the findings from their AI-driven static application security testing (SAST) tools are noise, showing that handing work to AI agents helps only if you can trust their output. Agents reason well, but they cut corners to deliver an answer and can produce a convincing report about a test they never ran.

Built for DevSecOps teams, Agentic Tooling gives agents access to the testing engines Detectify has built over more than a decade, including payload assessments sourced from its ethical hacker community, Alfred AI, and its Surface Monitoring data. The tools run in customers’ own environments through MCP and a CLI, use customers’ own agents and models, and operate only on the data customers provide.

Agentic Tooling is built for loop engineering, the emerging practice of running AI agents in automated, repeating workflows instead of prompting them by hand at every step. A CI run or scheduled job starts the loop. Findings from code scans, bug bounty reports, red teams, and Detectify’s attack surface data each become a ticket. An agent picks up the ticket, reads the relevant code, and uses Detectify’s tools to test the live application from the outside, as an attacker would, to confirm whether the issue can be exploited. Each pass takes one finding from trigger to proof, then moves on to the next. Run continuously, the loop becomes what Detectify calls a verification factory: the counterpart to the software factory, able to keep pace with the code it ships.

Detectify’s Security Ledger makes all of that work verifiable. Each time an agent uses Detectify’s tools, the ledger records the testing session, including the requests sent, payloads used, and results returned, and links the evidence back to the original ticket. Engineers can see what the agent did, what it concluded, and the proof supporting its assessment in a single timeline. Because the ledger is written by Detectify’s tools rather than the agent, and is append-only, teams can distinguish findings backed by actual tests from unsupported AI-generated conclusions. This allows organizations to scale security investigations without losing visibility into how decisions were reached.

The launch comes as security teams are already struggling to fix known vulnerabilities. Detectify’s H2 2026 Cyber Hygiene Index found that nine in ten open critical and high-severity vulnerabilities had stayed exposed for more than 90 days. Meanwhile, security teams face a growing volume of alerts that demand investigation. A 2026 study by researchers at Fudan University and Tencent found that 76% of the static-analysis alerts examined were false positives, and developers spent 10 to 20 minutes reviewing each.

Agentic Tooling builds on the Detectify MCP Server, released in May 2026, which gave AI agents access to Detectify’s security findings and scanning capabilities. Detectify plans to feed the loop with data from across its platform. For example, a newly opened port could automatically trigger an agent investigation.

Detectify Agentic Tooling is available on request starting November 16th, 2026. For more information, visit detectify.com