2.5 Ensure Non-Default, Unique Cryptographic Material is in Use

Information

The cryptographic material used by MySQL, such as digital certificates and encryption keys, should be used only for MySQL and only for one instance. Default cryptographic material should not be used since it is not unique to the instance.

Rationale:

If a cryptographic material is used on multiple MySQL instances and/or systems then a compromise of one may lead to the compromise of the network traffic of all servers which use the same cryptographic material. If an attacker gains access to shared cryptographic material, including default material, the attacker can reuse that material to impersonate the MySQL server or otherwise compromise its operations.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Generate new certificates, keys, and other cryptographic material as needed for each affected MySQL instance.

See Also

https://workbench.cisecurity.org/files/3844

Item Details

Category: SYSTEM AND COMMUNICATIONS PROTECTION

References: 800-53|SC-13

Plugin: Windows

Control ID: 7501a20b20a8645a12c54ad5033b2749653068bebf0022bacad5c0b97fed6c3a