<?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 How to restrict external access to embedded report in Other Usage</title>
    <link>https://community.splunk.com/t5/Other-Usage/How-to-restrict-external-access-to-embedded-report/m-p/636139#M91</link>
    <description>&lt;P&gt;We have a requirement to share a Splunk report externally and I`m aware we can achieve this by using iframes to embed the report.&lt;/P&gt;&lt;P&gt;My question is who can access the iframe - assuming it`s everyone who has a copy of the iframe/URL - and if there`s a way to restrict access to certain users only ? Can the restriction be applied within Splunk, or does it need to be applied within the external web app that we`re sharing with ?&lt;/P&gt;</description>
    <pubDate>Mon, 27 Mar 2023 11:46:24 GMT</pubDate>
    <dc:creator>tomapatan</dc:creator>
    <dc:date>2023-03-27T11:46:24Z</dc:date>
    <item>
      <title>How to restrict external access to embedded report</title>
      <link>https://community.splunk.com/t5/Other-Usage/How-to-restrict-external-access-to-embedded-report/m-p/636139#M91</link>
      <description>&lt;P&gt;We have a requirement to share a Splunk report externally and I`m aware we can achieve this by using iframes to embed the report.&lt;/P&gt;&lt;P&gt;My question is who can access the iframe - assuming it`s everyone who has a copy of the iframe/URL - and if there`s a way to restrict access to certain users only ? Can the restriction be applied within Splunk, or does it need to be applied within the external web app that we`re sharing with ?&lt;/P&gt;</description>
      <pubDate>Mon, 27 Mar 2023 11:46:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Other-Usage/How-to-restrict-external-access-to-embedded-report/m-p/636139#M91</guid>
      <dc:creator>tomapatan</dc:creator>
      <dc:date>2023-03-27T11:46:24Z</dc:date>
    </item>
    <item>
      <title>Re: How to restrict external access to embedded report</title>
      <link>https://community.splunk.com/t5/Other-Usage/How-to-restrict-external-access-to-embedded-report/m-p/636239#M92</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/249836"&gt;@tomapatan&lt;/a&gt;&amp;nbsp;&lt;BR /&gt;&lt;BR /&gt;Yes, I believe embedded reports are readable by anyone with access to the iframe/URL.&amp;nbsp; Splunk does not have a way to be aware of who is accessing it, so this would need to be applied at the Web front end.&lt;BR /&gt;&lt;BR /&gt;Having said that, depending on needs, the content of a report is usually generalised/summarised data, with the report creator having control over what is presented or more importantly, not presented or obfuscated.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Mar 2023 01:15:47 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Other-Usage/How-to-restrict-external-access-to-embedded-report/m-p/636239#M92</guid>
      <dc:creator>yeahnah</dc:creator>
      <dc:date>2023-03-28T01:15:47Z</dc:date>
    </item>
  </channel>
</rss>

