<?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: Most critical files that must be monitoring on Linux in terms of security in Deployment Architecture</title>
    <link>https://community.splunk.com/t5/Deployment-Architecture/Most-critical-files-that-must-be-monitoring-on-Linux-in-terms-of/m-p/360580#M13309</link>
    <description>&lt;P&gt;hey in addition to that :&lt;/P&gt;

&lt;P&gt;Linux Networks. The most important files to monitor (or exclude)&lt;BR /&gt;
Linux. Files to INCLUDE in FIM:&lt;/P&gt;

&lt;P&gt;Root folder:&lt;BR /&gt;
– monitor the permissions&lt;BR /&gt;
Monitor the permissions, the access/modification time and the content of all files (except logs and cache files) in the following folders:&lt;BR /&gt;
– /bin&lt;BR /&gt;
– /sbin&lt;BR /&gt;
– /usr/sbin&lt;BR /&gt;
– /usr/bin.&lt;BR /&gt;
– /usr/local/bin&lt;BR /&gt;
– /usr/local/sbin&lt;BR /&gt;
– /opt/bin&lt;BR /&gt;
– /opt/sbin&lt;BR /&gt;
– /lib&lt;BR /&gt;
– /usr/lib&lt;BR /&gt;
– /usr/local/lib&lt;BR /&gt;
– /lib64&lt;BR /&gt;
– /usr/lib64&lt;BR /&gt;
– /root, /etc&lt;BR /&gt;
Some Linux attacks try to gain privileges by modifying the configuration of your grub file, therefore it must be properly monitored /boot/grub/grub.conf&lt;BR /&gt;
 &lt;A href="https://outpost24.com/blog/windows-linux-vulnerable-files"&gt;https://outpost24.com/blog/windows-linux-vulnerable-files&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Also, there is a good blog on Critical Linux Log Files You Must be Monitoring&lt;BR /&gt;
&lt;A href="https://www.eurovps.com/blog/important-linux-log-files-you-must-be-monitoring/"&gt;https://www.eurovps.com/blog/important-linux-log-files-you-must-be-monitoring/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;let me know if this helps!&lt;/P&gt;</description>
    <pubDate>Fri, 16 Mar 2018 08:10:09 GMT</pubDate>
    <dc:creator>mayurr98</dc:creator>
    <dc:date>2018-03-16T08:10:09Z</dc:date>
    <item>
      <title>Most critical files that must be monitoring on Linux in terms of security</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Most-critical-files-that-must-be-monitoring-on-Linux-in-terms-of/m-p/360579#M13308</link>
      <description>&lt;P&gt;Hi.&lt;BR /&gt;
I mean any critical points of Linux, any files, or directory that must be monitoring to detect any suspicious activity.&lt;/P&gt;

&lt;P&gt;For example:&lt;BR /&gt;
&lt;STRONG&gt;/tmp&lt;/STRONG&gt;&lt;BR /&gt;
because many exploits in the Unix world rely on creating temporary files in the /tmp standard folder which are not always deleted after the system hack&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;/etc/passwd&lt;/STRONG&gt; or /etc/shadow&lt;BR /&gt;
because, sometimes hacker attacks may add a new user in /etc/passwd which can be remotely logged in a later date.&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;/etc/services&lt;/STRONG&gt;&lt;BR /&gt;
Suspicious services added to /etc/services. Opening a backdoor in a Unix system is sometimes a matter of adding two text lines&lt;/P&gt;

&lt;P&gt;&lt;STRONG&gt;crontab&lt;/STRONG&gt; or &lt;STRONG&gt;/etc/init.d&lt;/STRONG&gt; &lt;BR /&gt;
It's good to detect any persistence&lt;/P&gt;

&lt;P&gt;If it has SSH running, then I would be monitoring /var/log/secure (or /var/log/auth.log) and alerting on brute force events. Or also have alerting on certain firewall logs. Example, when heartbleed came out, after patching I would set up log monitors for addresses attempting to exploit it.&lt;/P&gt;

&lt;P&gt;So, what about else? Of course I missed many and would be happy if you helped &lt;BR /&gt;
If you will share any blogs, article, etc, will be cool.&lt;/P&gt;</description>
      <pubDate>Thu, 15 Mar 2018 17:37:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Most-critical-files-that-must-be-monitoring-on-Linux-in-terms-of/m-p/360579#M13308</guid>
      <dc:creator>test_qweqwe</dc:creator>
      <dc:date>2018-03-15T17:37:38Z</dc:date>
    </item>
    <item>
      <title>Re: Most critical files that must be monitoring on Linux in terms of security</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Most-critical-files-that-must-be-monitoring-on-Linux-in-terms-of/m-p/360580#M13309</link>
      <description>&lt;P&gt;hey in addition to that :&lt;/P&gt;

&lt;P&gt;Linux Networks. The most important files to monitor (or exclude)&lt;BR /&gt;
Linux. Files to INCLUDE in FIM:&lt;/P&gt;

&lt;P&gt;Root folder:&lt;BR /&gt;
– monitor the permissions&lt;BR /&gt;
Monitor the permissions, the access/modification time and the content of all files (except logs and cache files) in the following folders:&lt;BR /&gt;
– /bin&lt;BR /&gt;
– /sbin&lt;BR /&gt;
– /usr/sbin&lt;BR /&gt;
– /usr/bin.&lt;BR /&gt;
– /usr/local/bin&lt;BR /&gt;
– /usr/local/sbin&lt;BR /&gt;
– /opt/bin&lt;BR /&gt;
– /opt/sbin&lt;BR /&gt;
– /lib&lt;BR /&gt;
– /usr/lib&lt;BR /&gt;
– /usr/local/lib&lt;BR /&gt;
– /lib64&lt;BR /&gt;
– /usr/lib64&lt;BR /&gt;
– /root, /etc&lt;BR /&gt;
Some Linux attacks try to gain privileges by modifying the configuration of your grub file, therefore it must be properly monitored /boot/grub/grub.conf&lt;BR /&gt;
 &lt;A href="https://outpost24.com/blog/windows-linux-vulnerable-files"&gt;https://outpost24.com/blog/windows-linux-vulnerable-files&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Also, there is a good blog on Critical Linux Log Files You Must be Monitoring&lt;BR /&gt;
&lt;A href="https://www.eurovps.com/blog/important-linux-log-files-you-must-be-monitoring/"&gt;https://www.eurovps.com/blog/important-linux-log-files-you-must-be-monitoring/&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;let me know if this helps!&lt;/P&gt;</description>
      <pubDate>Fri, 16 Mar 2018 08:10:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Most-critical-files-that-must-be-monitoring-on-Linux-in-terms-of/m-p/360580#M13309</guid>
      <dc:creator>mayurr98</dc:creator>
      <dc:date>2018-03-16T08:10:09Z</dc:date>
    </item>
    <item>
      <title>Re: Most critical files that must be monitoring on Linux in terms of security</title>
      <link>https://community.splunk.com/t5/Deployment-Architecture/Most-critical-files-that-must-be-monitoring-on-Linux-in-terms-of/m-p/360581#M13310</link>
      <description>&lt;P&gt;Hello. &lt;BR /&gt;
I already got acquainted with these links, but thank for response! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;BR /&gt;
To be trust, my question is very blurry and it's hard to answer. Security forumes not helped me.&lt;/P&gt;</description>
      <pubDate>Fri, 16 Mar 2018 14:44:02 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Deployment-Architecture/Most-critical-files-that-must-be-monitoring-on-Linux-in-terms-of/m-p/360581#M13310</guid>
      <dc:creator>test_qweqwe</dc:creator>
      <dc:date>2018-03-16T14:44:02Z</dc:date>
    </item>
  </channel>
</rss>

