Chapter 7. Security considerations in Satellite


Satellite supports multiple security mechanisms to provide additional layers of protection. Implementing these security features enhances the overall security of your Satellite deployment.

Note

These security considerations apply to both Satellite Server and Capsule Server environments.

Federal Information Processing Standards (FIPS) Mode

Satellite supports running on FIPS-enabled Red Hat Enterprise Linux hosts to comply with security standards for cryptographic modules. However, Satellite itself is not FIPS-certified. In addition, you cannot enable FIPS mode after the installation of Satellite.

FIPS mode enforces the use of validated cryptographic algorithms and modules. Enabling FIPS mode ensures that all cryptographic operations within the system adhere to strict security standards.

For more information, see Switching RHEL to FIPS mode in Red Hat Enterprise Linux 9 Security hardening.

Note

Satellite supports DEFAULT and FIPS crypto-policies. The FUTURE crypto-policy is not supported for Satellite Server and Capsule Server installations. The FUTURE policy is a stricter forward-looking security level intended for testing a possible future policy. For more information, see Using system-wide cryptographic policies in Red Hat Enterprise Linux 9 Security hardening.

File Access Policy Daemon (fapolicyd)

By enabling fapolicyd on your Satellite Server, you can monitor and control file and directory access, which provides an additional security layer.

This feature helps prevent unauthorized code execution and enhances system integrity. You can enable or disable fapolicyd on both Satellite Server and Capsule Server at any time, depending on your security requirements.

For additional information about fapolicyd, including instructions on enabling it, see Blocking and allowing applications by using fapolicyd in Red Hat Enterprise Linux 9 Security hardening.

Post-Quantum Cryptography (PQC)
Red Hat does not support PQC compatibility for Satellite.
Security-Enhanced Linux (SELinux)

Satellite requires SELinux, a mandatory access control system that restricts system access and reduces the risk of security vulnerabilities. SELinux enforces policies that define which processes can access specific system resources, providing protection against unauthorized access and exploitation.

To maintain a high-security environment, Red Hat recommends running Satellite with SELinux in enforcing mode. It ensures that access control policies are strictly enforced, minimizing the risk of privilege escalation or unauthorized actions.

Additional Security Recommendations
Regularly updating security policies and configurations, as well as monitoring system logs and security policies, can help detect and respond to potential threats effectively.
Security compliance
For certain use cases, your Satellite Server must meet the requirements of security compliance. You can use Security Content Automation Protocol (SCAP) to scan your system for security policy compliance. For more information, see Managing security compliance.
Back to top
Red Hat logoGithubredditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust. Explore our recent updates.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

Theme

© 2025 Red Hat