<?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: Splunk Enterprise Security Content management endpoint in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/unreadable-title/m-p/579378#M11009</link>
    <description>&lt;P&gt;While ES has its own API endpoints (see&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/ES/7.0.0/API/AbouttheSplunkEnterpriseSecurityAPI" target="_blank"&gt;https://docs.splunk.com/Documentation/ES/7.0.0/API/AbouttheSplunkEnterpriseSecurityAPI&lt;/A&gt;), it mostly uses core Splunk APIs.&amp;nbsp; For correlation searches, use the savedsearches endpoints.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Dec 2021 13:47:44 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2021-12-28T13:47:44Z</dc:date>
    <item>
      <title>..</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/unreadable-title/m-p/579353#M11005</link>
      <description />
      <pubDate>Wed, 19 Jan 2022 17:30:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/unreadable-title/m-p/579353#M11005</guid>
      <dc:creator>amys</dc:creator>
      <dc:date>2022-01-19T17:30:51Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security Content management endpoint</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/unreadable-title/m-p/579378#M11009</link>
      <description>&lt;P&gt;While ES has its own API endpoints (see&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/ES/7.0.0/API/AbouttheSplunkEnterpriseSecurityAPI" target="_blank"&gt;https://docs.splunk.com/Documentation/ES/7.0.0/API/AbouttheSplunkEnterpriseSecurityAPI&lt;/A&gt;), it mostly uses core Splunk APIs.&amp;nbsp; For correlation searches, use the savedsearches endpoints.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Dec 2021 13:47:44 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/unreadable-title/m-p/579378#M11009</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-12-28T13:47:44Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security Content management endpoint</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/unreadable-title/m-p/579380#M11010</link>
      <description>&lt;P&gt;..&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jan 2022 17:31:31 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/unreadable-title/m-p/579380#M11010</guid>
      <dc:creator>amys</dc:creator>
      <dc:date>2022-01-19T17:31:31Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Enterprise Security Content management endpoint</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/unreadable-title/m-p/579394#M11012</link>
      <description>&lt;P&gt;The saved/searches API documentation is at&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Splunk/8.2.4/RESTREF/RESTsearch#saved.2Fsearches" target="_blank"&gt;https://docs.splunk.com/Documentation/Splunk/8.2.4/RESTREF/RESTsearch#saved.2Fsearches &lt;/A&gt;.&lt;/P&gt;&lt;P&gt;As for which parameters are needed for a correlation search, I recommend using GET on an known correlation search to see which parameters are populated.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Dec 2021 14:58:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/unreadable-title/m-p/579394#M11012</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2021-12-28T14:58:57Z</dc:date>
    </item>
  </channel>
</rss>

