<?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: Detect Rootkit using Comparison of network packets to logged pc communications. in Tech Talk</title>
    <link>https://community.isc2.org/t5/Tech-Talk/Detect-Rootkit-using-Comparison-of-network-packets-to-logged-pc/m-p/36415#M2776</link>
    <description>&lt;P&gt;I don't seem to able to follow your idea...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First, you can assign multiple IP addresses to a single network card, many operating systems just don't allow it though a GUI interface. It's not something that is commonly done so I would guess they limited to just the one to simplify things for the average user.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you monitor the packets coming off of a machine anything going over HTTPS would not be readable by Wireshark, I believe. I think normally the detection happens based on the IP address the packs are going to and at times is normally unused port are suddenly used.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have an interest in gap between when a hack happens and when it is successfully detected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;John-&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 13 Jun 2020 15:07:46 GMT</pubDate>
    <dc:creator>JKWiniger</dc:creator>
    <dc:date>2020-06-13T15:07:46Z</dc:date>
    <item>
      <title>Detect Rootkit using Comparison of network packets to logged pc communications.</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Detect-Rootkit-using-Comparison-of-network-packets-to-logged-pc/m-p/36412#M2774</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have an idea for a tool to detect rootkits. Might not be possible.Might have already been done.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;1.Record packets sent from the suspect computer using wireshark.(All NICs...as I understand it there can be only one connection(IP address) to the network per Network interface card and this cannot be changed by a rootkit)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;2.Log all packets sent by the suspect computer using the computer's logging utilities.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3.Compare the two records of network communication to see if the computer is hiding its activities.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I might not know the technical aspects of this so if this is trivial please let me know politely and I'll leave it be.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jun 2020 13:25:29 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Detect-Rootkit-using-Comparison-of-network-packets-to-logged-pc/m-p/36412#M2774</guid>
      <dc:creator>Marcipicus</dc:creator>
      <dc:date>2020-06-13T13:25:29Z</dc:date>
    </item>
    <item>
      <title>Re: Detect Rootkit using Comparison of network packets to logged pc communications.</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Detect-Rootkit-using-Comparison-of-network-packets-to-logged-pc/m-p/36414#M2775</link>
      <description>&lt;P&gt;"Network Intrusion Detection System" and "Network Intrusion Prevention System" are the names for products that do this.&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The biggest in difficulty with monitoring for malware is that you are searching for a very small needle in a very large haystack and the bad actors work very hard to make their needles look like straw.&amp;nbsp; As a result, it works best to rely upon commercial IDS/IPS providers that specialize in keeping their "signatures" up-to-date.&amp;nbsp; Anymore, these are generally inbuilt into enterprise-grade network firewalls.&amp;nbsp; It is also why you should rely on well-reputed EPP (Endpoint Protection Platform) and EDR (Endpoint Detection and Response) platforms rather than trying to roll-your-own.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Gartner does have market analysis and magic quadrants for most all the technologies mentioned above.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jun 2020 15:02:36 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Detect-Rootkit-using-Comparison-of-network-packets-to-logged-pc/m-p/36414#M2775</guid>
      <dc:creator>denbesten</dc:creator>
      <dc:date>2020-06-13T15:02:36Z</dc:date>
    </item>
    <item>
      <title>Re: Detect Rootkit using Comparison of network packets to logged pc communications.</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Detect-Rootkit-using-Comparison-of-network-packets-to-logged-pc/m-p/36415#M2776</link>
      <description>&lt;P&gt;I don't seem to able to follow your idea...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;First, you can assign multiple IP addresses to a single network card, many operating systems just don't allow it though a GUI interface. It's not something that is commonly done so I would guess they limited to just the one to simplify things for the average user.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;If you monitor the packets coming off of a machine anything going over HTTPS would not be readable by Wireshark, I believe. I think normally the detection happens based on the IP address the packs are going to and at times is normally unused port are suddenly used.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have an interest in gap between when a hack happens and when it is successfully detected.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;John-&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jun 2020 15:07:46 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Detect-Rootkit-using-Comparison-of-network-packets-to-logged-pc/m-p/36415#M2776</guid>
      <dc:creator>JKWiniger</dc:creator>
      <dc:date>2020-06-13T15:07:46Z</dc:date>
    </item>
    <item>
      <title>Re: Detect Rootkit using Comparison of network packets to logged pc communications.</title>
      <link>https://community.isc2.org/t5/Tech-Talk/Detect-Rootkit-using-Comparison-of-network-packets-to-logged-pc/m-p/36423#M2778</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/1351384063"&gt;@Marcipicus&lt;/a&gt;,&amp;nbsp;what would be the benefit of such an approach? There are already EPS / EDR solutions for end-points &amp;amp; IDS / IDP solutions for network traffic --- these may either be signature-based / behavior-based, or use a combination of the two.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Should malicious activity be detected by an EPS / EDR, I could suspect that the end-point is compromised; should the EPS / EDR detect nothing, but traffic anomalies get picked up by the network IDS / IPS, I can also suspect this if it's traced back to an end-point.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;How is what you suggested offering an advantage over this?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 13 Jun 2020 23:45:18 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Tech-Talk/Detect-Rootkit-using-Comparison-of-network-packets-to-logged-pc/m-p/36423#M2778</guid>
      <dc:creator>Shannon</dc:creator>
      <dc:date>2020-06-13T23:45:18Z</dc:date>
    </item>
  </channel>
</rss>

