This document applies to Classic/Legacy Integrations. You may continue to use these integration configurations. While no active development is happening for these integrations, we continue to provide Classic/Legacy Integrations in the product. You do not have to move to MSI Integrations. If your support engineer or TSC recommends or you choose to move to MSI Integrations, you can take advantage of the latest features and functionality. For more information, see the MSI Integration documentation in the Integrations Overview.
Update the Validation Platform
Prerequisites
Information to gather before you start:
- IP address used to access QRadar.
- Port for QRadar communications (default is 443).
- Identify whether the protocol is HTTP or HTTPS for connections to the QRadar port (default is HTTPS).
- Identify or create credentials to access QRadar. Admin permissions are required, at minimum.
- Identify the timezone of the QRadar host.
Configuration
To add the QRadar integration
Go to Settings > Integrations.
- Click Add Integration > QRadar.
- Enter information for the Host, Port, and Protocol.
- Select the Credential type and add the appropriate credentials.
- Change the Time zone to match that of the QRadar host.
- Review and update the Query to include instance-specific field names, sources, data types, and other customizations.The default queries can be viewed by clicking Show default query.The query includes information that allows event matching based on any file hashes included in an Action.
- Expand Advanced options.
- (Optional) Update Query time and Delay time. The Query time is the amount of time (minutes) before and after the query runs that the platform looks for events, while the Delay time is the amount of time (minutes) that the platform waits to run the first query after a Job Action starts. For example, you configure your integration with the following values: Query time = 5, Query interval = 30 seconds, and Delay time = 0. When a Job Actions starts at 12:00:00, the first time the query runs, the platform looks for events from 11:55:00 to 12:00:00. Then 30 seconds later, it looks for events from 11:55:30 to 12:00:30. This interval continues, with the last query looking from 12:00:00 to 12:05:00. If you instead configured the Delay time to equal 10, it would run the same query, but it wouldn't start that query until 12:10:00.If your monitors are set to run more frequently than the query time, this configuration impacts the pass/fail results for AEDA monitors.
(Optional) Review and update the populated query information (Flows query, Offense query fields, Offense query filter, Correlated Events Query).
(Optional) Select Enable query for Malicious DNS Actions and configure the Query. This query will only be used when you run Malicious DNS Actions or Captive DNS Actions.
(Optional) Select Enable query for Email Actions and configure the Query. This query will be only be used when you run Email Actions.
(Optional) Select Enable query for Host CLI Actions and configure the Query. This query will only be used when you run Host CLI Actions.
If you enable the Host CLI Actions query and use the %HOST_CLI_ACTOR_HOSTNAMES% variable, the platform will substitute the plain hostname and the information from the Alternate Hostname field on the Actor configuration page.(Optional) Select Discover network devices automatically.
Modify the Query Interval and Event Time Adjustment, if necessary.
(Optional) Assign a Name.
(Optional) Choose Yes to save suspicious events.
Click Submit.
The QRadar integration can also include these two fields in its queries:
host, which when populated will be used to indicate the source of the events.url, which when populated is used for matching events to DNS query Actions.The url field is not a default qradar field, so you name it yourself. For example,
select qid, qidname(qid), "DNS_Domain" as url, sourceip,
Set up Proxy Assignment
If all outbound connections go through a proxy, you may want to set up a proxy definition and assignment for your integration. For information on setting up your proxy rules, see Proxy Rules.
Verify connectivity
to verify connectivity to QRadar
Click Test to verify that:
- The Director can communicate with QRadar on the port and protocol specified.
- QRadar credentials are valid and working.
- Times match.
Run a Malicious or Captive DNS Action and then review the last run query to verify:
- The custom DNS query works as expected (if configured).