<?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 NSA Releases Guidance on Eliminating Obsolete TLS in Threats</title>
    <link>https://community.isc2.org/t5/Threats/NSA-Releases-Guidance-on-Eliminating-Obsolete-TLS/m-p/42178#M223</link>
    <description>&lt;P&gt;&lt;SPAN&gt;The National Security Agency (NSA) has released a Cybersecurity Information (CSI) sheet on eliminating obsolete &lt;A href="https://media.defense.gov/2021/Jan/05/2002560140/-1/-1/0/ELIMINATING_OBSOLETE_TLS_UOO197443-20.PDF" target="_blank" rel="noopener"&gt;Transport Layer Security (TLS) configurations&lt;/A&gt;. Although the guidance is not exactly new, the information sheet identifies strategies to detect obsolete cipher suites and key exchange mechanisms, discusses recommended TLS configurations, and provides remediation recommendations for organizations using obsolete TLS configurations. What I do like about the guidance is that they offer advice on traffic blocking.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 06 Jan 2021 02:46:53 GMT</pubDate>
    <dc:creator>AppDefects</dc:creator>
    <dc:date>2021-01-06T02:46:53Z</dc:date>
    <item>
      <title>NSA Releases Guidance on Eliminating Obsolete TLS</title>
      <link>https://community.isc2.org/t5/Threats/NSA-Releases-Guidance-on-Eliminating-Obsolete-TLS/m-p/42178#M223</link>
      <description>&lt;P&gt;&lt;SPAN&gt;The National Security Agency (NSA) has released a Cybersecurity Information (CSI) sheet on eliminating obsolete &lt;A href="https://media.defense.gov/2021/Jan/05/2002560140/-1/-1/0/ELIMINATING_OBSOLETE_TLS_UOO197443-20.PDF" target="_blank" rel="noopener"&gt;Transport Layer Security (TLS) configurations&lt;/A&gt;. Although the guidance is not exactly new, the information sheet identifies strategies to detect obsolete cipher suites and key exchange mechanisms, discusses recommended TLS configurations, and provides remediation recommendations for organizations using obsolete TLS configurations. What I do like about the guidance is that they offer advice on traffic blocking.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jan 2021 02:46:53 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/NSA-Releases-Guidance-on-Eliminating-Obsolete-TLS/m-p/42178#M223</guid>
      <dc:creator>AppDefects</dc:creator>
      <dc:date>2021-01-06T02:46:53Z</dc:date>
    </item>
    <item>
      <title>Re: NSA Releases Guidance on Eliminating Obsolete TLS</title>
      <link>https://community.isc2.org/t5/Threats/NSA-Releases-Guidance-on-Eliminating-Obsolete-TLS/m-p/42215#M225</link>
      <description>&lt;P&gt;I saw this today as it popped up on the Reddit sysadmin forum. I'll agree that it's one of the better government documents I've seen on the topic. More straightforward with what you should do and lacks the cover pages and other language not needed to mitigate, much more straightforward. Also appreciate the list to many scanners on the github link. There were a few in there I hadn't used and like the results page more than the ones I had been using.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;For those not familiar, the best way to implement, in Windows IIS servers at least, is to utilize the &lt;A href="https://www.nartac.com/Products/IISCrypto" target="_blank" rel="noopener"&gt;IIS Crypto&lt;/A&gt; utility. That will save you from modifying multiple registry keys and makes backing up the original keys easy.&lt;/P&gt;</description>
      <pubDate>Wed, 06 Jan 2021 18:30:16 GMT</pubDate>
      <guid>https://community.isc2.org/t5/Threats/NSA-Releases-Guidance-on-Eliminating-Obsolete-TLS/m-p/42215#M225</guid>
      <dc:creator>ITProJeff</dc:creator>
      <dc:date>2021-01-06T18:30:16Z</dc:date>
    </item>
  </channel>
</rss>

