<?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>question Navigator Hdfs  - audit in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Navigator-Hdfs-audit/m-p/64859#M74866</link>
    <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to audit these commands in Navigator or any other place ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Fs shell commands&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;copyFromLocal
copyToLocal
cp
MoveFromLocal
MoveToLocal &lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 23 Feb 2018 07:05:43 GMT</pubDate>
    <dc:creator>csguna</dc:creator>
    <dc:date>2018-02-23T07:05:43Z</dc:date>
    <item>
      <title>Navigator Hdfs  - audit</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Navigator-Hdfs-audit/m-p/64859#M74866</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to audit these commands in Navigator or any other place ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;Fs shell commands&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;copyFromLocal
copyToLocal
cp
MoveFromLocal
MoveToLocal &lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 23 Feb 2018 07:05:43 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Navigator-Hdfs-audit/m-p/64859#M74866</guid>
      <dc:creator>csguna</dc:creator>
      <dc:date>2018-02-23T07:05:43Z</dc:date>
    </item>
    <item>
      <title>Re: Navigator Hdfs  - audit</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Navigator-Hdfs-audit/m-p/64964#M74867</link>
      <description>&lt;P&gt;Hi csguna,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Navigator audit is auditing the Hadoop Master roles only, and the hdfs shell commands are working as a regular HDFS client from the NameNode's perspective.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;At the namenode side, where HDFS&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN class="il"&gt;audit&lt;/SPAN&gt;&lt;SPAN&gt;&amp;nbsp;logs are generated, is not possible to determine why a client would like to read a file. The only thing that the namenode knows &amp;amp; can log that a client/user would like to open&amp;amp;read a file, but we have no information about what the client will actually do with the data. The client could save the data to a local disk, send it to a network service, simply display the contents of the file, or do an ordinary ETL job and write the results back to HDFS, etc.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;That is why an "open" operation is logged for both 'hadoop fs -cat size.log' and 'hadoop fs -get size.log'.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Therefore with Navigator Audit, this is not currently possible, as the knowledge what the client will do with the data read from HDFS is missing.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Usually there are some ways on the OS level itself to audit what users/processes do (like the Linux audit framework), and that can be used to audit file access on the OS level.&amp;nbsp;It might be possible to combine audit data form the OS and Navigator to pinpoint such operations that you mentioned, but I do not know any automated way to do that.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 27 Feb 2018 15:08:49 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Navigator-Hdfs-audit/m-p/64964#M74867</guid>
      <dc:creator>zegab</dc:creator>
      <dc:date>2018-02-27T15:08:49Z</dc:date>
    </item>
  </channel>
</rss>

