Skip to content
This repository has been archived by the owner on Sep 6, 2023. It is now read-only.

📚 Document a security threat modell for the secureCodeBox Project #42

Closed
rseedorff opened this issue Oct 19, 2020 · 4 comments
Closed
Labels
documentation Improvements or additions to documentation

Comments

@rseedorff
Copy link
Member

As a secureCodeBox user i want to know more about the security aspects of the secureCodeBox itself. Therfore i would like to find a documented threat modell of the project which lists all known threats and countermeasures.

Topics which could be interesting therefore:

  • security aspects of the underlying SCB architecture
  • data flow and data processing within the SCB Operator and all components (storage, scanner, hooks)
  • kubernetes security aspects like network security policies , pod security policies, security Context, ressource limits and namespace quota and their impact to the secureCodeBox
  • authentication and authorization of used service accounts and their impact in multi tenancy clusters
  • CICD security of the SCB Project (SDLC)

To give you an impression how such and threat modell can be documented here a good example from the OAUTH2 spec: https://tools.ietf.org/html/rfc6819

@rseedorff rseedorff added the documentation Improvements or additions to documentation label Oct 19, 2020
@rseedorff rseedorff changed the title Document a security threat modell for the secureCodeBox Project 📚 Document a security threat modell for the secureCodeBox Project Oct 19, 2020
@Weltraumschaf
Copy link
Member

Weltraumschaf commented Jun 10, 2022

This is a very old one, but important one IMO.

This is a good one for @fbelz and @fphoer to do their first own threat modeling. @malexmave what do you think?

@malexmave
Copy link
Member

Might be an interesting option to try a TM run by them, yes. But would probably be end of July / beginning of August at the earliest, given the current workload.

@Weltraumschaf
Copy link
Member

This issue is since over a year old, so IMO this is not a problem to wait some more months 😬

@Weltraumschaf
Copy link
Member

Nothing done since 3 years. Not important enough.

This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants