Using Geolocation in Firepower Access Control Policies
The use of geolocation is fairly obvious in monitoring networks with Firepower Management Center. What may be less obvious is that Continents and Countries can also be specified as the source or destination of connections in an Access Control Policy. Basically, this geographical information becomes one more match criteria that can be used to identify traffic for a block or allow action.
To get to this capability, open the Access Control Policy that is in use by the Firepower device. Within the policy, open or create an applicable rule. On the network tab (where you configure the source and destination addresses) a Geolocation tab can also be found. Clicking on this tab exposes Continents and Countries. These can be added as sources and/or destinations.

Note to reader: All Firepower content can be accessed by clicking here (or choosing Firepower from the menu at the top of the page).
As can be seen in the diagram above, I am creating a rule to block traffic to France. Before I save and deploy the policy changes to the device, I will confirm reachability to an IP address that exists in that part of Europe.
Last login: Mon Jul 17 11:48:29 on ttys000 PAULS:~ pauls$ Continue reading
Juniper’s former CTO was the founder of the company.
This partnership has been in the works since Ixia announced the availability of CloudLens for the public cloud.
It struck managed services deals with the two companies.
Gartner predicts automated penetration testing to hit 10 percent by 2020.
Ericsson's network business was impacted by operators expanding fiber instead of investing in radios.
Its security product is based on open-source Bro.
Will there be any room left for Wi-Fi in the brave new world of LTE-Unlicensed (LTE-U) and LTE Licensed Assisted Access (LAA) deployed in the 5 Gigahertz (GHz) spectrum band? These two technologies are just starting to be promoted by a number of mobile carriers and embraced by some early adopter enterprises that want better...