Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Cloud

2/26/2019
10:30 AM
Scott Shinn
Scott Shinn
Commentary
Connect Directly
Twitter
LinkedIn
RSS
E-Mail vvv
100%
0%

A 'Cloudy' Future for OSSEC

As more organizations move to the public cloud and to DevOps and DevSecOps processes, the open source alternative for host-based intrusion detection is finding new uses.

Used by more than 10,000 organizations around the world, OSSEC has provided an open source alternative for host-based intrusion detection for more than 10 years. From Fortune 10 enterprises to governments to small businesses, OSSEC has long been a standard part of the toolkit for both security and operations teams.

As more organizations move to the public cloud infrastructure and to DevOps and DevSecOps processes, OSSEC is finding new use cases and attracting new fans. Downloads of the project nearly quadrupled in 2018, ending the year at more than 500,000. Much of this new activity was driven by Amazon, Google, and Azure public cloud users.

While many security and operations engineers are familiar with OSSEC in the context of on-premise intrusion detection, this article will focus on the project's growing use and applicability to cloud and DevSecOps use cases for security and compliance.

OSSEC Capabilities
OSSEC offers six key intrusion detection capabilities to users in any environment, on physical servers, in containers or virtual machines, or in public or private clouds.

  • Log-based intrusion detection (LIDS): Actively monitors and analyzes data from multiple log data points in real time.
  • File integrity monitoring (FIM): For both files and Windows registry settings in real time, detects changes to the system, and maintains a forensic copy of the data as it changes over time.
  • Rootkit and malware detection: Process- and file-level analysis detects malicious applications and rootkits.
  • Compliance auditing: Application- and system-level auditing ensures compliance with many common standards, such as PCI-DSS and CIS benchmarks.
  • System inventory: Collects system information, such as installed software, hardware, utilization, network services, and listeners.
  • Active response: Responds to attacks and changes on the system in real time through multiple mechanisms, including firewall policies, integration with third parties such as content delivery networks and support portals, as well as self-healing actions.

OSSEC provides intrusion detection capabilities on Linux, MacOS, and Windows, as well as on legacy operating systems, including AIX, HP-UX, and Solaris. This gives operators the ability to run a single host-based intrusion detection system (HIDS) across an entire environment.

Many organizations integrate OSSEC with a security information and event management (SIEM) system, such as Splunk, ArcSight, Elasticsearch, or QRadar, to pipe events to their security operations center (SOC). In this case, OSSEC plays the role of a log aggregator and only sends actionable information to the SIEM. This reduces data volume in the SIEM, which cuts down on noise for SOC personnel and often results in dramatic reductions in SIEM costs.

The Cloud and DevSecOps Imperative
As public cloud customers are discovering, moving to the cloud presents a host of security and compliance responsibilities for enterprise security and IT teams. While cloud providers handle hardware and infrastructure, cloud workloads themselves must be secured by the customer.

This fact is often obscured in the quest for cost savings and efficiencies of the public cloud. However, all major cloud providers publish "shared responsibility matrices" that highlight which security and compliance requirements are owned by the customer. This can be summarized nicely by Amazon as "Amazon is responsible for security and compliance of the cloud, the customer is responsible for security and compliance in the cloud."

This leaves the enterprise with the need to bring its own security and compliance tools to the cloud. And traditional on-premise controls and network security don't work in the perimeter-less software defined environment of the public cloud. Security must be built directly into the workload.

In this area, the cloud presents another challenge: Whatever additional security and compliance tools are added to the workload will increase the cost of cloud usage. In on-premise environments, enterprises do not need to concern themselves with the amount of computing resources consumed by their security software. In the cloud, this can cost real money.

OSSEC provides a solid foundation to meet multiple security and compliance requirements not handled by the cloud provider. It is installed directly on the workload and offers all of the same functional capabilities outlined above.

From a cost perspective, OSSEC offers two distinct advantages. First, it's open source, so users can get started for free and without enduring long and complicated procurement processes. Perhaps more importantly, OSSEC runs in a very small footprint. When added to a cloud workload, it typically adds less than 3% overhead, which means it will have almost no impact on cloud usage costs.

Most organizations moving to the public cloud have also adopted a DevOps process with hundreds or even thousands of releases a week. To effectively secure these releases, security tools must be deployed easily using DevOps orchestration tools such as Ansible, Puppet, and Chef. OSSEC easily integrates with these tools as well as custom scripts to ensure it can be deployed with every release.

Getting Started with OSSEC
OSSEC is free and licensed under the GNU Public License. The project may be downloaded here, along with documentation, release notes, and options for commercial support and advanced functionality.

The annual OSSEC user conference will be held March 20-21 in Herndon, Virginia. The agenda includes a keynote talk from Daniel Cid, the founder of the OSSEC project, how-tos from OSSEC contributors and power users, and hands-on tutorials and workshops. Click here to learn more.

Related Content:

 

 

Join Dark Reading LIVE for two cybersecurity summits at Interop 2019. Learn from the industry's most knowledgeable IT security experts. Check out the Interop agenda here.

Scott Shinn is an avid advocate of open source security software and currently serves as the project manager of the OSSEC project. In addition to OSSEC, Shinn has contributed to dozens of open source projects, including substantial contributions ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 10/23/2020
7 Tips for Choosing Security Metrics That Matter
Ericka Chickowski, Contributing Writer,  10/19/2020
Russian Military Officers Unmasked, Indicted for High-Profile Cyberattack Campaigns
Kelly Jackson Higgins, Executive Editor at Dark Reading,  10/19/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-24847
PUBLISHED: 2020-10-23
A Cross-Site Request Forgery (CSRF) vulnerability is identified in FruityWifi through 2.4. Due to a lack of CSRF protection in page_config_adv.php, an unauthenticated attacker can lure the victim to visit his website by social engineering or another attack vector. Due to this issue, an unauthenticat...
CVE-2020-24848
PUBLISHED: 2020-10-23
FruityWifi through 2.4 has an unsafe Sudo configuration [(ALL : ALL) NOPASSWD: ALL]. This allows an attacker to perform a system-level (root) local privilege escalation, allowing an attacker to gain complete persistent access to the local system.
CVE-2020-5990
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in the ShadowPlay component which may lead to local privilege escalation, code execution, denial of service or information disclosure.
CVE-2020-25483
PUBLISHED: 2020-10-23
An arbitrary command execution vulnerability exists in the fopen() function of file writes of UCMS v1.4.8, where an attacker can gain access to the server.
CVE-2020-5977
PUBLISHED: 2020-10-23
NVIDIA GeForce Experience, all versions prior to 3.20.5.70, contains a vulnerability in NVIDIA Web Helper NodeJS Web Server in which an uncontrolled search path is used to load a node module, which may lead to code execution, denial of service, escalation of privileges, and information disclosure.