For strict TLS compliance, security teams often require the server to dictate the order of preferred cipher suites during the TLS handshake (similar to the Nginx directive ssl_prefer_server_ciphers on;).
Modifying the nginx.conf file directly via the root shell is strictly unsupported on the NSX Manager. This article explains how to enforce cipher priority using the officially supported REST API.
VMware NSX
VMware has always tried to follow industry standards when it comes to TLS and encryption ciphers for security purposes.
The NSX Manager determines cipher priority strictly based on the top-down order of the ciphers provided in the API configuration array. To change the priority, you must retrieve the configuration, rearrange the array, and push it back.
Step 1: Retrieve the current API service configuration
Step 2: Rearrange the JSON array
Step 3: Push the new configuration
Example snippet of a prioritized array:
"cipher_suites": [
{
"name": "TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384",
"enabled": true
},
{
"name": "TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256",
"enabled": true
}
]
Reference KB : https://knowledge.broadcom.com/external/article/319144/disableenable-nsxt-manager-ciphers-or-tl.html