Blog
/
Email
/
May 9, 2023

Breaking Down "ICES": An Umbrella Term With Wide Variety

Integrated Cloud Email Security (ICES) can be an effective email security solution, but Darktrace/Email's self-learning AI should be your solution of choice.
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.
Written by
Dan Fein
VP, Product
Default blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
09
May 2023

While organizing email security solutions into categories can help security teams understand the types of products available, it can also lead to generalizations that overlook important differences within those categories and can become like comparing apples to oranges.

This is true for the Integrated Cloud Email Security (ICES) category. Among the products that qualify, there are important variations in approach that can mean the difference between stopping a novel phishing attack on the first encounter and catching it as many as 13 days later.

These distinctions highlight that not all ICES products and not all AI tools are made equal, and it’s critical to look deeper than the “ICES” label when examining an email security solution. 

What is an ICES solution?

Gartner devised the term ICES in 2021 to describe an advanced email security that augments the native capabilities of email providers by using API access to analyze email content without requiring changing the MX record. 

In other words, ICES solutions integrate with an organization’s cloud email provider to filter out malicious emails.

ICES has risen in popularity as more and more organizations shift to cloud-based or hybrid email servers, and encounter new, more sophisticated threats. Organizations pair ICES with improved native capabilities of email providers. For example, in the 2023 Market Guide for Email Security, Gartner acknowledged that “Microsoft, in particular, continues to make significant investments in improving protection effectiveness and providing better configuration guidance.” 

Native capabilities can detect traditional indicators of compromise, while ICES products can detect nuanced attacks. They integrate directly with cloud-based email providers, meaning emails do not have to be rerouted for analysis, therefore reducing the time security teams would have to spend configuring and maintaining that connection or risking operational outage. 

ICES protects against sophisticated attacks

Before the rise of ICES, the mainstream email security solutions were Secure Email Gateways (SEGs), which can be characterized as tools that rely on historic data to create rules and signatures. This purely reactive approach cannot contend with the current email threat landscape, which includes attacks that abuse legitimate services, originate from compromised known senders, or are entirely novel. They also struggle to detect multi-stage attacks and insider threats

Instead, ICES products use natural language processing and natural language understanding to identify social engineering like business email compromises, spoofing, supply chain attacks, account takeovers, and more.  However, although ICES products can detect more sophisticated threats than SEGs, not all of them can stop entirely unknown attacks. 

Achieving bespoke security with AI that understands you

Even though several ICES products rely on machine learning to identify and stop malicious emails, not all AI is the same. Typically, other vendors’ AIs are trained on insights pulled from across their respective customer-bases and past attacks. However, this does not account for nuanced distinctions that arise from organizations’ sizes, industries, or even the individual employees working at each company. 

Instead, Darktrace understands you. Self-Learning AI™ focuses on the organization it is installed in, instead of generalizing across a wider pool. Darktrace even learns on a granular level, building profiles of every individual employee by analyzing behaviors like how they typically communicate, where and when they log in, the tone and sentiment of their emails, file and link sharing patterns, and hundreds of other signals. This level of specificity ensures that the email security is tailored to each specific organization. 

The ability to learn employee behavior allows Darktrace to detect what is not normal, therefore revealing sophisticated threats on the first encounter. It can detect all types of attacks, including BEC, account takeover, insider threat, compromised internal accounts, and even human error. 

But it’s the ability to stop novel attacks upon the first encounter that sets it apart. Darktrace/Email™ can detect novel email attacks an average of 13 days earlier than email security tools that are trained on knowledge of historical threats. 

Moreover, Darktrace can take precise action to respond to threats, beyond simply allowing or blocking a suspicious email. The AI makes micro-decisions to neutralize only the malicious components of emails. For example, it might flatten an attached PDF, rewrite a shared link, or file an email as junk. 

Darktrace/Email goes further than other ICES by considering the employee experience. With an employee-AI feedback loop, the AI can fine-tune security based on the employees while also providing inline security awareness training in real-time and with real-life examples. By engaging down to the employee level, Darktrace AI can even leverage personalized insights for productivity gains, sorting out graymail based on how each user prefers to interact with it. 

Putting the “I” in “ICES”

Many ICES vendors emphasize the “integrated” part of the acronym, however Darktrace excels at this. Since Darktrace can be installed anywhere a company has data, it can natively interact across the digital estate, saving the security team time and resources otherwise spent learning various dashboards and languages, correlating data across different areas, and manually monitoring daily activity. Darktrace/Email can also integrate with external tools, including SIEMs and SOARs, to further enhance workflows

Moreover, since combining ICES solutions with native security email capabilities creates a hardened security posture, Darktrace/Email benefits from its strong, established integration with Microsoft

Introducing flexibility to ICES deployments

Finally, the security and integration capabilities of Darktrace/Email deploy easily. In the 2023 Market Guide for Email Security, Gartner predicted that “by 2025, 20% of anti-phishing solutions will be delivered via API integration with the email platform, up from less than 5% today.” Darktrace/Email can be rolled out via API or API + Journaling in Microsoft 365, whichever better fits the organization’s needs.

While all ICES products are API-based, that does not mean they are AI-first, or are using the best AI approach. Even some SEGs can deploy via API. That means that the ability to deploy via API does not guarantee a level of security that can stop the most sophisticated threats. Security teams should look beyond deployment method and select the ICES and AI solutions that provide tailored, effective security. 

Finding nuance as an ICES solution

Email security continues to advance in tandem with the threat landscape and organizations’ digital infrastructures. ICES solutions are supplanting SEGs as the mainstream email security solutions, however that broad category includes a range of tools with varying applications of AI. These differences make it critical to not put all ICES products in the same basket. 

Darktrace/Email is the only ICES solution that uses Self-Learning AI to detect all types of email threats, including novel attacks, within seconds.

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.
Written by
Dan Fein
VP, Product

Blog

/

/

September 23, 2025

It’s Time to Rethink Cloud Investigations

cloud investigationsDefault blog imageDefault blog image

Cloud Breaches Are Surging

Cloud adoption has revolutionized how businesses operate, offering speed, scalability, and flexibility. But for security teams, this transformation has introduced a new set of challenges, especially when it comes to incident response (IR) and forensic investigations.

Cloud-related breaches are skyrocketing – 82% of breaches now involve cloud-stored data (IBM Cost of a Data Breach, 2023). Yet incidents often go unnoticed for days: according to a 2025 report by Cybersecurity Insiders, of the 65% of organizations experienced a cloud-related incident in the past year, only 9% detected it within the first hour, and 62% took more than 24 hours to remediate it (Cybersecurity Insiders, Cloud Security Report 2025).

Despite the shift to cloud, many investigation practices remain rooted in legacy on-prem approaches. According to a recent report, 65% of organizations spend approximately 3-5 days longer when investigating an incident in the cloud vs. on premises.

Cloud investigations must evolve, or risk falling behind attackers who are already exploiting the cloud’s speed and complexity.

4 Reasons Cloud Investigations Are Broken

The cloud’s dynamic nature – with its ephemeral workloads and distributed architecture – has outpaced traditional incident response methods. What worked in static, on-prem environments simply doesn’t translate.

Here’s why:

  1. Ephemeral workloads
    Containers and serverless functions can spin up and vanish in minutes. Attackers know this as well – they’re exploiting short-lived assets for “hit-and-run” attacks, leaving almost no forensic footprint. If you’re relying on scheduled scans or manual evidence collection, you’re already too late.
  2. Fragmented tooling
    Each cloud provider has its own logs, APIs, and investigation workflows. In addition, not all logs are enabled by default, cloud providers typically limit the scope of their logs (both in terms of what data they collect and how long they retain it), and some logs are only available through undocumented APIs. This creates siloed views of attacker activity, making it difficult to piece together a coherent timeline. Now layer in SaaS apps, Kubernetes clusters, and shadow IT — suddenly you’re stitching together 20+ tools just to find out what happened. Analysts call it the ‘swivel-chair Olympics,’ and it’s burning hours they don’t have.
  3. SOC overload
    Analysts spend the bulk of their time manually gathering evidence and correlating logs rather than responding to threats. This slows down investigations and increases burnout. SOC teams are drowning in noise; they receive thousands of alerts a day, the majority of which never get touched. False positives eat hundreds of hours a month, and consequently burnout is rife.  
  4. Cost of delay
    The longer an investigation takes, the higher its cost. Breaches contained in under 200 days save an average of over $1M compared to those that linger (IBM Cost of a Data Breach 2025).

These challenges create a dangerous gap for threat actors to exploit. By the time evidence is collected, attackers may have already accessed or exfiltrated data, or entrenched themselves deeper into your environment.

What’s Needed: A New Approach to Cloud Investigations

It’s time to ditch the manual, reactive grind and embrace investigations that are automated, proactive, and built for the world you actually defend. Here’s what the next generation of cloud forensics must deliver:

  • Automated evidence acquisition
    Capture forensic-level data the moment a threat is detected and before assets disappear.
  • Unified multi-cloud visibility
    Stitch together logs, timelines, and context across AWS, Azure, GCP, and hybrid environments into a single unified view of the investigation.
  • Accelerated investigation workflows
    Reduce time-to-insight from hours or days to minutes with automated analysis of forensic data, enabling faster containment and recovery.
  • Empowered SOC teams
    Fully contextualised data and collaboration workflows between teams in the SOC ensure seamless handover, freeing up analysts from manual collection tasks so they can focus on what matters: analysis and response.

Attackers are already leveraging the cloud’s agility. Defenders must do the same — adopting solutions that match the speed and scale of modern infrastructure.

Cloud Changed Everything. It’s Time to Change Investigations.  

The cloud fundamentally reshaped how businesses operate. It’s time for security teams to rethink how they investigate threats.

Forensics can no longer be slow, manual, and reactive. It must be instant, automated, and cloud-first — designed to meet the demands of ephemeral infrastructure and multi-cloud complexity.

The future of incident response isn’t just faster. It’s smarter, more scalable, and built for the environments we defend today, not those of ten years ago.  

On October 9th, Darktrace is revealing the next big thing in cloud security. Don’t miss it – sign up for the webinar.

darktrace live event launch
Continue reading
About the author
Kellie Regan
Director, Product Marketing - Cloud Security

Blog

/

/

September 22, 2025

Understanding the Canadian Critical Cyber Systems Protection Act

Canadian critical cyber systems protection actDefault blog imageDefault blog image

Introduction: The Canadian Critical Cyber Systems Protection Act

On 18 June 2025, the Canadian federal Government introduced Bill C-8 which, if adopted following completion of the legislative process, will enact the Critical Cyber Systems Protection Act (CCSPA) and give Canada its first federal, cross-sector and legally binding cybersecurity regime for designated critical infrastructure providers. As of August 2025, the Bill has completed first reading and stands at second reading in the Canadian House of Commons.

Political context

The measure revives most of the stalled 2022 Bill C-26 “An Act Respecting Cyber Security” which “died on Paper” when Parliament was prorogued in January 2025, in the wake of former Prime Minister Justin Trudeau’s resignation.

The new government, led by Mark Carney since March 2025, has re-tabled the package with the same two-part structure: (1) amendments to the Telecommunications Act that enable security directions to telecoms; and (2) a new CCSPA setting out mandatory cybersecurity duties for designated operators. This blog focuses on the latter.

If enacted, Canada will join fellow Five Eyes partners such as the United Kingdom and Australia, which already impose statutory cyber-security duties on operators of critical national infrastructure.

The case for new cybersecurity legislation in Canada

The Canadian cyber threat landscape has expanded. The country's national cyber authority, the Canadian Centre for Cybersecurity (Cyber Centre), recently assessed that the number of cyber incidents has “sharply increased” in the last two years, as has the severity of those incidents, with essential services providers among the targets. Likewise, in its 2025-2026 National Cyber Threat Assessment, the Cyber Centre warned that AI technologies are “amplifying cyberspace threats” by lowering barriers to entry, improving the speed and sophistication of social-engineering attacks and enabling more precise operations.

This context mirrors what we are seeing globally: adversaries, including state actors, are taking advantage of the availability and sophistication of AI tools, which they have leverage to amplify the effectiveness of their operations. In this increasingly complex landscape, regulation must keep pace and evolve in step with the risk.

What the Canadian Critical Cyber Systems Protection Act aims to achieve

  • If enacted, the CCSPA will apply to operators in federally regulated critical infrastructure sectors which are vital to national security and public safety, as further defined in “Scope” below (the “Regulated Entities”), to adopt and comply with a minimum standard of cybersecurity duties (further described below)  which align with those its Five Eyes counterparts are already adhering to.

Who does the CCSPA apply to

The CCSPA would apply to designated operators that deliver services or systems within federal jurisdiction in the following priority areas:

  • telecommunications services
  • interprovincial or international pipeline and power line systems, nuclear energy systems, transportation systems
  • banking and clearing  
  • settlement systems

The CCSPA would also grant the Governor in Council (Federal Cabinet) with powers to add or remove entities in scope via regulation.

Scope of the CCSPA

The CCSPA introduces two key instruments:

First, it strengthens cyber threat information sharing between responsible ministers, sector regulators, and the Communications Security Establishment (through the Cyber Centre).

Second, it empowers the Governor in Council (GIC) to issue Cyber Security Directions (CSDs) - binding orders requiring a designated operator to implement specified measures to protect a critical cyber system within defined timeframes.

CSDs may be tailored to an individual operator or applied to a class of operators and can address technology, process, or supplier risks. To safeguard security and commercial confidentiality, the CCSPA restricts disclosure of the existence or content of a CSD except as necessary to carry it out.

Locating decision-making with the GIC ensures that CSDs are made with a cross-government view that weighs national security, economic priorities and international agreement.

New obligations for designated providers

The CCSPA would impose key cybersecurity compliance and obligations on designated providers. As it stands, this includes:

  1. Establishing and maintaining cybersecurity programs: these will need to be comprehensive, proportionate and developed proactively. Once implemented, they will need to be continuously reviewed
  2. Mitigating supply chain risks: Regulated Entities will be required to assess their third-party products and services by conducting a supply chain analysis, and take active steps to mitigate any identified risks
  3. Reporting incidents:  Regulated Entities will need to be more transparent with their reporting, by making the Communications Security Establishment (CSE) aware of any incident which has, or could potentially have, an impact on a critical system. The reports must be made within specific timelines, but in any event within no more than 72 hours;
  4. Compliance with cybersecurity directions:  the government will, under the CCSPA, have the authority to issue cybersecurity directives in an effort to remain responsive to emerging threats, which Regulated Entities will be required to follow once issued
  5. Record keeping: this shouldn’t be a surprise to many of those Regulated Entities which fall in scope, which are already likely to be subject to record keeping requirements. Regulated Entities should expect to be maintaining records and conducting audits of their systems and processes against the requirements of the CCSPA

It should be noted, however, that this may be subject to change, so Regulated Entities should keep an eye on the progress of the Bill as it makes its way through parliament.

Enforcement of the Act would be carried out by sector-specific regulators identified in the Act such as the Office of the Superintendent of Financial Institutions, Minister of Transport, Canada Energy Regulator, Canadian Nuclear Safety Commission and the Ministry of Industry.

What are the penalties for CCSPA non-compliance?

When assessing the penalties associated with non-compliance with the requirements of the CCSPA, it is clear that such non-compliance will be taken seriously, and the severity of the penalties follows the trend of those applied by the European Union to key pieces of EU legislation. The “administrative monetary penalties” (AMPs) set by regulation could see fines being applied of up to C$1 million for individuals and up to C$15 million for organizations.

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