| Summary: | RSA has qualified the PowerVault self-encrypting hard drive feature on the RSA SecurID Hardware Appliance 350.
The RSA Authentication Manager 8.4 Patch 8 Readme describes how to enable the self-encrypting hard drive, which is present on all RSA SecurID Hardware Appliance 350 sold since the Model 350 was first announced. This feature helps make the Model 350 even more secure by encrypting your data with a passphrase, with minimal impact on performance. You can enable this feature on any Model 350 hardware appliance, including ones you already own.
This feature is not included on other RSA SecurID Hardware Appliance models.
Note: You must back up or record your passphrase. RSA cannot recover it, and you cannot reverse encryption without resetting your hard drive. |
| Platforms: | RSA SecurID Hardware Appliance 350 |
| Details: | For more information, see "Encrypt the RSA SecurID Hardware Appliance 350 Hard Drive" in the RSA Authentication Manager 8.4 Patch 8 Readme. |
| For additional documentation, downloads and more, visit the RSA SecurID Access page on RSA Link. | |
| EOPS Policy: | RSA has a defined End of Primary Support policy associated with all major versions. Please refer to the Product Version Life Cycle for additional details. |
Related Articles
SAML 2.0 Requirements for Service Providers - Metadata 10Number of Views You uploaded an invalid file error during Quick Setup of the RSA SecurID Appliance 8.x 329Number of Views DSA-2020-098: RSA Identity Governance and Lifecycle Security Update for Dell EMC iDRAC Vulnerability 7Number of Views RSA SecurID Appliance 3.0 Model 250 - How to configure the DRAC 528Number of Views An Invalid Content Type error occurs when uploading images in RSA Identity Governance & Lifecycle 48Number of Views
Trending Articles
Authentication Manager Supported Hardware and Upgrade Paths RSA Authentication Manager Upgrade Process Artifacts to gather in RSA Identity Governance & Lifecycle How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Authentication Manager 'Principal Does Not Possess Authenticator' Error for Users with Multiple IDs