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

[security] Prepare a Threat Model for both projects #1628

Open
azych opened this issue Jan 16, 2025 · 0 comments
Open

[security] Prepare a Threat Model for both projects #1628

azych opened this issue Jan 16, 2025 · 0 comments

Comments

@azych
Copy link
Contributor

azych commented Jan 16, 2025

Keeping in mind one of the OLMv1's main guiding principle - "Security by default" (https://operator-framework.github.io/operator-controller/) the security posture of both catalogd and operator-controller projects should be analyzed and a threat model for each of them should be prepared. Those models should then be kept up to date and be included in PR checklist.

CNCF tag-security's Manual for Practicing Threat Modeling to Assess and Fortify Open Source Security might be a good resource in helping to do that, as well as other resources or discussions (eg. cncf/tag-security#903) from that group - https://github.com/cncf/tag-security

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