Image: any.run · rights & removal
Your New MTTR Shortcut — Introducing Related Threat Context: Cut Time
Reporting by Any.run BlogRead the original at any.run
Executive Summary
The integration of Related Threat Context into the ANY.RUN Interactive Sandbox aims to resolve triage bottlenecks for SOC and MSSP analysts. By surfacing industry-specific observations, previous team findings, and broader threat intelligence directly alongside Indicators of Compromise (IOCs), the system seeks to reduce the time required for Tier 1 analysts to decide whether to close, escalate, or further investigate a case. This approach is intended to lower the Mean Time to Remediate (MTTR) and prevent duplicated efforts across different analyst shifts.
The system employs specific signals—"Never Seen Before" and "Commonly Seen"—to help analysts prioritize their attention, though these are framed as supplementary signals rather than definitive verdicts. While internal SOCs benefit from anonymized industry data to identify potential targeting, MSSPs are excluded from this specific data stream. The overall objective is to transition the security workflow from isolated sandbox analysis to a connected enrichment process, providing Tier 2 analysts with a more comprehensive starting point for incident response.
Facts Only
* ANY.RUN Enterprise clients have access to a feature called Related Threat Context.
* The feature integrates three types of information: Industry Context, Team Context, and ANY.RUN Threat Intelligence.
* Industry Context provides anonymized data on whether an IOC appeared in analyses associated with the organization's industry.
* Team Context links IOCs to previous sandbox analyses performed by the user's own team.
* ANY.RUN Threat Intelligence provides a path to Threat Intelligence Lookup for investigating samples and infrastructure.
* The feature includes signals labeled "Never Seen Before" and "Commonly Seen."
* MSSPs have access to Team Context and ANY.RUN Threat Intelligence, but not Industry Context.
* The tool is designed for use during Interactive Sandbox analysis.
* ANY.RUN is SOC 2 Type II certified.
* The company serves over 16,000 organizations and 700,000 security professionals.
Full Take
The strongest version of this narrative is that the "fragmentation of intelligence" is a primary driver of SOC burnout and inefficiency, and that consolidating context at the moment of analysis is the most effective way to empower junior analysts.
However, this is a classic vendor-driven narrative where the problem is framed specifically to make the product the only logical solution. The push relies on a Fear Appeal—highlighting the "missing context" that leads to "unnecessary escalations" and "duplicated investigations"—and then utilizes an Authority Game by presenting the vendor's own tool as the definitive mechanism for "SOC maturity." The evidence provided is circular: the tool's value is demonstrated through use cases that only the tool can solve.
Patterns detected: ARC-0012 Fear Appeal, ARC-0061 Authority Game
The driving paradigm here is "Efficiency through Integration." It assumes that the primary barrier to security is the speed of information retrieval rather than the quality of analysis or the shortage of skilled personnel. This echoes the broader industry trend of "single-pane-of-glass" promises, which often trade deep, critical investigation for rapid, signal-based triage.
The benefit accrues to the vendor and the SOC manager looking for scalable metrics (lower MTTR). The cost may be a subtle erosion of analyst agency, where "Commonly Seen" signals might lead to the premature dismissal of a sophisticated, blended threat that mimics common noise.
Bridge Questions:
1. Does automating context discovery encourage analysts to trust the tool's signals over their own behavioral analysis?
2. How does the exclusion of industry context for MSSPs affect the quality of service provided to their clients?
3. What evidence exists that faster triage leads to more accurate detection, rather than just faster closures?
Counterstrike Scan: A coordinated campaign would identify a common pain point (analyst fatigue), amplify the risk of "missing" a threat, and present a proprietary tool as the only way to achieve "maturity." This content aligns structurally with that playbook.
From the original · Any.run Blog
During triage, analysts may overlook valuable threat intelligence simply because they don’t know it exists. Previous investigations, related malicious activity, and industry-specific observations could provide the context needed to decide what to investigate next.Read the full story at any.run
