- Notes, cautions, and warnings
- Disclaimer
- Preface
- Introduction
- Authentication
- Component access control
- Log in to PowerProtect Data Manager
- User and credential management
- Login security settings
- Authentication types and setup
- Identity providers
- Authentication to external systems
- Authorization
- Log Settings
- Network and Communication Security Settings
- Data Security Settings
- Cryptography
- Security Updates and Patching
- Authenticity and Integrity
- About product authenticity and integrity
- Verification
- Verify the signer or signers for Windows binaries
- Verify the vendor for Linux (RPM-based) packages
- Verify the vendor for Linux (Debian-based) packages
- Verify GPG signatures for Linux (RPM-based) packages
- Verify the signature for JAR files
- Verify SHA-256 checksums in Windows
- Verify SHA-256 checksums in Linux
- Verify SHA-256 checksums in AIX
- Miscellaneous Configuration and Management Elements
- REST API Procedures
PowerProtect Data Manager 19.10 Security Configuration Guide
About product authenticity and integrity
PowerProtect Data Manager uses multiple methods to protect product code and downloads against compromise or corruption. These methods include SHA-256 checksums and digital signatures that you can verify through the methods included in this chapter.
The Drivers & Downloads area on Customer Support provides a set of checksum values for every file.
Critical processes, such as the deployment and update workflows, automatically check authenticity and integrity, and fail if either is compromised. However, there are several points where you should verify components and binaries before using them:
- After you download the deployment or update packages.
- After you download the application agents and other PowerProtect Data Manager installable binaries.
- After you download hotfixes.
Some procedures, such as PowerProtect Data Manager deployment and updates, contain steps or opportunities to verify certificates or signatures.
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: <>()\