Network data for humans.

You don't need more alerts, most of them crying wolf and wasting your time. And you don’t need packet upon packet dumped on you indiscriminately. What you need is a unifying foundation that gives you the right amount of data at the right time, organized into highly actionable logs. We needed it too. That’s why we founded Corelight.

Compare to Open-Source Bro

Bro expert? The biggest risk to your company's security might be you.

We love open-source Bro, just like you. But when it comes to production deployment, usually the incident responders or threat hunters who know Bro become the sys admins too, and that poses a risk to your company. Read more in Seth's blog post.

Besides, don't you have better things to do?

When you deploy a Corelight Sensor, you're getting the expertise of Bro's creators packaged into a high performance appliance. You and your team can spend your time defending your network, not keeping Bro patched, upgraded, integrated and running.

Corelight Sensors are built to ensure Bro is secure, easy to integrate, higher performing and not suceptible to inadvertent misconfiguration.

Secured for greater security.

Since we started developing the first Corelight Sensor in 2016, we thought about security, from the operating system on up. Every Bro feature we enable in the Sensor gets thorough design consideration from the creators of Bro, so you can be sure your deployment is as secure as possible.

Get the best minds in a box.

Bro was created in 1995 by Corelight's chief scientist, Vern Paxson. Since then Bro's co-founders and their colleagues have been improving Bro, culminating in the development of the Corelight Sensor. When you buy one, you're buying decades of person-years of Bro expertise born from hundreds of real-world production deployments.

“Corelight was the easiest product to use. Setting up their appliance took me only 15 minutes, fully integrated.”

Compare the Corelight Sensor to open-source Bro.

Most Bro users start with open-source. We get it (we built it!). But at some point you may be wondering whether it’s time for an enterprise solution. Here are the key differences.

Features & Benefits
Open-source Bro
Flexible and simple data export
Yes
No
Web management UI
Yes
No
Hardware accelerated NIC
Included
Separate purchase required
Analysis throughput, per sensor
Up to 25 Gbps
3-4 Gbps
3rd party integrations
Yes
No
LDAP support
Yes
No
Support for Bro intelligence framework
Yes
Yes
Streaming data export
Yes
No
Shunting of large flows
Yes
Separate NIC purchase required
Optimized file extraction
Yes
No
Filtering to control export volume
Yes
No
Comprehensive API
Yes
No
Performance charts
Yes
No
Geolocation
Yes
No
Encrypted drives
Yes
System implementation required
Bro logs
Yes
Yes
FIPS Certified
Yes
No
Support for custom scripts and the Bro Package Manager
Yes
Yes
Support
Commercial support from the creators of Bro
Community mailing lists
Staff required for deployment
Minimal—appliance model
Bro experts and systems specialists
Updates and maintenance
Automatic updates, optional real-time monitoring
Manual patching, tuning, and updating required
Time for deployment
Application configuration in minutes
Typically weeks to months
Time for deployment
Application configuration in minutes
Typically weeks to months
Flexible and simple data export
Yes
Open-Source Bro
No
Web management UI
Yes
Open-Source Bro
No
Hardware accelerated NIC
Included
Open-Source Bro
Separate purchase required
Analysis throughput, per sensor
Up to 25 Gbps
Open-Source Bro
3-4 Gbps
3rd party integrations
Yes
Open-Source Bro
No
LDAP support
Yes
Open-Source Bro
No
Support for Bro intelligence framework
Yes
Open-Source Bro
Yes
Streaming data export
Yes
Open-Source Bro
No
Shunting of large flows
Yes
Open-Source Bro
Separate NIC purchase required
Optimized file extraction
Yes
Open-Source Bro
No
Filtering to control export volume
Yes
Open-Source Bro
No
Comprehensive API
Yes
Open-Source Bro
No
Performance charts
Yes
Open-Source Bro
No
Geolocation
Yes
Open-Source Bro
No
Encrypted drives
Yes
Open-Source Bro
System implementation required
Bro logs
Yes
Open-Source Bro
Yes
FIPS Certified
Yes
Open-Source Bro
No
Support for custom scripts and the Bro Package Manager
Yes
Open-Source Bro
Yes
Support
Commercial support from the creators of Bro
Open-Source Bro
Community mailing lists
Staff required for deployment
Minimal—appliance model
Open-Source Bro
Bro experts and systems specialists
Updates and maintenance
Automatic updates, optional real-time monitoring
Open-Source Bro
Manual patching, tuning, and updating required
Time for deployment
Application configuration in minutes
Open-Source Bro
Typically weeks to months
Time for deployment
Application configuration in minutes
Open-Source Bro
Typically weeks to months