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

Audit repositories for security tools #12

Open
9 of 68 tasks
codeboten opened this issue Aug 16, 2023 · 15 comments
Open
9 of 68 tasks

Audit repositories for security tools #12

codeboten opened this issue Aug 16, 2023 · 15 comments

Comments

@codeboten
Copy link
Contributor

codeboten commented Aug 16, 2023

Get a questionnaire to SIGs in the org asking them what tools are enabled in their repos:

@codeboten
Copy link
Contributor Author

Start this by documenting what's enabled in the collector repository and producing a form from it

@codeboten
Copy link
Contributor Author

codeboten commented Aug 16, 2023

The following tools are configured for the OpenTelemetry Collector repository:

  • CodeQL enabled via GitHub Actions
  • Static code analysis: govulncheck [https://pkg.go.dev/golang.org/x/vuln] enabled on every build
  • Repository security settings
    • Security Policy ✅
    • Security advisories ✅
    • Private vulnerability reporting ✅
    • Dependabot alerts ✅
    • Code scanning alerts ✅

@codeboten
Copy link
Contributor Author

codeboten commented Aug 16, 2023

Confirmed the same is configured for the OpenTelemetry Collector Contrib repository

@JonZeolla
Copy link

We should consider Allstar for monitoring organization-wide policies. The quickstart may meet our needs

@svrnm
Copy link
Member

svrnm commented Aug 31, 2023

+1 for Allstar

@oly-baby
Copy link

oly-baby commented Oct 5, 2023

GOOD DAY,

I AM AN OUTREACH APPLICANT, CAN I WORK ON THIS

@jpkrohling
Copy link
Member

@oly-baby, welcome! Sure, feel free to pick one of the repositories from the list (see the issue description), create an issue on the repository to track the work, and write a report similar to @codeboten's one (a few comments up, here: #12 (comment)).

@Davidlred
Copy link

Hello guys, i'm an Outreachy applicant, and i'd like to work on one of the issue.

how do i take off ?

@jpkrohling
Copy link
Member

@Davidlred, see my previous comment. I'd recommend leaving a comment on the issue you pick, stating that you are working on it. If you need ideas for other tasks, join the #otel-sig-security channel on the CNCF Slack.

EjiroLaurelD added a commit to EjiroLaurelD/sig-security that referenced this issue Oct 5, 2023
@EjiroLaurelD EjiroLaurelD mentioned this issue Oct 5, 2023
@sakshi-1505
Copy link

Hello @jpkrohling , I am picking up one of the issue from the above list.

@sakshi-1505
Copy link

We can use the following tracking issue for opentelemetry-python: open-telemetry/opentelemetry-python#3467

@sakshi-1505
Copy link

We can use the following tracking issue for build-tools: open-telemetry/build-tools#212

@sakshi-1505
Copy link

We can use the following tracking issue for opentelemetry-python-contrib: open-telemetry/opentelemetry-python-contrib#1991

@arademm
Copy link

arademm commented Oct 12, 2023

Hello, I'm an Outreachy applicant. I would love to contribute to this project.

@jpkrohling
Copy link
Member

@arademm, see my previous comment. I'd recommend leaving a comment on the issue you pick, stating that you are working on it. If you need ideas for other tasks, join the #otel-sig-security channel on the CNCF Slack.

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

8 participants