Veritas Velocity™ User's Guide
- Getting to know Velocity
- Setting up Velocity
- How to set up the Velocity Storage Server
- How to set up the Velocity Client
- Setting up the Velocity on-premises management server
- Upgrading Velocity
- Velocity Storage Server
- Users and roles
- Oracle database ingestion using Velocity
- How to use copy preparation to mask or sanitize sensitive data
- Oracle database ingestion using NetBackup CoPilot
- Microsoft SQL Server database ingestion using Velocity
- Database sources and copies
- About scheduling ingestions for a database source
- Retention periods for database sources and copies
- Sandboxes
- Database recovery
- Alerts and logs
- Managing the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- About WAN optimization on the Velocity physical appliance
- About the Veritas Remote Management Console on the Velocity physical appliance
- About Velocity physical appliance storage
- About users on the Velocity physical appliance
- About Velocity physical appliance checkpoints
- About factory reset on the Velocity physical appliance
- Configuring network address settings on the Velocity physical appliance
- Monitoring the Velocity physical appliance
- Velocity physical appliance security
- About Velocity physical appliance user account privileges
- About the Velocity physical appliance intrusion detection system
- About Velocity physical appliance operating system security
- Recommended IPMI settings on the Velocity physical appliance
- Best practices
- Troubleshooting
- Glossary
- Context-sensitive topics
- Section I. Velocity shell menu commands
- Introduction
- Appendix A. Main > Manage > Storage
- Appendix B. Main > Manage > Cloud
- Appendix C. Main > Manage > Software
- Appendix D. Main > Monitor
- Appendix E. Main > Network
- Appendix F. Main > Settings
- Appendix G. Main > Support
Recommended IPMI settings on the Velocity physical appliance
Review this section to ensure that the Veritas Remote Management Console and the IPMI port are secure.
Do not allow accounts with null user name or password.
It is recommended to have one administrative user.
It is recommended to disable the anonymous user.
To mitigate the CVE-2013-4786 vulnerability:
Use strong passwords to limit the effectiveness of offline dictionary attacks and brute force attacks. The recommended password length is 16-20 characters.
Change the password of the default user (
sysadmin
) as soon as possible.Use Access Control Lists (ACLs) or isolated networks to limit access to the IPMI interface.
Table: Login security settings
Settings | Recommended values |
---|---|
Failed login attempts | 3 |
User Lockout time (min) | 60 seconds |
Force HTTPS | Yes The Force HTTPS check-box must be enabled to ensure that the IPMI connection always takes place over HTTPS. |
Web Session Timeout | 1800 |
Veritas recommends that you should enable LDAP authentication, if possible in your environment.
Veritas recommends that you import a new or custom SSL certificate.
Table: Remote session security settings
Settings | Recommended values |
---|---|
KVM Encryption | AES |
Media Encryption | Enable |
Do not set cipher to zero on the IPMI channel
Warning:
If the cipher 0 enabled on a channel, it allows anyone to perform any IPMI action with no authentication, effectively subverting IPMI security entirely. Disable it at all costs.
Only use ciphers 3, 8, and 12.
Recommended to have a dedicated Ethernet connection for IPMI, that is you should avoid sharing the server's physical connection.
Use a static IP
Avoid DHCP