# Configuring Cisco ASA **Step by step instructions to register an ASA SFR module with the FirePOWER Management Center **Cisco Adaptive Security Appliance (ASA) can run software or hardware modules known as FirePOWER or SFR modules (short for Sourcefire). The FirePOWER module for [Cisco ASA](https://www.fieldengineer.com/skills/cisco-asa?utm_source=social&utm_medium=skills&utm_campaign=outreach) provides a few cutting edge firewall services. Indeed, a portion of his capacities directly cover with what ASA can do alone. If you have a FirePOWER module, use its features rather than ASA, because the FirePOWER module is centrally configured will in general take into consideration more regular updates. The FirePOWER module chooses what traffic is acceptable and awful, yet it is the ASA that makes the decision. So we need to send visitors to FirePOWER to make a decision, and furthermore, we need to have a policy in the FirePOWER module that make sthe decision to take. The issue is, FirePOWER expects us to utilize an administration place known as the FireSIGHT Management Center (FMC) to configure it. In this post I'll tell you the best way to register FirePOWER with a management center. For this case we utilize the Virtual FireSIGHT Management Center.  Virtual FireSIGHT Management Center The FireSIGHT Management Center (FMC) can be downloaded from Cisco and deployed as an open source programming (OVA) in your VMware environment. Once deployed, there is a little configuration that you need to do on common gadgets, however once you sign in to the web interface, you can set the system policy and IPS policies, file policies, etc. On account of FMC, FirePOWER is known as a managed device. You should add a managed device device to FMC and permit. That's right, everything gets authorized. When you add ASA it will utilize your preferred licenses. Note: The authorizing process for ASA isn't the most evident way. You should separate the PAK file and send it to Cisco. The PAK, along with the license number from FMC, will give a Protection and Control license which is permanent. From that point you should add an IPS filter license and URL. For more information on the best way to give an ASA license for FirePOWER services, see the user guide. Firepower module design If you have an ASA that is already configured and has the nuts and bolts of network connection previously settled. This incorporates translation of network addresses and routing alongside all the other things that makes your ASA tick. What's more, there are some little differences between ASA's hardware model and how the communication for the FirePOWER module works. The large takeaway here is that ASA's management interface is utilized to communicate with FMC. This is an interface that lone handles traffic, so you specify a gateway and FMC should be available on that network. The command line interface for the FirePOWER module is limited. It's like a Linux shell and there truly isn't a lot to do there. The configuration of the FirePOWER module requires the following command: > configure manager add <hostname | IPv4_address | IPv6_address | DONTRESOLVE> reg_key <nat_id> > **[Configuration guide **](https://www.techrepublic.com/article/how-to-register-an-asa-sfr-module-with-the-firepower-management-center/)