<?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: CISA releases Mobile Communications Best Practices Guide in Threats</title>
    <link>https://community.isc2.org/t5/Threats/CISA-releases-Mobile-Communications-Best-Practices-Guide/m-p/75754#M1448</link>
    <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;SPAN&gt;The write-up says these practices should be applied to "targeted users", but this list is a good idea for cautious users to consider.&lt;BR /&gt;&lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Completely agree.&amp;nbsp; We protect all company accounts to a particular baseline using the theory of defense-in-depth.&amp;nbsp; Most everything on this list belongs in the baseline standard (#7 being the primary outlier -- we only require everything be "eligible for support" throughout the duty cycle).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;SPAN&gt;consider avoiding personal VPN services &lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;As I see it, &lt;STRONG&gt;availability&lt;/STRONG&gt; is always harmed.&amp;nbsp; &amp;nbsp;Hair pinning and concentrating traffic at a distant location increases latency and risks throttling, while adding additional failure points (the VPN supplier and their ISP) without removing any (your ISP is still in the mix).&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Integrity&lt;/STRONG&gt;&amp;nbsp;comes into question because they can adversary-in-the-middle you, since they inline your traffic and by having privileged software on your machine, they can inject their own root certificate, DNS servers, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Confidentiality&lt;/STRONG&gt; might be improved, but only if you trust them and their ISP more than your own ISP.&amp;nbsp; Even without a 'privacy VPN', the trend towards "encrypt everything" means that my ISP knows I used Google, but not what search terms I used.&lt;/P&gt;</description>
    <pubDate>Fri, 20 Dec 2024 14:50:13 GMT</pubDate>
    <dc:creator>denbesten</dc:creator>
    <dc:date>2024-12-20T14:50:13Z</dc:date>
    <item>
      <title>CISA releases Mobile Communications Best Practices Guide</title>
      <link>https://community.isc2.org/t5/Threats/CISA-releases-Mobile-Communications-Best-Practices-Guide/m-p/75747#M1447</link>
      <description>&lt;P&gt;&lt;SPAN&gt;CISA has released their Mobile Communication Best Practices Guide. The write-up says these practices should be applied to "targeted users", but this list is a good idea for cautious users to consider.&lt;BR /&gt;&lt;BR /&gt;Number eight on the list was a surprise, but after chatting with a colleague it makes sense to consider avoiding personal VPN services that advertise -- and doing business with any VPN service with whom you're unwilling to read the terms and conditions&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://www.cisa.gov/resources-tools/resources/mobile-communications-best-practice-guidance" target="_blank"&gt;https://www.cisa.gov/resources-tools/resources/mobile-communications-best-practice-guidance&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 19 Dec 2024 22:35:22 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/CISA-releases-Mobile-Communications-Best-Practices-Guide/m-p/75747#M1447</guid>
      <dc:creator>ericgeater</dc:creator>
      <dc:date>2024-12-19T22:35:22Z</dc:date>
    </item>
    <item>
      <title>Re: CISA releases Mobile Communications Best Practices Guide</title>
      <link>https://community.isc2.org/t5/Threats/CISA-releases-Mobile-Communications-Best-Practices-Guide/m-p/75754#M1448</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;SPAN&gt;The write-up says these practices should be applied to "targeted users", but this list is a good idea for cautious users to consider.&lt;BR /&gt;&lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;Completely agree.&amp;nbsp; We protect all company accounts to a particular baseline using the theory of defense-in-depth.&amp;nbsp; Most everything on this list belongs in the baseline standard (#7 being the primary outlier -- we only require everything be "eligible for support" throughout the duty cycle).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;SPAN&gt;consider avoiding personal VPN services &lt;/SPAN&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;As I see it, &lt;STRONG&gt;availability&lt;/STRONG&gt; is always harmed.&amp;nbsp; &amp;nbsp;Hair pinning and concentrating traffic at a distant location increases latency and risks throttling, while adding additional failure points (the VPN supplier and their ISP) without removing any (your ISP is still in the mix).&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Integrity&lt;/STRONG&gt;&amp;nbsp;comes into question because they can adversary-in-the-middle you, since they inline your traffic and by having privileged software on your machine, they can inject their own root certificate, DNS servers, etc.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Confidentiality&lt;/STRONG&gt; might be improved, but only if you trust them and their ISP more than your own ISP.&amp;nbsp; Even without a 'privacy VPN', the trend towards "encrypt everything" means that my ISP knows I used Google, but not what search terms I used.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 14:50:13 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/CISA-releases-Mobile-Communications-Best-Practices-Guide/m-p/75754#M1448</guid>
      <dc:creator>denbesten</dc:creator>
      <dc:date>2024-12-20T14:50:13Z</dc:date>
    </item>
  </channel>
</rss>

