<?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 cloud rest API call related security questions in Security</title>
    <link>https://community.splunk.com/t5/Security/Splunk-cloud-rest-API-call-related-security-questions/m-p/555213#M12285</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/234565"&gt;@santosh121&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's quite extensive list, some of them being directly supported and others need to be supported through other products example Load balancer front of Splunk API's. I would&amp;nbsp; recommend to connect with Splunk support for the correct guidance.&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;An upvote would be appreciated if it helps!&lt;/P&gt;</description>
    <pubDate>Thu, 10 Jun 2021 03:08:51 GMT</pubDate>
    <dc:creator>venkatasri</dc:creator>
    <dc:date>2021-06-10T03:08:51Z</dc:date>
    <item>
      <title>Splunk cloud rest API call related security questions</title>
      <link>https://community.splunk.com/t5/Security/Splunk-cloud-rest-API-call-related-security-questions/m-p/553825#M12264</link>
      <description>&lt;P&gt;Dear All,&lt;/P&gt;&lt;P&gt;We are trying to build splunk cloud rest api call where we will be sending data from splunk cloud to another server via rest api call.&lt;/P&gt;&lt;P&gt;Since it is production data below are few points raised by security team and asked us to get that verified whether splunk supports these security noums or not.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;DIV&gt;&lt;P&gt;&lt;SPAN&gt;1. All the APIs must be served securely over HTTPS using TLS v1.2 with oauth 2.0 implementation.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;2. Any HTTP API requests must be rejected or redirected to HTTPS.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;3. The API token must be validated for signing, tampering and expiry before any details are extracted from the token.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;4. The API token expiry must be limited to 15 mins only.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;5. The IP whitelisting must be performed for all INTERNET facing API endpoints to reject any unauthorized requests. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;6. The API credentials must be set to expire and rotated at least annually.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;7. The API credentials must be stored encrypted in Key vault and access must be granted to application or user following principle of least privilege.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;8. The API credentials must not be hardcoded within the application source code, client-side scripts, or configuration files.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;9. The tokens or credentials must not be passed in the URL parameters.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;10. The API tokens must be scoped following the principle of least privilege and validated at method level.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;11. Enumerable ID values must not be used in API methods.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;12. Proper error or exception handling must be performed to return only generic error messages.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;13. API rate limiting must be performed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;14. Proper input and content validation must be performed at the APIs including length, datatype etc. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;15. In case of file uploads, file type, content type validation and scanning must be performed.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;16. Un wanted HTTP methods must be disabled.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;17. Log failed attempts, denied access, input validation failures, any failures in security policy checks must be logged.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;18. No sensitive data must be captured in the logs.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;19. The API logs must be ingested automatically into Genpact SIEM using standard integration mechanism for monitoring.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;20. APIs must implement strict authentication, security headers, redirects, CORS etc.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;21. All the API endpoints internally or externally exposed must undergo InfoSec design review and security testing before moving to production.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;can someone provide any details on them.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Regards,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Santosh&lt;/SPAN&gt;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Tue, 01 Jun 2021 10:06:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-cloud-rest-API-call-related-security-questions/m-p/553825#M12264</guid>
      <dc:creator>santosh121</dc:creator>
      <dc:date>2021-06-01T10:06:04Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk cloud rest API call related security questions</title>
      <link>https://community.splunk.com/t5/Security/Splunk-cloud-rest-API-call-related-security-questions/m-p/555213#M12285</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/234565"&gt;@santosh121&lt;/a&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;It's quite extensive list, some of them being directly supported and others need to be supported through other products example Load balancer front of Splunk API's. I would&amp;nbsp; recommend to connect with Splunk support for the correct guidance.&lt;/P&gt;&lt;P&gt;---&lt;/P&gt;&lt;P&gt;An upvote would be appreciated if it helps!&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jun 2021 03:08:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Splunk-cloud-rest-API-call-related-security-questions/m-p/555213#M12285</guid>
      <dc:creator>venkatasri</dc:creator>
      <dc:date>2021-06-10T03:08:51Z</dc:date>
    </item>
  </channel>
</rss>

