The Firepower System® database access feature allows you to query intrusion, discovery, user activity, correlation, connection, vulnerability, and application and URL statistics database tables on a Cisco Firepower Management Center, using a third-party client that supports JDBC SSL connections.
You can use an industry-standard reporting tool such as Crystal Reports, Actuate BIRT, or JasperSoft iReport to design and submit queries. Or, you can configure your own custom application to query Cisco data under program control. For example, you can build a servlet to report intrusion and discovery event data periodically or refresh an alert dashboard.
Note that you can connect to multiple Firepower Management Centers with a single client, but you must configure access to each one individually.
When deciding which appliance or appliances to connect to, keep in mind that querying the database on a Cisco appliance reduces available appliance resources. You should carefully design your queries and submit them at times consistent with your organization’s priorities.
For more information, see the following sections:
Major Changes for Database Access in Version 6.2
If you are upgrading your Firepower System deployment from Version 6.1 to Version 6.2, please note the following changes, some of which may require you to update your queries.
New and Modified Tables for Version 6.2
The table below lists changes to database access tables in Version 6.2.
Table 1-1 Summary of Changes to Tables in Version 6.2
Stores compromise state for hosts.
You must fulfill the prerequisites listed in the following sections before you can use the database access feature:
You can query the external database with any Cisco license installed. However, certain tables are associated with licensed features. These tables are only populated with data if you have configured licensing to allow use of that feature and your deployment is properly configured to generate the data. You may not be able to query tables associated with unlicensed features. For more information about licensing, see Understanding Licensing in the Firepower Management Center Configuration Guide.
Firepower System Features and Terminology
To understand the information in this guide, you should be familiar with the features and nomenclature of the Firepower System, and the function of its components. You should be familiar with the different types of event data these components generate. Note that you can frequently obtain definitions of unfamiliar or product-specific terms in the Firepower Management Center Configuration Guide. The configuration guide also contains additional information about the data in the fields documented in this guide.
The Firepower System requires the use of specific ports to communicate internally and externally, between appliances, and to enable certain functionality within the network deployment.
After you enable database access on the Firepower Management Center, the system uses ports 1500 and 2000 for the connection that carries JDBC traffic between the client and the appliance.
On the computer that you want to use to connect to the Firepower System database, you must install Java software, also known as the Java Runtime Environment (JRE) or the Java Virtual Machine (JVM). You can download the latest version of Java from
You must download and unzip a package from the Firepower Management Center that contains the JDBC driver files you will use to connect to the database. The package also contains executable files used to install an SSL certificate for encrypted communication with the Firepower Management Center, and other source files for these utilities.
You should also understand how to change applicable system settings on your computer, such as environment variables.
To query the Firepower System database, you can use commercially available reporting tools such as Actuate BIRT, JasperSoft iReport, or Crystal Reports, or any other application (including custom applications) that supports JDBC SSL connections. This guide provides the information you need to connect to the database, including the JDBC URL, driver JAR files, driver class, and so on. However, you should refer to your reporting tool documentation for detailed instructions on how to configure a JDBC SSL connection.
Cisco also provides a sample command-line Java application named RunQuery, which you can use to test your database connection, view the schema, and run basic ad hoc queries manually. The RunQuery source code is also a reference for setting up the database connection in a custom Java application. The RunQuery source code is included in the ZIP package that you download from the Firepower Management Center.
RunQuery is a sample client only, not a fully featured reporting tool. Cisco strongly recommends against using it as your primary method of querying the database. For information on using RunQuery, refer to the README file included in the ZIP package.
Note that the database access feature uses only the following JDBC functionalities:
- database metadata, which includes information such as schema, version, and supported features
- SQL query execution
Database access does not use any other JDBC functionality, including stored procedures, transactions, batch commands, multiple result sets, or insert/update/delete functions.
To query the database, you should know how to construct and execute
SELECT statements on single tables and on multiple tables using join conditions.
To assist you, this guide contains information on supported MySQL query syntax, the Firepower System database schema, allowed joins, and other important query-related requirements and limitations.
Where Do I Begin?
After you have met the prerequisites described in Prerequisites, you can begin configuring your client system to connect to a Firepower Management Center.
Setting Up Database Access explains how to configure the appliance to allow access, how to configure your client system to connect to the appliance, and how to configure your reporting application to connect to the appliance. It also contains some basic query instructions and information on supported MySQL syntax.
The rest of the guide contains schema and join information for the database and sample queries, and is split into the following chapters: