-
Notifications
You must be signed in to change notification settings - Fork 133
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: zhzhuang-zju <[email protected]>
- Loading branch information
1 parent
b535bb7
commit 9b58d85
Showing
1 changed file
with
34 additions
and
0 deletions.
There are no files selected for viewing
34 changes: 34 additions & 0 deletions
34
blog/2025-01-17-karmada-security-audit/karmada-security-audit.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,34 @@ | ||
# Announcing the results of the Karmada security audit | ||
|
||
Community post cross-posted on the [OSTIF blog](https://ostif.org/karmada-audit-complete/) and [CNCF blog](https://www.cncf.io/blog/2025/01/16/announcing-the-results-of-the-karmada-security-audit/) | ||
|
||
[OSTIF](https://ostif.org/) is proud to share the results of our security audit of Karmada. Karmada is an open source Kubernetes orchestration | ||
system for running cloud-native applications seamlessly across different clouds and clusters. With the help of [Shielder](https://www.shielder.com/) and | ||
the [Cloud Native Computing Foundation (CNCF)](https://www.cncf.io/), this project offers users improved open, multi-cloud, multi-cluster Kubernetes management. | ||
|
||
## Audit Process: | ||
|
||
While Karmada is a part of the Kubernetes ecosystem and therefore utilizes Kubernetes libraries and implementations, the focus | ||
of this particular work was on the overall security health of the custom implementations of Karmada and its third party dependencies. | ||
Karmada’s function utilizes multiple components, CLI tools, and add ons to extend the standard Kubernetes features, which can be | ||
customized from deployment to deployment. This makes Karmada’s attack scenarios complex, so it was necessary to perform a scoped | ||
threat modelling in order to evaluate potential attack surfaces. Utilizing this custom threat model and a combination of manual, | ||
tooling, and dynamic review, Shielder identified six findings with security impact on the project. | ||
|
||
## Audit Results: | ||
|
||
- 6 Findings | ||
- 1 High, 1 Medium, 2 Low, 2 Informational | ||
- Recommendations for Future Efforts | ||
- Proposal for Long-term Improvements to Overall Security | ||
|
||
The Karmada maintainer team worked quickly and in tandem with Shielder to resolve and fix the reported issues. Their work on behalf of | ||
the project was meticulous and mindful of users as well as relevant third-party dependencies and projects. They published necessary | ||
advisories and alerted users as to the impact and resolution of this audit. OSTIF wishes them the best of luck on their journey to | ||
graduated status with the CNCF. | ||
|
||
**Thank you** to the individuals and groups that made this engagement possible: | ||
|
||
- Karmada maintainers and community: especially Hongcai Ren, Kevin Wang, and Zhuang Zhang | ||
- Shielder: Abdel Adim “Smaury” Oisfi, Pietro Tirenna, Davide Silvetti | ||
- The Cloud Native Computing Foundation |