{{Header}}
{{Title|title=
Enterprise Security
}}
{{#seo:
|description=Definition of "maximum security" in computing.
}}
{{maintainability_mininav}}
{{intro|
A discussion of the definition of "enterprise security" in computing.

While the idea of achieving enterprise security is appealing, it comes with a lot of unexpected drawbacks. Namely high costs for certifications and little actually tangible security improvements that couldn't or wouldn't be achieved otherwise.

}}

{{stub}}

{| class="wikitable"
|+ ''Build Integrity & Transparency Features''
|-

! Feature
! Description
! {{project_name_short}}
! Most <ref>
This is to avoid saying "all". None where this does not apply was known to the author at time of writing.
</ref> Enterprise Linux Distributions
|-

! Protection from supply chain attacks
| Mandates digital signature verification at all stages of development. This includes source code commits, git tags, the build process, and final downloads. Execution or deployment of unsigned code is strictly forbidden. The policy helps prevent supply chain attacks by ensuring the authenticity and integrity of software throughout its development and distribution.
| {{Yes}} <ref>
[[Digital_Signature_Policy|Digital Signature Policy]]
</ref>
| {{No}} <ref>
Usually does not have a Digital Signature Policy.
</ref>
|-

! Signed (ISO) images downloads
| All downloads are cryptographically signed, allowing users to verify the authenticity and integrity of releases.
| {{Yes}}
| <ref>
Some provide only sha256 checksum files. No file signed by tools such as gpg, signify and/or codecrypt.
</ref>
|-

! Signed software packages are verified by the package manager
|
| {{Yes}}
| {{Yes}}
|-

! Documentation encourages users to perform digital software signature verification
| [[Verifying Software Signatures]] is consistently pointed out in documentation.
| {{Yes}} <ref>
[[Digital_Signature_Policy|Digital Signature Policy]]
</ref>
| {{No}}
|-


! Certification
| Cybersecurity validations and certifications, product compliance
| {{No}} <ref>
[[Dev/certification]]
</ref>
| {{Yes}} <ref>
* https://access.redhat.com/en/compliance?products=Red+Hat+Enterprise+Linux
</ref>
|-

! Kernel livepatching
| [https://en.wikipedia.org/wiki/Kpatch kpatch]
| {{No}} <ref>
https://debconf24.debconf.org/talks/91-linux-live-patching-in-debian/
</ref>
| {{Yes}}
|-

! Community support
|
| {{Yes}} <ref>
[[Community Support]]
</ref>
| {{Yes}} <ref>
https://www.reddit.com/r/redhat
</ref>
|-

! Enterprise support
| Onboard new companies, answer questions, resolve issues at scale according to a service agreement.
| {{No}}
| {{Yes}} <ref>
* https://www.redhat.com/en/services/support
* https://www.reddit.com/r/redhat/comments/1d8b5ww/level_of_support_expected/
</ref>
|-

! Professional 24/7 support
| Access to support engineers 24x7 for high-severity issues according to service agreement.
| {{No}}
| {{Yes}}
|-

! Extended LTS long-term support (5 years) by vendor
|
| {{No}}
| {{Yes}}
|-

! Extended LTS long-term support (5 - 19 years) by vendor
|
| {{No}}
| {{Yes}} <ref>
{{quotation
|quote=Maintain system consistency with up to 19 years of support.
|context=[https://www.suse.com/products/long-term-service-pack-support/ SUSE Linux Enterprise Long Term Service Pack Support]
}}
</ref>
|-

|}

= See Also =
* https://wiki.almalinux.org/Comparison.html

= Footnotes =
<references />

{{Footer}}
[[Category:Documentation]]
[[Category:Design]]