Here you can create an "inside" zone and "outside" zone corresponding with each interface. Choose the interface tab and edit the interfaces. After the device is connected, click on the name of the device in the Device Management. This might take a few minutes while the Access Control Policy is applied. I'm not going to configure this in my lab.Ĭlick Register when done and join the device to the FMC for management. This is a unique key for configuring Firepower devices over the internet that need to go through a NAT. There is a optional setting for NAT ID under Advanced Settings.
Then choose the licenses that will be applied to the device including Protection (intrusion detection and prevention, file control, and Security Intelligence filtering), Control (user and application control), Malware (network-based Advanced Malware Protection), URL Filtering (category and reputatio-based URL filtering), and VPN (7000/8000 appliances only.Open up your browser and navigate to the IP address that you just configured for the FMC and login with the default credentials. After you have configured all the applicable information, it will save the configuration. It will walk you through the network configuration script. We will still need to configure the network by issuing the following command: Next we will start the Firepower Management Center and login with the default credentials. The first thing I'm going to do is configure the domain name and time information:Ĭlock timezone UTC 0 " prompt, enter the following to configure the IP information:Īfter configuring the IP address, we will next configure the Firepower module to point towards the Firepower Management Center for management: To start, I'm going to configure the ASA side of things. Instead, I'm going to go through the basic setup of the ASA and the Firepower Management Center (FMC).
I'm not going to dig too deep into individual policies since those should be dedicated to their own blog post. In this post, I'm going to do a basic setup of my ASA with Firepower.