"Before upgrading to Guardium 12.x, take the following actions: Disable TLS 1.0 and TLS 1.1 in your environment. Guardium 12.0 requires TLS 1.2 or later, and any managed units or S-TAPs that do not support at least TLS 1.2 are disconnected after upgrade. From a central manager, use the API command … all=true to identify any connected components that do not support at least TLS 1.2. Upgrade those components to TLS 1.2 or later so they remain connected after upgrade."
The risk is loss of connectivity. A managed unit or agent that can speak only TLS 1.0 or 1.1 would be cut off from the upgraded Central Manager or collector. The pre-check finds those components while they are still reachable.
Compatible versions: Guardium 12.0 supports TLS 1.2 and TLS 1.3, where earlier releases supported 1.0, 1.1 and 1.2.
Mixed-version state: After the Central Manager is upgraded, managed units keep working at the old level, but you should not make configuration changes until everything is upgraded.
GIM certificates: After upgrading to 12.0 or later, custom SHA256 GIM certificates are required before you can deploy new SHA256-signed GIM bundles.
Order: Upgrade top-down, as in Question 1.
Why not the others: Opening a support case, disabling SCP and SFTP, or enabling Secure Boot is not an upgrade prerequisite.
Submit