1.11 Security Best Practices for AHF Fleet Insights
Review the key security measures to secure the AHF Fleet Insights application, including changing default credentials, managing SSL certificates, enforcing file permissions, and ensuring Nginx FIPS compliance.
Change default user credentials
During installation, a user account is created with a default username and password. Upon first login, the application requires the admin user to change the credentials. The application enforces this password change to secure the UI admin account.
Replace SSL certificates
You can replace expired SSL certificates or use your own custom SSL certificates for the application. The unified CLI offers a simple way to do this using the importcert
command, allowing you to update certificates seamlessly when needed. For more information, see Import SSL Certificates.
File permissions
All AHF Fleet Insights application files and directories are restricted to the necessary user group, typically just the install user. Files containing credentials are further secured by being set to read-only, ensuring that sensitive information remains protected.
Nginx Configuration
Nginx is configured to allow only FIPS-compliant ciphers as listed on NGINX FIPS Compliance. This configuration is enabled by default, so no additional setup is required.
Passwords
Passwords are not stored in any installation files; they are encrypted and removed from the properties and other files once the installation is successfully completed.
Command Line Interface
Only the installation user can run the CLI commands.
Parent topic: Get Started