サポートと今すぐチャット
サポートとのチャット

Change Auditor 7.4 - SIEM Integration User Guide

Integrating Change Auditor and SIEM Tools Subscription Management
Adding the PowerShell module Viewing available commands and help Connecting to Change Auditor Managing subscriptions Working with event subscriptions in the client Managing a Splunk integration Managing an IBM QRadar integration Managing a Micro Focus Security ArcSight Logger and Enterprise Security Manager (ESM) integration Managing a Quest IT Security Search integration (Preview) Managing a Syslog integration Managing a Microsoft Sentinel integration
Webhook technical insights

Set-CASplunkEventSubscription

Use this command to modify a Splunk subscription.

Table 2. Available parameters

Parameter
Description

-Connection

A connection obtained by using the Connect-CAClient command. See the Change Auditor Command Guide for details.

-Subscription

The PSCAEventWebhookStatus object that corresponds to the subscription to modify. This parameter is required if the SubscriptionId parameter is not specified. Use the Get-CASplunkEventSubscriptions command to get a list of objects.

-SubscriptionId

The ID of the subscription to modify. This parameter is required if the Subscription parameter is not specified. Use the Get-CASplunkEventSubscriptions command to find the ID.

-SplunkUrl (Optional)

Specifies the address of your Splunk instance that will receive the event data.

•
For a Splunk Enterprise instance, use https://[hostname]:[port]/services/collector/event ([hostname] is the hostname of your Splunk instance, [port] is the port defined in your Splunk instance's HTTP Event Collector token page (default is 8088)
•
For a Splunk cloud instance, use:
“https://input-[hostname]:[port]/services/collector/event”. (Hostname is available in the address bar of an open Splunk cloud instance.)

For details, see the Splunk documentation on HTTP Event Collector data inputs.

-EventToken (Optional)

The unique identifier (token) used by Splunk to confirm that the specified SplunkUri is authorized to accept event data.

The token value is created during the Splunk instance configuration.

For details on creating an event collector token, see the Splunk documentation on HTTP Event Collector data inputs.

-BatchSize (Optional)

Specifies the maximum number of events to include in a single notification. The default is 10000 events.

-Enabled (Optional)

Specifies whether the subscription is enabled or disabled. By default it is enabled.

-HeartbeatUrl (Optional)

Specifies where (URL) to send heartbeat notifications.

NOTE: If no value is specified, heartbeat notifications are not sent.

-HeartbeatToken (Optional)

The unique identifier (token) used by Splunk to confirm that the specified heartbeatUri is authorized to accept heartbeat notifications.

NOTE: This is optional as you may have opted to send your heartbeat notifications to a URL that does not require a token for verification.

-NotificationInterval (Optional)

Specifies how often (in milliseconds) notifications are sent to the Splunk instance. By default this is set to 0 which results in a continuous stream of events.

-HeartbeatInterval (Optional)

Specifies how often (in milliseconds) heartbeat notifications are sent to the HeartbeatURL. By default, this is set to every 5 minutes. Setting this to 0 disables the heartbeat notifications.

-AllowedCoordinators (Optional)

Specifies the DNS or NetBIOS name of the coordinators permitted to send events. By default, any coordinator can send the events.

NOTE: The list order does not determine which coordinator is selected to send events.

-Subsystems (Optional)

Specifies an array of event subsystems from which to send events. This can be single or multiple subsystems.

NOTE: To obtain an array of subsystems, use the Get-CAEventExportSubsystems command and filter the list to specify the required subsystems.
NOTE: The subsystems specified override the current subsystems included in the subscription.

-IncludeO365AADDetails (Optional)

Specifies whether to include the raw JSON event details provided by Microsoft. When set to true, the event will include a field named additionalDetails, containing the raw JSON string for Office 365 and Azure Active Directory events. When set to false, the additionalDetails field is not included.

By default, this is set to true.

Example: Disable a subscription

Set-CASplunkEventSubscription -Connection $connection -SubscriptionId $SubscriptionId -Enabled $false

Example: Edit the subsystems included in a webhook subscription

$newSubsystems = Get-CAEventExportSubsystems -Connection $connection | ? { $_.DisplayName -eq "File System" -or $_.DisplayName -eq "Active Directory" }

Set-CASplunkEventSubscription -Connection $connection -SubscriptionId cd87b774-8e65-46e1-8520-da478c60c4c3 -Subsystems $newSubsystems

Remove-CASplunkEventSubscription

Use this command to remove a Splunk subscription.

Table 8. Available parameters
Parameter
Description

-Connection

A connection obtained by using the Connect-CAClient command. See the Change Auditor Command Guide for details.

-Subscription

The PSCAEventWebhookStatus object that corresponds to the subscription to remove. This parameter is required if the SubscriptionId parameter is not specified.

-SubscriptionId

The ID of the subscription to remove. This parameter is required if the Subscription parameter is not specified. Use the Get-CASplunkEventSubscriptions command to find the ID.

Example: Remove a Splunk subscription

Remove-CASplunkEventSubscription -Connection $connection -SubscriptionId $subscriptionId

Managing an IBM QRadar integration

You can take advantage of the rich data gathered by Change Auditor and use it with QRadar on-premises deployments. To begin sending event data, you need to create the QRadar extension and a QRadar event subscription with Change Auditor. The subscription contains information about where to send the notifications and heartbeats and the event subsystems to include.

* 
IMPORTANT: To ensure that QRadar can read and present Change Auditor events, you need to import the extension created during the subscription creation or with the New-CAQRadarExtension command.
1
Open the QRadar console and select the Admin tab.
2
Select Extensions Management | Add.
3
Select the extension zip file and follow the instructions.
If prompted that the extension is not signed, select Install. When prompted to overwrite or keep existing data, select Overwrite.
* 
IMPORTANT: If your Change Auditor coordinator IP addresses change, you must update the corresponding log source identifier in QRadar.
1
Open the QRadar console and select the Admin tab.
2
Select Log Sources.
3
Select the Change Auditor log source and select Edit.
4
Enter the new IP address into the Log Source Identifier field and select Save.
•
Working with QRadar subscriptions through the client
•
New-CAQRadarExtension
•
New-CAQRadarEventSubscription
•
Get-CAQRadarEventSubscriptions
•
Set-CAQRadarEventSubscription
•
Remove-CAQRadarEventSubscription

Working with QRadar subscriptions through the client

* 
NOTE: All new subscriptions created through the client are encrypted with TLS/SSL. QRadar must be configured to accept the TLS protocol.

To create a subscription that is not encrypted, use the New-CAQRadarEventSubscription command and set -TlsEnabled to false.
To create a QRadar subscription
1
From the Administration Tasks, select Configuration | Event Subscriptions.
2
Click Add QRadar Subscription to open the event subscription wizard.
3
Specify the IPv4 address or FQDN (fully qualified domain name) of the QRadar instance that will receive the event data.
4
Specify the port number for your QRadar instance that will receive the event data. The default port is 6514.
5
Click Next to select the events to forward based on subsystem and event date. Once the subscription is created the starting event date and time cannot be changed.
•
By default, events start sending after the subscription is created. To change when to begin sending events, click Send events starting and select the desired date and time. The time cannot be more than 30 days prior to the Change Auditor installation date.
•
Select the subsystems to include in the subscription.
6
Click Next to create the required extension to import to your QRadar instance. The extension instructs QRadar on how to read and present Change Auditor events. Specifically, it defines the log source (coordinator) and maps Change Auditor event columns to QRadar event columns.
* 
NOTE: If you create a new extension, the subscription is created in the disabled state. After you have imported and applied the extension, you need to enable the subscription.
* 
NOTE: If you have previously configured your QRadar instance for Change Auditor, you can select My QRadar instance is already configured and click Finish to complete the subscription setup.
7
Specify the file path and name for the file and click Generate extension.
8
Click OK in the confirmation dialog. Copy the file path to import the extension to your QRadar instance.
9
Click Finish.
To view existing QRadar subscription details:
1
From the Administration Tasks, select Configuration | Event Subscriptions.
2
Expand the required subscription.
The summary page displays the type of subscription (Target), where the events are being sent, the subscription status (Enabled or Disabled), and when the last event was sent (Last Event).
To create a new extension
1
From the Administration Tasks, select Configuration | Event Subscriptions.
2
Right-click the required subscription and click Generate Extension.
3
Specify the file path and name for the file and click Generate file.
4
Click OK in the confirmation dialog.
5
Copy the file path to import the extension to your QRadar instance.
To edit the QRadar subscription
1
From the Administration Tasks, select Configuration | Event Subscriptions.
2
Select the required subscription and click Edit.
3
If required, enter the server and port and click Next.
4
If required, add and remove the subsystems included in the subscription and click Next.
5
If required, you can generate a new extension.
6
Click Finish.
To remove a QRadar subscription
1
From the Administration Tasks, select Configuration | Event Subscriptions.
2
Select the required subscription and click Delete.
3
Confirm the removal.
To enable and disable a subscription
•
When viewing the summary information, select the status column and choose to enable or disable the subscription as required.
To refresh the summary information
1
From the Administration Tasks, select Configuration | Event Subscriptions.
2
Click Refresh.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択