Get a Demo
Under Attack?
A graphic with the Upwind logo in the top left corner shows rows of rounded rectangles in shades of blue and purple. A bright pink bar with a warning symbol appears in the center.

Achieve Deeper Runtime Threat Investigation with Upwind Detection Logs 

<br />
<b>Warning</b>:  Undefined variable $photo in <b>/nas/content/live/landing173/wp-content/themes/bricks/includes/elements/code.php(236) : eval()'d code</b> on line <b>24</b><br />
<br />
<b>Warning</b>:  Trying to access array offset on value of type null in <b>/nas/content/live/landing173/wp-content/themes/bricks/includes/elements/code.php(236) : eval()'d code</b> on line <b>24</b><br />
Chris Lentricchia April 17, 2025

Imagine a threat appears, vanishes, and then reappears two days later – same process, slightly different path. Without the right visibility, you’d treat it like a new incident each time. But with Upwind Detection Logs, you get the historical context to see the full picture.

Upwind provides deep runtime visibility and security across all environments, regardless of complexity. Building on this premise, we are thrilled to announce Upwind Detection Logs. Upwind’s detection logs enable you to deliver deeper and more accurate threat investigation at runtime, by providing a historical record of how often a process associated with a specific threat has occurred. 

What are Logs and Why are Logs Important for Security?


Logs are a cornerstone of visibility and security, and Upwind’s detection logs provide a uniquely powerful lens into recurring threats by connecting runtime behavior to historical patterns. Just like their physical counterparts, logs are digital receipts that provide a record of information for every digital transaction that has taken place inside a particular system. From a security perspective, logs play a critical line of defense. By analyzing log entries, you can uncover how attackers gained access to your system, how they escalated privileges, or moved across containers. 

Logs can also help conduct post-incident forensics, creating a detailed timeline, pinpointing an attack vector, assessing the scope of the attack, and ultimately, assigning accountability.

A log is generated whenever an event occurs within a system. Each log entry typically contains vital historical information, such as a timestamp, the source of the event, the type of event, and additional details specific to the event. 

Timestamp: 2025-04-02T14:35:42Z  
User ID: johndoe  
Event Type: LOGIN_FAILURE  
Source IP: 192.168.1.200  
Target System: Web Application  
Details: Invalid password entered 3 times; account temporarily locked. 

A yaml log informing of a failed login attempt.

Using Logs For Deeper Threat Investigation

Recognizing the critical role of logs in threat analysis, the Upwind Platform now includes a log tab to display logs and surface historical activity tied to each detected threat. Our detection logs are a simple and powerful tool that records recurring processes associated with a threat, enabling deeper investigation, and revealing the frequency of the malicious process that triggered the threat. 

A cybersecurity dashboard shows a detection alert titled “A container is executing a reverse shell” with visual graphs, resource risk analysis, executed process details, and navigation panels on the left.

Detection logs contain key data points: the process that was executed, the command being run, and the IDs of the node, host, and container involved. This granularity helps pinpoint where and how a threat is unfolding.  You can also view a process tree in order to gain a contextual understanding of how the process that is triggering the threat is interacting with your environment.

A cybersecurity dashboard displays a detection alert for a Ncat Reverse Shell. The left pane lists other alerts, while the main section shows details about the incident, including process tree and actionable response options.

Benefits

Detection logs take Upwind’s detection  runtime threat detection and investigation capabilities to the next level by providing access to not just the most recent malicious process associated with a threat, but up to 100 past malicious processes, from the past seven days. This is invaluable for several reasons:

  • Identifying Patterns: Examining multiple malicious processes enables you to identify recurring tactics, techniques, and procedures used by attackers. This information helps to anticipate future attacks, then proactively implement countermeasures before they happen. 
  • Assessing Threat Severity: Understanding the full scope of a threat’s activity, rather than just the most recent action, enables a more accurate assessment of a threat’s severity and potential impact.
  • Improving Security Posture:  Easily identifying weaknesses in your existing security controls allows you to then prioritize remediation efforts, leading to a stronger overall security posture.
Screenshot of a security dashboard showing a detection alert titled A container is executing a reverse shell, with logs, user comments, and prevention response options listed on the right side of the interface.

Learn More

Traditionally, security platforms have only been able to record the most recent process associated with a threat – often due to architectural constraints or performance limitations that prevent capturing a full historical view. By providing a historical and comprehensive record of malicious processes associated with a threat, Upwind enables deeper visibility into threat activity, ultimately, empowering you to conduct a more thorough investigation.

Interested in achieving deep visibility at runtime with Upwind? Visit the Upwind Documentation Center (login required), schedule a demo with us, or drop us a line at [email protected]

Contents

Further Reading

OpenAI Breach

Everyone Read the OpenAI Breach as a Model Story, But It Was a Runtime Story

Key Takeaways Autonomous AI agents can now break out of a sandbox, cross an internal network, and breach a production system with no human at the keyboard. OpenAI's evaluation that hacked Hugging Face this month is the clearest proof on record. Most of the coverage read it as a story about a model turning dangerous.…
upwind-identities

Introducing the Upwind Identity Graph: End-to-End Identity Security

Identity used to be treated as a directory problem: find the user, inspect the groups, review the assigned roles, and decide whether the account has too much access. That model no longer matches the cloud. A single person may authenticate through Okta, inherit permissions from multiple groups, receive role assignments in more than one cloud,…
AI-Graph

Introducing the Upwind AI Graph: Extending AI Inventory Beyond Cloud Infrastructure

As enterprise adoption of artificial intelligence accelerates, modern AI infrastructure has expanded far beyond traditional cloud perimeters. Securing enterprise AI today requires complete visibility across four distinct operational layers: Traditional cloud security tools stop at the cloud provider boundary. When enterprise teams connect directly to external AI Providers, security teams lose sight of access paths,…
Add the Upwind RSS Feed to Slack
Connect the Upwind RSS Feed to your Slack.
Follow the how-to here.
Threat RSS
Add the Upwind RSS Feed to Slack
Connect the Upwind RSS Feed to your Slack.
Follow the how-to here.
Main RSS