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 guidelines #15

Open
2 of 8 tasks
philnewm opened this issue Sep 11, 2024 · 0 comments
Open
2 of 8 tasks

Security guidelines #15

philnewm opened this issue Sep 11, 2024 · 0 comments

Comments

@philnewm
Copy link
Collaborator

philnewm commented Sep 11, 2024

Is there an existing issue for this?

  • I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

We need to standardize a bunch of security guidelines.
This would enbale more secure automation workflows, in abest case even automated security checks

How would you imagine the implementation of the feature?

This should be done by researching a bunch of important topics

  • Research on security features
  • Configure each repository permissions to clearly define who is allowed to do what
  • Under which circumstances automated workflows are allowed to run
  • Define who is responsible for what in the code - Code Owners file as an option
  • Branch protection rules
  • Apply principle of least privilege to tokens and similar things

Are there any labels you wish to add?

  • I have added the relevant labels to the feature request.

Describe alternatives you've considered:

Beeing risky and not caring

Additional context:

No response

@philnewm philnewm added the feature Additional functionality which doesn't exist yet label Sep 11, 2024
@mkolar mkolar removed the feature Additional functionality which doesn't exist yet label Oct 30, 2024
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

2 participants