- Notes, cautions, and warnings
- Preface
- Introduction
- Access Control
- Access control settings
- Security for management access
- Authentication
- Authorization
- Component access controls
- Data security settings
- Password policy
- Physical security controls
- Login banner and message of the day
- Logging
- Communication Security
- Communication security settings
- Port usage
- Ports used by Unisphere components on VNX for block
- How VNX for file works on the network
- Network encryption
- Management support for TLS communications on VNX2 systems
- SSL certificates
- Planning considerations for Public Key Infrastructure on VNX for file
- IP packet reflect on VNX for file systems
- Effect of filtering management network
- vSphere Storage API for Storage Awareness (VASA) support
- Special configurations
- Secure Remote Procedure Call
- Other security considerations
- Data Security Settings
- Data at Rest Encryption overview
- Data at Rest Encryption feature activation
- Encryption status
- Backup keystore file
- Data in place upgrade
- Hot spare operations
- Adding a disk drive to a VNX with encryption activated
- Removing a disk drive from a VNX with encryption enabled
- Replacing a chassis and SPs from a VNX with encryption enabled
- Security Maintenance
- Advanced Management Capabilities
- Secure deployment and usage settings
- TLS cipher suites
- LDAP-based directory server configuration
- VNX for file CLI role-based access
- VNX for file CLI security configuration operations
- Configuring password policy
- Configuring session timeout
- Protect session tokens
- Configuring network encryption and authentication using the SSL protocol
- Configuring PKI
- Creating the certificate provided by the persona
- Using the Control Station as the CA
- Obtaining CA certificates
- Generate a key set and certificate request
- Send the certificate request to the CA
- Import a CA-signed certificate
- List the available CA certificates
- Acquire a CA certificate
- Import a CA certificate
- Generate a new Control Station CA certificate
- Display the certificate
- Distribute the Control Station CA certificate
- Request and Install Customer-Supplied Certificates for Control Station
- Managing PKI
- Customize a login banner
- Create a MOTD
- Restrict anonymous root login
- Locking accounts after a specific number of failed logins
- VNX for block SSL certificate import
EMC® VNX® Series Security Configuration Guide for VNX
Encryption status
The following D@RE feature status can be viewed either through Unisphere or a VNX for block CLI command:
- Encryption Mode: type of encryption in use; for example, Controller-Based Encryption
- Encryption Status: based on the actual encryption status:
- Not started
- In Process
- Encrypted
- Scrubbing
- Encryption Percentage: encryption percentage of the overall storage system
To view the status of the D@RE feature in Unisphere, select System and, from the task list under System Management, select System Properties. The status of the encryption appears on the Encryption tab in the Storage System Properties view.
NOTE:As an alternative, use the VNX for block CLI command
securedata -feature -info to view the feature status. Also, use the
securedata -backupkeys -status CLI command to view the status of the keystore and to determine whether any user operations are required. See the
VNX Series Command Line Interface Reference for Block for detailed information about these CLI commands.
After enabling encryption on the system, you may notice that the encryption percentage remains at a certain level and does not increase. Several conditions may cause encryption to halt:
- Faulted disk
- Disk zeroing in progress
- Disk rebuild in progress
- Disk verify in progress
- Cache disabled
If this occurs, check the system logs to determine the cause. If corrective action is required, correct the condition. Encryption should complete after the correction has taken effect or the operation in progress completes.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\