Collect Cisco firewalls
Choose FMC, FTD or ASA based on where configuration is managed.
Choose the correct source
| Source | Method | Credential |
|---|---|---|
| FMC | HTTPS REST API | Authorized FMC API account and accessible domains. |
| FTD managed by FDM | HTTPS API, or supported SSH capture | Authorized FDM/device account. |
| ASA | SSH | Account permitted to read configuration and required operational commands. |
Prepare access
Enable the required API/SSH service and allow the collector source. FMC domain access and ASA/FTD command privileges determine the available reads.
For FMC, confirm REST API availability
FMC 10.0: Administration > Configuration > REST API Preferences. Older releases: System > Configuration > REST API Preferences. Have the administrator enable REST API unless UCAPL requirements prohibit it.
Use a dedicated FMC API account
Use a dedicated API reader for the intended domains. Avoid simultaneous UI/API use of one account; one session can end the other.
Let the collector authenticate
Enter the FMC account locally; the app obtains the API session token.
Collect from the matching target
Choose FMC, FTD or ASA and the supported method. Enter the management address, vendor account and workspace token.
ASA may need an enable credential. An FMC certificate hostname can become its display name; the management address still identifies the read endpoint.
Review the scope
FMC and managed firewalls are separate analysis contexts. Select ASA contexts when prompted and verify the source identity.