Blog
/
/
July 15, 2025

Forensics or Fauxrensics: Five Core Capabilities for Cloud Forensics and Incident Response

This blog covers the five core capabilities that security teams should consider when evaluating a cloud forensics and incident response solution.
No items found.
Inside the SOC
Darktrace cyber analysts are world-class experts in threat intelligence, threat hunting and incident response, and provide 24/7 SOC support to thousands of Darktrace customers around the globe. Inside the SOC is exclusively authored by these experts, providing analysis of cyber incidents and threat trends, based on real-world experience in the field.
No items found.
people working and walking in officeDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
15
Jul 2025

The speed and scale at which new cloud resources can be spun up has resulted in uncontrolled deployments, misconfigurations, and security risks. It has had security teams racing to secure their business’ rapid migration from traditional on-premises environments to the cloud.

While many organizations have successfully extended their prevention and detection capabilities to the cloud, they are now experiencing another major gap: forensics and incident response.

Once something bad has been identified, understanding its true scope and impact is nearly impossible at times. The proliferation of cloud resources across a multitude of cloud providers, and the addition of container and serverless capabilities all add to the complexities. It’s clear that organizations need a better way to manage cloud incident response.

Security teams are looking to move past their homegrown solutions and open-source tools to incorporate real cloud forensics capabilities. However, with the increased buzz around cloud forensics, it can be challenging to decipher what is real cloud forensics, and what is “fauxrensics.”

This blog covers the five core capabilities that security teams should consider when evaluating a cloud forensics and incident response solution.

[related-resource]

1. Depth of data

There have been many conversations among the security community about whether cloud forensics is just log analysis. The reality, however, is that cloud forensics necessitates access to a robust dataset that extends far beyond traditional log data sources.

While logs provide valuable insights, a forensics investigation demands a deeper understanding derived from multiple data sources, including disk, network, and memory, within the cloud infrastructure. Full disk analysis complements log analysis, offering crucial context for identifying the root cause and scope of an incident.

For instance, when investigating an incident involving a Kubernetes cluster running on an EC2 instance, access to bash history can provide insights into the commands executed by attackers on the affected instance, which would not be available through cloud logs alone.

Having all of the evidence in one place is also a capability that can significantly streamline investigations, unifying your evidence be it disk images, memory captures or cloud logs, into a single timeline allowing security teams to reconstruct an attacks origin, path and impact far more easily. Multi–cloud environments also require platforms that can support aggregating data from many providers and services into one place. Doing this enables more holistic investigations and reduces security blind spots.

There is also the importance of collecting data from ephemeral resources in modern cloud and containerized environments. Critical evidence can be lost in seconds as resources are constantly spinning up and down, so having the ability to capture this data before its gone can be a huge advantage to security teams, rather than having to figure out what happened after the affected service is long gone.

darktrace / cloud, cado, cloud logs, ost, and memory information. value of cloud combined analysis

2. Chain of custody

Chain of custody is extremely critical in the context of legal proceedings and is an essential component of forensics and incident response. However, chain of custody in the cloud can be extremely complex with the number of people who have access and the rise of multi-cloud environments.

In the cloud, maintaining a reliable chain of custody becomes even more complex than it already is, due to having to account for multiple access points, service providers and third parties. Having automated evidence tracking is a must. It means that all actions are logged, from collection to storage to access. Automation also minimizes the chance of human error, reducing the risk of mistakes or gaps in evidence handling, especially in high pressure fast moving investigations.

The ability to preserve unaltered copies of forensic evidence in a secure manner is required to ensure integrity throughout an investigation. It is not just a technical concern, its a legal one, ensuring that your evidence handling is documented and time stamped allows it to stand up to court or regulatory review.

Real cloud forensics platforms should autonomously handle chain of custody in the background, recording and safeguarding evidence without human intervention.

3. Automated collection and isolation

When malicious activity is detected, the speed at which security teams can determine root cause and scope is essential to reducing Mean Time to Response (MTTR).

Automated forensic data collection and system isolation ensures that evidence is collected and compromised resources are isolated at the first sign of malicious activity. This can often be before an attacker has had the change to move latterly or cover their tracks. This enables security teams to prevent potential damage and spread while a deeper-dive forensics investigation takes place. This method also ensures critical incident evidence residing in ephemeral environments is preserved in the event it is needed for an investigation. This evidence may only exist for minutes, leaving no time for a human analyst to capture it.

Cloud forensics and incident response platforms should offer the ability to natively integrate with incident detection and alerting systems and/or built-in product automation rules to trigger evidence capture and resource isolation.

4. Ease of use

Security teams shouldn’t require deep cloud or incident response knowledge to perform forensic investigations of cloud resources. They already have enough on their plates.

While traditional forensics tools and approaches have made investigation and response extremely tedious and complex, modern forensics platforms prioritize usability at their core, and leverage automation to drastically simplify the end-to-end incident response process, even when an incident spans multiple Cloud Service Providers (CSPs).

Useability is a core requirement for any modern forensics platform. Security teams should not need to have indepth knowledge of every system and resource in a given estate. Workflows, automation and guidance should make it possible for an analyst to investigate whatever resource they need to.

Unifying the workflow across multiple clouds can also save security teams a huge amount of time and resources. Investigations can often span multiple CSP’s. A good security platform should provide a single place to search, correlate and analyze evidence across all environments.

Offering features such as cross cloud support, data enrichment, a single timeline view, saved search, and faceted search can help advanced analysts achieve greater efficiency, and novice analysts are able to participate in more complex investigations.

5. Incident preparedness

Incident response shouldn't just be reactive. Modern security teams need to regularly test their ability to acquire new evidence, triage assets and respond to threats across both new and existing resources, ensuring readiness even in the rapidly changing environments of the cloud.  Having the ability to continuously assess your incident response and forensics workflows enables you to rapidly improve your processes and identify and mitigate any gaps identified that could prevent the organization from being able to effectively respond to potential threats.

Real forensics platforms deliver features that enable security teams to prepare extensively and understand their shortcomings before they are in the heat of an incident. For example, cloud forensics platforms can provide the ability to:

  • Run readiness checks and see readiness trends over time
  • Identify and mitigate issues that could prevent rapid investigation and response
  • Ensure the correct logging, management agents, and other cloud-native tools are appropriately configured and operational
  • Ensure that data gathered during an investigation can be decrypted
  • Verify that permissions are aligned with best practices and are capable of supporting incident response efforts

Cloud forensics with Darktrace

Darktrace delivers a proactive approach to cyber resilience in a single cybersecurity platform, including cloud coverage. Darktrace / CLOUD is a real time Cloud Detection and Response (CDR) solution built with advanced AI to make cloud security accessible to all security teams and SOCs. By using multiple machine learning techniques, Darktrace brings unprecedented visibility, threat detection, investigation, and incident response to hybrid and multi-cloud environments.

Darktrace’s cloud offerings have been bolstered with the acquisition of Cado Security Ltd., which enables security teams to gain immediate access to forensic-level data in multi-cloud, container, serverless, SaaS, and on-premises environments.

[related-resource]

Need help evaluating cloud security solutions?

Discover five essential capabilities for effective cloud forensics and incident response and how AI-based security solutions can make a difference.

No items found.
Inside the SOC
Darktrace cyber analysts are world-class experts in threat intelligence, threat hunting and incident response, and provide 24/7 SOC support to thousands of Darktrace customers around the globe. Inside the SOC is exclusively authored by these experts, providing analysis of cyber incidents and threat trends, based on real-world experience in the field.
No items found.

More in this series

No items found.

Blog

/

/

May 20, 2026

Prompt Security in Enterprise AI: Strengths, Weaknesses, and Common Approaches

prompt securityDefault blog imageDefault blog image

How enterprise AI Agents are changing the risk landscape  

Generative AI Agents are changing the way work gets done inside enterprises, and subsequently how security risks may emerge. Organizations have quickly realized that providing these agents with wider access to tooling, internal information, and granting permissions for the agent to perform autonomous actions can greatly increase the efficiency of employee workflows.

Early deployments of Generative AI systems led many organizations to scope individual components as self-contained applications: a chat interface, a model, and a prompt, with guardrails placed at the boundary. Research from Gartner has shown that while the volume and scope of Agentic AI deployments in enterprise environments is rapidly accelerating, many of the mechanisms required to manage risk, trust, and cost are still maturing.

The issue now resides on whether an agent can be influenced, misdirected, or manipulated in ways that leads to unsafe behavior across a broader system.

Why prompt security matters in enterprise AI

Prompt security matters in enterprise AI because prompts are the primary way users and systems interact with Agentic AI models, making them one of the earliest and most visible indicators of how these systems are being used and where risk may emerge.

For security teams, prompt monitoring is a logical starting point for understanding enterprise AI usage, providing insight into what types of questions are being asked and tasks are being given to AI Agents, how these systems are being guided, and whether interactions align with expected behavior. Complete prompt security takes this one step further, filtering out or blocking sensitive or dangerous content to prevent risks like prompt injection and data leakage.

However, visibility only at the prompt layer can create a false sense of security. Prompts show what was asked, but not always why it was asked, or what downstream actions were triggered by the agent across connected systems, data sources, or applications.

What prompt security reveals  

The primary function of prompt security is to minimize risks associated with generative and agentic AI use, but monitoring and analysis of prompts can also grant insight into use cases for particular agents and model. With comprehensive prompt security, security teams should be able to answer the following questions for each prompt:

  • What task was the user attempting to complete?
  • What data was included in the request, and was any of the data high-risk or confidential?
  • Was the interaction high-risk, potentially malicious, or in violation of company policy?
  • Was the prompt anomalous (in comparison to previous prompts sent to the agent / model)?

Improving visibility at this layer is a necessary first step, allowing organizations to establish a baseline for how AI systems are being used and where potential risks may exist.  

Prompt security alone does not provide a complete view of risk. Further data is needed to understand how the prompt is interpreted, how context is applied, what autonomous actions the agent takes (if any), or what downstream systems are affected. Understanding the outcome of a query is just as important for complete prompt security as understanding the input prompt itself – for example, a perfectly normal, low-risk prompt may inadvertently result in an agent taking a high-risk action.

Comprehensive AI security systems like Darktrace / SECURE AI can monitor and analyze both the prompt submitted to a Generative AI system, as well as the responses and chain-of-thought of the system, providing greater insight into the behavior of the system. Darktrace / SECURE AI builds on the core Darktrace methodology, learning the expected behaviors of your organization and identifying deviations from the expected pattern of life.

How organizations address prompt security today

As prompt-level visibility has become a focus, a range of approaches have emerged to make this activity more observable and controllable. Various monitoring and logging tools aim to capture prompt inputs to be analyzed after the fact.  

Input validation and filtering systems attempt to intervene earlier, inspecting prompts before they reach the model. These controls look for known jailbreak patterns, language indicative of adversarial attacks, or ambiguous instructions which could push the system off course.

Importantly, for a prompt security solution to be accurate and effective, prompts must be continually observed and governed, rather than treated as a point-in-time snapshot.  

Where prompt security breaks down in real environments

In more complex environments, especially those involving multiple agents or extensive tool use, AI security becomes harder to define and control.

Agent-to-Agent communications can be harder to monitor and trace as these happen without direct user interaction. Communication between agents can create routes for potential context leakage between agents, unintentional privilege escalation, or even data leakage from a higher privileged agent to a lower privileged one.

Risk is shaped not just by what is asked, but by the conditions in which that prompt operates and the actions an agent takes. Controls at the orchestration layer are starting to reflect this reality. Techniques such as context isolation, scoped memory, and role-based boundaries aim to limit how far a prompt’s influence can extend.  

Furthermore, Shadow AI usage can be difficult to monitor. AI systems that are deployed outside of formal governance structures and Generative AI systems hosted on unknown endpoints can fly under the radar and can go unseen by monitoring tools, leaving a critical opening where adversarial prompts may go undetected. Darktrace / SECURE AI features comprehensive detection of Shadow AI usage, helping organizations identify potential risk areas.

How prompt security fits in a broader AI risk model

Prompt security is an important starting point, but it is not a complete security strategy. As AI systems become more integrated into enterprise environments, the risks extend to what resources the system can access, how it interprets context, and what actions it is allowed to take across connected tools and workflows.

This creates a gap between visibility and control. Prompt security alone allows security teams to observe prompt activity but falls short of creating a clear understanding of how that activity translates into real-world impact across the organization.

Closing that gap requires a broader approach, one that connects signals across human and AI agent identities, SaaS, cloud, and endpoint environments. It means understanding not just how an AI system is being used, but how that usage interacts with the rest of the digital estate.

Prompt security, in that sense, is less of a standalone solution and more of an entry point into a larger problem: securing AI across the enterprise as a whole.

Explore how Darktrace / SECURE AI brings prompt security to enterprises

Darktrace brings more than a decade of AI expertise, built on an enterprise‑wide platform designed to operate in and understand the behaviors of the complex, ambiguous environments where today’s AI now lives. With Darktrace / SECURE AI, enterprises can safely adopt, manage, monitor, and build AI within their business.  

Learn about Darktrace / SECURE AI here.

Sign up today to stay informed about innovations across securing AI.

[related-resource]

Continue reading
About the author
Jamie Bali
Technical Author (AI) Developer

Blog

/

/

May 20, 2026

State of AI Cybersecurity 2026: 77% of security stacks include AI, but trust is lagging

Default blog imageDefault blog image

Findings in this blog are taken from Darktrace’s annual State of AI Cybersecurity Report 2026.

AI is a contributing member of nearly every modern cybersecurity team. As we discussed earlier in this blog series, rapid AI adoption is expanding the attack surface in ways that security professionals have never before experienced while also empowering attackers to operate at unprecedented speed and scale. It’s only logical that defenders are harnessing the power of AI to fight back.

After all, AI can help cybersecurity teams spot the subtle signs of novel threats before humans can, investigate events more quickly and thoroughly, and automate response. But although AI has been widely adopted, this technology is also frequently misunderstood, and occasionally viewed with suspicion.

For CISOs, the cybersecurity marketplace can be noisy. Making sense of competing vendors’ claims to distinguish the solutions that truly deliver on AI’s full potential from those that do not isn’t always easy. Without a nuanced understanding of the different types of AI used across the cybersecurity stack, it is difficult to make informed decisions about which vendors to work with or how to gain the most value from their solutions. Many security leaders are turning to Managed Security Service Providers (MSSPs) for guidance and support.

The right kinds of AI in the right places?

Back in 2024, when we first conducted this annual survey, more than a quarter of respondents were only vaguely familiar with generative AI or hadn’t heard of it at all. Today, GenAI plays a role in 77% of security stacks. This percentage marks a rapid increase in both awareness and adoption over a relatively short period of time.

According to security professionals, different types of AI are widely integrated into cybersecurity tooling:

  • 67% report that their organization’s security stack uses supervised machine learning
  • 67% report that theirs uses agentic AI
  • 58% report that theirs uses natural language processing (NLP)
  • 35% report that theirs uses unsupervised machine learning

But their responses suggest that organizations aren’t always using the most valuable types of AI for the most relevant use cases.

Despite all the recent attention AI has gotten, supervised machine learning isn’t new. Cybersecurity vendors have been experimenting with models trained on hand-labeled datasets for over a decade. These systems are fed large numbers of examples of malicious activity – for instance, strains of ransomware – and use these examples to generalize common indicators of maliciousness – such as the TTPs of multiple known ransomware strains – so that the models can identify similar attacks in the future. This approach is more effective than signature-based detection, since it isn’t tied to an individual byte sequence or file hash. However, supervised machine learning models can miss patterns or features outside the training data set. When adversarial behavior shifts, these systems can’t easily pivot.

Unsupervised machine learning, by contrast, can identify key patterns and trends in unlabeled data without human input. This enables it to classify information independently and detect anomalies without needing to be taught about past threats. Unsupervised learning can continuously learn about an environment and adapt in real time.

One key distinction between supervised and unsupervised machine learning is that supervised learning algorithms require periodic updating and re-training, whereas unsupervised machine learning trains itself while it works.

The question of trust

Even as AI moves into the mainstream, security professionals are eyeing it with a mix of enthusiasm and caution. Although 89% say they have good visibility into the reasoning behind AI-generated outputs, 74% are limiting AI’s ability to take autonomous action in their SOC until explainability improves. 86% do not allow AI to take even small remediation actions without human oversight.

This model, commonly known as “human in the loop,” is currently the norm across the industry. It seems like a best-of-both-worlds approach that allows teams to experience the benefits of AI-accelerated response without relinquishing control – or needing to trust an AI system.

Keeping humans somewhat in the loop is essential for getting the best out of AI. Analysts will always need to review alerts, make judgement calls, and set guardrails for AI's behavior. Their input helps AI models better understand what “normal” looks like, improving their accuracy over time.

However, relying on human confirmation has real costs – it delays response, increases the cognitive burden analysts must bear, and creates potential coverage gaps when security teams are overwhelmed or unavailable. The traditional model, in which humans monitor and act on every alert, is no longer workable at scale.

If organizations depend too heavily on in-the-loop humans, they risk recreating the very problem AI is meant to solve: backlogs of alerts waiting for analyst review. Removing the human from the loop can buy back valuable time, which analysts can then invest in building a proactive security posture. They can also focus more closely on the most critical incidents, where human attention is truly needed.

Allowing AI to operate autonomously requires trust in its decision-making. This trust can be built gradually over time, with autonomous operations expanding as trust grows. But it also requires knowledge and understanding of AI — what it is, how it works, and how best to deploy it at enterprise scale.

Looking for help in all the right places

To gain access to these capabilities in a way that’s efficient and scalable, growing numbers of security leaders are looking for outsourced support. In fact, 85% of security professionals prefer to obtain new SOC capabilities in the form of a managed service.

This makes sense: Managed Security Service Providers (MSSPs) can deliver deep, continuously available expertise without the cost and complexity of building an in-house team. Outsourcing also allows organizations to scale security coverage up or down as needs change, stay current with evolving threats and regulatory requirements, and leverage AI-native detection and response without needing to manage the AI tools themselves.

Preferences for MSSP-delivered security operations are particularly strong in the education, energy (87%), and healthcare sectors. This makes sense: all are high-value targets for threat actors, and all tend to have limited cybersecurity budgets, so the need for a partner who can deliver affordable access to expertise at scale is strong. Retailers also voiced a strong preference for MSSP-delivered services. These companies are tasked with managing large volumes of consumer personal and financial data, and with transforming an industry traditionally thought of as a late adopter to a vanguard of cyber defense. Technology companies, too, have a marked preference for SOC capabilities delivered by MSSPs. This may simply be because they understand the complexity of the threat landscape – and the advantages of specialized expertise — so well.

In order to help as many organizations as possible – from major enterprises to small and midmarket companies – benefit from enterprise-grade, AI-native security, Darktrace is making it easier for MSSPs to deliver its technology. The ActiveAI Security Portal introduces an alert dashboard designed to increase the speed and efficiency of alert triage, while a new AI-powered managed email security solution is giving MSSPs an edge in the never-ending fight against advanced phishing attacks – helping partners as well as organizations succeed on the frontlines of cyber defense.

Explore the full State of AI Cybersecurity 2026 report for deeper insights into how security leaders are responding to AI-driven risks.

Learn more about securing AI in your enterprise.

[related-resource]

Continue reading
About the author
The Darktrace Community
Your data. Our AI.
Elevate your network security with Darktrace AI