![Lead Image © Yuri Arcurs, fotolia.com Lead Image © Yuri Arcurs, fotolia.com](/var/ezflow_site/storage/images/archive/2016/35/implementing-custom-security-frameworks-with-bro/po-22946-fotolia-yuri_arcurs_fotolia-security_resized.png/129818-1-eng-US/PO-22946-Fotolia-Yuri_Arcurs_Fotolia-Security_resized.png_medium.png)
Lead Image © Yuri Arcurs, fotolia.com
Implementing custom security frameworks with Bro
Don't Hack Me Bro
Bro [1] is high-quality security monitoring tool designed to discover and analyze traffic trends on your network. Bro provides in-depth analysis of network traffic without limiting itself to traditional signature-based approaches. I first heard about the Bro network security monitoring framework when a consultant friend of mine talked about melding the world of big data and security together. My friend believed that traditional signature-based intrusion detection and monitoring simply wasn't enough to ensure a secure network.
The problem with networks is that, because of the increased number of devices, services, and tools used today, it's easy for attackers to enter networks in many different ways. Ransomware, botnets, malware, and remote control tools are readily available. Social engineering is especially prevalent now. Traditional intrusion detection and perimeter security tools just aren't up to the task.
Traditional monitoring tools are also having a hard time catching all of the anomalies. Bro, however, takes a different approach. The Bro framework is designed to monitor traffic on any layer. The default focus is on application layer traffic, but you can train Bro on any layer of the OSI stack. Bro is not really signature-based in its approach; it reviews traffic and looks for anomalous patterns. However, Bro also looks for similarities. It is ideal for setting baselines. Like many projects, Bro offers extensive commercial support.
Understanding Bro
The Bro application has three elements or layers:
- Monitoring engine: Software that listens to a network segment and reviews network traffic. This monitoring is similar to what Snort, Ntop, and other tools do. The engine also includes the event handler, which is designed to identify traffic and then act according to its configuration files.
- Policies:
Buy this article as PDF
(incl. VAT)