Skip to content

Carbon Black - Palo Alto Network WildFire binary detonation connector

License

Notifications You must be signed in to change notification settings

carbonblack/cb-wildfire-connector

Repository files navigation

Carbon Black - Wildfire Connector

The Wildfire connector submits binaries collected by Carbon Black to a Wildfire appliance for binary analysis. The results are collected and placed into an Intelligence Feed on your Carbon Black server. The feed will then tag any binaries executed on your endpoints identified as malware by Wildfire. Only binaries submitted by the connector for analysis will be included in the generated Intelligence Feed.

Installation Quickstart

As root on your Carbon Black or other RPM based 64-bit Linux distribution server:

cd /etc/yum.repos.d
curl -O https://opensource.carbonblack.com/release/x86_64/CbOpenSource.repo
yum install python-cb-wildfire-connector

Once the software is installed via YUM, copy the /etc/cb/integrations/wildfire/connector.conf.example file to /etc/cb/integrations/wildfire/connector.conf. Edit this file and place your Carbon Black API key into the carbonblack_server_token variable and your Carbon Black server's base URL into the carbonblack_server_url variable. Next, add your WildFire API keys to the wildfire_api_keys variable. If you have multiple keys, they can be separated by a semicolon (;).

Once the software is configured, then you can start the connector via service cb-wildfire-connector start. Any errors will be logged into /var/log/cb/integrations/wildfire/wildfire.log. The connector will automatically create a feed in the connected Carbon Black server's console.

Troubleshooting

If you suspect a problem, please first look at the Wildfire connector logs found here: /var/log/cb/integrations/wildfire/wildfire.log (There might be multiple files as the logger "rolls over" when the log file hits a certain size).

If you want to re-run the analysis across your binaries:

  1. Stop the service: service cb-wildfire-connector stop
  2. Remove the database file: rm /usr/share/cb/integrations/wildfire/db/sqlite.db
  3. Remove the feed from your Cb server's Threat Intelligence page
  4. Restart the service: service cb-wildfire-connector start

Support

  1. Use the Developer Community Forum to discuss issues and ideas with other API developers in the Carbon Black Community.
  2. Report bugs and change requests through the GitHub issue tracker. Click on the + sign menu on the upper right of the screen and select New issue. You can also go to the Issues menu across the top of the page and click on New issue.
  3. View all API and integration offerings on the Developer Network along with reference documentation, video tutorials, and how-to guides.