<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Using the Insight Command Line Interface (CLI) on</title><link>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/infra_cli/insight/</link><description>Recent content in Using the Insight Command Line Interface (CLI) on</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/infra_cli/insight/index.xml" rel="self" type="application/rss+xml"/><item><title>Sending logs to an external security information and event management (SIEM)</title><link>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/infra_cli/insight/cli_siem/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.protegrity.com/aiteam-edition/1.0.0/docs/infrastructure/infra_cli/insight/cli_siem/</guid><description>&lt;blockquote>
&lt;p>This is an optional step.&lt;/p>&lt;/blockquote>
&lt;p>The Protegrity infrastructure provides a robust setup for logging and analyzing the logs generated. It might be possible that an existing infrastructure is available for collating and analyzing logs.&lt;/p>
&lt;p>In the &lt;em>default setup&lt;/em>, the logs are sent from the protectors directly to the Audit Store using the Log Forwarder on the protector. Use the configuration provided in this section to send the logs to the Audit Store and the external SIEM.&lt;/p></description></item></channel></rss>