> For the complete documentation index, see [llms.txt](https://docs.keeper.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeper.io/enterprise-guide/jp/event-reporting/qradar.md).
# IBM QRadar
Keeper SIEMからIBM QRadarへのイベントプッシュ連携
### 概要
KeeperはIBM QRadarへのイベントストリーミングに対応しています。外部へのログ出力はリアルタイムで行われ、新しいイベントは数分以内に表示されます。設定手順は以下のとおりです。
QRadarプッシュ連携の設定
QRadarでは、TCP経由の標準的なSyslogプッシュを使用します。
**ポート**\
TCPポート514および6514 (TLS)
**エクスポートされるフィールド**\
"audit\_event"、"username"、"client\_version"、"remote\_address"、"channel"、"result\_code"、"email"、"to\_username"、"client\_version\_new"、"username\_new"、"file\_format"、"record\_uid"、"folder\_uid"、"folder\_type"、"shared\_folder\_uid"、"attachment\_id"、"team\_uid"、"role\_id"
**ペイロードの例**
{% code overflow="wrap" %}
```
<165>1 2022-10-13T21:05:51.996Z yourLogSourceID keeper - - - {"record_uid":"XXX","audit_event":"fast_fill","remote_address":"12.34.56.78","category":"usage","client_version":"Browser Extensions.16.4.7","username":"user@company.com","enterprise_id":123456}
```
{% endcode %}
{% hint style="info" %}
エンドポイントでは、証明書のサブジェクト名と一致する有効な署名付きSSL証明書を使用してください。証明書には、CAからの完全な証明書チェーンも含まれている必要があります。Keeperは自己署名証明書には接続しません。
また、QRadarサーバーでKeeperサーバーからのトラフィックが許可されていることも確認してください。詳しくは[ファイアウォールの設定ページ](/enterprise-guide/jp/event-reporting/firewall.md)をご参照ください。
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.keeper.io/enterprise-guide/jp/event-reporting/qradar.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
