2017-11-17 12:56 AM
We would like to 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.
testsslserver <SP Card IP Address> 50000
TLSv1.0 TLSv1.1 TLSv1.2
Deflate compression: no
Supported cipher suites (ORDER IS NOT SIGNIFICANT):
e50304b62d8f97bff54a6a3dbac0eaf1cbdcf6b7: E="", OU="", O="", L="", S="", C="", CN=sp.spcs.server
Minimal encryption strength: strong encryption (96-bit or more)
Achievable encryption strength: strong encryption (96-bit or more)
BEAST status: vulnerable
CRIME status: protected
The NETAPP device itself has only TLS1.2 only enabled and has resticted ciphers allowed
<Cluster name>::*> security config show
Cluster Cluster Security
Interface FIPS Mode Supported Protocols Supported Ciphers Config Ready
--------- ---------- ----------------------- ----------------- ----------------
SSL false TLSv1.2 AES:!LOW:!MEDIUM: yes
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 convinced that this will make any difference whatsoever to the SP card security profile and even it is does it will require Node Reboots to complete the alteration. All of our netapp devices host CIFS shares so unfortunately as a consequence Node reboots will involve some service disruption.
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
2017-11-26 06:31 PM - edited 2017-11-26 06:33 PM
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.
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.