<?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: Splunkd access capability in Security</title>
    <link>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337487#M8614</link>
    <description>&lt;P&gt;You mean restricting rest API calls is it? Unfortunately there is not one. We correlate the splunk web access logs and the audit logs to identify if there are searches without user logs on web access and alert on it to identify rest users. May be there is a better way.&lt;/P&gt;</description>
    <pubDate>Wed, 07 Jun 2017 17:37:26 GMT</pubDate>
    <dc:creator>pradeepkumarg</dc:creator>
    <dc:date>2017-06-07T17:37:26Z</dc:date>
    <item>
      <title>Splunkd access capability</title>
      <link>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337486#M8613</link>
      <description>&lt;P&gt;Is there a capability that can be removed from a role that will remove the ability to run a remote search via the Splunkd port and force the user to use the UI?&lt;/P&gt;</description>
      <pubDate>Tue, 06 Jun 2017 15:34:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337486#M8613</guid>
      <dc:creator>pkeller</dc:creator>
      <dc:date>2017-06-06T15:34:40Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkd access capability</title>
      <link>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337487#M8614</link>
      <description>&lt;P&gt;You mean restricting rest API calls is it? Unfortunately there is not one. We correlate the splunk web access logs and the audit logs to identify if there are searches without user logs on web access and alert on it to identify rest users. May be there is a better way.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2017 17:37:26 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337487#M8614</guid>
      <dc:creator>pradeepkumarg</dc:creator>
      <dc:date>2017-06-07T17:37:26Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkd access capability</title>
      <link>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337488#M8615</link>
      <description>&lt;P&gt;Have not tested but this looks promising. You may have to define custom capability to assign to search REST endpoint.&lt;BR /&gt;
&lt;A href="https://answers.splunk.com/answers/423859/how-do-you-disable-the-rest-api-endpoint-servicess.html"&gt;https://answers.splunk.com/answers/423859/how-do-you-disable-the-rest-api-endpoint-servicess.html&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Check the $Splunk_home/etc/system/default/restmap.conf for full list of available endpoints.&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jun 2017 17:46:22 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337488#M8615</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2017-06-07T17:46:22Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkd access capability</title>
      <link>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337489#M8616</link>
      <description>&lt;P&gt;Splunk itself is also getting information by REST call to other machines, so please be carful trying disableing stuff&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jun 2017 12:29:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337489#M8616</guid>
      <dc:creator>teunlaan</dc:creator>
      <dc:date>2017-06-08T12:29:35Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkd access capability</title>
      <link>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337490#M8617</link>
      <description>&lt;P&gt;Thank you very much.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jun 2017 14:12:05 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337490#M8617</guid>
      <dc:creator>pkeller</dc:creator>
      <dc:date>2017-06-08T14:12:05Z</dc:date>
    </item>
    <item>
      <title>Re: Splunkd access capability</title>
      <link>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337491#M8618</link>
      <description>&lt;P&gt;Ultimately I determined that 2 factor authentication will, by nature, prevent this. So, we have that nailed. And, if we need to bypass that for strong use cases, we can set up local users. &lt;/P&gt;</description>
      <pubDate>Thu, 08 Jun 2017 14:13:59 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunkd-access-capability/m-p/337491#M8618</guid>
      <dc:creator>pkeller</dc:creator>
      <dc:date>2017-06-08T14:13:59Z</dc:date>
    </item>
  </channel>
</rss>

