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 vulnerability reporting process #4

Open
dthaler opened this issue Feb 16, 2022 · 4 comments
Open

Security vulnerability reporting process #4

dthaler opened this issue Feb 16, 2022 · 4 comments

Comments

@dthaler
Copy link
Collaborator

dthaler commented Feb 16, 2022

We need to document what the inbound and outbound vulnerability management process is.

There is work in progress linked at bottom of https://github.com/ossf/wg-vulnerability-disclosures

@dthaler
Copy link
Collaborator Author

dthaler commented Mar 8, 2022

Another comparable:

@vmbrasseur
Copy link
Contributor

I was looking into this and think it's something that we ought to be following the LFN policy for. Unfortunately, I can't locate an LFN security vulnerability disclosure policy.

@lilluzzi, could you please lend a hand here?

@lilluzzi
Copy link
Contributor

@vmbrasseur LFN policy is to use LFx Security (see link above). Projects will be onboarding in the coming weeks. The security team is working on the rollout plan to communities.

@vmbrasseur
Copy link
Contributor

@lilluzzi That's for scanning for vulnerabilities though, not reporting them, isn't it?

For instance, here's the template for a policy for the projects under CCC: security-response-policies.md

Does LFN have a policy for vulnerability disclosure for its projects?

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

3 participants