Skip to content

Introduction

Cisco Secure Firewall Management Center (FMC) is the central manager for Cisco Secure Firewall Threat Defense (FTD) devices, where access control policies and their rules are defined and assigned to devices. This guide walks you through the steps to gather the necessary information and configure your FMC for the purpose of creating a Cisco Secure Firewall (FMC) Network Security integration.

Prerequisites

Before you begin, ensure that you have:

  • Access to a Cisco Secure Firewall Management Center with the REST API enabled
  • Access to an FMC account with the Administrator role, so that you can create user roles and users
  • Network access to your FMC over HTTPS, either directly or through a Synqly Bridge
  • If your FMC's certificate was issued by your organization's own certificate authority (CA), a copy of that CA's certificate. The section titled TLS Certificate explains how to get it

Required Permissions

PermissionPurpose
Policies > Access Control > Access Control PolicyRead access control policies and their access rules.
Devices > Device ManagementRead which devices and device groups each access control policy is assigned to.

We recommend a custom user role with only these two permissions, and with their Modify sub-permissions cleared, so the integration can read but not change your firewall configuration.

If you prefer a built-in role, Network Admin also covers both permissions, but additionally allows the account to modify policies and devices.

Generating Credentials

Create a user role

  1. Log in to your FMC using an account with the Administrator role
  2. Select System (gear icon) > Users, then open the User Roles tab
  3. Click Create User Role, and give the role a name such as Synqly Read Only
  4. Under Menu Based Permissions, select Policies > Access Control > Access Control Policy and clear its Modify Access Control Policy option
  5. Select Devices > Device Management and clear its Modify Devices option
  6. Click Save. The permissions are described in the section above titled Required Permissions

Create a user

  1. Select System (gear icon) > Users, then open the Users tab
  2. Click Create User, and enter a username for a dedicated service account. Use a dedicated account rather than a personal one: if the same account signs in to the FMC web interface and the REST API, one session ends the other
  3. Set Authentication to Use Internal Authentication, then enter and confirm a password
  4. Clear Force Password Reset on Login, since the integration cannot complete a password reset
  5. Under User Role Configuration, select the role created above
    • If your FMC has multiple domains, assign the role in the domain the integration should read
  6. Click Save
  7. Take note of the username and password, and store these values in a safe location
  8. You have now created a service account for the integration. Proceed to the next section titled TLS Certificate

The REST API is enabled by default. If it has been turned off, enable it under System (gear icon) > Configuration > REST API Preferences > Enable REST API.

TLS Certificate

Before it sends any credentials, the integration checks that it is really talking to your FMC by verifying the FMC's HTTPS certificate. The TLS Verification setting tells it how to do that. Choose the Mode that matches your FMC's certificate:

ModeUse it whenWhat else you enter
VerifyYour FMC's certificate was issued by a public certificate authority, such as DigiCert, Let's Encrypt or Sectigo. This is the default.Nothing
Custom CAYour FMC's certificate was issued by your organization's own certificate authority, such as an internal company CA.The CA's certificate (see Get the CA certificate below)
SkipYour FMC still uses its default self-signed certificate, and you are setting up a test or development integration.Nothing

If unsure about which to use, open your FMC's web interface in your browser and check what happens:

  • The page opens without a warning, and the certificate's issuer is a well-known public company: use verify
  • The page opens without a warning, and the issuer is your organization's own CA (its name often includes your company's name, or words such as Internal, Corporate or Issuing CA): use custom_ca
  • The browser warns that the connection is not private: open System (gear icon) > Configuration > HTTPS Certificate in your FMC (in version 10 and later, Administration > Configuration > HTTPS Certificate) and compare the certificate's Issuer and Subject:
    • If they are the same, the FMC uses its default self-signed certificate: use skip for testing, and see If your FMC uses its default self-signed certificate below before going to production
    • If the issuer is your organization's CA, your computer just does not trust that CA yet: use custom_ca, and get the CA certificate from the team that manages your organization's certificates

To view the certificate's issuer in your browser, click the padlock or site information icon next to the address bar and open the certificate details. If you are still not sure, ask the team that manages your FMC or your organization's certificates.

skip keeps the connection encrypted, but anyone able to intercept the connection could pretend to be your FMC and receive the integration's credentials. Use verify or custom_ca for production.

Get the CA certificate (custom_ca only)

For custom_ca, the integration needs the certificate of the CA that issued your FMC's certificate. This is a text file that starts with -----BEGIN CERTIFICATE-----, known as PEM format. It is not secret, and you can get it in either of these ways.

Option 1: Export it from your browser. If your FMC's web interface opens in your browser without a certificate warning, your computer already trusts your organization's CA, and you can export it:

  1. Open your FMC's web interface
  2. Click the padlock or site information icon next to the address bar, and open the certificate details
  3. Find the certificate hierarchy (sometimes called the certificate path or chain). It lists your FMC's certificate at the bottom and the CAs above it
  4. Select the top certificate in the hierarchy. This is your organization's root CA
  5. Click Export, and save it in Base64 or PEM format. If you are given a choice, export a single certificate rather than the whole chain
  6. Open the saved file in a text editor and copy its contents, including the -----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines

These steps differ slightly between browsers (Chrome, Edge, Firefox and Safari each place the certificate viewer and export button in different spots). If you cannot find them, search for how to view and export a site's certificate in your browser.

Option 2: Ask your organization. If your browser shows a certificate warning for your FMC, cannot export the certificate, or you are not sure which certificate to choose, contact the person or team that manages your organization's certificates, often IT or security. Ask them for "the root CA certificate in PEM format that issued our FMC's HTTPS certificate". Whoever installed the certificate on your FMC also had this CA certificate at that time.

Only paste the CA certificate. Never paste a private key, which starts with -----BEGIN PRIVATE KEY----- or similar; the integration rejects it.

If the connection test fails with "certificate signed by unknown authority" even though you used custom_ca, your FMC is probably not sending the intermediate certificate that sits between its own certificate and the root CA. Your browser can still show the full hierarchy because it fills in the missing certificate on its own, but the integration cannot. To fix this, do one of the following:

  • In the browser's certificate hierarchy, select the certificate directly above your FMC's certificate instead of the top one, export it the same way, and use it as the CA Certificate. If the hierarchy has more than one certificate between the top and your FMC's certificate, you can export each of them and paste them one after another into the same field.
  • Or ask your FMC administrator to re-import the FMC's HTTPS certificate with its intermediate certificates included. Then the root CA alone works.
If your FMC uses its default self-signed certificate

skip keeps the connection encrypted, but it does not confirm that the integration is talking to your FMC. Use it only for development or testing.

For production, ask your FMC administrator to replace the default certificate. They can do this on the same HTTPS Certificate page with Import HTTPS Server Certificate, using a certificate from a public CA or from your organization's own CA. Then use verify or custom_ca.

If the integration connects through a Synqly Bridge

The TLS Verification setting is not used. The Bridge checks the FMC's certificate itself: against public CAs by default, or against the CA you configure for the FMC's host when you start the Bridge, using --tls-trust and --tls-host. For example:

--tls-trust corp=/path/to/corp-root-ca.pem --tls-host fmc.example.com=corp

The CA file for the Bridge is the same PEM certificate described in Get the CA certificate above.

Configuring the Integration

To configure a new Cisco Secure Firewall (FMC) integration in the Synqly system, provide each of the values as defined below:

Integration ParameterDescription
Base URLThis is the root URL of your FMC, for example https://fmc.example.com. Do not include any path components such as /api.
UsernameThis is the username of the FMC service account gathered when creating the user above.
PasswordThis is the password of the FMC service account gathered when creating the user above.
DomainOptional. The FMC domain to read from. For a subdomain, enter its full path, for example Global/Engineering. Defaults to Global. The service account must have its role assigned in this domain.
TLS Verification: ModeOptional. How the FMC's certificate is checked: verify, custom_ca or skip. Defaults to verify. See TLS Certificate. Not used over a Synqly Bridge.
TLS Verification: CA CertificateRequired when Mode is custom_ca, otherwise ignored. The PEM certificate of the CA that issued your FMC's certificate. See TLS Certificate. Not used over a Synqly Bridge.

Additional Resources