Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Discussion / Proposal to move Security and Compliance to a top-level category #4164

Open
JimBugwadia opened this issue Dec 2, 2024 · 0 comments

Comments

@JimBugwadia
Copy link

JimBugwadia commented Dec 2, 2024

Currently, Security and Compliance is under the Provisioning category and has ~30 items in it:

https://landscape.cncf.io/?group=projects-and-products&project=cncf&category=Provisioning

Since security spans provisioning, deployment, and runtime, it may be best to move it to a top level category and have sub-categories in it:

  • Security and Compliance
    • Runtime
    • Policy
    • Identity
    • Secrets Management
    • Key Management

Key Management is currently under Provisioning, as a peer to Security and Compliance. It can be moved under Security and Compliance and potentially combined with Secrets Management.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant