Red Hat Enterprise Linux

Red Hat Enterprise Linux (RHEL) is a commercial Linux distribution with a subscription-based model that includes several potential additional costs beyond the base subscription fee. Here’s a breakdown of typical costs and what they cover:

1. Subscription Fees

• Base Subscription: Required for every RHEL installation (physical, virtual, or cloud). The subscription grants access to software, updates, security patches, documentation, and support.

• Support Levels: Different tiers are available—Self-support, Standard, and Premium—with increasing levels of support, response time, and access to Red Hat resources.

2. Setup Fees

• No Separate Setup Fee: There is typically no separate setup fee charged by Red Hat; setup is included as part of the subscription, which covers installation tools and documentation.

3. Maintenance and Support Charges

• Included in Subscription: Ongoing maintenance (updates, bug fixes, security patches) and technical support are included in the subscription fee for the chosen support level.

• Optional Add-ons:

  • Extended Update Support (EUS): For organizations needing to stay on a specific minor release longer, EUS is available as a paid add-on for certain versions and tiers.

  • Extended Life-cycle Support (ELS): For continued support after the official end of life, ELS is available as an add-on for eligible editions.

  • Red Hat Satellite: For advanced lifecycle and infrastructure management, available as a separate paid product.

  • Technical Account Management: Additional premium support services can be purchased on top of standard subscriptions.

4. Cloud and VM Pricing

• Cloud Deployments:
  When running RHEL on cloud platforms (e.g., AWS, Azure, IONOS), subscription fees are often charged per vCPU or core, and may scale with the size and duration of the instance.

• New Pricing Models: From 2024, some providers use a tiered, per-core pricing model, so costs scale with resources used.

5. Third-Party or Managed Support

• Alternative Support Providers: Some organizations choose third-party managed services for RHEL, which may offer lower costs or additional services, but these are separate from Red Hat’s own support.

Red Hat Enterprise Linux (RHEL) offers a range of training and support options for new users, combining official courses, certifications, self-paced resources, and robust technical support:

• Official Training and Certification: Red Hat provides hands-on training courses for all experience levels, from Linux fundamentals to advanced system administration and automation. Popular entry-level courses include Red Hat System Administration I (RH124) and II (RH134), and the Red Hat Certified System Administrator (RHCSA) exam. There are also specialized courses for automation, security, cloud, and containerization.

• Red Hat Learning Subscription: This subscription grants unlimited access to all Red Hat online courses, learning paths, and certification preparation, supporting continuous learning and skill advancement.

• Free Introductory Courses: Red Hat offers free online courses such as Red Hat Enterprise Linux Technical Overview (RH024) and technical overviews for OpenStack, Ansible, containers, and more, making it easy for beginners to get started.

• Skill Assessments: Users can take skill assessments to identify knowledge gaps and receive personalized training recommendations.

• Third-Party Training Providers: Authorized partners like New Horizons and Nexus Human deliver instructor-led courses, exam preparation, and hands-on labs for RHEL certifications.

• Self-Paced and Online Learning: Platforms like Coursera offer introductory courses on RHEL basics, command-line usage, and system administration tasks, suitable for those who prefer self-study.

• Documentation and Knowledgebase: Extensive official documentation, how-tos, and access to the Red Hat Knowledgebase are available to all users.

• Technical Support: RHEL subscriptions include access to Red Hat’s technical support team. Users can open support cases, access troubleshooting resources, and use the Red Hat Support Tool directly from the command line for knowledgebase searches, case management, and file uploads.

• Interactive Support Tools: The Red Hat Support Tool allows users to interact with support resources and open cases from the terminal, streamlining the support process.

Red Hat Enterprise Linux (RHEL) implements a multi-layered security framework to protect data and ensure compliance across hybrid, cloud, and on-premises environments. Here are the key security measures RHEL puts in place:

• SELinux (Security-Enhanced Linux): Mandatory access control is enabled by default, isolating processes, users, and containers to prevent unauthorized access and contain breaches.

• System-wide Cryptography Policies: Administrators can enforce strong, consistent cryptographic standards (including FIPS and TLS 1.3) across all applications and services, simplifying compliance and improving security for data in transit and at rest.

• Firewall and Network Security: Comprehensive firewall management tools restrict network traffic and reduce attack surfaces, while SSH root password login is disabled by default to prevent brute-force attacks.

• Application Allow-listing (fapolicyd): Only approved applications can run, preventing execution of unauthorized or malicious code.

• Identity and Access Management: Centralized identity controls, integration with external identity providers, smart card authentication, and support for passwordless authentication (including FIDO2 devices) help secure access to systems and data.

• Live Kernel Patching: Apply critical security patches to the kernel without rebooting, reducing downtime and exposure to vulnerabilities.

• Integrity Measurement Architecture (IMA): Uses digital hashes and signatures to verify and monitor the integrity of the operating system, detecting unauthorized changes or tampering.

• Supply Chain Security: Secure build processes, package signing, and vulnerability scanning protect against supply chain threats and ensure only trusted software is installed.

• Automated Compliance and Auditing Tools: Built-in tools and system roles automate the enforcement of security baselines (e.g., CIS Benchmarks), perform vulnerability scans, and maintain detailed audit logs for compliance reporting and incident response.

• Container and Virtualization Security: Enhanced isolation and attestation technologies (like Keylime) ensure that containerized and virtual workloads meet strict security and integrity requirements.

• Regular Security Updates: RHEL provides timely security patches and updates, with extended support options, to address emerging threats and vulnerabilities.

• Security Certifications: RHEL is certified for standards such as Common Criteria and FIPS 140-2, supporting deployments in highly regulated industries.

Red Hat Enterprise Linux (RHEL) follows a predictable and stable release and update lifecycle to ensure long-term support and minimize disruption for enterprise users. Here's a breakdown of how updates are released and managed:

Release Cadence:

1. Major Releases

• Frequency: Approximately every 3–5 years.

• Examples: RHEL 7 (2014), RHEL 8 (2019), RHEL 9 (2022).

• These are significant upgrades with new features, architectures, and deprecations.

2. Minor Releases

• Frequency: Approximately every 6 months.

• Examples: RHEL 8.8, 8.9, 9.3, etc.

• These include enhancements, new hardware support, and non-disruptive updates.

• Backward compatibility is maintained within a major release.

Update Types

1. Security Updates

• Delivered as soon as they are available and tested.

• Often released via Red Hat's Errata system.

2. Bug Fixes

• Released regularly through minor updates and errata.

3. Enhancements

• Non-critical improvements are rolled into minor releases.

Update Channels and Tools

• Red Hat Satellite: For managing updates across many systems.

• DNF/YUM: For system-level updates (package-based).

• RHEL Repositories: Updates are delivered through structured repos (e.g., BaseOS, AppStream).

• Red Hat Subscription Management (RHSM): Controls access to updates and entitlements.

Lifecycle Management

RHEL offers up to 10 years of support per major release:

1. Full Support (first 5 years): All updates, including new hardware enablement.

2. Maintenance Support (next 5 years): Critical security fixes and high-priority bug fixes.

3. Extended Lifecycle Support (ELS): Optional paid add-on for extended updates after EOL.

Red Hat Enterprise Linux (RHEL) has clear policies around data ownership and portability, which align with Red Hat’s broader enterprise-friendly, open-source philosophy. Here's a breakdown of their approach:

Data Ownership:

• You Own Your Data:

  
  Red Hat does not claim ownership over any data you generate, store, or process using RHEL. The operating system is a platform; you retain full rights and control over your data.

• Subscription Model:

  
  RHEL is provided under a subscription license, which governs access to updates, support, and tools—not ownership of user data.

• Privacy Commitment:

  
  Red Hat collects minimal telemetry (opt-in for most versions) and is transparent about what data is collected, typically only for:

  • Product improvement

  • Support

  • Security insight (e.g., Insights service)

Data Portability:

• Vendor Lock-In Avoidance:

  
  RHEL adheres to open standards and tools, making it easier to move your data and workloads between:

  • On-premises systems
  • Private clouds
  • Public cloud providers (AWS, Azure, GCP, etc.)

  • Other Linux distributions (with some effort for compatibility)

• Container and Cloud Native Support:
  With Red Hat OpenShift and Podman, RHEL supports containerization, which improves workload portability across platforms.

• Exportability of System Data:
  System configurations, logs, and other data can be exported without restrictions. Admins can freely back up or move these data assets.

Red Hat Enterprise Linux (RHEL) is designed to scale flexibly with organizational needs, whether you're increasing or decreasing your infrastructure footprint. Here's a summary of the key terms and practices for scaling up or down under a Red Hat subscription:

Scaling Up (Adding Systems or Capacity)

1. Add More Subscriptions:

   • You can purchase additional subscriptions at any time to cover more systems, CPUs, or cores.

   • Red Hat offers subscription types based on:
     • Socket pairs (physical or virtual servers)
     • Virtual Data Centers (for large-scale virtual environments)

     • Core-based pricing (for cloud environments)

2. Cloud & Hybrid Support:

   • Use Red Hat Cloud Access to move your RHEL subscriptions to supported cloud providers (AWS, Azure, etc.).

   • Or use RHEL images from cloud marketplaces, which are billed on a pay-as-you-go basis (no need to manage your own subscription).

3. Automation at Scale:

   • Tools like Red Hat Satellite, Ansible, and Red Hat Insights help automate provisioning and configuration as you scale up.

Scaling Down (Reducing Usage)

1. Reducing Systems:
   • You can stop using RHEL on systems and reclaim or cancel unused subscriptions at renewal time.

   • Subscriptions are typically annual, so reductions take effect at the next renewal cycle.

2. Subscription Management:
   • Use Red Hat Subscription Management (RHSM) or Satellite to track and reallocate subscriptions to where they’re needed most.

   • This is useful for rebalancing licenses across departments, data centers, or cloud environments.

3. Downgrade Option:
   • You can switch to lower-tier subscriptions (e.g., Standard to Self-Support) if your support needs change.

Red Hat Enterprise Linux (RHEL) operates on a subscription-based model governed by the Red Hat Enterprise Agreement. Here are the key terms and conditions for contract (subscription) renewal and cancellation, with supporting data points:

Subscription Term and Renewal:

• Term-Based Subscriptions: RHEL subscriptions are typically sold in one- or three-year terms23. The term begins on the start date specified in the order form and ends at the expiration of the service term unless terminated earlier.

• Automatic Renewal: Subscriptions generally automatically renew for successive terms of the same duration as the original, unless either party provides written notice of non-renewal at least 30 days (sometimes 60 days for government contracts) before the end of the current term.

• Renewal Process: Red Hat contacts customers via email or a representative before expiration. Customers can renew online (if purchased via the Red Hat Store), through their sales representative, or by contacting their Red Hat partner6. Renewal pricing is available from Red Hat or the original partner.

• Importance of Renewal: Renewing ensures continued access to software updates, security patches, upgrades, certified binaries, and technical support. If a subscription expires, these benefits end.

Cancellation and Termination

• Notice of Non-Renewal: Either party may cancel automatic renewal by providing written notice within the required timeframe (typically 30 days before term end).

• Early Termination: The agreement or an order form may be terminated early if either party materially breaches the terms and fails to cure the breach within 30 days of notice.

• Effect of Cancellation/Expiration: Upon cancellation or expiration, the right to receive updates, support, and other subscription benefits ceases, but the software may continue to function. Continued use without an active subscription is not compliant with Red Hat’s terms.

• Unsubscribing Systems: Administrators can remove subscriptions from systems at any time using the subscription-manager unsubscribe command.

• No Refunds: All fees and payments made under the agreement are non-refundable.

Other Key Points

• Per-Instance Requirement: Each RHEL installation requires its own valid subscription; all active systems must be covered.

• Third-Party Support: Customers may purchase third-party support, but as long as any Red Hat subscriptions are active, all instances must remain covered by a valid subscription.

• Unused Services: Any professional services ordered must be consumed within the service term or will be forfeited

Red Hat Enterprise Linux (RHEL) meets a broad range of internationally recognized compliance standards and certifications, making it suitable for use in highly regulated industries and sensitive computing environments. Here are the key compliance standards and certifications RHEL supports or holds:

• Common Criteria (CC): An international standard (ISO/IEC 15408) for computer security certification. RHEL’s minor releases and every Extended Update Support (EUS) release are independently validated against Common Criteria requirements.

• FIPS 140-2/140-3 (Federal Information Processing Standards): RHEL’s cryptographic modules are validated to FIPS 140-2/140-3 standards, ensuring proper implementation of cryptographic algorithms for government and regulated sectors.

• PCI DSS (Payment Card Industry Data Security Standard): RHEL achieves PCI DSS 4.0 certification and provides guidance and tools to help organizations meet PCI processing payment card data requirements.

• SOC 2 Type 2: RHEL and associated Red Hat services have achieved SOC 2 Type 2 attestation, demonstrating strong controls for security, availability, and confidentiality.

• ISO 27001, ISO 27017, ISO 27018: RHEL and Red Hat cloud services are certified for ISO 27001 (information security management), ISO 27017 (cloud security), and ISO 27018 (protection of personal data in the cloud).

• STIG (Secure Technical Implementation Guidelines): Red Hat provides automation tools and guidance for implementing U.S. Department of Defense STIG requirements on RHEL systems.

• FedRAMP: While FedRAMP is specific to cloud services, Red Hat OpenShift Service on AWS (built on RHEL) is approved for FedRAMP High, indicating the platform’s alignment with federal cloud security requirements.

• ANSSI BP-028: RHEL follows security configuration guidance from the French National Cybersecurity Agency (ANSSI), supporting compliance with ANSSI BP-028.

• UK Cyber Essentials: RHEL supports the UK government’s minimum baseline for cybersecurity, known as Cyber Essentials.

• Automated Compliance Tools: RHEL includes built-in tools (such as OpenSCAP and scap-security-guide) for automated configuration, vulnerability scanning, and compliance reporting to help organizations validate and maintain compliance.