SectionSecurity Operations
Technology category
SIEM
SIEM belongs to the Security Operations area. SIEM collects, normalizes, and correlates security events from multiple sources. It supports incident detection, investigation, reporting, and audit.
Acronym Glossary
This glossary explains acronyms used in this part so the intended security function is clear.
- SIEM
- Security Information and Event ManagementCollection, normalization, correlation, and analysis of security events from multiple sources.
What This Technology Covers
SIEM collects, normalizes, and correlates security events from multiple sources. It supports incident detection, investigation, reporting, and audit.
Why It Matters
Its value depends on log quality, rules, integrations, and the team's ability to work with alerts.
In practice, this is not only a technical function. It is a way to place the solution into a broader security architecture. Many organizations operate dozens of consoles and tools, so the challenge is also to understand which technology solves which type of risk.
This category helps name the problem precisely, narrow the list of relevant solutions, and distinguish technologies that may look similar at first glance. That is useful for partners and customers who already understand cybersecurity but need a clear map of the market and available portfolio.
Typical Use Cases
SIEM is usually considered when an organization needs tighter control over a specific security layer within Security Operations. It can complement an existing architecture, replace an outdated tool, improve visibility, or consolidate functions currently split across multiple products.
Place In The Architecture
Within the broader Security Operations architecture, SIEM should be assessed by how it connects to existing security and operational processes. Its practical value appears when the solution provides usable data, clear policies, understandable reporting, and integrations with existing tools.
When mapping this technology to SecTec portfolio vendors, it is important to consider not only the feature itself, but also deployment model, licensing, management level, supported platforms, and integration with adjacent areas. In a specific architecture, SIEM may be a standalone platform, a capability, or part of a broader solution.
How To Assess The Technology
When selecting a solution, the most important assessment points are:
- which problem the solution covers and where its boundaries are
- whether it supports the organization's existing environment
- how it integrates with SIEM, SOAR, XDR, IAM, cloud, or ticketing
- what level of automation, reporting, and auditability it provides
- whether it reduces operational complexity or only adds another isolated console
Related Areas
Vendors From The SecTec Portfolio
Attack coverage and defensive context
MITRE ATT&CK® Enterprise version 19.1 is used as a reference model. The mapping is a SecTec expert interpretation and does not imply endorsement by MITRE.
Practical attack scenarios
- Phishing and identity abuseAn adversary manipulates a user, obtains credentials, or abuses a trusted account to gain access to the environment.
- Public application or API abuseAn adversary exploits a vulnerable web application, API, client-side code, or software component for initial access and execution.
- Cloud and SaaS compromiseAn adversary abuses cloud identities, permissions, configurations, or application integrations to access services and data.
- Lateral movement inside the networkAfter initial access, an adversary discovers systems, accounts, and services and moves toward higher-value assets.
- Malware and Command and ControlMalicious code executes, maintains access, and communicates with adversary infrastructure through common or covert channels.
- Data exfiltration and leakageAn adversary searches for, collects, and transfers sensitive data from endpoints, cloud services, email, or internal repositories.
- Ransomware and availability impactAn adversary encrypts or manipulates data, stops services, inhibits recovery, and creates operational impact.
- Supply chain and trusted accessAn adversary abuses a supplier, software dependency, external access path, or trusted relationship to bypass normal controls.
- Attacks on OT and IoT environmentsAn adversary discovers industrial or connected devices, abuses remote access and network services, and threatens operational availability.
- Business Email Compromise and mailbox takeoverAn adversary takes over or impersonates a trusted email identity and abuses communications for fraud, payment diversion, data collection, or further phishing.
- Privilege escalation and persistenceAn adversary expands privileges, creates or modifies accounts and policies, and establishes repeatable access to systems, identities, or cloud environments.
- Insider threat and authorized access abuseAn insider or an adversary with a valid account abuses legitimate permissions to discover, copy, manipulate, or transfer sensitive data.
- BFLA – Broken Function Level AuthorizationA regular or unauthenticated user invokes an administrative or privileged API function that should not be available to them.
- Broken API authentication and token abuseAn adversary bypasses login, password recovery, or token validation and assumes the identity of a user or service.
- Sensitive business flow and bot abuseAn automated adversary abuses legitimate functionality such as purchasing, booking, registration, voting, commenting, or account recovery.
- Credential stuffing and password sprayingAn adversary automatically tests leaked username-password pairs or a small set of common passwords against many accounts.
- MFA fatigue, push bombing, and interceptionAn adversary floods a user with MFA prompts, intercepts a code, or uses social engineering to make the user approve an unauthorized sign-in.
- Session and access-token hijackingAn adversary steals a cookie, OAuth token, or another session artifact and accesses a service without re-entering a password or MFA.
- Injection and command executionUntrusted input changes the meaning of a command, query, or template and enables data access, logic bypass, or code execution.
- Malicious file upload and unsafe deserializationAn application accepts or processes a malicious file or serialized object and enables code execution, control bypass, or compromise of other users.
Relevant ATT&CK techniques
- T1021 · Remote ServicesDetect, Respond
- T1041 · Exfiltration Over C2 ChannelDetect, Respond
- T1059 · Command and Scripting InterpreterDetect, Respond
- T1071 · Application Layer ProtocolDetect, Respond
- T1078 · Valid AccountsDetect, Respond
- T1486 · Data Encrypted for ImpactDetect, Respond
- T1685 · Disable or Modify ToolsDetect, Respond