Blog
/
Network
/
January 4, 2023

BlackMatter's Smash-and-Grab Ransom Attack Incident Analysis

Stay informed on cybersecurity trends! Read about a BlackMatters ransom attack incident and Darktrace's analysis on how RESPOND could have stopped the attack.
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
The Darktrace Analyst Team
Default blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
04
Jan 2023

Only a few years ago, popular reporting announced that the days of smash-and-grab attacks were over and that a new breed of hackers were taking over with subtler, ‘low-and-slow’ tactics [1]. Although these have undoubtedly appeared, smash-and-grab have quickly become overlooked – perhaps with worrying consequences. Last year, Google saw repeated phishing campaigns using cookie theft malware and most recently, reports of hacktivists using similar techniques have been identified during the 2022 Ukraine Conflict [2 & 3]. Where did their inspiration come from? For larger APT groups such as BlackMatter, which first appeared in the summer of 2021, smash-and-grabs never went out of fashion.

This blog dissects a BlackMatter ransomware attack that hit an organization trialing Darktrace back in 2021. The case reveals what can happen when a security team does not react to high-priority alerts. 

When entire ransomware attacks can be carried out over the course of just 48 hours, there is a high risk to relying on security teams to react to detection notifications and prevent damage before the threat escalates. Although there has been hesitancy in its uptake [4], this blog also demonstrates the need for automated response solutions like Darktrace RESPOND.

The Name Game: Untangling BlackMatter, REvil, and DarkSide

Despite being a short-lived criminal organization on the surface [5], a number of parallels have now been drawn between the TTPs (Tactics, Techniques and Procedures) of the newer BlackMatter group and those of the retired REvil and DarkSide organizations [6]. 

Prior to their retirement, DarkSide and REvil were perhaps the biggest names in cyber-crime, responsible for two of last year’s most devastating ransomware attacks. Less than two weeks after the Colonial Pipeline attack, DarkSide announced it was shutting down its operation [7]. Meanwhile the FBI shutdown REvil in January 2022 after its devastating Fourth of July Kaseya attacks and a failed return in September [8]. It is now suspected that members from one or both went on to form BlackMatter.

This rebranding strategy parallels the smash-and-grab attacks these groups now increasingly employ: they make their money, and a lot of noise, and when they’re found out, they disappear before organizations or governments can pull together their threat intelligence and organize an effective response. When they return days, weeks or months later, they do so having implemented enough small changes to render themselves and their attacks unrecognizable. That is how DarkSide can become BlackMatter, and how its attacks can slip through security systems trained on previously encountered threats. 

Attack Details

In September 2021 Darktrace was monitoring a US marketing agency which became the victim of a double extortion ransomware attack that bore hallmarks of a BlackMatter operation. This began when a single domain-authenticated device joined the company’s network. This was likely a pre-infected company device being reconnected after some time offline. 

Only 15 minutes after joining, the device began SMB and ICMP scanning activities towards over 1000 different internal IPs. There was also a large spike of requests for Epmapper, which suggested an intent for RPC-based lateral movement. Although one credential was particularly prominent, multiple were used including labelled admin credentials. Given it’s unexpected nature, this recon quickly triggered a chain of DETECT/Network model breaches which ensured that Darktrace’s SOC were alerted via the Proactive Threat Notification service. Whilst SOC analysts began to triage the activity, the organization failed to act on any of the alerts they received, leaving the detected threat to take root within their digital environment. 

Shortly after, a series of C2 beaconing occurred towards an endpoint associated with Cobalt Strike [9]. This was accompanied by a range of anomalous WMI bind requests to svcctl, SecAddr and further RPC connections. These allowed the initial compromised device to quickly infect 11 other devices. With continued scanning over the next day, valuable data was soon identified. Across several transfers, 230GB of internal data was then exfiltrated from four file servers via SSH port 22. This data was then made unusable to the organization through encryption occurring via SMB Writes and Moves/Renames with the randomly generated extension ‘.qHefKSmfd’. Finally a ransom note titled ‘qHefKSmfd.README.txt’ was dropped.

This ransom note was appended with the BlackMatter ASCII logo:

Figure 1- The ASCII logo which accompanied BlackMatter’s ransom note

Although Darktrace DETECT and Cyber AI Analyst continued to provide live alerting, the actor successfully accomplished their mission.  

There are numerous reasons that an organization may fail to organize a response to a threat, (including resource shortages, out of hours attacks, and groups that simply move too fast). Without Darktrace’s RESPOND capabilities enabled, the threat actors could proceed this attack without obstacles. 

Figure 2- Cyber AI Analyst breaks down the stages of the attack [Note: this screenshot is from V5 of DETECT/Network] 

How would the attack have unfolded with RESPOND?

Armed with Darktrace’s evolving knowledge of ‘self’ for the customer’s unique digital environment, RESPOND would have activated within seconds of the first network scan, which was recognized as highly anomalous. The standard action taken here would usually involve enforcing the standard ‘pattern of life’ for the compromised device over a set time period in order to halt the anomaly while allowing the business to continue operating as normal.

RESPOND constantly re-evaluates threats as attacks unfold. Had the first stage still been successful, it would have continued to take targeted action at each corresponding stage of this attack. RESPOND models would have alerted to block the external connections to C2 servers over port 443, the outbound exfil attempts and crucially the SMB write activity over port 445 related to encryption.

As DETECT and RESPOND feed into one another, Darktrace would have continued to assess its actions as BlackMatter pivoted tactics. These actions buy back critical time for security teams that may not be in operation over the weekend, and stun the attacker into place without applying overly aggressive responses that create more problems than they solve.

Ultimately although this incident did not resolve autonomously, in response to the ransom event, Darktrace offered to enable RESPOND and set it in active mode for ransomware indicators across all client and server devices. This ensured an event like this would not occur again. 

Why does RESPOND work?

Response solutions must be accurate enough to fire only when there is a genuine threat, configurable enough to let the user stay in the driver’s seat, and intelligent enough to know the right action to take to contain only the malicious activity- without disrupting normal business operations. 

This is only possible if you can establish what ‘normal’ is for any one organization. And this is how Darktrace’s RESPOND product family ensures its actions are targeted and proportionate. By feeding off DETECT alerting which highlights subtle or large deviations across the network, cloud and SaaS, RESPOND can provide a measured response to the potential threat. This includes actions such as:

  • Enforcing the device’s ‘pattern of life’ for a given length of time 
  • Enforcing the ‘group pattern of life’ (stopping a device from doing anything its peers haven’t done in the past)
  • Blocking connections of a certain type to a certain destination
  • Logging out of a cloud account 
  • ‘Smart quarantining’ an endpoint device- maintaining access to VPNs and company’s AV solution

Conclusion 

In its report on BlackMatter [10], CISA recommended that organizations invest in network monitoring tools with the capacity to investigate anomalous activity. Picking up on unusual behavior rather than predetermined rules and signatures is an important step in fighting back against new threats. As this particular story shows, however, detection alone is not always enough. Turning on RESPOND, which takes immediate and precise action to contain threats, regardless of when and where they come in, is the best way to counter smash-and-grab attacks and protect organizations’ digital assets. There is little doubt that the threat actors behind BlackMatter will or have already returned with new names and strategies- but organizations with RESPOND will be ready for them.

Appendices

Darktrace Model Detections (in order of breach)

Those with the ‘PTN’ prefix were alerted directly to Darktrace’s 24/7 SOC team.

  • Device / ICMP Address Scan
  • Device / Suspicious SMB Scanning Activity
  • (PTN) Device / Suspicious Network Scan Activity
  • Anomalous Connection / SMB Enumeration
  • Device / Possible RPC Lateral Movement
  • Device / Active Directory Reconnaissance
  • Unusual Activity / Possible RPC Recon Activity
  • Device / Possible SMB/NTLM Reconnaissance
  • Compliance / Default Credential Usage
  • Device / New or Unusual Remote Command Execution
  • Anomalous Connection / New or Uncommon Service Control
  • Device / New or Uncommon SMB Named Pipe
  • Device / SMB Session Bruteforce
  • Device / New or Uncommon WMI Activity
  • (PTN) Device / Multiple Lateral Movement Model Breaches
  • Compromise / Sustained SSL or HTTP Increase
  • Compromise / SSL or HTTP Beacon
  • Compromise / Sustained TCP Beaconing Activity To Rare Endpoint
  • Device / Anomalous SMB Followed By Multiple Model Breaches
  • Device / Anomalous RDP Followed By Multiple Model Breaches
  • Anomalous Server Activity / Rare External from Server
  • Anomalous Connection / Anomalous SSL without SNI to New External
  • Anomalous Connection / Rare External SSL Self-Signed
  • Device / Long Agent Connection to New Endpoint
  • Compliance / SMB Drive Write
  • Anomalous Connection / Unusual Admin SMB Session
  • Anomalous Connection / High Volume of New or Uncommon Service Control
  • Anomalous Connection / Unusual Admin RDP Session
  • Device / Suspicious File Writes to Multiple Hidden SMB Shares
  • Anomalous Connection / Multiple Connections to New External TCP Port
  • Compliance / SSH to Rare External Destination
  • Anomalous Connection / Uncommon 1 GiB Outbound
  • Anomalous Connection / Data Sent to Rare Domain
  • Anomalous Connection / Download and Upload
  • (PTN) Unusual Activity / Enhanced Unusual External Data Transfer
  • Anomalous File / Internal / Additional Extension Appended to SMB File
  • (PTN) Compromise / Ransomware / Suspicious SMB Activity

List of IOCs 

Reference List 

[1] https://www.designnews.com/industrial-machinery/new-age-hackers-are-ditching-smash-and-grab-techniques 

[2] https://cybernews.com/cyber-war/how-do-smash-and-grab-cyberattacks-help-ukraine-in-waging-war/

[3] https://blog.google/threat-analysis-group/phishing-campaign-targets-youtube-creators-cookie-theft-malware/

[4] https://www.ukcybersecuritycouncil.org.uk/news-insights/articles/the-benefits-of-automation-to-cyber-security/

[5] https://techcrunch.com/2021/11/03/blackmatter-ransomware-shut-down/ 

[6] https://www.trellix.com/en-us/about/newsroom/stories/research/blackmatter-ransomware-analysis-the-dark-side-returns.html

[7] https://www.nytimes.com/2021/05/14/business/darkside-pipeline-hack.html

[8] https://techcrunch.com/2022/01/14/fsb-revil-ransomware/ 

[9] https://www.virustotal.com/gui/domain/georgiaonsale.com/community

[10] https://www.cisa.gov/uscert/ncas/alerts/aa21-291a

Credit to: Andras Balogh, SOC Analyst and Gabriel Few-Wiegratz, Threat Intelligence Content Production Lead

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
The Darktrace Analyst Team

More in this series

No items found.

Blog

/

Network

/

May 16, 2025

Catching a RAT: How Darktrace neutralized AsyncRAT

woman working on laptopDefault blog imageDefault blog image

What is a RAT?

As the proliferation of new and more advanced cyber threats continues, the Remote Access Trojan (RAT) remains a classic tool in a threat actor's arsenal. RATs, whether standardized or custom-built, enable attackers to remotely control compromised devices, facilitating a range of malicious activities.

What is AsyncRAT?

Since its first appearance in 2019, AsyncRAT has become increasingly popular among a wide range of threat actors, including cybercriminals and advanced persistent threat (APT) groups.

Originally available on GitHub as a legitimate tool, its open-source nature has led to widespread exploitation. AsyncRAT has been used in numerous campaigns, including prolonged attacks on essential US infrastructure, and has even reportedly penetrated the Chinese cybercriminal underground market [1] [2].

How does AsyncRAT work?

Original source code analysis of AsyncRAT demonstrates that once installed, it establishes persistence via techniques such as creating scheduled tasks or registry keys and uses SeDebugPrivilege to gain elevated privileges [3].

Its key features include:

  • Keylogging
  • File search
  • Remote audio and camera access
  • Exfiltration techniques
  • Staging for final payload delivery

These are generally typical functions found in traditional RATs. However, it also boasts interesting anti-detection capabilities. Due to the popularity of Virtual Machines (VM) and sandboxes for dynamic analysis, this RAT checks for the manufacturer via the WMI query 'Select * from Win32_ComputerSystem' and looks for strings containing 'VMware' and 'VirtualBox' [4].

Darktrace’s coverage of AsyncRAT

In late 2024 and early 2025, Darktrace observed a spike in AsyncRAT activity across various customer environments. Multiple indicators of post-compromise were detected, including devices attempting or successfully connecting to endpoints associated with AsyncRAT.

On several occasions, Darktrace identified a clear association with AsyncRAT through the digital certificates of the highlighted SSL endpoints. Darktrace’s Real-time Detection effectively identified and alerted on suspicious activities related to AsyncRAT. In one notable incident, Darktrace’s Autonomous Response promptly took action to contain the emerging threat posed by AsyncRAT.

AsyncRAT attack overview

On December 20, 2024, Darktrace first identified the use of AsyncRAT, noting a device successfully establishing SSL connections to the uncommon external IP 185.49.126[.]50 (AS199654 Oxide Group Limited) via port 6606. The IP address appears to be associated with AsyncRAT as flagged by open-source intelligence (OSINT) sources [5]. This activity triggered the device to alert the ‘Anomalous Connection / Rare External SSL Self-Signed' model.

Model alert in Darktrace / NETWORK showing the repeated SSL connections to a rare external Self-Signed endpoint, 185.49.126[.]50.
Figure 1: Model alert in Darktrace / NETWORK showing the repeated SSL connections to a rare external Self-Signed endpoint, 185.49.126[.]50.

Following these initial connections, the device was observed making a significantly higher number of connections to the same endpoint 185.49.126[.]50 via port 6606 over an extended period. This pattern suggested beaconing activity and triggered the 'Compromise/Beaconing Activity to External Rare' model alert.

Further analysis of the original source code, available publicly, outlines the default ports used by AsyncRAT clients for command-and-control (C2) communications [6]. It reveals that port 6606 is the default port for creating a new AsyncRAT client. Darktrace identified both the Certificate Issuer and the Certificate Subject as "CN=AsyncRAT Server". This SSL certificate encrypts the packets between the compromised system and the server. These indicators of compromise (IoCs) detected by Darktrace further suggest that the device was successfully connecting to a server associated with AsyncRAT.

Model alert in Darktrace / NETWORK displaying the Digital Certificate attributes, IP address and port number associated with AsyncRAT.
Figure 2: Model alert in Darktrace / NETWORK displaying the Digital Certificate attributes, IP address and port number associated with AsyncRAT.
Darktrace’s detection of repeated connections to the suspicious IP address 185.49.126[.]50 over port 6606, indicative of beaconing behavior.
Figure 3: Darktrace’s detection of repeated connections to the suspicious IP address 185.49.126[.]50 over port 6606, indicative of beaconing behavior.
Darktrace's Autonomous Response actions blocking the suspicious IP address,185.49.126[.]50.
Figure 4: Darktrace's Autonomous Response actions blocking the suspicious IP address,185.49.126[.]50.

A few days later, the same device was detected making numerous connections to a different IP address, 195.26.255[.]81 (AS40021 NL-811-40021), via various ports including 2106, 6606, 7707, and 8808. Notably, ports 7707 and 8808 are also default ports specified in the original AsyncRAT source code [6].

Darktrace’s detection of connections to the suspicious endpoint 195.26.255[.]81, where the default ports (6606, 7707, and 8808) for AsyncRAT were observed.
Figure 5: Darktrace’s detection of connections to the suspicious endpoint 195.26.255[.]81, where the default ports (6606, 7707, and 8808) for AsyncRAT were observed.

Similar to the activity observed with the first endpoint, 185.49.126[.]50, the Certificate Issuer for the connections to 195.26.255[.]81 was identified as "CN=AsyncRAT Server". Further OSINT investigation confirmed associations between the IP address 195.26.255[.]81 and AsyncRAT [7].

Darktrace's detection of a connection to the suspicious IP address 195.26.255[.]81 and the domain name identified under the common name (CN) of a certificate as AsyncRAT Server
Figure 6: Darktrace's detection of a connection to the suspicious IP address 195.26.255[.]81 and the domain name identified under the common name (CN) of a certificate as AsyncRAT Server.

Once again, Darktrace's Autonomous Response acted swiftly, blocking the connections to 195.26.255[.]81 throughout the observed AsyncRAT activity.

Figure 7: Darktrace's Autonomous Response actions were applied against the suspicious IP address 195.26.255[.]81.

A day later, Darktrace again alerted to further suspicious activity from the device. This time, connections to the suspicious endpoint 'kashuub[.]com' and IP address 191.96.207[.]246 via port 8041 were observed. Further analysis of port 8041 suggests it is commonly associated with ScreenConnect or Xcorpeon ASIC Carrier Ethernet Transport [8]. ScreenConnect has been observed in recent campaign’s where AsyncRAT has been utilized [9]. Additionally, one of the ASN’s observed, namely ‘ASN Oxide Group Limited’, was seen in both connections to kashuub[.]com and 185.49.126[.]50.

This could suggest a parallel between the two endpoints, indicating they might be hosting AsyncRAT C2 servers, as inferred from our previous analysis of the endpoint 185.49.126[.]50 and its association with AsyncRAT [5]. OSINT reporting suggests that the “kashuub[.]com” endpoint may be associated with ScreenConnect scam domains, further supporting the assumption that the endpoint could be a C2 server.

Darktrace’s Autonomous Response technology was once again able to support the customer here, blocking connections to “kashuub[.]com”. Ultimately, this intervention halted the compromise and prevented the attack from escalating or any sensitive data from being exfiltrated from the customer’s network into the hands of the threat actors.

Darktrace’s Autonomous Response applied a total of nine actions against the IP address 191.96.207[.]246 and the domain 'kashuub[.]com', successfully blocking the connections.
Figure 8: Darktrace’s Autonomous Response applied a total of nine actions against the IP address 191.96.207[.]246 and the domain 'kashuub[.]com', successfully blocking the connections.

Due to the popularity of this RAT, it is difficult to determine the motive behind the attack; however, from existing knowledge of what the RAT does, we can assume accessing and exfiltrating sensitive customer data may have been a factor.

Conclusion

While some cybercriminals seek stability and simplicity, openly available RATs like AsyncRAT provide the infrastructure and open the door for even the most amateur threat actors to compromise sensitive networks. As the cyber landscape continually shifts, RATs are now being used in all types of attacks.

Darktrace’s suite of AI-driven tools provides organizations with the infrastructure to achieve complete visibility and control over emerging threats within their network environment. Although AsyncRAT’s lack of concealment allowed Darktrace to quickly detect the developing threat and alert on unusual behaviors, it was ultimately Darktrace Autonomous Response's consistent blocking of suspicious connections that prevented a more disruptive attack.

Credit to Isabel Evans (Cyber Analyst), Priya Thapa (Cyber Analyst) and Ryan Traill (Analyst Content Lead)

Appendices

  • Real-time Detection Models
       
    • Compromise / Suspicious SSL Activity
    •  
    • Compromise / Beaconing Activity To      External Rare
    •  
    • Compromise / High Volume of      Connections with Beacon Score
    •  
    • Anomalous Connection / Suspicious      Self-Signed SSL
    •  
    • Compromise / Sustained SSL or HTTP      Increase
    •  
    • Compromise / SSL Beaconing to Rare      Destination
    •  
    • Compromise / Suspicious Beaconing      Behaviour
    •  
    • Compromise / Large Number of      Suspicious Failed Connections
  •  
  • Autonomous     Response Models
       
    • Antigena / Network / Significant      Anomaly / Antigena Controlled and Model Alert
    •  
    • Antigena / Network / Significant      Anomaly / Antigena Enhanced Monitoring from Client Block

List of IoCs

·     185.49.126[.]50 - IP – AsyncRAT C2 Endpoint

·     195.26.255[.]81 – IP - AsyncRAT C2 Endpoint

·      191.96.207[.]246 – IP – Likely AsyncRAT C2 Endpoint

·     CN=AsyncRAT Server - SSL certificate - AsyncRATC2 Infrastructure

·      Kashuub[.]com– Hostname – Likely AsyncRAT C2 Endpoint

MITRE ATT&CK Mapping:

Tactic –Technique – Sub-Technique  

 

Execution– T1053 - Scheduled Task/Job: Scheduled Task

DefenceEvasion – T1497 - Virtualization/Sandbox Evasion: System Checks

Discovery– T1057 – Process Discovery

Discovery– T1082 – System Information Discovery

LateralMovement - T1021.001 - Remote Services: Remote Desktop Protocol

Collection/ Credential Access – T1056 – Input Capture: Keylogging

Collection– T1125 – Video Capture

Commandand Control – T1105 - Ingress Tool Transfer

Commandand Control – T1219 - Remote Access Software

Exfiltration– T1041 - Exfiltration Over C2 Channel

 

References

[1]  https://blog.talosintelligence.com/operation-layover-how-we-tracked-attack/

[2] https://intel471.com/blog/china-cybercrime-undergrond-deepmix-tea-horse-road-great-firewall

[3] https://www.attackiq.com/2024/08/01/emulate-asyncrat/

[4] https://www.fortinet.com/blog/threat-research/spear-phishing-campaign-with-new-techniques-aimed-at-aviation-companies

[5] https://www.virustotal.com/gui/ip-address/185.49.126[.]50/community

[6] https://dfir.ch/posts/asyncrat_quasarrat/

[7] https://www.virustotal.com/gui/ip-address/195.26.255[.]81

[8] https://www.speedguide.net/port.php?port=8041

[9] https://www.esentire.com/blog/exploring-the-infection-chain-screenconnects-link-to-asyncrat-deployment

[10] https://scammer.info/t/taking-out-connectwise-sites/153479/518?page=26

Continue reading
About the author
Isabel Evans
Cyber Analyst

Blog

/

OT

/

May 13, 2025

Revolutionizing OT Risk Prioritization with Darktrace 6.3

man in hard hat on tabletDefault blog imageDefault blog image

Powering smarter protection for industrial systems

In industrial environments, security challenges are deeply operational. Whether you’re running a manufacturing line, a power grid, or a semiconductor fabrication facility (fab), you need to know: What risks can truly disrupt my operations, and what should I focus on first?

Teams need the right tools to shift from reactive defense, constantly putting out fires, to proactively thinking about their security posture. However, most OT teams are stuck using IT-centric tools that don’t speak the language of industrial systems, are consistently overwhelmed with static CVE lists, and offer no understanding of OT-specific protocols. The result? Compliance gaps, siloed insights, and risk models that don’t reflect real-world exposure, making risk prioritization seem like a luxury.

Darktrace / OT 6.3 was built in direct response to these challenges. Developed in close collaboration with OT operators and engineers, this release introduces powerful upgrades that deliver the context, visibility, and automation security teams need, without adding complexity. It’s everything OT defenders need to protect critical operations in one platform that understands the language of industrial systems.

additions to darktrace / ot 6/3

Contextual risk modeling with smarter Risk Scoring

Darktrace / OT 6.3 introduces major upgrades to OT Risk Management, helping teams move beyond generic CVE lists with AI-driven risk scoring and attack path modeling.

By factoring in real-world exploitability, asset criticality, and operational context, this release delivers a more accurate view of what truly puts critical systems at risk.

The platform now integrates:

  • CISA’s Known Exploited Vulnerabilities (KEV) database
  • End-of-life status for legacy OT devices
  • Firewall misconfiguration analysis
  • Incident response plan alignment

Most OT environments are flooded with vulnerability data that lacks context. CVE scores often misrepresent risk by ignoring how threats move through the environment or whether assets are even reachable. Firewalls are frequently misconfigured or undocumented, and EOL (End of Life) devices, some of the most vulnerable, often go untracked.

Legacy tools treat these inputs in isolation. Darktrace unifies them, showing teams exactly which attack paths adversaries could exploit, mapped to the MITRE ATT&CK framework, with visibility into where legacy tech increases exposure.

The result: teams can finally focus on the risks that matter most to uptime, safety, and resilience without wasting resources on noise.

Automating compliance with dynamic IEC-62443 reporting

Darktrace / OT now includes a purpose-built IEC-62443-3-3 compliance module, giving industrial teams real-time visibility into their alignment with regulatory standards. No spreadsheets required!

Industrial environments are among the most heavily regulated. However, for many OT teams, staying compliant is still a manual, time-consuming process.

Darktrace / OT introduces a dedicated IEC-62443-3-3 module designed specifically for industrial environments. Security and operations teams can now map their security posture to IEC standards in real time, directly within the platform. The module automatically gathers evidence across all four security levels, flags non-compliance, and generates structured reports to support audit preparation, all in just a few clicks.Most organizations rely on spreadsheets or static tools to track compliance, without clear visibility into which controls meet standards like IEC-62443. The result is hidden gaps, resource-heavy audits, and slow remediation cycles.

Even dedicated compliance tools are often built for IT, require complex setup, and overlook the unique devices found in OT environments. This leaves teams stuck with fragmented reporting and limited assurance that their controls are actually aligned with regulatory expectations.

By automating compliance tracking, surfacing what matters most, and being purpose built for industrial environments, Darktrace / OT empowers organizations to reduce audit fatigue, eliminate blind spots, and focus resources where they’re needed most.

Expanding protocol visibility with deep insights for specialized OT operations

Darktrace has expanded its Deep Packet Inspection (DPI) capabilities to support five industry-specific protocols, across healthcare, semiconductor manufacturing, and ABB control systems.

The new protocols build on existing capabilities across all OT industry verticals and protocol types to ensure the Darktrace Self-Learning AI TM can learn intelligently about even more assets in complex industrial environments. By enabling native, AI-driven inspection of these protocols, Darktrace can identify both security threats and operational issues without relying on additional appliances or complex integrations.

Most security platforms lack native support for industry-specific protocols, creating critical visibility gaps in customer environments like healthcare, semiconductor manufacturing, and ABB-heavy industrial automation. Without deep protocol awareness, organizations struggle to accurately identify specialized OT and IoT assets, detect malicious activity concealed within proprietary protocol traffic, and generate reliable device risk profiles due to insufficient telemetry.

These blind spots result in incomplete asset inventories, and ultimately, flawed risk posture assessments which over-index for CVE patching and legacy equipment.

By combining protocol-aware detection with full-stack visibility across IT, OT, and IoT, Darktrace’s AI can correlate anomalies across domains. For example, connecting an anomaly from a Medical IoT (MIoT) device with suspicious behavior in IT systems, providing actionable, contextual insights other solutions often miss.

Conclusion

Together, these capabilities take OT security beyond alert noise and basic CVE matching, delivering continuous compliance, protocol-aware visibility, and actionable, prioritized risk insights, all inside a single, unified platform built for the realities of industrial environments.

[related-resource]

Continue reading
About the author
Pallavi Singh
Product Marketing Manager, OT Security & Compliance
Your data. Our AI.
Elevate your network security with Darktrace AI