Blog
/
Network
/
January 31, 2024

How Darktrace Defeated SmokeLoader Malware

Read how Darktrace's AI identified and neutralized SmokeLoader malware. Gain insights into their proactive approach to cybersecurity.
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
Patrick Anjos
Senior Cyber Analyst
Default blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog imageDefault blog image
31
Jan 2024

What is Loader Malware?

Loader malware is a type of malicious software designed primarily to infiltrate a system and then download and execute additional malicious payloads.

In recent years, loader malware has emerged as a significant threat for organizations worldwide. This trend is expected to continue given the widespread availability of many loader strains within the Malware-as-a-Service (MaaS) marketplace. The MaaS marketplace contains a wide variety of innovative strains which are both affordable, with toolkits ranging from USD 400 to USD 1,650 [1], and continuously improving, aiming to avoid traditional detection mechanisms.

SmokeLoader is one such example of a MaaS strain that has been observed in the wild since 2011 and continues to pose a significant threat to organizations and their security teams.

How does SmokeLoader Malware work?

SmokeLoader’s ability to drop an array of different malware strains onto infected systems, from backdoors, ransomware, cryptominers, password stealers, point-of-sale malware and banking trojans, means its a highly versatile loader that has remained consistently popular among threat actors.

In addition to its versatility, it also exhibits advanced evasion strategies that make it difficult for traditional security solutions to detect and remove, and it is easily distributed via methods like spam emails or malicious file downloads.

Between July and August 2023, Darktrace observed an increasing trend in SmokeLoader compromises across its customer base. The anomaly-based threat detection capabilities of Darktrace, coupled with the autonomous response technology, identified and contained the SmokeLoader infections in their initial stages, preventing attackers from causing further disruption by deploying other malicious software or ransomware.

SmokeLoader Malware Attack Details

PROPagate Injection Technique

SmokeLoader utilizes the PROPagate code injection technique, a less common method that inserts malicious code into existing processes in order to appear legitimate and bypass traditional signature-based security measures [2] [3]. In the case of SmokeLoader, this technique exploits the Windows SetWindowsSubclass function, which is typically used to add or change the behavior of Windows Operation System. By manipulating this function, SmokeLoader can inject its code into other running processes, such as the Internet Explorer. This not only helps to disguise  the malware's activity but also allows attackers to leverage the permissions and capabilities of the infected process.

Obfuscation Methods

SmokeLoader is known to employ several obfuscation techniques to evade the detection and analysis of security teams. The techniques include scrambling portable executable files, encrypting its malicious code, obfuscating API functions and packing, and are intended to make the malware’s code appear harmless or unremarkable to antivirus software. This allows attackers to slip past defenses and execute their malicious activities while remaining undetected.

Infection Vector and Communication

SmokeLoader typically spreads via phishing emails that employ social engineering tactics to convince users to unknowingly download malicious payloads and execute the malware. Once installed on target networks, SmokeLoader acts as a backdoor, allowing attackers to control infected systems and download further malicious payloads from command-and-control (C2) servers. SmokeLoader uses fast flux, a DNS technique utilized by botets whereby IP addresses associated with C2 domains are rapidly changed, making it difficult to trace the source of the attack. This technique also boosts the resilience of attack, as taking down one or two malicious IP addresses will not significantly impact the botnet's operation.

Continuous Evolution

As with many MaaS strains, SmokeLoader is continuously evolving, with its developers regularly adding new features and techniques to increase its effectiveness and evasiveness. This includes new obfuscation methods, injection techniques, and communication protocols. This constant evolution makes SmokeLoader a significant threat and underscores the importance of advanced threat detection and response capabilities solution.

Darktrace’s Coverage of SmokeLoader Attack

Between July and August 2023, Darktrace detected one particular SmokeLoader infection at multiple stages of its kill chain on a customer network. This detection was made possible by Darktrace DETECT’s anomaly-based approach and Self-Learning AI that allows it to identify subtle deviations in device behavior.

One of the key components of this process is the classification of endpoint rarity and determining whether an endpoint is new or unusual for any given network. This classification is applied to various aspects of observed endpoints, such as domains, IP addresses, or hostnames within the network. It thereby plays a vital role in identifying SmokeLoader activity, such as the initial infection vector or C2 communication, which typically involve a device contacting a malicious endpoint associated with SmokeLoader.

The First Signs of Infection SmokeLoader Infection

Beginning in July 2023, Darktrace observed a surge in suspicious activities that were assessed with moderate to high confidence to be associated with SmokeLoader malware.

For example on July 30, a device was observed making a successful HTTPS request to humman[.]art, a domain that had never been seen on the network, and therefore classified as 100% rare by DETECT. During this connection, the device in question received a total of 6.0 KiB of data from the unusual endpoint. Open-source intelligence (OSINT) sources reported with high confidence that this domain was associated with the SmokeLoader C2 botnet.

The device was then detected making an HTTP request to another 100% rare external IP, namely 85.208.139[.]35, using a new user agent. This request contained the URI ‘/DefenUpdate.exe’, suggesting a possible download of an executable (.exe) file. This was corroborated by the total amount of data received in this connection, 4.3 MB. Both the file name and its size suggest that the offending device may have downloaded additional malicious tooling from the SmokeLoader C2 endpoint, such as a trojan or information stealer, as reported on OSINT platforms [4].

Figure 1: Device event log showing the moment when a device made its first connection to a SmokeLoader associated domain, and the use of a new user agent. A few seconds later, the DETECT model “Anomalous Connection / New User Agent to IP Without Hostname” breached.

The observed new user agent, “Mozilla/5.0 (Windows NT 10.0; Win64; x64; Trident/7.0; rv:11.0) like Gecko” was identified as suspicious by Darktrace leading to the “Anomalous Connection / New User Agent to IP Without Hostname” DETECT model breach.

As this specific user agent was associated with the Internet Explorer browser running on Windows 10, it may not have appeared suspicious to traditional security tools. However, Darktrace’s anomaly-based detection allows it to identify and mitigate emerging threats, even those that utilize sophisticated evasion techniques.

This is particularly noteworthy in this case because, as discussed earlier, SmokeLoader is known to inject its malicious code into legitimate processes, like Internet Explorer.

Figure 2: Darktrace detecting the affected device leveraging a new user agent and establishing an anomalous HTTP connection with an external IP, which was 100% rare to the network.

C2 Communication

Darktrace continued to observe the device making repeated connections to the humman[.]art endpoint. Over the next few days. On August 7, the device was observed making unusual POST requests to the endpoint using port 80, breaching the ‘Anomalous Connection / Multiple HTTP POSTs to Rare Hostname’ DETECT model. These observed POST requests were observed over a period of around 10 days and consisted of a pattern of 8 requests, each with a ten-minute interval.

Figure 3: Model Breach Event Log highlighting the Darktrace DETECT model breach ‘Anomalous Connection / Multiple HTTP POSTs to Rare Hostname’.

Upon investigating the details of this activity identified by Darktrace DETECT, a particular pattern was observed in these requests: they used the same user-agent, “Mozilla/5.0 (Windows NT 10.0; Win64; x64; Trident/7.0; rv:11.0) like Gecko”, which was previously detected in the initial breach.

Additionally, they the requests had a constantly changing  eferrer header, possibly using randomly generated domain names for each request. Further examination of the packet capture (PCAP) from these requests revealed that the payload in these POST requests contained an RC4 encrypted string, strongly indicating SmokeLoader C2 activity.

Figure4: Advanced Search results display an unusual pattern in the requests made by the device to the hostname humman[.]art. This pattern shows a constant change in the referrer header for each request, indicating anomalous behavior.
Figure 5: The PCAP shows the payload seen in these POST requests contained an RC4 encrypted string strongly indicating SmokeLoader C2 activity.  

Unfortunately in this case, Darktrace RESPOND was not active on the network meaning that the attack was able to progress through its kill chain. Despite this, the timely alerts and detailed incident insights provided by Darktrace DETECT allowed the customer’s security team to begin their remediation process, implementing blocks on their firewall, thus preventing the SmokeLoader malware from continuing its communication with C2 infrastructure.

Darktrace RESPOND Halting Potential Threats from the Initial Stages of Detection

With Darktrace RESPOND, organizations can move beyond threat detection to proactive defense against emerging threats. RESPOND is designed to halt threats as soon as they are identified by DETECT, preventing them from escalating into full-blown compromises. This is achieved through advanced machine learning and Self-Learning AI that is able to understand  the normal ‘pattern of life’ of customer networks, allowing for swift and accurate threat detection and response.

One pertinent example was seen on July 6, when Darktrace detected a separate SmokeLoader case on a customer network with RESPOND enabled in autonomous response mode. Darktrace DETECT initially identified a string of anomalous activity associated with the download of suspicious executable files, triggering the ‘Anomalous File / Multiple EXE from Rare External Locations’ model to breach.

The device was observed downloading an executable file (‘6523.exe’ and ‘/g.exe’) via HTTP over port 80. These downloads originated from endpoints that had never been seen within the customer’s environment, namely ‘hugersi[.]com’ and ‘45.66.230[.]164’, both of which had strongly been linked to SmokeLoader by OSINT sources, likely indicating the initial infection stage of the attack [5].

Figure 6: This figure illustrates Darktrace DETECT observing a device downloading multiple .exe files from rare endpoints and the associated model breach, ‘Anomalous File / Multiple EXE from Rare External Locations’.

Around the same time, Darktrace also observed the same device downloading an unusual file with a numeric file name. Threat actors often employ this tactic in order to avoid using file name patterns that could easily be recognized and blocked by traditional security measures; by frequently changing file names, malicious executables are more likely to remain undetected.

Figure 7: Graph showing the unusually high number of executable files downloaded by the device during the initial infection stage of the attack. The orange and red circles represent the number of model breaches that the device made during the observed activity related to SmokeLoader infection.
Figure 8: This figure illustrates the moment when Darktrace DETECT identified a suspicious download with a numeric file name.

With Darktrace RESPOND active and enabled in autonomous response mode, the SmokeLoader infection was thwarted in the first instance. RESPOND took swift autonomous action by blocking connections to the suspicious endpoints identified by DETECT, blocking all outgoing traffic, and enforcing a pre-established “pattern of life” on offending devices. By enforcing a patten of life on a device, Darktrace RESPOND ensures that it cannot deviate from its ‘normal’ activity to carry out potentially malicious activity, while allowing the device to continue expected business operations.

Figure 9:  A total of 8 RESPOND actions were applied, including blocking connections to suspicious endpoints and domains associated with SmokeLoader.

In addition to the autonomous mitigative actions taken by RESPOND, this customer also received a Proactive Threat Notification (PTN) informing them of potentially malicious activity on their network. This prompted the Darktrace Security Operations Center (SOC) to investigate and document the incident, allowing the customer’s security team to shift their focus to remediating and removing the threat of SmokeLoader.

Conclusion

Ultimately, Darktrace showcased its ability to detect and contain versatile and evasive strains of loader malware, like SmokeLoader. Despite its adeptness at bypassing conventional security tools by frequently changing its C2 infrastructure, utilizing existing processes to infect malicious code, and obfuscating malicious file and domain names, Darktrace’s anomaly-based approach allowed it to recognize such activity as deviations from expected network behavior, regardless of their apparent legitimacy.

Considering SmokeLoader’s wide array of functions, including C2 communication that could be used to facilitate additional attacks like exfiltration, or even the deployment of information-stealers or ransomware, Darktrace proved to be crucial in safeguarding customer networks. By identifying and mitigating SmokeLoader at the earliest possible stage, Darktrace effectively prevented the compromises from escalating into more damaging and disruptive compromises.

With the threat of loader malware expected to continue growing alongside the boom of the MaaS industry, it is paramount for organizations to adopt proactive security solutions, like Darktrace DETECT+RESPOND, that are able to make intelligent decisions to identify and neutralize sophisticated attacks.

Credit to Patrick Anjos, Senior Cyber Analyst, Justin Torres, Cyber Analyst

Appendices

Darktrace DETECT Model Detections

- Anomalous Connection / New User Agent to IP Without Hostname

- Anomalous Connection / Multiple HTTP POSTs to Rare Hostname

- Anomalous File / Multiple EXE from Rare External Locations

- Anomalous File / Numeric File Download

List of IOCs (IOC / Type / Description + Confidence)

- 85.208.139[.]35 / IP / SmokeLoader C2 Endpoint

- 185.174.137[.]109 / IP / SmokeLoader C2 Endpoint

- 45.66.230[.]164 / IP / SmokeLoader C2 Endpoint

- 91.215.85[.]147 / IP / SmokeLoader C2 Endpoint

- tolilolihul[.]net / Hostname / SmokeLoader C2 Endpoint

- bulimu55t[.]net / Hostname / SmokeLoader C2 Endpoint

- potunulit[.]org / Hostname / SmokeLoader C2 Endpoint

- hugersi[.]com / Hostname / SmokeLoader C2 Endpoint

- human[.]art / Hostname / SmokeLoader C2 Endpoint

- 371b0d5c867c2f33ae270faa14946c77f4b0953 / SHA1 / SmokeLoader Executable

References:

[1] https://bazaar.abuse.ch/sample/d7c395ab2b6ef69210221337ea292e204b0f73fef8840b6e64ab88595eda45b3/#intel

[2] https://malpedia.caad.fkie.fraunhofer.de/details/win.smokeloader

[3] https://www.darkreading.com/cyber-risk/breaking-down-the-propagate-code-injection-attack

[4] https://n1ght-w0lf.github.io/malware%20analysis/smokeloader/

[5] https://therecord.media/surge-in-smokeloader-malware-attacks-targeting-ukrainian-financial-gov-orgs

MITRE ATT&CK Mapping

Model: Anomalous Connection / New User Agent to IP Without Hostname

ID: T1071.001

Sub technique: T1071

Tactic: COMMAND AND CONTROL

Technique Name: Web Protocols

Model: Anomalous Connection / Multiple HTTP POSTs to Rare Hostname

ID: T1185

Sub technique: -

Tactic: COLLECTION

Technique Name: Man in the Browser

ID: T1071.001

Sub technique: T1071

Tactic: COMMAND AND CONTROL

Technique Name: Web Protocols

Model: Anomalous File / Multiple EXE from Rare External Locations

ID: T1189

Sub technique: -

Tactic: INITIAL ACCESS

Technique Name: Drive-by Compromise

ID: T1588.001

Sub technique: - T1588

Tactic: RESOURCE DEVELOPMENT

Technique Name: Malware

Model: Anomalous File / Numeric File Download

ID: T1189

Sub technique: -

Tactic: INITIAL ACCESS

Technique Name: Drive-by Compromise

ID: T1588.001

Sub technique: - T1588

Tactic: RESOURCE DEVELOPMENT

Technique Name: Malware

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
Patrick Anjos
Senior Cyber Analyst

More in this series

No items found.

Blog

/

/

August 13, 2025

ISO/IEC 42001: 2023: A milestone in AI standards at Darktrace  

Default blog imageDefault blog image

Darktrace announces ISO/IEC 42001 accreditation

Darktrace is thrilled to announce that we are one of the first cybersecurity companies to achieve ISO/IEC 42001 accreditation for the responsible management of AI systems. This isn’t just a milestone for us, it’s a sign of where the AI industry is headed. ISO/IEC 42001 is quickly emerging as the global benchmark for separating vendors who truly innovate with AI from those who simply market it.

For customers, it’s more than a badge, it’s assurance that a vendor’s AI is built responsibly, governed with rigor, and backed by the expertise of real AI teams, keeping your data secure while driving meaningful innovation.

This is a critical milestone for Darktrace as we continue to strengthen our offering, mature our governance and compliance frameworks for AI management, expand our research and development capabilities, and further our commitment to the development of responsible AI.  

It cements our commitment to providing secure, trustworthy and proactive cybersecurity solutions that our customers can rely on and complements our existing compliance framework, consisting of certifications for:

  • ISO/IEC 27001:2022 – Information Security Management System
  • ISO/IEC 27018:2019 – Protection of Personally Identifiable Information in Public Cloud Environments
  • Cyber Essentials – A UK Government-backed certification scheme for cybersecurity baselines

What is ISO/IEC 42001:2023?

In response to the unique challenges that AI poses, the International Organization for Standardization (ISO) introduced the ISO/IEC 42001:2023 framework in December 2023 to help organizations providing or utilizing AI-based products or services to demonstrate responsible development and use of AI systems. To achieve the accreditation, organizations are required to establish, implement, maintain, and continually improve their Artificial Intelligence Management System (AIMS).

ISO/IEC 42001:2023 is the first of its kind, providing valuable guidance for this rapidly changing field of technology. It addresses the unique ethical and technical challenges AI poses by setting out a structured way to manage risks such as transparency, accuracy and misuse without losing opportunities. By design, it balances the benefits of innovation against the necessity of a proper governance structure.

Being certified means the organization has met the requirements of the ISO/IEC 42001 standard, is conforming to all applicable regulatory and legislative requirements, and has implemented thorough processes to address AI risks and opportunities.

What is the  ISO/IEC 42001:2023 accreditation process?

Darktrace partnered with BSI over an 11-month period to undertake the accreditation. The process involved developing and implementing a comprehensive AI management system that builds on our existing certified frameworks, addresses the risks and opportunities of using and developing cutting-edge AI systems, underpins our AI objectives and policies, and meets our regulatory and legal compliance requirements.

The AI Management System, which takes in our people, processes, and products, was extensively audited by BSI against the requirements of the standard, covering all aspects spanning the design of our AI, use of AI within the organization, and our competencies, resources and HR processes. It is an in-depth process that we’re thrilled to have undertaken, making us one of the first in our industry to achieve certification for a globally recognized AI system.

The scope of Darktrace’s certification is particularly wide due to our unique Self-Learning approach to AI for cybersecurity, which uses multi-layered AI systems consisting of varied AI techniques to address distinct cybersecurity tasks. The certification encompasses production and provision of AI systems based on anomaly detection, clustering, classifiers, regressors, neural networks, proprietary and third-party large language models for proactive, detection, response and recovery cybersecurity applications. Darktrace additionally elected to adopt all Annex A controls present in the ISO/IEC 42001 standard.

What are the benefits of an AI Management System?

While AI is not a new or novel concept, the AI industry has accelerated at an unprecedented rate in the past few years, increasing operational efficiency, driving innovation, and automating cumbersome processes in the workplace.

At the same time, the data privacy, security and bias risks created by rapid innovation in AI have been well documented.

Thus, an AI Management System enables organizations to confidently establish and adhere to governance in a way that conforms to best practice, promotes adherence, and is in line with current and emerging regulatory standards.

Not only is this vital in a unique and rapidly evolving field like AI, it additionally helps organization’s balance the drive for innovation with the risks the technology can present, helping to get the best out of their AI development and usage.

What are the key components of ISO/IEC 42001?

The Standard puts an emphasis on responsible AI development and use, requiring organizations to:

  • Establish and implement an AI Management System
  • Commit to the responsible development of AI against established, measurable objectives
  • Have in place a process to manage, monitor and adapt to risks in an effective manner
  • Commit to continuous improvement of their AI Management System

The AI Standard is similar in composition to other ISO standards, such as ISO/IEC 27001:2022, which many organizations may already be familiar with. Further information as to the structure of ISO/IEC 42001 can be found in Annex A.

What it means for Darktrace’s customers

Our certification against ISO/IEC 42001 demonstrates Darktrace’s commitment to delivering industry-leading Self-Learning AI in the name of cybersecurity resilience. Our stakeholders, customers and partners can be confident that Darktrace is responsibly, ethically and securely developing its AI systems, and is managing the use of AI in our day-to-day operations in a compliant, secure and ethical manner. It means:

  • You can trust our AI: We can demonstrate our AI is developed responsibly, in a transparent manner and in accordance with ethical rules. For more information and to learn about Darktrace's responsible AI in cybersecurity approach, please see here.
  • Our products are backed by innovation and integrity: Darktrace drives cutting edge AI innovation with ethical governance and customer trust at its core.
  • You are partnering with an organization which stays ahead of regulatory changes: In an evolving AI landscape, partnering with Darktrace helps you to stay prepared for emerging compliance and regulatory demands in your supply chain.

Achieving ISO/IEC 42001:2023 certification is not just a checkpoint for us. It represents our unwavering commitment to setting a higher standard for AI in cybersecurity. It reaffirms our leadership in building and implementing responsible AI and underscores our mission to continuously innovate and lead the way in the industry.

Why ISO/IEC 42001 matters for every AI vendor you trust

In a market where “AI” can mean anything from a true, production-grade system to a thin marketing layer, ISO/IEC 42001 acts as a critical differentiator. Vendors who have earned this certification aren’t just claiming they build responsible AI, they’ve proven it through an independent, rigorous audit of how they design, deploy, and manage their systems.

For you as a customer, that means:

You know their AI is real: Certified vendors have dedicated, skilled AI teams building and maintaining systems that meet measurable standards, not just repackaging off-the-shelf tools with an “AI” label.

Your data is safeguarded: Compliance with ISO/IEC 42001 includes stringent governance over data use, bias, transparency, and risk management.

You’re partnering with innovators: The certification process encourages continuous improvement, meaning your vendor is actively advancing AI capabilities while keeping ethics and security in focus.

In short, ISO/IEC 42001 is quickly becoming the global badge of credible AI development. If your vendor can’t show it, it’s worth asking how they manage AI risk, whether their governance is mature enough, and how they ensure innovation doesn’t outpace accountability.

Annex A: The Structure of ISO/IEC 42001

ISO/IEC 42001 has requirements for which seven adherence is required for an organization seeking to obtain or maintain its certification:

  • Context of the organization – organizations need to demonstrate an understanding of the internal and external factors influencing the organization’s AI Management System.
  • Leadership – senior leadership teams need to be committed to implementing AI governance within their organizations, providing direction and support across all aspects AI Management System lifecycle.
  • Planning – organizations need to put meaningful and manageable processes in place to identify risks and opportunities related to the AI Management System to achieve responsible AI objectives and mitigate identified risks.
  • Support – demonstrating a commitment to provisioning of adequate resources, information, competencies, awareness and communication for the AI Management System is a must to ensure that proper oversight and management of the system and its risks can be achieved.
  • Operation – establishing processes necessary to support the organization’s AI system development and usage, in conformance with the organization’s AI policy, objectives and requirements of the standard. Correcting the course of any deviations within good time is paramount.
  • Performance evaluation – the organization must be able to demonstrate that it has the capability and willingness to regularly monitor and evaluate the performance of the AI Management System effectively, including actioning any corrections and introducing new processes where relevant.
  • Improvement – relying on an existing process will not be sufficient to ensure compliance with the AI Standard. Organizations must commit to monitoring of existing systems and processes to ensure that the AI Management System is continually enhanced and improved.

To assist organizations in seeking the above, four annexes are included within the AI Standard’s rubric, which outline the objectives and measures an organization may wish to implement to address risks related to the design and operation of their AI Management System through the introduction of normative controls. Whilst they are not prescriptive, Darktrace has implemented the requirements of these Annexes to enable it to appropriately demonstrate the effectiveness of its AI Management System. We have placed a heavy emphasis on Annex A which contains these normative controls which we, and other organizations seeking to achieve certification, can align with to address the objectives and measures, such as:

  • Enforcement of policies related to AI.
  • Setting responsibilities within the organization, and expectation of roles and responsibilities.
  • Creating processes and guidelines for escalating and handling AI concerns.
  • Making resources for AI systems available to users.
  • Assessing impacts of AI systems internally and externally.
  • Implementing processes across the entire AI system life cycle.
  • Understanding treatment of Data for AI systems.
  • Defining what information is, and should be available, for AI systems.
  • Considering and defining use cases for the AI systems.
  • Considering the impact of the AI System on third-party and customer relationships.

The remaining annexes provide guidance on implementing Annex A’s controls, objectives and primary risk sources of AI implementation, and considering how the AI Management System can be used across domains or sectors responsibly.

[related-resource]

Continue reading
About the author

Blog

/

/

August 12, 2025

Minimizing Permissions for Cloud Forensics: A Practical Guide to Tightening Access in the Cloud

Default blog imageDefault blog image

Most cloud environments are over-permissioned and under-prepared for incident response.

Security teams need access to logs, snapshots, and configuration data to understand how an attack unfolded, but giving blanket access opens the door to insider threats, misconfigurations, and lateral movement.

So, how do you enable forensics without compromising your security posture?

The dilemma: balancing access and security

There is a tension between two crucial aspects of cloud security that create a challenge for cloud forensics.

One aspect is the need for Security Operations Center (SOC) and Incident Response (IR) teams to access comprehensive data for investigating and resolving security incidents.

The other conflicting aspect is the principle of least privilege and minimal manual access advocated by cloud security best practices.

This conflict is particularly pronounced in modern cloud environments, where traditional physical access controls no longer apply, and infrastructure-as-code and containerization have transformed the landscape.

There are several common but less-than-ideal approaches to this challenge:

  • Accepting limited data access, potentially leaving incidents unresolved
  • Granting root-level access during major incidents, risking further compromise

Relying on cloud or DevOps teams to retrieve data, causing delays and potential miscommunication

[related-resource]

Challenges in container forensics

Containers present unique challenges for forensic investigations due to their ephemeral and dynamic nature. The orchestration and management of containers, whether on private clusters or using services like AWS Elastic Kubernetes Service (EKS), introduce complexities in capturing and analyzing forensic data.

To effectively investigate containers, it's often necessary to acquire the underlying volume of a node or perform memory captures. However, these actions require specific Identity and Access Management (IAM) and network access to the node, as well as familiarity with the container environment, which may not always be straightforward.

An alternative method of collection in containerized environments is to utilize automated tools to collect this evidence. Since they can detect malicious activity and collect relevant data without needing human input, they can act immediately, securing evidence that might be lost by the time a human analyst is available to collect it manually.

Additionally, automation can help significantly with access and permissions. Instead of analysts needing the correct permissions for the account, service, and node, as well as deep knowledge of the container service itself, for any container from which they wish to collect logs. They can instead collect them, and have them all presented in one place, at the click of a button.

A better approach: practical strategies for cloud forensics

It's crucial to implement strategies that strike a balance between necessary access and stringent security controls.

Here are several key approaches:

1. Dedicated cloud forensics accounts

Establishing a separate cloud account or subscription specifically for forensic activities is foundational. This approach isolates forensic activities from regular operations, preventing potential contamination from compromised environments. Dedicated accounts also enable tighter control over access policies, ensuring that forensic operations do not inadvertently expose sensitive data to unauthorized users.

A separate account allows for:

  • Isolation: The forensic investigation environment is isolated from potentially compromised environments, reducing the risk of cross-contamination.
  • Tighter access controls: Policies and controls can be more strictly enforced in a dedicated account, reducing the likelihood of unauthorized access.
  • Simplified governance: A clear and simplified chain of custody for digital evidence is easier to maintain, ensuring that forensic activities meet legal and regulatory requirements.

For more specifics:

2. Cross-account roles with least privilege

Using cross-account IAM roles, the forensics account can access other accounts, but only with permissions that are strictly necessary for the investigation. This ensures that the principle of least privilege is upheld, reducing the risk of unauthorized access or data exposure during the forensic process.

3. Temporary credentials for just-in-time access

Leveraging temporary credentials, such as AWS STS tokens, allows for just-in-time access during an investigation. These credentials are short-lived and scoped to specific resources, ensuring that access is granted only when absolutely necessary and is automatically revoked after the investigation is completed. This reduces the window of opportunity for potential attackers to exploit elevated permissions.

For AWS, you can use commands such as:

aws sts get-session-token --duration-seconds 43200

aws sts assume-role --role-arn role-to-assume --role-session-name "sts-session-1" --duration-seconds 43200

For Azure, you can use commands such as:

az ad app credential reset --id <appId> --password <sp_password> --end-date 2024-01-01

For more details for Google Cloud environments, see “Create short-lived credentials for a service account” and the request.time parameter.

4. Tag-based access control

Pre-deploying access control based on resource tags is another effective strategy. By tagging resources with identifiers like "Forensics," access can be dynamically granted only to those resources that are relevant to the investigation. This targeted approach minimizes the risk of overexposure and ensures that forensic teams can quickly and efficiently access the data they need.

For example, in AWS:

Condition: StringLike: aws:ResourceTag/Name: ForensicsEnabled

Condition: StringLike: ssm:resourceTag/SSMEnabled: True

For example, in Azure:

"Condition": "StringLike(Resource[Microsoft.Resources/tags.example_key], '*')"

For example, in Google Cloud:

expression: > resource.matchTag('tagKeys/ForensicsEnabled', '*')

Tighten access, enhance security

The shift to cloud environments demands a rethinking of how we approach forensic investigations. By implementing strategies like dedicated cloud forensic accounts, cross-account roles, temporary credentials, and tag-based access control, organizations can strike the right balance between access and security. These practices not only enhance the effectiveness of forensic investigations but also ensure that access is tightly controlled, reducing the risk of exacerbating an incident or compromising the investigation.

Find the right tools for your cloud security

Darktrace delivers a proactive approach to cyber resilience in a single cybersecurity platform, including cloud coverage.

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.

In addition to having these forensics capabilities, 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.

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