<?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: Service Processor Card Security - TLS in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/136270#M30008</link>
    <description>&lt;P&gt;I found the case you submitted and read through the notes and checked our developer documentation and can confirm - FIPS mode is the only way to modify ciphers on the SP. TLS is only used internally for redirecting node console to the SP, and other cipher types will be removed in a future version of SP firmware.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The SP is designed to be as simple as possible - it operates in a number of very finite states and has a very limited command set. There is an existing request for enhancement to enable changing ciphers without enabling FIPS mode that your request has been added to.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 27 Nov 2017 02:33:45 GMT</pubDate>
    <dc:creator>AlexDawson</dc:creator>
    <dc:date>2017-11-27T02:33:45Z</dc:date>
    <item>
      <title>Service Processor Card Security - TLS</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/136067#M29944</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We would like to&amp;nbsp;improve security on our SP Cards (Service Processor) by disabling TLS 1.0 and 1.1 and removing 3DES cipher. All Storage devices are on ONTAP9.1P1. Our current scenarion when running SSL checkers against the card IPs shows the following output.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;testsslserver &amp;lt;SP Card IP Address&amp;gt; 50000&lt;BR /&gt;Supported versions:&lt;BR /&gt;&amp;nbsp;TLSv1.0 TLSv1.1 TLSv1.2&lt;BR /&gt;Deflate compression: no&lt;BR /&gt;Supported cipher suites (ORDER IS NOT SIGNIFICANT):&lt;BR /&gt;&amp;nbsp; TLSv1.0&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_3DES_EDE_CBC_SHA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_AES_128_CBC_SHA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_AES_256_CBC_SHA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_CAMELLIA_128_CBC_SHA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_CAMELLIA_256_CBC_SHA&lt;BR /&gt;&amp;nbsp; (TLSv1.1: idem)&lt;BR /&gt;&amp;nbsp; TLSv1.2&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_3DES_EDE_CBC_SHA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_AES_128_CBC_SHA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_AES_256_CBC_SHA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_AES_128_CBC_SHA256&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_AES_256_CBC_SHA256&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_CAMELLIA_128_CBC_SHA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; RSA_WITH_CAMELLIA_256_CBC_SHA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TLS_RSA_WITH_AES_128_GCM_SHA256&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TLS_RSA_WITH_AES_256_GCM_SHA384&lt;BR /&gt;----------------------&lt;BR /&gt;Server certificate(s):&lt;BR /&gt;&amp;nbsp; e50304b62d8f97bff54a6a3dbac0eaf1cbdcf6b7: E="", OU="", O="", L="", S="", C="", CN=sp.spcs.server&lt;BR /&gt;----------------------&lt;BR /&gt;Minimal encryption strength:&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; strong encryption (96-bit or more)&lt;BR /&gt;Achievable encryption strength:&amp;nbsp; strong encryption (96-bit or more)&lt;BR /&gt;BEAST status: vulnerable&lt;BR /&gt;CRIME status: protected&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The NETAPP device itself has only TLS1.2 only enabled and has resticted ciphers allowed&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ie.&lt;/P&gt;&lt;P&gt;&amp;lt;Cluster name&amp;gt;::*&amp;gt; security config show&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Cluster&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Cluster Security&lt;BR /&gt;Interface FIPS Mode&amp;nbsp; Supported Protocols&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Supported Ciphers Config Ready&lt;BR /&gt;--------- ---------- ----------------------- ----------------- ----------------&lt;BR /&gt;SSL&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; false&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; TLSv1.2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; AES:!LOW:!MEDIUM: yes&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;nbsp;!aNULL:!EXP:&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; !eNULL:!3DES&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have asked NETAPP support for assistance with this. There recommendations have centered around altering the storage device Security Config by enabling FIPS. I am not&amp;nbsp; convinced that this will make any difference whatsoever&amp;nbsp;to the SP card security profile and even it is does it will require Node Reboots to complete the alteration.&amp;nbsp;All of our&amp;nbsp;netapp&amp;nbsp;devices&amp;nbsp;host&amp;nbsp;CIFS&amp;nbsp;shares&amp;nbsp;so unfortunately as a consequence&amp;nbsp;Node reboots will involve&amp;nbsp;some service disruption.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Has anyone else encountered this before and does anyone have any recommendations or knowledge relevant to SP Card security? I am surprised by the lack of available information&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thank you,&lt;/P&gt;&lt;P&gt;D&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 14:20:42 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/136067#M29944</guid>
      <dc:creator>diarmuidn</dc:creator>
      <dc:date>2025-06-04T14:20:42Z</dc:date>
    </item>
    <item>
      <title>Re: Service Processor Card Security - TLS</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/136270#M30008</link>
      <description>&lt;P&gt;I found the case you submitted and read through the notes and checked our developer documentation and can confirm - FIPS mode is the only way to modify ciphers on the SP. TLS is only used internally for redirecting node console to the SP, and other cipher types will be removed in a future version of SP firmware.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The SP is designed to be as simple as possible - it operates in a number of very finite states and has a very limited command set. There is an existing request for enhancement to enable changing ciphers without enabling FIPS mode that your request has been added to.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Nov 2017 02:33:45 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/136270#M30008</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2017-11-27T02:33:45Z</dc:date>
    </item>
    <item>
      <title>Re: Service Processor Card Security - TLS</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/140772#M31130</link>
      <description>&lt;P&gt;I am curious if this feature has been implemented. We just upgraded to ver&amp;nbsp;9.3P4 and we are getting dinged by our security department because the SPs are not TLS 1.2&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jun 2018 13:30:44 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/140772#M31130</guid>
      <dc:creator>dmcneil</dc:creator>
      <dc:date>2018-06-07T13:30:44Z</dc:date>
    </item>
    <item>
      <title>Re: Service Processor Card Security - TLS</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/140795#M31133</link>
      <description>&lt;P&gt;The current status is that there is no Ontap or SP firmware release avilable that will result in the SP card using TLS.1.2 only. The best you can achieve is TLS1.1 &amp;amp; 1.2. We asked NETAPP recently if a fix was pending and we are anticipating a reply shortly. I will post on here once I have an update.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jun 2018 07:53:08 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/140795#M31133</guid>
      <dc:creator>diarmuidn</dc:creator>
      <dc:date>2018-06-08T07:53:08Z</dc:date>
    </item>
    <item>
      <title>Re: Service Processor Card Security - TLS</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/142245#M31541</link>
      <description>Hi,
can anyone explain how to get rid of TLS1.0 in SP (which version of SP?) ?
The answer before was:
"The best you can achieve is TLS1.1 &amp;amp; 1.2"
But unfortunately no details how to do it ...

Many thanks in advance !</description>
      <pubDate>Wed, 22 Aug 2018 08:27:24 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/142245#M31541</guid>
      <dc:creator>ThirtySeven</dc:creator>
      <dc:date>2018-08-22T08:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: Service Processor Card Security - TLS</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/142376#M31573</link>
      <description>&lt;P&gt;Hi&amp;nbsp;&lt;a href="https://community.netapp.com/t5/user/viewprofilepage/user-id/27699"&gt;@ThirtySeven&lt;/a&gt;,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is detailed in this &lt;A href="http://docs.netapp.com/ontap-9/index.jsp?topic=%2Fcom.netapp.doc.dot-cm-nmg%2FGUID-A799B86D-B1B5-4AB6-B610-D0651D7C1548.html" target="_self"&gt;document&lt;/A&gt;, but basically&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;c94::&amp;gt; set -priv adv

Warning: These advanced commands are potentially dangerous; use them only when directed to do so by NetApp personnel.
Do you want to continue? {y|n}: y

c94::*&amp;gt; security config 
    modify ocsp   show   status 

c94::*&amp;gt; security config modify -interface SSL -is-fips-enabled true&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 28 Aug 2018 02:31:51 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/142376#M31573</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2018-08-28T02:31:51Z</dc:date>
    </item>
    <item>
      <title>Re: Service Processor Card Security - TLS</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/142568#M31631</link>
      <description>&lt;P&gt;Does this apply to the service processor or just ontap?&amp;nbsp; We're running firmware v3.3 on an 8040 and getting the same thing from our IRT.&lt;/P&gt;</description>
      <pubDate>Thu, 06 Sep 2018 20:33:50 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/142568#M31631</guid>
      <dc:creator>JBurelbach</dc:creator>
      <dc:date>2018-09-06T20:33:50Z</dc:date>
    </item>
    <item>
      <title>Re: Service Processor Card Security - TLS</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/142572#M31632</link>
      <description>&lt;P&gt;Both ONTAP and the SP&lt;/P&gt;</description>
      <pubDate>Thu, 06 Sep 2018 23:30:49 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Service-Processor-Card-Security-TLS/m-p/142572#M31632</guid>
      <dc:creator>AlexDawson</dc:creator>
      <dc:date>2018-09-06T23:30:49Z</dc:date>
    </item>
  </channel>
</rss>

