<?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: Man in the Middle and  TLS in CISSP Study Group</title>
    <link>https://community.isc2.org/t5/CISSP-Study-Group/Man-in-the-Middle-and-TLS/m-p/63734#M970</link>
    <description>&lt;P&gt;It's still a "man-in-the-middle" attack, because none of the other answers fit.&amp;nbsp;&amp;nbsp;&lt;EM&gt;How&lt;/EM&gt; it happens all depends on the talents of the attacker.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.broadcom.com/doc/responsibly-intercepting-tls-and-the-impact-of-tls-1.3.en" target="_blank" rel="noopener"&gt;This Broadcom guide&lt;/A&gt; offers a brief suggestion on how such an attack could occur, for reference.&lt;/P&gt;</description>
    <pubDate>Thu, 19 Oct 2023 13:08:27 GMT</pubDate>
    <dc:creator>ericgeater</dc:creator>
    <dc:date>2023-10-19T13:08:27Z</dc:date>
    <item>
      <title>Man in the Middle and  TLS</title>
      <link>https://community.isc2.org/t5/CISSP-Study-Group/Man-in-the-Middle-and-TLS/m-p/63730#M969</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As per official guide correct answer for below question is C: "Man&amp;nbsp; in the middle". Can anyone explain how attcker will be to read TLS encrypted communication in this case?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Question : The following figure shows an example of an attack where Mal, the attacker, has redirected&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;traffic from a user’s system to their own, allowing them to read TLS encrypted traffic. Which&lt;/STRONG&gt;&lt;BR /&gt;&lt;STRONG&gt;of the following terms best describes this attack?&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Sundas_0-1697709048148.png" style="width: 400px;"&gt;&lt;img src="https://community.isc2.org/t5/image/serverpage/image-id/7846i8066457723AB90ED/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Sundas_0-1697709048148.png" alt="Sundas_0-1697709048148.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;A. A DNS hijacking attack&lt;BR /&gt;B. An ARP spoofing attack&lt;BR /&gt;C. A man-in-the-middle attack&lt;BR /&gt;D. A SQL injection attack&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 09:53:04 GMT</pubDate>
      <guid>https://community.isc2.org/t5/CISSP-Study-Group/Man-in-the-Middle-and-TLS/m-p/63730#M969</guid>
      <dc:creator>Sundas</dc:creator>
      <dc:date>2023-10-19T09:53:04Z</dc:date>
    </item>
    <item>
      <title>Re: Man in the Middle and  TLS</title>
      <link>https://community.isc2.org/t5/CISSP-Study-Group/Man-in-the-Middle-and-TLS/m-p/63734#M970</link>
      <description>&lt;P&gt;It's still a "man-in-the-middle" attack, because none of the other answers fit.&amp;nbsp;&amp;nbsp;&lt;EM&gt;How&lt;/EM&gt; it happens all depends on the talents of the attacker.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.broadcom.com/doc/responsibly-intercepting-tls-and-the-impact-of-tls-1.3.en" target="_blank" rel="noopener"&gt;This Broadcom guide&lt;/A&gt; offers a brief suggestion on how such an attack could occur, for reference.&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 13:08:27 GMT</pubDate>
      <guid>https://community.isc2.org/t5/CISSP-Study-Group/Man-in-the-Middle-and-TLS/m-p/63734#M970</guid>
      <dc:creator>ericgeater</dc:creator>
      <dc:date>2023-10-19T13:08:27Z</dc:date>
    </item>
    <item>
      <title>Re: Man in the Middle and  TLS</title>
      <link>https://community.isc2.org/t5/CISSP-Study-Group/Man-in-the-Middle-and-TLS/m-p/63737#M971</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.isc2.org/t5/user/viewprofilepage/user-id/62028885"&gt;@Sundas&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;Can anyone explain how attacker will be to read TLS encrypted communication in this case?&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;&lt;BR /&gt;MITM/AITM (Adversary in the middle) is a necessary, but not sufficient step. More components are necessary:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;The AITM could keep a copy of the encrypted communications until technology has evolved to break it.&lt;/LI&gt;&lt;LI&gt;The AITM could steal the right-side TLS private-key and use it to act as a server on the left side, proxying the communications as a client on the right side.&lt;/LI&gt;&lt;LI&gt;&amp;nbsp;The MITM inserts their own CA into the left-hand side so they can issue certificates and proxy as above.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;When done by (questionably) good actors, such as the corporate firewall, this is called "SSL Inspection", which is a good term to Google for a deeper explanation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Many technologies (pinning, stapling, CAA) are being developed to address this risk, with varying success.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Oct 2023 13:40:42 GMT</pubDate>
      <guid>https://community.isc2.org/t5/CISSP-Study-Group/Man-in-the-Middle-and-TLS/m-p/63737#M971</guid>
      <dc:creator>denbesten</dc:creator>
      <dc:date>2023-10-19T13:40:42Z</dc:date>
    </item>
  </channel>
</rss>

