What are the most relevant security events/incidents any company should monitor using event management tools? Related to servers, antivirus, networks, etc.
closed as too broad by Steve Sether, Neil Smithline, John Deters, Mark, Deer Hunter Dec 24 '15 at 11:04
Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
You should log everything and analyze anything. People trying to brute your sites and servers. All of these are relevant incidents as they pose a threat.
It's not relevant to say to what is an incident, as every attempt might be a relevant event some time. What is important is to catalog them with different levels. Some threats pose greater danger than others. Some of them might contain a lot of "normal behavior". The thing is that some things only become relevant after analyzing over a longer period of time. You might notice one attacker is doing his best extra hard to get in. You might get a hacked server and then you'd have to be able to go back and look for related security events to learn from the incident.
It depends on source of logs! If logs source is windows then look for account logon failures, password reset or change attempt, deletion or creation of new account, conflict in hostnames. You can visit ultimatewindowssecurity where you can find critical events to look for.
In firewall logs you can check for port scan (one host ip visiting more than 100 destination ports in short time),FTP logins on SAP,Malware activity.
Check for high bandwidth consumption by any application or process.
In proxy logs check for SQL Injection,Data tempering, Search queries etc.
Warn if 5 failed logon attempts are tried with different usernames from the same IP to the same machine in 15 minutes and after that, if a successful login occurs from the same IP to any machine.
Warn if a host scan is made by an IP and then if a successful connection is established by the same IP and then backward connection is established from connected IP to connecting IP.
- Warn if more than 100 connections are established from the different external IPs to the same destination IP in one minute.
- Warn if 100 connections are established from the same external IP through different ports to the same destination IP in one minute.
- Warn if the same user tries more than three failed logon attempts to the same machine in an hour.
- Warn if a user can’t log into any server and caused failed authentication and in two hours if that user can’t log into the same server.
- Warn one if more than 100 packets are blocked by UTM/FireWall from the same source IP and don’t warn within an hour. (Millions of packets are blocked in case of DDOS attack. If email is sent for each, you are exposed yo yourself DDOS attack.)
- Report the source IP which causes UnusualUDPTraffic.
- Warn if a traffic is occurred to a source or from a source in IPReputation list.
- Warn if network traffic occurs from the source or to a source in malicious link list published by TRCERT - Turkey - Computer Emergency Response Team
- If someone sets up DHCP server in your network or if a different gateway broadcasts, to find out this: Warn if a traffic occurs from inside to outside or from outside to inside whose protocol is UDP, destination port is 67, and destination IP is not in registered IP list.
- Warn if an IP scan occurs.
- Warn if SQL attack occurs via web server.
- Warn if the servers are accessed out of hours.
- Warn if the same user tries more than three failed logon attempts to different machines in an minute.
- Warn If an attack followed by account change
- Warn If scan followed by an attack
- Detects An Unusual Condition Where A Source Has Authentication Failures At A Host But That Is Not Followed By A Successful Authentication At The Same Host Within 2 Hours
- Look for a new account being created followed by immediate authentication activity from that same account would detect the backdoor account creation followed by the account being used to telnet back into the system
- Monitor same source having excessive logon failures at distinct hosts,
- Check whether the source of an attack was previously the destination of an attack (within 15 minutes)
- Check whether there are 5 events from host firewalls with severity 4 or greater in 10 minutes between the same source and destination IP
- Look for a new account being created, followed shortly by access/authentication failure activity from the same account
- Monitor system access outside of business hours