Context
For security operations teams, an SIEM is a central tool that supports different core outcomes. Most commonly, an SIEM is used to:
Perform TDIR operations.
Offer a system of record for investigation, reporting and forensics.
Be a single source of truth for bigger picture insights.
The evolution of the SIEM market reflects these varying buyer needs, as vendors specialize in meeting various customer objectives based on their organization types. Buyers should carefully assess their needs and select criteria that best support those outcomes most favorable to their organization. In other words, even a market-leading SIEM may not be right for every size and type of organization.
Use the common customer type scenarios below to select certain capabilities that most reflect your organizational needs and weight them accordingly.
Large Organization or Those With High Security Maturity
Typically, this sort of customer type will need many different outcomes that may service security, compliance and governance teams. They also need to integrate with many different data sources and support the workflow of larger SOC teams. Lastly, they are often concerned about the costs associated with large-scale data ingestion.
To support these needs, clients of this type often weigh these criteria higher:
Integrations to support various data sources and support the dependency management of their broader TDIR stack and other supporting technologies.
Customizations that allow for specialized reporting and role-based workflow.
Data management options that allow for more options to manage ingestion into the SIEM and control cost.
Federated and/or multitennant deployment models that support the need for distributed monitoring, often needed for global organizations.
Workflow augmentation that drives team efficacy and performance.
Cloud-First Organizations
Security buyers in these organizations have usually been given a mandate by senior management to support the company’s direction to be cloud-first or support the organization’s chosen cloud provider. They need to perform the TDIR function best aligned to their chosen environment and also need to maximize their investment in their cloud platform.
To support those needs, buyers of this type often weigh these criteria higher:
Natively support TDIR functions within their chosen cloud environment.
Offer extended integrations into other security and cloud components that increase visibility and simplify operations within the cloud platform.
Support other cloud integrations into SaaS applications, multicloud support or federated architectures.
Midsize or Small In-House SOC Organizations
This group represents the bulk of everyday enterprise buyers looking to use SIEM to support their TDIR objectives. Although this group desires many security outcomes, they often have smaller security teams and limited overall resources to operate an SIEM. They seek an overall reduction in complexity and simplified operations as a driving factor.
Organizations of this type often weigh these criteria higher:
Simplification of basic functions such as query, detection creation, investigation and built-in response.
Workflow augmentation through both AI and automation that can simplify operations, provide guidance and overall scale their team’s abilities.
Converged TDIR platforms that help reduce complexity through vendors that can better integrate supporting TDIR technologies into the SIEM, assist in managing dependencies and provide more detailed security insights.
Rich content libraries that offer detection content, automation playbooks and other such features that help streamline operations.
Native or readily available support for ongoing operations assistance.
Critical Capabilities Definition
Architecture and Deployment
This capability addresses the SIEM architecture requirements for buyers, in addition to the effort required to deploy and integrate a solution and capabilities that support and ease that deployment experience.
SIEM solution architectures must support a variety of buyer environments, including on-premises, cloud-hosted and cloud-native, ranging from midsize enterprises and less complex environments that may want a simple solution to global enterprises and managed security service providers with complex environments that require distributed, n-tier architectures and deployments or data residency in specific regions. SIEM buyers need to assess how best to integrate with the solution and constituent components. Increasingly, SIEM buyers must account for requirements to monitor and collect data on demand from third-party cloud services via API with their SIEM solution.
Ease of deployment and time to value are also important to buyers as they look to quickly and efficiently implement and operationalize SIEM solutions.
Data Collection
This capability addresses an SIEM solution’s ability to properly and easily manage logs, API calls and other data of increasing volumes and velocity, from a variety of sources, using a variety of methods across on-premises and/or in cloud infrastructure.
Data collection and management must address different forms of data (structured or unstructured) and remote access or collection mechanisms (syslog, batch collection, API). In addition to collecting the data, the SIEM solution needs corresponding parsers in order to process data for a variety of functions (analysis, reporting and search). Once collected, the data can be stored in a raw form; a normalized, enriched or contextualized form; or a combination thereof. Management of the data to ensure the appropriate confidentiality, integrity and availability in transport, use and storage is also important (via encryption, masking or tokenization, for example). The adoption of big data type solutions to handle the increasing volume, velocity and variety of data is becoming more common with SIEM solutions.
Decentralized/federated searching to query events outside the SIEM data repository is also becoming commonplace. The ability to manage how data is stored and retained is covered in this capability. Data storage for the various activities performed with the SIEM can range from local storage, the use of SAN and NAS systems and cloud storage solutions.
Add-On Components
This capability addresses the solutions available from an SIEM solution vendor that are highly complementary and integrated with the SIEM solution and integration with complementary third-party solutions.
A segment of SIEM buyers, such as those with lower security operations maturity, those replacing legacy solutions or those building a new SOC, may prefer to purchase technologies and tools that are complementary and tightly integrated to the SIEM from a single vendor.
These could include, but not limited to:
Network detection and response (NDR) and network packet capture
Endpoint detection and response (EDR)
Extended detection and response (XDR)
Cloud security solutions, including cloud-native application protection platforms (CNAPPs)
Security orchestration automation and response (SOAR)
Tools specifically oriented around the security of operational technology (OT)/industrial control systems (ICS) environments
User and entity behavior analytics (UEBA)
Threat intelligence platform (TIP)
Others like exposure and vulnerability assessment (VA)
How these solutions are integrated by the SIEM vendor with their solution as well as how they are packaged for consumption by buyers are also considerations.
Content
This capability addresses the mechanisms available through the SIEM to detect, prioritize and report on activities that represent a threat to the business or are otherwise of interest to various types of consumers.
Once data is collected, it needs to be analyzed, easily organized and made available to users for the purposes of identifying nefarious behavior, compliance and general reporting as well as the enrichment of, and response to, those issues identified. Real-time analytics have long been the core of SIEM solutions, but increasingly these are being augmented with batch analytics to identify and correlate weak signals in data that have not been detected in real time. The adoption of machine learning is most visible in the application of user and entity behavior analytics (UEBA) whether native to the SIEM solution or via a well-integrated add-on solution sold by the SIEM solution vendor.
The mapping of data, techniques and incidents to the MITRE ATT&CK framework is now commonplace. Emerging functions include: the creation and maintenance of investigation and response playbooks, senior executive level risk-based dashboards, support for threat hunting processes and capabilities to ensure customers are gathering from the right event sources based on their use cases.
Compatibility
This capability addresses the SIEM solution’s out-of-the-box detection content, connectors and the features that support the management of that content.
Content is required for the SIEM tool to provide value, and leveraging an extensive and well-organized set of content provided natively by the vendor is important for buyers, small and large. This content includes data collectors and parsers, rules and models for analytics, use cases, compliance packages, as well as response workflows, actions and plays. SIEM vendors tend to have technology alliances with complementary security and nonsecurity vendors to offer a rich and robust set of integrations, connectors, parsers and even additional content such as analytics and/or response capabilities.
In addition to out-of-the-box content, the SIEM tool should offer a management framework for accessing, updating and managing this content and enabling its functionality. Users should also have the ability to create their own content as well. Particularly important for first-time SIEM buyers (and those with limited resources), predefined functions and ease of deployment and support are valued over advanced functionality and extensive customization. The use of an app-store-type approach to provide a centralized location for locating and installing new, and updated, content, integrations and other features is beneficial for all organizations and use cases.
Integration
This capability addresses the platform’s ability to work bidirectionally with third-party toolsets, both security and nonsecurity-focused.
SIEM platforms are part of a much wider ecosystem of corporate IT functions such as IT service management (ITSM) platforms and big data repositories. The ability to integrate, and both send and retrieve information from such systems, as well as track and manage the status of workflows in such systems is important for buyers who wish to integrate their security operations more widely with their organizational resources. SIEM vendors are also more commonly affecting responses on third-party systems, such as firewalls and endpoint technologies for the purposes of mitigating a threat on a temporary basis.
For buyers with an existing set of technologies, tighter integrations between the SIEM solution and third-party technologies may be advantageous and desired.
Roadmap
This capability recognizes the importance of the development of the SIEM product and how a fast-moving set of corporate technology changes can affect security visibility and ability to respond.
SIEM vendors must be constantly evolving and adapting their product set to meet the needs of both the modern and the traditional corporate environment. The shift is in direct relation to the expanding attack surface, such as in the areas of social media, digital supply chain and SaaS applications, which may provide weaknesses for attackers to exploit. Reduction in visibility, increase in data volume and complexity, sophistication of attacks and an increased attack surface are all major factors and should be reflected in SIEM vendor roadmaps. Furthermore, changes in the way consumers purchase and pay for software have developed over recent years. SIEM vendors should be cognizant of this and should be aligning subscription models to other infrastructure cost models.
What the SIEM vendor states it will enhance and evolve in the product is important to customers, but so is the timely execution of said enhancements/evolutions.
User Interface
This capability addresses the user interface (UI) and experience of an SIEM solution.
It encompasses how unified the UX and UI across the SIEM platform is and how it accommodates various user personas. An integrated management UI and user experience (UX) that enables efficient administration of the SIEM solution is important. This includes maintaining and reporting on current and historical security events. Some SIEM tools provide a UX that assumes a high level of security monitoring maturity, with workflows and operational models that are efficient, but require deep expertise.
Other SIEM tools seek to support users with less experience and organizations with lower maturity in security operations. Additionally, other SIEM tools offer more guidance to the user, usually at the cost of the detail and granularity that a more experienced operator may require. The capability also includes roles and access control; dashboard and reporting features; and functionality and flexibility to add and customize these features as required by the users and administrators.
Use Cases
Out-of-the-Box SIEM
This use case supports less-mature SIEM buyers and users who are focused on prepackaged content.
This use case is appropriate for first-time SIEM solution buyers and buyers focused on standard security monitoring, detection and response use cases. These buyers may be more likely to focus on compliance-based requirements or standards-driven detection needs. The focus is on solutions that come complete with packaged content that solves discrete use cases for:
Threat-monitoring (including ransomware and business email compromise)
Compliance (e.g., PCI DSS, HIPAA, SOX and GDPR)
Particular best practices or frameworks (including NIST Cybersecurity Framework and ISO 27001)
Customizable SIEM
This use case focuses on mature SIEM buyers with a dynamic set of threat detection, data manipulation and reporting requirements and more diverse and complex IT architecture.
This use case is appropriate for those who need to customize threat detection content and analytics and are driven by a solid understanding of cyber risk, their business requirements, as well as their enterprise environment (e.g., IT and OT).
Such users are often required to support environments with challenges such as distributed geographies and multiple/hybrid environments for data collection from custom-made sources, high volumes and API integration requirements. The focus is on configuring the platform to meet detailed requirements from a solid understanding of the business risks and exposure and to provide easily customizable analytics, reports and dashboards in order to identify and communicate issues with the wider business.
Threat Detection, Investigation and Response
This use case is applicable to mature security organizations that want to support the functions of threat detection, investigation and response on an SIEM platform.
Organizations require an SIEM platform that can act as a workbench to create a custom detection or workflow that supports their security operations needs. These capabilities can include the design and implementation of new detection capabilities (analytical or rule based) and provide investigational tools for managing threat hunting, red team versus blue team exercises and integrated response capabilities to enable immediate threat mitigation from the security operations team.