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

Add Security guidelines #16

Merged
merged 1 commit into from
Mar 26, 2024
Merged

Add Security guidelines #16

merged 1 commit into from
Mar 26, 2024

Conversation

SamuelBeaurepaire
Copy link
Collaborator

Description

This PR add security related guidelines to address issue #3

Changes Made

  • Add guide for security repo setup and security policy template
  • Add links to the main readme and docsify's sidebar

Checklist:

  • I have followed the style guidelines of this project.
  • I have performed a self-review of my own changes.
  • I have made corresponding changes to the documentation.
  • I have reviewed the CONTRIBUTING.md guidelines.

Copy link

github-actions bot commented Mar 5, 2024

PR Preview Action v1.4.7
Preview removed because the pull request was closed.
2024-03-26 14:38 UTC

@@ -9,3 +9,4 @@
* [Contributor's Handbook](/guides/CONTRIBUTING_GUIDE.md)
* [Pull Request Manual](/guides/PULL_REQUEST_GUIDE.md)
* [Code of Conduct Guidelines](/guides/CODE_OF_CONDUCT_GUIDE.md)
* [Security policy Guidelines](/guides/SECURITY_GUIDE.md)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* [Security policy Guidelines](/guides/SECURITY_GUIDE.md)
* [Security Policy Guidelines](/guides/SECURITY_GUIDE.md)

@MGaetan89 MGaetan89 linked an issue Mar 6, 2024 that may be closed by this pull request
2 tasks
maintain confidentiality and control access. For open-source projects or non-sensitive content,
consider making the repository public to encourage collaboration and transparency.

## Enable Dependency Graph for Private Repositories
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why only for private repositories?

We could also look to have Dependency Graph enabled by default for every repositories in the SRGSSR organisation: https://docs.github.com/en/code-security/getting-started/securing-your-organization

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dependency graph is enabled for public repositories by default (and cannot be disabled AFAIK). Here is an example with our Pillarbox Apple repository:

Screenshot 2024-03-06 at 09 39 23

Comment on lines +14 to +18
## Enable Dependabot Alerts, Security Updates, and Version Updates
Enable Dependabot alerts to receive notifications about vulnerable dependencies in your
repositories.
Configure Dependabot to automatically apply security updates and version updates when available.
Regularly review and merge Dependabot pull requests to keep dependencies up-to-date and secure.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we should also explain how to enable and configure these features? Or provide links to relevant documentation?

Comment on lines +40 to +41
This template will assist you in creating a concise SECURITY POLICY for your project which should
be a `SECURITY.md` file at the root of the repository.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
This template will assist you in creating a concise SECURITY POLICY for your project which should
be a `SECURITY.md` file at the root of the repository.
This template will assist you in creating a concise security policy for your project, which should
be a `SECURITY.md` file at the root of the repository.

Comment on lines +68 to +69
To report a vulnerability, open an issue with the "security" label on GitHub. Additionally, open a
Jira SMAC issue with a link to the GitHub issue for tracking and coordination.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  • It's a detail, but by default, I don't think that the "security" label exists. So it would be nice to mention that it needs to be created first (or see if it's possible to create it at the organisation level)
  • Add a link to Jira SMAC?
Suggested change
To report a vulnerability, open an issue with the "security" label on GitHub. Additionally, open a
Jira SMAC issue with a link to the GitHub issue for tracking and coordination.
To report a vulnerability, open an issue with the "security" label on GitHub.
Additionally, open a
[Jira SMAC](https://srgssr-ch.atlassian.net/browse/SMAC) issue with a link to the GitHub issue for tracking and coordination.

@SamuelBeaurepaire SamuelBeaurepaire merged commit 3bdc590 into main Mar 26, 2024
1 check passed
@SamuelBeaurepaire SamuelBeaurepaire deleted the feature/security_policy branch March 26, 2024 14:38
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

Successfully merging this pull request may close these issues.

Define a company wide Security Policy
3 participants