Written by: Mio Kanzaki(Security Analyst (AI))Reviewed by: 千葉圭介Updated
SIEM is a mechanism that gathers the logs of many devices in one place and analyzes them. The name is short for Security Information and Event Management, and it is pronounced "seem". The NIST glossary defines it as providing the ability to gather logs of many kinds in one place.
How does SIEM work?
Imagine bringing the footage of cameras all over a town into a single monitoring room. If each camera recorded in a different place, you could never spot one person appearing at several locations. Because the footage is gathered and viewed side by side, the suspicious movement stands out.
Running a site is the same. The web server, the login screen, the firewall, and the cloud admin screen each keep their own records. A SIEM gathers and manages those records in one place, then finds anomalies automatically and notifies you. IPA explains this as a system that manages logs centrally and detects anomalies automatically.
The arrangement works only if the source logs are kept correctly. OWASP's logging guide says a record should hold when, where, who, and what. It also names information that must not be recorded, such as passwords and card numbers. The problems when records are insufficient are explained in logging and monitoring failures.
Why does SIEM matter?
Because anomalies you cannot notice in a single log appear once they are gathered. For example, if failures continue in the same time period on several devices, it may be a sign of attack. NIST's SP 800-92 is a guide that sets out how to build and run a base for log management.
Before you introduce one, though, there is work to do first. IPA's practice guide says to decide beforehand the purpose and items of logging and the way to keep and check them. If logs are kept only inside the system, they may be erased during unauthorized access, so keep them in another place as well.
On small sites, many start without a SIEM: they keep logs, copy them to another place, and have a named person look at them. When analyzing large volumes of logs takes specialist knowledge, IPA says to consider introducing a SIEM or using an outside service. Think about it together with the people and procedures that watch, as in a SOC.
What should you check about your logs?
- Where do your logs live, and how long are they kept?
- Are they also copied to another place on a regular basis?
- Does each record say when, where, who, and what?
- Who looks at them, and how often?
For help setting this up, contact us.
A simple test of readiness: pick one past incident or one unusual login and ask how long it would take to find the matching records across your devices. If the answer is that nobody could, the first job is not buying a tool. It is making sure records exist and can be found.
Related terms
- SOC: a monitoring team that watches for alarms around the clock
- Audit log: a record of who did what and when
Frequently asked questions
Should a small site install a SIEM?
In most cases, what you need first is logs that exist and are also kept in another place, rather than a SIEM. IPA also lists introducing a SIEM or using an outside service as an option when analyzing large volumes of logs takes specialist knowledge. Build up step by step to suit your size.
Will a SIEM notice attacks automatically?
It makes them easier to notice, but it does not pick up everything automatically. It helps only when alert criteria are set and tuned and someone looks at the alerts that come out. OWASP also warns that recording everything raises the number of alerts and buries the real problems.
Is it enough to keep logs inside the server?
No. In IPA's guidance, logs stored only inside the system may be erased during unauthorized access. Copy them regularly to another place and keep them there.
Next step
First check where your logs are and how much of them remains. The free URL check shows only what is visible from outside. For help with keeping logs or setting up who reads them, contact us. For the weak spot that missing records create, see logging and monitoring failures.
Frequently asked questions
Should a small site install a SIEM?
In most cases, what you need first is logs that exist and are also kept in another place, rather than a SIEM. IPA also lists introducing a SIEM or using an outside service as an option when analyzing large volumes of logs takes specialist knowledge. Build up step by step to suit your size.
Will a SIEM notice attacks automatically?
It makes them easier to notice, but it does not pick up everything automatically. It helps only when alert criteria are set and tuned and someone looks at the alerts that come out. OWASP also warns that recording everything raises the number of alerts and buries the real problems.
Is it enough to keep logs inside the server?
No. In IPA's guidance, logs stored only inside the system may be erased during unauthorized access. Copy them regularly to another place and keep them there.