Turtini Docs GitHub White Papers Events Trident
Public Sector Security Logo
Turtini Docs GitHub White Papers Events Trident
  • Public Sector Security
    • Repository Contents
    • Why This Repository Exists
    • FedRAMP: Foundational Context
    • Red Hat Alignment with FedRAMP
    • Managed OpenShift Services
    • Foundational Platforms Within Authorized Boundaries
      • Red Hat Enterprise Linux (RHEL)
      • Red Hat Ansible Automation Platform
    • Shared Responsibility in Practice
    • Verification and Due Diligence
    • How to Use This Repository
    • Licensing and Reuse
    • Maintained By
  • Authorization Boundaries Explained
    • What Is an Authorization Boundary?
    • Why Authorization Boundaries Matter
    • Common Boundary Layers in Federal Systems
    • Inside vs. Outside the Boundary
      • Components Inside the Boundary
      • Components Outside the Boundary
    • Boundary Changes and Impact
    • Common Misconceptions
    • Summary
    • Related Resources
  • Frequently Asked Questions (FAQ)
    • Is Red Hat “FedRAMP approved”?
    • Is Red Hat Enterprise Linux (RHEL) FedRAMP authorized?
    • Is Ansible FedRAMP authorized?
    • Does using FedRAMP-authorized infrastructure make my system FedRAMP authorized?
    • What is an authorization boundary?
    • What is control inheritance?
    • Where can FedRAMP authorization status be verified?
    • Does this repository represent official authorization guidance?
  • FedRAMP Explained
    • What FedRAMP Is — and Is Not
    • Authorization Is Service-Specific
    • Impact Levels
    • Authorization Boundaries
    • Shared Responsibility Models
    • Control Inheritance in Practice
    • Verification and Transparency
    • Summary
Public Sector Security
Notice: This is Turtini’s official plain-language documentation for federal and regulated environments.
  • Public Sector Security
  • View page source

Public Sector Security

Clear, audit-safe guidance on how security and compliance are evaluated in U.S. public sector environments.

  • Public Sector Security
    • Repository Contents
    • Why This Repository Exists
    • FedRAMP: Foundational Context
    • Red Hat Alignment with FedRAMP
    • Managed OpenShift Services
    • Foundational Platforms Within Authorized Boundaries
    • Shared Responsibility in Practice
    • Verification and Due Diligence
    • How to Use This Repository
    • Licensing and Reuse
    • Maintained By
  • Authorization Boundaries Explained
    • What Is an Authorization Boundary?
    • Why Authorization Boundaries Matter
    • Common Boundary Layers in Federal Systems
    • Inside vs. Outside the Boundary
    • Boundary Changes and Impact
    • Common Misconceptions
    • Summary
    • Related Resources
  • Frequently Asked Questions (FAQ)
    • Is Red Hat “FedRAMP approved”?
    • Is Red Hat Enterprise Linux (RHEL) FedRAMP authorized?
    • Is Ansible FedRAMP authorized?
    • Does using FedRAMP-authorized infrastructure make my system FedRAMP authorized?
    • What is an authorization boundary?
    • What is control inheritance?
    • Where can FedRAMP authorization status be verified?
    • Does this repository represent official authorization guidance?
  • FedRAMP Explained
    • What FedRAMP Is — and Is Not
    • Authorization Is Service-Specific
    • Impact Levels
    • Authorization Boundaries
    • Shared Responsibility Models
    • Control Inheritance in Practice
    • Verification and Transparency
    • Summary
Next

© Copyright 2026, Turtini LLC. Last updated on March 08, 2026.

Built with Sphinx using a theme provided by Read the Docs.