Cisco Security Cloud Control: Secure Firewall ASA Management
Is this content helpful?
Thank you for your feedback. Your response has been recorded.
AI responses are currently only available to logged in users. Log in
Important. Results generated by AI. Before using results, verify accuracy and completeness.
Only ask questions about this document. To ask questions about this product as a whole, go to Technical Documentation .
Suggestions
Sorry, we couldn't generate a response for this query.
Launch error. Something went wrong. Please try again.
Cisco Security Cloud Control: Secure Firewall ASA Management
Updated: July 17, 2026
Want to summarize with AI?
Log inImportant. Results generated by AI. Before using results, verify accuracy and completeness.
On this page
Learn how to create and import an ASA model to Security Cloud Control Firewall Management, including configuration file import, device identity, labels, and offline policy setup.
| 1. | From the Security Cloud Control Home page, click Firewall. |
|
| 2. | Choose Security Devices. |
|
| 3. | Click the Devices tab. |
|
| 4. | Click the ASA tab. |
|
| 5. | Select an ASA device. In the Management section, click Configuration. |
|
| 6. | To download the device configuration to your local computer, click Download. |
| 1. | From the Security Cloud Control Home page, click Firewall. |
|
| 2. | Choose Security Devices. |
|
| 3. | Click the add button ( |
|
| 4. | Click Import configuration for offline management. |
|
| 5. | Select the Device Type as ASA. |
|
| 6. | Click Browse, and select the configuration file in text format to upload. |
|
| 7. | Once the configuration is verified, you are prompted to label the device or service. For more information about labels and label groups, refer to Labels and Label Groups. |
|
| 8. | After labeling your model device, you can view it in the Security Devices list. Note |
Need help?
(Requires a Cisco Service Contract)
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
) to import the configuration file.