# SIEM Log Management Explained: What SIEM Is, Which Logs to Collect and an 8-Step Rollout Plan

> What is SIEM log management and how does it differ from log collection? Learn which logs to collect first, retention, cost drivers and an 8-step plan.

Source: https://digitalbridge.com.tr/en/blog/siem-log-management-basics.html
Publisher: Digital Bridge Teknoloji (https://digitalbridge.com.tr)
Topic: Cyber Security & Compliance
Published: 2026-10-05 · Updated: 2026-10-22

[SIEM](https://digitalbridge.com.tr/en/glossary.html#siem) (Security Information and Event Management) is a security system that collects logs from servers, firewalls, email, cloud services and business applications in one place, correlates them to turn suspicious patterns into alerts, and retains them for investigation. Log management gathers and stores records; SIEM goes a step further and tells you that an attack may be under way.

## Key takeaways

- SIEM maps logs from different systems onto common fields and correlates them, raising alerts on events that look harmless in isolation.
- IBM's Cost of a Data Breach Report 2025 puts the global average time to identify and contain a breach at 241 days.
- Connect identity and email logs to a SIEM first; perimeter devices and critical applications come second and third.
- A successful SIEM rollout starts before product selection, with use cases, a source inventory, time synchronisation and retention rules.
- A SIEM deployed without named people to read alerts and respond becomes an expensive log archive.

## Why don't logs turn into incident detection?

Few companies lack logs; what they lack is anyone reading them. The firewall records every connection, the domain controller every sign-in, the mail server every message and the ERP every user transaction. The trouble is that these records sit on ten different devices, in ten different formats, and are often overwritten after a few days.

When an incident happens, the story is familiar. Someone signs in to the finance manager's account from abroad at midnight, and shortly afterwards hundreds of files are read from a file server. Both traces are recorded somewhere, but because nobody sees them together, the incident only surfaces weeks later when a supplier asks why they received an odd email from you.

The questions that follow a security incident are always the same: when did the attacker get in, which account did they use, and what data did they touch? Without complete, centralised logs the answers are guesswork. For companies operating in Türkiye, the clock on [data breach notification within 72 hours under KVKK](https://digitalbridge.com.tr/en/blog/data-breach-72-hours-kvkk.html) makes guesswork the most expensive answer of all.

## What does leaving logs unmonitored cost?

Without log monitoring, detection is delayed, and the longer detection takes, the longer an attacker stays inside and the more damage they can do. [IBM and the Ponemon Institute's Cost of a Data Breach Report 2025](https://newsroom.ibm.com/2025-07-30-ibm-report-13-of-organizations-reported-breaches-of-ai-models-or-applications,-97-of-which-reported-lacking-proper-ai-access-controls) found that the global average time to identify and contain a breach, including restoring services, was 241 days. Organisations that used AI and automation extensively in security operations shortened that lifecycle by 80 days on average.

> According to security vendor Sophos' [State of Identity Security 2026 survey](https://www.sophos.com/en-us/press/press-releases/2026/05/71-percent-organizations-suffered-identity-breach-state-of-identity-security-2026) of 5,000 IT and security leaders in 17 countries, only 24% of responding organisations continually monitor for unusual login attempts.

Where attacks begin also explains why log monitoring matters. Verizon's [2026 Data Breach Investigations Report (DBIR)](https://www.verizon.com/business/resources/T1ae/reports/2026-dbir-data-breach-investigations-report.pdf) found that, as of 2026, exploitation of vulnerabilities had become the most common initial access vector, at 31% of breaches. An exploit attempt against a server that slipped through your [patch management process](https://digitalbridge.com.tr/en/blog/patch-management-process.html) shows up in firewall and web server logs; unread, it goes unnoticed.

Log monitoring has a regulatory side as well. [KVKK](https://digitalbridge.com.tr/en/glossary.html#kvkk), Türkiye's Personal Data Protection Law (Law No. 6698), requires data controllers to take all necessary technical and administrative measures to ensure an appropriate level of security, and a company that cannot show who accessed personal data, and when, will struggle to evidence those measures. Separately, [Law No. 5651](https://www.mevzuat.gov.tr/mevzuat?MevzuatNo=5651&MevzuatTur=1&MevzuatTertip=5), Türkiye's internet law, requires certain businesses, such as those offering internet access to guests or staff, to keep access logs. Who falls in scope and what must be kept is covered in our guide to [Law 5651 log retention](https://digitalbridge.com.tr/en/blog/turkey-law-5651-log-retention.html); this article focuses on turning logs into detection rather than on the legal duty.

## What is SIEM log management, and how does it differ from log collection?

SIEM merged two older disciplines: security information management (SIM, collecting and retaining records) and security event management (SEM, real-time monitoring and alerting). It works in four stages: it ingests logs from sources, maps different formats onto common fields (normalisation), links events across sources using rules (correlation), and presents the result as alerts, dashboards and reports.

A single example shows why correlation matters. Five failed sign-ins alone are noise. Five failures, then a successful sign-in, then a new mailbox forwarding rule is the signature of a compromised account. Those three records live in three different systems, and SIEM is what puts them on one timeline.

Centralised log management, SIEM and a SOC are often confused; the table below compares the three approaches:

| Aspect | Centralised log management | SIEM | SOC (security operations centre) / managed monitoring |
|---|---|---|---|
| Core job | Collect, store and search logs | Correlate logs and raise alerts | Have people review alerts around the clock and respond |
| Real-time detection | Limited | Yes, through rules and behaviour analytics | Yes, with analyst judgement |
| Effort required | Low | Medium; rules need tuning and alerts need owners | High; an in-house team or a provider |
| Compliance and investigation | Good, if log integrity is protected | Good, with ready reports and timelines | Good, with incident reports |
| Best fit | First step; small, simple estates | Several critical systems, personal data, remote access | When alerts must be handled outside office hours |

The key lesson of SIEM projects is that SIEM is a process more than a product. Deployed without someone to read alerts, tune rules and act on findings, it becomes an expensive log archive. We explain the general approach to spotting deviations with machine learning in our [anomaly detection guide](https://digitalbridge.com.tr/en/blog/anomaly-detection-guide.html).

## Which logs should you connect to a SIEM first?

Connecting every log source to a SIEM on day one overwhelms both the budget and the team. The right question is not "what can we collect?" but "which attacks do we want to see, and where do they leave traces?" In practice, sources fall into three priority groups.

The first group is identity: domain controllers, the cloud identity provider, VPN (virtual private network) and remote desktop sign-ins, and mailbox logins. Because so many breaches start with a compromised account, these records deliver the highest return. If you use single sign-on, every session arrives from one source; we cover the wider benefits in our guide to [single sign-on for business](https://digitalbridge.com.tr/en/blog/single-sign-on-sso-benefits.html).

The second group is the network perimeter: firewall, web servers, email gateway and DNS (Domain Name System). These reveal exploit attempts from outside and unusual data leaving the network; how to block that data leaving in the first place is covered in our [data loss prevention (DLP) guide](https://digitalbridge.com.tr/en/blog/data-loss-prevention-dlp.html). The third group covers critical applications and endpoints, such as ERP (enterprise resource planning), file servers, databases, antivirus or EDR (endpoint detection and response), and SCADA servers in factories. Which production logs can be collected safely is covered in our article on [OT and SCADA security](https://digitalbridge.com.tr/en/blog/ot-security-scada.html).

## How do you implement a SIEM? An 8-step rollout plan

This SIEM rollout sequence suits a small IT team. The first four steps come before choosing a product, and most failed projects fail precisely because they skip them.

1. **Write your use cases.** Define 10–15 concrete scenarios, such as "admin sign-in outside office hours from abroad", "one user reading an unusual number of files in a short period" or "new mailbox forwarding rule". Note which log each one will be detected from.
2. **Inventory your sources.** Which system produces which log, where is it kept and for how long? The inventory also exposes blind spots.
3. **Fix time and identity.** Every device should use the same time source (NTP), or you cannot reconstruct the order of events. Replace shared accounts with personal ones, otherwise logs cannot answer "who?".
4. **Set retention and integrity rules.** Decide in writing how long logs stay in fast, searchable storage and how long in archive, based on legal duties, contracts and investigation needs. Logs containing personal data belong in your [data retention and disposal policy](https://digitalbridge.com.tr/en/blog/data-retention-disposal-policy.html).
5. **Connect the first priority group.** Start with identity and email; confirm that collection agents and network traffic do not slow production systems.
6. **Tune rules against noise.** In the first weeks most alerts will be false positives. Improve or retire every rule; an alert nobody looks at is worse than no alert.
7. **Attach response steps to alerts.** For every critical alert, one page should say who investigates, how quickly and which accounts get locked. For ransomware, these steps must work alongside your [3-2-1 backup and recovery plan](https://digitalbridge.com.tr/en/blog/ransomware-backup-3-2-1.html).
8. **Test regularly.** During a controlled [penetration test](https://digitalbridge.com.tr/en/blog/penetration-testing-guide.html), measure whether the SIEM saw each attack step. Every step it missed is a new rule or a missing log source.

These eight SIEM rollout steps also produce direct evidence for the [ISO 27001 logging and monitoring controls](https://digitalbridge.com.tr/en/blog/iso-27001-guide-for-smes.html). If basic controls are not yet in place, begin with our [SME cyber security checklist](https://digitalbridge.com.tr/en/blog/sme-cyber-security-checklist.html); watching an account without multi-factor authentication (MFA) being taken over costs more than protecting it.

## Common mistakes in SIEM projects

The most common mistake in SIEM projects is "collect everything and work it out later". Licence and storage costs usually scale with data volume, so aimless collection drains the budget and buries the signal in noise. The second is deploying SIEM purely for audit and never writing an alert rule.

The third is treating log access as an ordinary permission. Logs contain usernames, IP addresses and sometimes email subjects, all of which can be personal data, so anyone with SIEM access sees that data. Restrict access by role and log the searches made in the SIEM itself.

Finally, do not forget leavers. A former employee's session on an account that was never closed is one of the easiest events for a SIEM to catch, yet it is often missed because no rule was written. We walk through the process in our guide to [offboarding and email access](https://digitalbridge.com.tr/en/blog/offboarding-email-access.html).

## How does Digital Bridge support SIEM and log monitoring?

At Digital Bridge, we start log monitoring projects by finding the gaps and attack paths, not by choosing a product. The penetration testing and vulnerability scanning in our [cyber security consultancy](https://digitalbridge.com.tr/en/consultancy/cyber-security.html) rank findings by risk and give a remediation step for each; that report shows which attack paths deserve monitoring first and where your use cases should begin. In the same engagement we assess access and logging controls on the systems that hold personal data.

Through our [data protection compliance](https://digitalbridge.com.tr/en/consultancy/data-protection-compliance.html) work we build the data inventory, prepare the retention and disposal policy, switch on access logging for systems holding personal data and write an incident response plan that says who does what during a breach. How long logs are kept, and who may access them, becomes part of that policy.

For ERP and custom software that produce no logs, or produce them in non-standard formats, our [system integration](https://digitalbridge.com.tr/en/technology-hardware/system-integrations.html) service builds data transfers that keep their own records. For deviations that rule-based alerts miss, we can connect [anomaly detection](https://digitalbridge.com.tr/en/technology-hardware/anomaly-detection.html) models, which learn each user's and device's own normal behaviour, to your system logs. If your estate is moving to the cloud, access and security configuration is reviewed together with our cyber security team as part of our [cloud migration and infrastructure consultancy](https://digitalbridge.com.tr/en/consultancy/cloud-migration-infrastructure-consultancy.html).

In organisations using our own products, their records belong in the log inventory too. [SmartMail business email](https://digitalbridge.com.tr/en/smart360/smartmail.html) writes actions such as granting access, changing settings and adding sender rules to an audit log with the actor, time and IP address, while [SmartPass access control](https://digitalbridge.com.tr/en/smartpass.html) links access and audit records in a hash chain, so deleting or altering a record shows up when the chain is verified. Physical entry records also help when you interpret a sign-in at an unexpected hour.

When log data needs to move into a separate store for long-term analysis or reporting, we design it using the principles in our [data warehouse and ETL guide](https://digitalbridge.com.tr/en/blog/data-warehouse-etl-guide.html). For more articles in this area, browse our [cyber security and compliance guides](https://digitalbridge.com.tr/en/blog/topic/guvenlik-kvkk.html).

## Three questions to answer before deciding on SIEM

Before deciding on SIEM, answer three questions. Where are the logs for your ten most critical systems today, and how long do they last? If an admin account were taken over tonight, who would notice, and when? Could you build an attacker's timeline after an incident?

If any answer is "we don't know", your starting point is clear. [Get in touch](https://digitalbridge.com.tr/en/contact.html) to map your log sources and use cases together; together we can turn that into a prioritised list of what to monitor first.

## Frequently Asked Questions

### What is SIEM in simple terms?

SIEM is a security system that gathers logs from servers, network devices, email, cloud services and applications in one place, correlates records from different sources to turn suspicious patterns into alerts, and retains them for investigation and audit. Its main benefit is showing, in time, that events which look harmless on their own together point to an attack.

### What is the difference between log management and SIEM?

Log management collects, stores and indexes records so they can be searched, which may be enough for investigations and legal retention. SIEM adds normalisation, correlation rules and real-time alerting on top. Put simply, log management answers "what happened?" after the fact, while SIEM aims to answer "what is happening right now?" while an incident is still unfolding.

### Does a small business need a SIEM?

Not every small business needs a full SIEM product. However, any business that processes personal data, allows remote access or runs several critical systems needs at least centralised log management and a handful of core alerts. The sensible route is to start small with identity and email logs, then widen coverage as needs and in-house capability grow.

### How long should logs be retained?

There is no single answer. Retention depends on the regulations you are subject to, customer contracts, industry standards and how late an incident might realistically be discovered. Good practice is to keep recent logs in fast, searchable storage, move older records to a tamper-resistant archive, and include logs containing personal data in your retention and disposal policy.

### What drives the cost of a SIEM?

The main cost factors are the daily volume of logs ingested, the number of sources and devices connected, how long logs stay in searchable storage and in archive, whether the platform runs on-premises or in the cloud, and who monitors the alerts. Rule tuning and staff time matter as much as the licence, and aimless collection is the fastest way to inflate the bill.

### What is the difference between SIEM and a SOC?

A SIEM is a software platform, whereas a SOC (security operations centre) is the team and process that reviews the alerts the platform produces and responds to them. The SIEM collects logs, correlates them and raises alerts; SOC analysts judge whether each alert is a real attack and take steps such as locking accounts. A SOC can be built in-house or bought as a managed monitoring service.

### Do we need a 24/7 security team to run a SIEM?

No, but you must define who reviews alerts and during which hours. Small teams can start with office-hours review, phone notifications for critical alerts and automatic account lockouts. If alerts need human review outside office hours as well, a managed monitoring service or an in-house security operations centre becomes the option to evaluate.
