Security alerts help organizations quickly detect advanced cyber attacks. However, organizations are often bombarded with alerts from an array of IT devices. In fact, IDC found that half or more of the untuned security alerts generated by organizations end up as false positives. The sheer volume of alerts generated from an IT environment can be overwhelming for security teams. Not to mention, the biggest challenge for a Security Operation Center (SOC) is simply understanding what is normal behavior, what are false positives, and what are actual threats. (NOTE: a properly tuned SIEM helps mitigate this.)
Here’s an example. An IP Address 10.1.15.10 makes an outbound connection to an unknown IP over port 80, is this bad? It could be depending on what 10.1.15.10 is and its function. If you do not know what that device is, your SOC doesn’t either –it’s worth noting that a SIEM not only addresses security concerns but can also assists with the SANS top 3 including: hardware inventory, software inventory, and automated Vulnerability and Configuration Management (VCM).
It’s important that your security analysts are focused on the right security alerts. Here some of the important ones to start following and begin sifting out false positives.
Privileged User & Account Monitoring
Privileged user accounts are one of the most common security weaknesses for organizations. End users with endpoints can have administrator or root privileges which can lead to downloading malicious software, making changes to network or system settings, or inadvertently letting a hacker obtain access to sensitive data.
Your security team should create dashboards to track privileged user activity. Hackers regularly attempt to obtain privileged user accounts and ways to escalate privileges as they are an entry to other systems and applications on your network. If a hacker has access to one of your privileged accounts, they can potentially bypass firewalls or Intrusion Detection Systems (IDS).
Abnormal External Communication
Your security team may be investigating lots of inbound traffic but, are they monitoring for abnormal outbound activity as well? External communication can take place on your network through an abnormal port or protocol. Your firewall can help with traffic filtering but may not catch everything. Abnormal external communication could be a hacker attempting to deploy malicious software, carry on Command and Control Activities, or more recently conduct hivebot and swarm activities.
Your security team should review how external communications are filtered, monitored, and blocked. External communications toward an open resource are typically allowed, but if the communication is not for public resources, then it could be an unauthorized communication. Any traffic that gives cause for concern should be validated against your security policy and reviewed against malicious patterns. Security alerts can be generated from your IDS/IPS, firewalls, and switches to monitor these external communications. And of course, the best way to monitor all of these is with a SIEM.
Acceptable Use Policy Violations
Acceptable Use Policies (AUP) can be something that your employees signed when they first onboarded but rarely follow now. Every organization should have a security briefing as part of onboarding, and an annual review and signoff thereafter. The AUP policy defines what end users can and cannot do with organizational technology. AUPs are important to protecting your organization from malicious activity on your network but are often not enforced or monitored.
Your security team should set up security alerts and dashboards to review AUP violations. Employees may browse inappropriate websites, download Torrent content, or fall for phishing schemes that leave your company susceptible to threat actors. As a result, monitoring AUP violations can help you quickly find endpoints with malware installed.
Data Exfiltration/Unusual Port Activity
Data exfiltration is one of the main objectives for advanced persistent threats (APTs). Threat actors can infiltrate frequently used ports to avoid firewalls and IDS and steal your company data. Or, they can use phishing and other social methods for infiltrating your environment.
Commonly used ports for data exfiltration include common Internet services, hoping that they’ll have an any/any rule for that port on firewalls:
- TCP: 80 (HTTP)
- TCP: 443 (HTTPS)
- TCP/UDP:53 (DNS)
Hackers typically use the following techniques to conduct an attack:
- Backdoors: collects files and uses ports like 80, 443, and 53 to hide traffic
- Web applications: an attacker can access data directly from web pages using ports above
- File transfer protocol (FTP): hackers use FTP as it’s a standard for transferring files – use SFTP or FTPS instead, or even better, use a secure cloud provider; lookup https://thruinc.com.
- Windows Management Instrumentation: a threat actor can use this to look at files and receive emails from Microsoft Outlook
Your security team can set up alerts using your network intrusion and prevention system logs to identify any of the suspicious port activity mentioned above. Your team may find that the traffic represents malware infiltration. Your team could also consider setting up specific security alerts when data is shared externally more than normal. It could be a threat actor or insider stealing company data.
Have a SIEM configuration that baselines what normal traffic looks like, and alerts when traffic outside the baseline occurs.
File Integrity Monitoring
Another area your analysts may want to look at closely is File Integrity Monitoring (FIM). Your auditing policy should include unexpected changes in a file’s status and alert on it, through NG Endpoint Protection (EPP), SIEM or both. Your team could setup an alert and dashboards to find out if files have been changed recently. If file access auditing looks suspicious or like something changed that shouldn’t have, then you should investigate the event in more detail.
File access auditing can tell you which files have been viewed, what programs are executing using those files, and if any files were deleted or created. Any suspicious files should run through your antivirus tool or next-gen endpoint protection solution to identify if there are malicious executables. You may find correlations with patterns like ransomware, data compromise, and exfiltration.
Of course, setting up the right security alerts all depends on what assets you’re protecting, it can vary for each organization and on the activities generated by the SIEM.
What types of security alerts does your team follow? Tell us below in the comments!
*** This is a Security Bloggers Network syndicated blog from Cipher Cyber Security Blog authored by Marc von Mandel. Read the original post at: http://blog.cipher.com/the-security-alerts-your-analysts-should-be-following