Image: any.run · rights & removal
Run and Scale Your MSSP or SOC Like Never Before: Meet ANY.RUN’s Multi
Reporting by Any.run BlogRead the original at any.run
Executive Summary
ANY.RUN Multi-Tenant Teamspace is a new feature built upon existing Teamwork capabilities designed to manage security operations for MSSPs and MSPs by creating separate, isolated environments. This system introduces features like multi-tenancy to ensure customer data and investigations remain private, direct customer views for transparency, and centralized management for teams. Key functionalities include distinct areas for managing customers, teams, resources, and security results. The workflow is designed to connect customer alerts, threat investigations, team handoffs, customer visibility, and overall security overviews, aiming to streamline the process from initial alert through to reporting and management.
The system facilitates specific operational benefits for different stakeholders. For MSSPs, it allows for the secure separation of client data while enabling them to provide customers with controlled access to their results, enhancing service transparency. For SOC teams, features like Teamhistory allow analysts to reuse previous findings across related analyses, reducing redundant work during investigations. Furthermore, managers gain oversight through team performance overviews and threat landscape views, providing context for resource allocation and strategic decision-making.
Facts Only
* Multi-Tenant Teamspace builds on existing Teamwork capabilities.
* It creates separate client environments to maintain customer data and investigations privacy.
* Features include a Customer View allowing customers direct access to their security work and results.
* It supports Multi-Team & Centralized Management with independent teams, access control, and shared resources.
* Case and Teamhistory allow related analyses in one case and shared investigation history for repeated work.
* Team Performance Overview tracks team activity, investigation results, and detection metrics.
* Threat Landscape Overview shows detected threats, trends, and analysis coverage across organizations or customers.
* An MSSP scenario involves an analyst investigating an alert, grouping analyses into a Case, handing off the investigation, showing customer visibility, and reviewing team performance.
* Managers can control team access and redistribute available seats and limits based on workload.
* The system is available to eligible Enterprise and Enterprise Suite customers.
Full Take
The introduction of Multi-Tenant Teamspace represents a structural shift from managing security operations within a monolithic structure to accommodating the segmented realities of the MSSP/MSP ecosystem. The pattern driving this development is the tension between centralized organizational efficiency and decentralized client autonomy. By implementing multi-tenancy, the system attempts to resolve this tension by creating explicit boundaries for data privacy (Multi-Tenancy) while simultaneously introducing structured mechanisms for cross-client operational synergy (Teamhistory, Overview).
The integration of workflows—linking alerts directly into Cases, linking sandbox analyses via Teamhistory, and providing aggregated metrics via the Overview—suggests a deliberate design to optimize the knowledge flow during complex investigations. This attempts to mitigate the inherent inefficiency of siloed work where findings often remain trapped in individual analyst workspaces, forcing analysts to repeat effort or rely solely on static reporting for situational awareness. The potential implication is that true security maturity relies not just on detection capability but on the ability to manage vast amounts of distributed investigative data cohesively.
What is unstated here is the inherent tension between granting flexibility and enforcing governance across separate entities. When access rules, resource sharing (seat redistribution), and historical context are all layered onto a system managing multiple customers, the complexity shifts from managing individual investigations to managing the complex interaction layer itself. The pattern observed is an attempt to use sophisticated linkage (Cases/Teamhistory) to compensate for the necessary separation imposed by multi-tenancy. This forces a critical question: does this organizational flow simplify the operational burden, or does it simply shift the administrative overhead into a more intricate system that requires specialized management skills?
Bridge questions: How do the established team structures and access controls interact with dynamic client workload changes when resource pooling is introduced? What are the unintended consequences of managing overlapping views (e.g., customer visibility versus internal metrics) on analyst focus and trust? How does this framework address the legal and compliance requirements that necessitate absolute data separation in a multi-tenant environment?
From the original · Any.run Blog
As your security operations grow, so does the work behind them. More clients, more analysts, more investigations, and more things to manage every day.Read the full story at any.run
Sentinel unavailable
The automated check of the source article's wording did not complete, so no result is shown.
This looks only at the wording of the original source article, not at this page's AI-written sections. A small local AI model made this estimate. It has not been checked against known human and machine texts, so treat it as provisional. It cannot show who wrote an article.
