I just need to know which ones (ciphers) are currently used by the on-premise Anypoint RTF to talk to the cloud so I know if I need to get an exemption or not
In some scenarios, there are compliances requiring a specific enhanced TLS/SSL cipher set for out facing communication. For example, the NZISM (New Zealand Information Security Manual, https://www.nzism.gcsb.govt.nz/ism-document). We need to know the ciphers supported on a TLS/SSL endpoint.
> nmap -sV --script ssl-enum-ciphers -p <port number> <hostname/IP>Similarly, the following command can be used to scan the Algorithms.
> nmap -sV --script ssh2-enum-algos -p <port number> <hostname/IP>
> nmap -sV --script ssl-enum-ciphers -p 443 transport-layer.prod.cloudhub.io Starting Nmap 7.91 ( https://nmap.org ) at 2020-12-22 12:20 AEDT Nmap scan report for transport-layer.prod.cloudhub.io (34.206.252.3) Host is up (0.34s latency). Other addresses for transport-layer.prod.cloudhub.io (not scanned): 52.0.44.181 34.233.101.109 rDNS record for 34.206.252.3: ec2-34-206-252-3.compute-1.amazonaws.com PORT STATE SERVICE VERSION 443/tcp open ssl/https? | ssl-enum-ciphers: | TLSv1.2: | ciphers: | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA (secp256r1) - A | TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 (secp256r1) - A | TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (secp256r1) - A | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA (secp256r1) - A | TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384 (secp256r1) - A | TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (secp256r1) - A | TLS_RSA_WITH_AES_128_CBC_SHA (rsa 4096) - A | TLS_RSA_WITH_AES_128_CBC_SHA256 (rsa 4096) - A | TLS_RSA_WITH_AES_128_GCM_SHA256 (rsa 4096) - A | TLS_RSA_WITH_AES_256_CBC_SHA (rsa 4096) - A | TLS_RSA_WITH_AES_256_CBC_SHA256 (rsa 4096) - A | TLS_RSA_WITH_AES_256_GCM_SHA384 (rsa 4096) - A | compressors: | NULL | cipher preference: client | warnings: | Key exchange (secp256r1) of lower strength than certificate key |_ least strength: A
An alternative method to do this can be found How to Get All Ciphers Supported From An Endpoint
001115821

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.