Blog
/
OT
/
November 21, 2022

How Darktrace Finds Misconfigurations

Explore Darktrace’s strategies for preventing IT misconfigurations. Our blog provides actionable insights and use cases.
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
Carlos Gray
Senior Product Marketing Manager, Email
Default blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
21
Nov 2022

During an initial demo with a water management company, Darktrace found an industrial control system exposed to the internet. Immediately, the organization went into incident response mode because this system was mission critical and could potentially impact the water facilities, as it had the power to adjust water flow.

This asset was exposed because of a simple misconfiguration, highlighting to the customer the need for proactive monitoring of its attack surface. In this case, the engineer who set up the system had simply not noticed the mistake, but these scenarios could be more dangerous and more likely if insider threat is involved.  

The growing threat of misconfigurations in cybersecurity

Misconfigurations arise when vital security settings are either not applied or applied incorrectly. Such misconfigurations produce vulnerable security openings that can be exploited by attackers to either gain a foothold in the asset or generate a more dangerous attack, like altering water flow or deploying ransomware. There is a wide variety of assets that are subject to potential misconfigurations, including web or application servers, cloud containers, custom code, network devices like desktops or servers, and entire databases.  

Unfortunately, the pervasiveness of misconfigurations is only increasing. In the past 12 months, there has been a 310% increase in hackers reporting misconfiguration vulnerabilities to the HackerOne platform.  

Unique risks for industrial control systems and critical infrastructure

Every digital environment has its own characteristics that alter the prevalence or the impact of misconfigurations. For example, industrial devices that support critical infrastructure are all the more sensitive to these types of changes, as these devices often have limited integrated security, despite their highly delicate functions. Because with every vendor and device has its own recommended configuration, security teams must take additional precautions.  

In cloud environments, the ease of deployment and increased capabilities also tend to produce more misconfigurations. Digital footprints are growing at such a pace that security departments may opt to skip onboarding processes of technologies to avoid becoming an obstacle for the business. It has become so easy for any department, regardless of their technical knowledge, to add cloud applications, software, or even hardware to the company's architecture. This is why shadow IT is so troublesome: it's impossible for the security team to ensure something is well configured if they don’t even know it exists.  

In addition, due to rapid growth, security and IT teams aren’t experts in every technology included within the enterprise architecture. So, the teams may do their best to apply security controls while being unaware the current configuration is a misconfiguration. With digital assets’ constant evolution, they may even be configured correctly at one point but become misconfigured in the future if not updated.  

Mitigating Misconfiguration

It’s human nature that we make mistakes, and the more assets and third parties that are introduced, the more mistakes are possible. However, there are certain steps organizations can take towards reducing the frequency and the impact of misconfigurations.  

Any organization needs to have discovery processes to maintain an updated inventory of their assets, and should categorize these assets based on their exposure as well as their criticality to the business. This information should feed into the organization’s risk analysis, which in turn informs the priority of mitigation actions or controls. This process, when done manually, can be long and arduous, and is not continuous: as organizations’ digital footprints are evolving so rapidly, these analyses can become obsolete quickly.  

On the other hand, organizations must also monitor the activity of these assets and not just assess them at face value. As with anything in security, security teams need to be weary of the symptoms. Inappropriate configurations will often generate alerts such as slow performance, multiple suspicious login attempts, bloatware, unexpected application behavior such as redirects or shutdowns.  

Misconfigurations are easier to identify, prioritize and remediate with an AI solution that provides continuous analysis of the organization’s external and internal attack surface. Darktrace / Proactive Exposure Management and Darktrace / Attack Surface Management achieve exactly this.  

Managing external assets

With ASM, security teams gain visibility of the entire external attack surface, including elusive assets like shadow IT and legacy devices. It frequently uncovers misconfigurations and recommends how to mitigate the risks caused by them. Some examples include email spoofing, no SPF records, no DKIM records, no DMARC records, subdomain takeover possible, and missing routes for netblocks.  

The truly unique aspect of a Self-Learning technology is that security teams receive notifications tailored to the precise assets within their architectures. In other words, the tool will only provide the misconfiguration recommendations for the specific assets that require it, instead of having to reverse engineer state-of-the-art security and then trying to see where it can apply within the organization. With Darktrace, security teams are already getting that information directly. In fact, it doesn’t stop there, misconfigurations are prirotized by the risk inherited. The security team only has to check the list of misconfigurations in order of priority and take action on them.  

Exposure management & attack paths

From an internal perspective, Darktrace / Proactive Exposure Management will map those misconfigurations to potential attack paths, answering the question of what damage each misconfiguration can lead to and more importantly how: an attacker could go from that initial misconfiguration through each lateral movement, whether it is via a device or a user, and then reach the most critical devices within the infrastructure.

Often in security, the focus can drift to the latest tactics and techniques being used by large Advanced Persistent Threats, but a simple misconfiguration caused by a rushed or distracted employee can pose an equally large threat. An innocent mistake can often open an even larger weakness in the digital architecture, as the attacker doesn’t have to force to open the window to break in.

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
Carlos Gray
Senior Product Marketing Manager, Email

Blog

/

/

January 13, 2026

Runtime Is Where Cloud Security Really Counts: The Importance of Detection, Forensics and Real-Time Architecture Awareness

runtime, cloud security, cnaapDefault blog imageDefault blog image

Introduction: Shifting focus from prevention to runtime

Cloud security has spent the last decade focused on prevention; tightening configurations, scanning for vulnerabilities, and enforcing best practices through Cloud Native Application Protection Platforms (CNAPP). These capabilities remain essential, but they are not where cloud attacks happen.

Attacks happen at runtime: the dynamic, ephemeral, constantly changing execution layer where applications run, permissions are granted, identities act, and workloads communicate. This is also the layer where defenders traditionally have the least visibility and the least time to respond.

Today’s threat landscape demands a fundamental shift. Reducing cloud risk now requires moving beyond static posture and CNAPP only approaches and embracing realtime behavioral detection across workloads and identities, paired with the ability to automatically preserve forensic evidence. Defenders need a continuous, real-time understanding of what “normal” looks like in their cloud environments, and AI capable of processing massive data streams to surface deviations that signal emerging attacker behavior.

Runtime: The layer where attacks happen

Runtime is the cloud in motion — containers starting and stopping, serverless functions being called, IAM roles being assumed, workloads auto scaling, and data flowing across hundreds of services. It’s also where attackers:

  • Weaponize stolen credentials
  • Escalate privileges
  • Pivot programmatically
  • Deploy malicious compute
  • Manipulate or exfiltrate data

The challenge is complex: runtime evidence is ephemeral. Containers vanish; critical process data disappears in seconds. By the time a human analyst begins investigating, the detail required to understand and respond to the alert, often is already gone. This volatility makes runtime the hardest layer to monitor, and the most important one to secure.

What Darktrace / CLOUD Brings to Runtime Defence

Darktrace / CLOUD is purpose-built for the cloud execution layer. It unifies the capabilities required to detect, contain, and understand attacks as they unfold, not hours or days later. Four elements define its value:

1. Behavioral, real-time detection

The platform learns normal activity across cloud services, identities, workloads, and data flows, then surfaces anomalies that signify real attacker behavior, even when no signature exists.

2. Automated forensic level artifact collection

The moment Darktrace detects a threat, it can automatically capture volatile forensic evidence; disk state, memory, logs, and process context, including from ephemeral resources. This preserves the truth of what happened before workloads terminate and evidence disappears.

3. AI-led investigation

Cyber AI Analyst assembles cloud behaviors into a coherent incident story, correlating identity activity, network flows, and Cloud workload behavior. Analysts no longer need to pivot across dashboards or reconstruct timelines manually.

4. Live architectural awareness

Darktrace continuously maps your cloud environment as it operates; including services, identities, connectivity, and data pathways. This real-time visibility makes anomalies clearer and investigations dramatically faster.

Together, these capabilities form a runtime-first security model.

Why CNAPP alone isn’t enough

CNAPP platforms excel at pre deployment checks all the way down to developer workstations, identifying misconfigurations, concerning permission combinations, vulnerable images, and risky infrastructure choices. But CNAPP’s breadth is also its limitation. CNAPP is about posture. Runtime defense is about behavior.

CNAPP tells you what could go wrong; runtime detection highlights what is going wrong right now.

It cannot preserve ephemeral evidence, correlate active behaviors across domains, or contain unfolding attacks with the precision and speed required during a real incident. Prevention remains essential, but prevention alone cannot stop an attacker who is already operating inside your cloud environment.

Real-world AWS Scenario: Why Runtime Monitoring Wins

A recent incident detected by Darktrace / CLOUD highlights how cloud compromises unfold, and why runtime visibility is non-negotiable. Each step below reflects detections that occur only when monitoring behavior in real time.

1. External Credential Use

Detection: Unusual external source for credential use: An attacker logs into a cloud account from a never-before-seen location, the earliest sign of account takeover.

2. AWS CLI Pivot

Detection: Unusual CLI activity: The attacker switches to programmatic access, issuing commands from a suspicious host to gain automation and stealth.

3. Credential Manipulation

Detection: Rare password reset: They reset or assign new passwords to establish persistence and bypass existing security controls.

4. Cloud Reconnaissance

Detection: Burst of resource discovery: The attacker enumerates buckets, roles, and services to map high value assets and plan next steps.

5. Privilege Escalation

Detection: Anomalous IAM update: Unauthorized policy updates or role changes grant the attacker elevated access or a backdoor.

6. Malicious Compute Deployment

Detection: Unusual EC2/Lambda/ECS creation: The attacker deploys compute resources for mining, lateral movement, or staging further tools.

7. Data Access or Tampering

Detection: Unusual S3 modifications: They alter S3 permissions or objects, often a prelude to data exfiltration or corruption.

Only some of these actions would appear in a posture scan, crucially after the fact.
Every one of these runtime detections is visible only through real-time behavioral monitoring while the attack is in progress.

The future of cloud security Is runtime-first

Cloud defense can no longer revolve solely around prevention. Modern attacks unfold in runtime, across a fast-changing mesh of workloads, services, and — critically — identities. To reduce risk, organizations must be able to detect, understand, and contain malicious activity as it happens, before ephemeral evidence disappears and before attacker's pivot across identity layers.

Darktrace / CLOUD delivers this shift by turning runtime, the most volatile and consequential layer in the cloud, into a fully defensible control point through unified visibility across behavior, workloads, and identities. It does this by providing:

  • Real-time behavior detection across workloads and identity activity
  • Autonomous response actions for rapid containment
  • Automated forensic level artifact preservation the moment events occur
  • AI-driven investigation that separates weak signals from true attacker patterns
  • Live cloud environment insight to understand context and impact instantly

Cloud security must evolve from securing what might go wrong to continuously understanding what is happening; in runtime, across identities, and at the speed attackers operate. Unifying runtime and identity visibility is how defenders regain the advantage.

[related-resource]

Continue reading
About the author
Adam Stevens
Senior Director of Product, Cloud | Darktrace

Blog

/

Network

/

January 12, 2026

Maduro Arrest Used as a Lure to Deliver Backdoor

maduro arrest used as lure to deliver backdoorDefault blog imageDefault blog image

Introduction

Threat actors frequently exploit ongoing world events to trick users into opening and executing malicious files. Darktrace security researchers recently identified a threat group using reports around the arrest of Venezuelan President Nicolàs Maduro on January 3, 2025, as a lure to deliver backdoor malware.

Technical Analysis

While the exact initial access method is unknown, it is likely that a spear-phishing email was sent to victims, containing a zip archive titled “US now deciding what’s next for Venezuela.zip”. This file included an executable named “Maduro to be taken to New York.exe” and a dynamic-link library (DLL), “kugou.dll”.  

The binary “Maduro to be taken to New York.exe” is a legitimate binary (albeit with an expired signature) related to KuGou, a Chinese streaming platform. Its function is to load the DLL “kugou.dll” via DLL search order. In this instance, the expected DLL has been replaced with a malicious one with the same name to load it.  

DLL called with LoadLibraryW.
Figure 1: DLL called with LoadLibraryW.

Once the DLL is executed, a directory is created C:\ProgramData\Technology360NB with the DLL copied into the directory along with the executable, renamed as “DataTechnology.exe”. A registry key is created for persistence in “HKCU\Software\Microsoft\Windows\CurrentVersion\Run\Lite360” to run DataTechnology.exe --DATA on log on.

 Registry key added for persistence.
Figure 2. Registry key added for persistence.
Folder “Technology360NB” created.
Figure 3: Folder “Technology360NB” created.

During execution, a dialog box appears with the caption “Please restart your computer and try again, or contact the original author.”

Message box prompting user to restart.
Figure 4. Message box prompting user to restart.

Prompting the user to restart triggers the malware to run from the registry key with the command --DATA, and if the user doesn't, a forced restart is triggered. Once the system is reset, the malware begins periodic TLS connections to the command-and-control (C2) server 172.81.60[.]97 on port 443. While the encrypted traffic prevents direct inspection of commands or data, the regular beaconing and response traffic strongly imply that the malware has the ability to poll a remote server for instructions, configuration, or tasking.

Conclusion

Threat groups have long used geopolitical issues and other high-profile events to make malicious content appear more credible or urgent. Since the onset of the war in Ukraine, organizations have been repeatedly targeted with spear-phishing emails using subject lines related to the ongoing conflict, including references to prisoners of war [1]. Similarly, the Chinese threat group Mustang Panda frequently uses this tactic to deploy backdoors, using lures related to the Ukrainian war, conventions on Tibet [2], the South China Sea [3], and Taiwan [4].  

The activity described in this blog shares similarities with previous Mustang Panda campaigns, including the use of a current-events archive, a directory created in ProgramData with a legitimate executable used to load a malicious DLL and run registry keys used for persistence. While there is an overlap of tactics, techniques and procedures (TTPs), there is insufficient information available to confidently attribute this activity to a specific threat group. Users should remain vigilant, especially when opening email attachments.

Credit to Tara Gould (Malware Research Lead)
Edited by Ryan Traill (Analyst Content Lead)

Indicators of Compromise (IoCs)

172.81.60[.]97
8f81ce8ca6cdbc7d7eb10f4da5f470c6 - US now deciding what's next for Venezuela.zip
722bcd4b14aac3395f8a073050b9a578 - Maduro to be taken to New York.exe
aea6f6edbbbb0ab0f22568dcb503d731  - kugou.dll

References

[1] https://cert.gov.ua/article/6280422  

[2] https://www.ibm.com/think/x-force/hive0154-mustang-panda-shifts-focus-tibetan-community-deploy-pubload-backdoor

[3] https://www.ibm.com/think/x-force/hive0154-targeting-us-philippines-pakistan-taiwan

[4] https://www.ibm.com/think/x-force/hive0154-targeting-us-philippines-pakistan-taiwan

Continue reading
About the author
Tara Gould
Malware Research Lead
Your data. Our AI.
Elevate your network security with Darktrace AI