FireEye and Cisco Umbrella Integration Overview
With integration between the FireEye security appliance and Cisco Umbrella, security officers and administrators are now able to extend protection against today's advanced threats to roaming laptops, tablets or phones while also providing another layer of enforcement to a distributed corporate network.
This guide outlines how to configure your FireEye to communicate with Umbrella so security events from FireEye are integrated into policies that can be applied to clients protected by your Cisco Umbrella.
- A FireEye appliance with access to the public Internet.
- Umbrella dashboard administrative rights.
- The Umbrella dashboard must have the FireEye integration enabled.
Note: The FireEye integration is only included in the Umbrella Platform package. If you do not have the Platform package and would like to have FireEye integration, please contact your Cisco Umbrella representative. If you have the Platform package but do not see FireEye as an integration for your dashboard, please contact Technical Support.
Cisco Umbrella and FireEye: How does it work?
The FireEye appliance first sends Internet-based threats it's found, such as domains that host malware, command and control for botnet, or phishing sites, to Umbrella.
Umbrella then validates the information passed to Umbrella to ensure it is valid and can be added to a policy. If the information from FireEye is confirmed to formatted correctly (eg: not a file or a complex URL, or a highly popular domain) the domain address is added to the FireEye Destination List as part of a security setting that can be applied to any Umbrella policy. That policy is immediately applied to any requests being made from devices using policies with the FireEye Destination List.
Going forward, Umbrella automatically parses FireEye alerts and adds malicious sites to the FireEye Destination List—extending FireEye protection to all remote users and devices and providing another layer of enforcement to your corporate network.
*Important: While Umbrella tries its best to validate and allow domains which are known to be generally safe (for example, Google and Salesforce), to avoid unwanted interruptions, we suggest adding domains you never wish to have blocked to the Global Allow List or other destination lists as per your policy.*
- The home page for your organization. For example, mydomain.com
- Domains representing services you provide that might have both internal and external records. For example, mail.myservicedomain.com and portal.myotherservicedomain.com
- Lesser-known cloud applications you depend on heavily that Umbrella may not be aware of or include in its automatic domain validation. For example, localcloudservice.com
These domains should be added to the Global Allow List, which is found at Policies > Destination Lists in Umbrella https://dashboard2.opendns.com/#configuration/policysettings/domainlists.
How to configure your Umbrella dashboard to receive information from FireEye
The first step is to find your unique URL in Umbrella for the FireEye appliance to communicate with.
- Log into your Umbrella dashboard, navigate to Settings > Integrations and click FireEye in the table to expand it.
- Check Enable and then click Save. This generates a unique, specific URL for your organization within Umbrella.
You'll need this URL later when you're configuring the FireEye appliance to send data to Umbrella, so copy the URL and let's get started!
How to configure your FireEye to communicate with Umbrella
In order to begin sending traffic from your FireEye appliance to Umbrella, you need to configure the FireEye with the URL information generated in the first step.
- Start by logging into your FireEye and then click Settings.
Next, select Notifications from the list of settings:
Ensure all "Event Types" you want sent to Umbrella are checked (we recommend starting with all) and then click the HTTP link at the top of the column.
When the menu expands, set the following to enable Event Notification. The numbered steps are outlined in the screenshot below.
- Default Delivery: Per Event.
- Default Provider: Generic.
- Default Format: JSON Extended.
- Name the Server "OpenDNS".
- Paste the Umbrella URL you generated from your Umbrella dashboard earlier here.
- Notification drop-down: Select "All Events" to ensure maximum coverage.
The final step is to ensure "Delivery", "Default Provider" and "Provider Parameters" drop-downs all match the default settings, or if multiple notification servers are being used:
- Delivery: Per Event basis
- Default Provider: Generic
- Provider Parameters: Message format JSON Extended
- (Optional) If you prefer to send traffic over SSL, click "SSL Enable".
At this point, your FireEye appliance is set to send the selected Event Types to Umbrella. Next, you'll want to know how to see this information in your Umbrella dashboard and set a policy to block against this traffic.
Ensuring connectivity: “Test Fire” between FireEye and Umbrella
At this point it's a good idea to test your connectivity to You can ensure that everything is set up properly.
- Click Test Fire with "Domain-match" selected from the dropdown:
In Umbrella, the FireEye integration includes a list of domains provided by the FireEye Appliance in order to see which domain(s) are being actively added.
- After you’ve clicked Test Fire, in Umbrella navigate to Settings > Integrations and click FireEye in the table to expand it.
- Click See Domains.
Clicking Test Fire generates a domain in the FireEye Destinations List named “fireeye-testevent.example.com-[date]”. Each time you click Test Fire, it creates a unique domain with the date in Unix Epoch time attached to the test, so future tests will have a unique test domain name.
If the Test Fire is successful, more events from FireEye will be sent to Umbrella and a searchable list will begin to be populated and grow.
Observing events added to the FireEye Security Category in ‘Audit mode’
The events from your FireEye appliance will begin to populate a specific destination list that can be applied to policies as a FireEye security category. By default, the destination list and the security category are in 'audit mode' and are not applied to any policies and will not result in any change to your existing Umbrella policies.
Note: ‘Audit’ mode can be enabled for however long is necessary based on your deployment profile and network configuration.
Review destination list
You can review the FireEye destination list at any time.
- Navigate to Settings > Integrations.
- Expand FireEye in the table and click See Domains.
Review security settings for a policy
You can review the security setting that can be added to a policy at any time.
- Navigate to Policies > Security Categories.
- Click a policy in the table to expand it and scroll to Integrations to locate the FireEye setting.
When getting started, it's best to leave this security setting set to Allow (default) in order to ensure domains are correctly populating in an 'audit' mode.
Applying the FireEye security settings in block mode to a policy for managed clients
Once you're ready to have these additional security threats enforced against by clients managed by Umbrella, simply change the security setting on an existing policy, or create a new policy that that sits above your default policy to ensure it is enforced first.
First, create or update a security setting at Policies > Security Categories. You can edit the default settings to enable the FireEye security category in block mode or create a new security setting with the FireEye security category enabled in block mode.
Simply click the icon to change the FireEye security setting from Allow to Block.
Next, in the Policy wizard, add a security setting to the policy you're editing:
- Navigate to Policies > Policy List.
- Expand a policy.
- Click the Select Policy Settings tab.
- In the Security Settings to enforce pull-down, select a security setting that includes the Block for FireEye setting.
- Click Save.
Note: It’s possible to edit your Security Settings from the Policy wizard if you so choose.
Complete and save the policy, and the FireEye domains contained within the security setting for FireEye will be blocked for identities using the policy.
Reporting within Umbrella for FireEye events
Reporting on FireEye Security Events
The FireEye destination list is one of the security categories you can report on. Most or all of the reports use the Security Categories as a filter. For instance, to see the activity for website addresses that were blocked by the FireEye destination list, navigate to Reporting > Activity Search. Apply a filter to only show the security category for FireEye and then click Run Report to see the activity for the time period selected in the report.
To run a report of the security activity associated with domains originating with the FireEye Appliance, navigate to Reporting > Activity Search and select the report to run only for that category as in the example above.
Reporting on when domains were added to the FireEye Destination List
The Admin Audit log includes events from the FireEye appliance as it adds domains to the destination list. A user named “FireEye Account”, which is also branded with the FireEye logo, generates the events. These events include the domain that was added and the time at which it was added.
You can filter to only include FireEye changes by applying a filter for the “FireEye Account” user.
If the “Test Fire” step earlier was performed, the addition of the FireEye test domain should appear in the Audit Log.
Handling Unwanted Detections or False Positives
Although unlikely, it is possible that domains added automatically by your FireEye appliance could potentially trigger an unwanted detection that blocks your users from accessing particular websites. In a situation like this, we recommend adding the domain(s) to an allow list (Policies > Destination Lists), which takes precedence over all other types of block lists, including security settings.
There are two reasons why this approach is preferable. First, in case the FireEye appliance was to re-add the domain after it was removed, the allow list safeguards against this causing further issues. Secondly, the allow list shows a historical record of problematic domains that can be used for forensics or audit reports.
By default, there is a Global Allow List that is applied to all policies. Adding a domain to the Global Allow List results in the domain being allowed in all policies.
If the FireEye security setting in block mode is only applied to a subset of your managed Umbrella identities (for instance, it's only applied to roaming computers and mobile devices), you can create a specific allow list for those identities or policies.
To create an allow list:
- Navigate to Policies > Destination Lists, click the (Add) icon and select Add Allow List.
- Give the list a meaningful name and add your domain to the list.
- Click Save.
Once the destination list has been saved, you can add it to an existing policy covering those clients that have been affected by the unwanted block.
Deleting Domains from the FireEye Destination List
Next to each domain name in the FireEye Destination List is a (Delete) icon. Deleting domains lets you clean up the FireEye Destination List in the event of an unwanted detection.
However, the delete is not permanent if the FireEye appliance resends the domain to Umbrella.
To delete a domain:
- Navigate to Settings > Integrations, then click FireEye to expand it.
- Click See Domains.
- Search for the domain name you want to delete.
- Click the Delete icon.
- Click Close.
- Click Save.
In the instance of an unwanted detection or false positive, we recommend creating an allow list in Umbrella immediately and then remediating the false positive within the FireEye Appliance. Later, you can remove the domain from the FireEye Destination List.