<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Bluecoat proxy integration in Security</title>
    <link>https://community.splunk.com/t5/Security/Bluecoat-proxy-integration/m-p/259516#M7120</link>
    <description>&lt;P&gt;The Splunk Add-on for Blue Coat ProxySG expects the ProxySG log files in W3C ELFF format.  So this wont work for your log format.&lt;/P&gt;

&lt;P&gt;You can try the AddOn for Squid PRoxy (&lt;A href="https://splunkbase.splunk.com/app/2965/#/overview"&gt;https://splunkbase.splunk.com/app/2965/#/overview&lt;/A&gt;) it is CIM compliant. &lt;/P&gt;

&lt;P&gt;Most likely the AddOn for Squid Proxy will get you close, but you will need to update the header fields and extractions to reflect the additional BlueCoat fields. * This also depends on what version of BlueCoat you have and what fields you have enabled on the appliances..&lt;/P&gt;</description>
    <pubDate>Wed, 07 Sep 2016 06:46:08 GMT</pubDate>
    <dc:creator>esix_splunk</dc:creator>
    <dc:date>2016-09-07T06:46:08Z</dc:date>
    <item>
      <title>Bluecoat proxy integration</title>
      <link>https://community.splunk.com/t5/Security/Bluecoat-proxy-integration/m-p/259515#M7119</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;

&lt;P&gt;I'm trying to integrate blue coat proxy with Splunk, however stuck at the below point.&lt;BR /&gt;
The bluecoat proxy is sending its log in squid format through syslog to my indexer which app should i use ( TA- Blue coat or TA - Squid ) in order to make it CIM compatible.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2016 06:26:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Bluecoat-proxy-integration/m-p/259515#M7119</guid>
      <dc:creator>himapate</dc:creator>
      <dc:date>2016-09-07T06:26:57Z</dc:date>
    </item>
    <item>
      <title>Re: Bluecoat proxy integration</title>
      <link>https://community.splunk.com/t5/Security/Bluecoat-proxy-integration/m-p/259516#M7120</link>
      <description>&lt;P&gt;The Splunk Add-on for Blue Coat ProxySG expects the ProxySG log files in W3C ELFF format.  So this wont work for your log format.&lt;/P&gt;

&lt;P&gt;You can try the AddOn for Squid PRoxy (&lt;A href="https://splunkbase.splunk.com/app/2965/#/overview"&gt;https://splunkbase.splunk.com/app/2965/#/overview&lt;/A&gt;) it is CIM compliant. &lt;/P&gt;

&lt;P&gt;Most likely the AddOn for Squid Proxy will get you close, but you will need to update the header fields and extractions to reflect the additional BlueCoat fields. * This also depends on what version of BlueCoat you have and what fields you have enabled on the appliances..&lt;/P&gt;</description>
      <pubDate>Wed, 07 Sep 2016 06:46:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Bluecoat-proxy-integration/m-p/259516#M7120</guid>
      <dc:creator>esix_splunk</dc:creator>
      <dc:date>2016-09-07T06:46:08Z</dc:date>
    </item>
  </channel>
</rss>

