Status
Supported
Fedora Linux is an explicitly supported SHP platform.
Support is established by the applicable Active Fedora Platform Admission Record.
View the Fedora Platform Admission Record →
Platform support does not by itself mean that production certification signing is operational or that certification services are currently available.
Platform boundary
The admitted Fedora platform boundary covers the Fedora environments defined by the applicable Fedora specifications.
The current Fedora threat model formally scopes the platform to:
- Fedora Workstation
- Fedora Silverblue
Certification claims must remain within that defined platform boundary.
A Fedora control or certification result must not be assumed to apply to another Linux distribution merely because the underlying technologies are similar.
Admitted specification set
Fedora certification is governed by the applicable SHP core specifications together with the admitted Fedora-specific specification set.
That set includes:
- Fedora Threat Model
- Fedora Certification Mathematics
- Fedora Tier 1 Full Control Catalogue
- Fedora Tier 2 Full Control Catalogue
- Fedora Tier 3 Full Control Catalogue
- Fedora Platform Admission Record
The applicable versions of those artefacts define the Fedora certification context.
Browse the SHP Specification Library →
Fedora tiers
Fedora currently has defined control catalogues for:
- Tier 1
- Tier 2
- Tier 3
Those tiers are Fedora-specific governed hardening postures.
They are not generic Linux security levels.
They must not be interpreted as equivalent to the same numbered tiers on Wi-Fi, Network Gateway, or another SHP platform.
Threat model first
Fedora controls derive their meaning from the applicable Fedora threat model.
The threat model defines the adversaries, attack classes, assumptions, protected objectives, constraints, and exclusions against which the platform controls are interpreted.
Certification must not be read as protection against threats outside that defined boundary.
Verification
Fedora certification is based on structured verification of observed state.
Verification must follow the applicable Fedora controls and the SHP verification model.
Applicable Non-Negotiable Controls remain hard certification gates.
They cannot be bypassed by discretionary judgement.
Certification
Fedora certification is:
- device-bound
- state-bound
- specification-bound
- time-bounded
It is derived from eligible verification results and issued only under SHP-controlled certification authority.
Certification does not mean that compromise is impossible.
It does not survive arbitrary material state change.
An expired or revoked certification is not active certification.
Understand SHP Certification →
Signing readiness
Formal Fedora platform support and production certification signing readiness are separate states.
Platform Support means Fedora has been formally admitted under SHP governance.
Certification Signing Readiness means the required operational trust infrastructure exists for issuing Fedora certification artefacts.
Service Availability means those certification services are actually being offered.
None of these states should be inferred from another.
Platform independence
Fedora remains structurally independent from other SHP platforms.
Fedora controls, tier semantics, threat coverage, and certification meaning must not be transferred automatically to Wi-Fi, Network Gateway, another Linux distribution, or another technical domain.