Glossary

SIEM

security information and event management

Definition

Security information and event management combines activity records from different systems to help detect and investigate security threats.

It brings security records together to help detect and investigate suspicious activity. Analysts or an operated service are still needed to act on findings.

A customer may include “SIEM” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.

Security information and event management (SIEM) collects logs and other security data from multiple systems in one place. Detection rules and analysis look for combinations of events that deserve investigation, such as suspicious sign-ins followed by changes to account permissions.

A SIEM is a tool, not a team. Someone must choose the data sources, maintain detection rules and decide what to do with alerts. It can support a security operations centre or an external monitoring service, but installing it does not create either.

Imagine a small online retailer sending email sign-in logs and server activity to a SIEM. Joining those records could help an analyst investigate whether an unusual account session was followed by access to customer data. Missing or delayed logs can leave that sequence incomplete.

Costs and workload often depend on data volume and retention. Choose the threats the SIEM should detect, connect the relevant log sources, set useful retention and assign someone to investigate alerts. Collecting everything without a purpose can create expense and noise. Logs have value only when the necessary records remain usable and someone knows how to interpret them.

Sources