A security analyst asks an AI agent to summarize a customer file. The agent has valid credentials, approved tools and no sign of intrusion, yet still returns information it should not disclose or claims a task was completed when it was not.
That is the operational gap CrowdStrike expects to address through two planned acquisitions: Fiddler AI for observing agent behavior and Dreadnode for AI security testing. The combined reported price is $495 million, making the deals a substantial bet that enterprises will buy security controls for AI systems within the Falcon platform.
- CrowdStrike plans to acquire Fiddler AI and Dreadnode in separate transactions.
- Fiddler’s technology will be offered as Falcon Observe, while Dreadnode’s testing results are expected to feed Falcon Guardian.
- The reported purchase prices are about $400 million for Fiddler and $95 million for Dreadnode.
- Both acquisitions are expected to close by Jan. 31, 2027.
- Dreadnode’s technology can test systems against more than 100 attack strategies, including jailbreaks and prompt injection.
What CrowdStrike is buying
The acquisitions cover different stages of the AI lifecycle. Dreadnode focuses on automated security evaluation before production. Its technology is designed to test AI models, applications, agents, reasoning loops and Model Context Protocol servers against more than 100 attack strategies.
CrowdStrike says Dreadnode can run tests described in ordinary language. It can prioritize issues by impact and associate discovered weaknesses with several security frameworks, including the MITRE ATLAS knowledge base, NIST AI Risk Management Framework and OWASP guidance for large language models and agentic systems. Testing results are also intended to shape protection policies in Falcon Guardian.
Fiddler supplies the post-deployment side. Its technology evaluates agent accuracy, task completion and policy compliance before release, then traces decisions, reasoning paths and tool calls in production. Planned Falcon Observe features include detection of behavioral drift, hallucinations and unintended actions, along with records of agent activity for compliance and audit purposes.
Bankinfosecurity reported that Falcon Observe could become generally available as soon as this month, while Dreadnode’s automated AI security testing was expected to become generally available between then and February. CSO Online instead placed both capabilities on a later schedule: availability during CrowdStrike’s fiscal 2027 fourth quarter. The reports therefore differ on rollout timing, though both identify the acquisitions as extending Falcon across the AI deployment lifecycle.
Why AI security testing changes the risk model
Conventional application testing generally examines functions built around defined rules. An AI agent may instead interpret instructions, choose tools, retrieve information and take actions based on probabilistic outputs. That flexibility creates failures that do not necessarily look like a compromised system.
Androguider described a particularly awkward case: an agent tied to email, customer databases or internal applications might be induced to leak information or perform unauthorized operations. The same outcome could emerge without an attack if its instructions are ambiguous or its reasoning is faulty.
AI security testing addresses this by probing behavior before release. Agent observability then provides evidence of what happened afterward. Neither function is a complete replacement for the other. Testing cannot enumerate every production condition, while monitoring may flag degradation only after exposure has occurred.
The acquisitions would also give CrowdStrike a way to connect AI-related telemetry with its endpoint, identity, cloud and threat-intelligence products. That is strategically valuable because a separate dashboard for agent behavior can leave defenders with fragmented evidence. The trade-off is concentration: buyers gain a unified workflow but increase their dependence on a vendor whose controls will govern a rapidly evolving class of systems.
The practical gap for security teams
Say you operate an agent with access to customer records and an internal ticketing system. Before deployment, you could use Dreadnode-style tests to check whether prompt injection, unsafe tool use or data leakage appears under known attack strategies. After release, Fiddler-style telemetry could show whether the agent began making different tool calls, drifting from approved behavior or producing records that cannot be reconciled with its stated reasoning.
For defenders, the immediate priority is not buying a product category by name. It is determining which agents can act, what data they can reach and how their decisions are recorded. Testing without production evidence can miss context-dependent failures. Production monitoring without adversarial tests can normalize unsafe behavior as “the model’s decision.”
The reported scope also raises governance questions. Bankinfosecurity noted that CrowdStrike has previously bought SGNL for continuous identity and Seraphic for browser-session visibility. The Seraphic deal closed in February, while SGNL also closed that month. Combining agent permissions, browser activity and model behavior may support stronger correlation, but it also creates substantial data-governance requirements around prompts, tool arguments, retrieved content and audit records.
What to watch next
CSO Online reported that Dreadnode’s team will join CrowdStrike’s Cyber Superintelligence Lab, but the company did not specify how the Fiddler team would be integrated. That detail matters as much as the product roadmap.
The acquisitions are not expected to close until Jan. 31, 2027. Before then, readers should watch the differing availability claims, the treatment of customer data, integration with Falcon Guardian and the practical quality of attack coverage and production tracing.
There is also a financial reason to look beyond the launch schedule. The reported $495 million total price means CrowdStrike must demonstrate that Fiddler and Dreadnode can produce measurable risk reduction, not merely attractive product demonstrations.
Bottom line: CrowdStrike is making a clear strategic bet on AI security testing and agent observability. The approach fits a real control gap, but the timeline is unsettled and the platform’s value will depend on evidence that defenders can use before and after deployment.
Key takeaways
- Separate pre-deployment AI security testing from post-deployment observability; the reports position the acquisitions as complementary rather than interchangeable.
- Treat agents with valid credentials as a distinct security risk because flawed decisions and unsupported actions do not require compromise.
- Evaluate proposed tools against operational needs: attack coverage, severity ranking, reasoning traces, tool-call records, policy integration and auditability.
- Compare the reported rollouts carefully, since CSO Online and Bankinfosecurity describe different availability windows for the acquired capabilities.
- Watch integration details and data governance as closely as product features, especially for tools that record prompts, retrieved content and agent actions.
Frequently asked questions
What is CrowdStrike acquiring Fiddler AI and Dreadnode for?
Fiddler adds agent observability and explainability through Falcon Observe. Dreadnode adds automated AI security testing intended to find weaknesses before systems reach production.
What AI security testing capabilities does Dreadnode provide?
Dreadnode can test models, applications, agents, reasoning loops and MCP servers against more than 100 attack strategies. It can also rank findings and map them to established AI security frameworks.
How much are the two acquisitions expected to cost?
The reported prices are $400 million for Fiddler and $95 million for Dreadnode. That puts the total near $495 million; most is reportedly cash, with some stock subject to vesting conditions.
When will the acquisitions close?
Bankinfosecurity reported an expected closing date of Jan. 31, 2027. The publications gave different timelines for general availability of the offerings.
Are existing antivirus, EDR and endpoint controls enough for AI agents?
They remain important for conventional infrastructure and runtime activity, but agents add decision, tool-use and permission risks. The reported acquisitions are intended to cover those AI-specific stages through testing and observability.