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

oneMKL Adopt Vulnerability Policy (Security.md) #72

Closed
rozhukov opened this issue Mar 28, 2024 · 4 comments
Closed

oneMKL Adopt Vulnerability Policy (Security.md) #72

rozhukov opened this issue Mar 28, 2024 · 4 comments
Milestone

Comments

@rozhukov
Copy link
Collaborator

rozhukov commented Mar 28, 2024

  1. Adopt Public Security Policy (Security.md file) to UXL.
    (!) There is no Security.md file for oneMKL at all: https://github.com/oneapi-src/oneMKL?tab=security-ov-file
    You can use oneDNN as an example: Security.md
    Pay attention to Supported Versions section, it may vary based on your Support policy.
    Please add @rozhukov to the reviewers list.

  2. Enable Private Vulnerability reporting
    GitHub Security tab -> Enable Vulnerability Reporting

image

@rozhukov rozhukov added this to the Q2 2024 milestone Mar 29, 2024
@vmalia
Copy link

vmalia commented May 8, 2024

@rozhukov you can assign this one to me.

@rozhukov
Copy link
Collaborator Author

rozhukov commented May 9, 2024

@vmalia I thought it's WIP already. Please let me know once done. Thx.

@vmalia
Copy link

vmalia commented May 28, 2024

@rozhukov
I have maintainer permissions for the oneMKL project but cannot see the "Private Vulnerability Reporting" option.

Image

Verified the same with another maintainer. Is there something else that needs to be configured for this option to appear?

@rozhukov
Copy link
Collaborator Author

@rozhukov I have maintainer permissions for the oneMKL project but cannot see the "Private Vulnerability Reporting" option.

Image

Verified the same with another maintainer. Is there something else that needs to be configured for this option to appear?

Yes, you should be either owner or admin. With our internal Intel guidance I advised it many times to get added to owner-* GitHub teams. I think it'd make sense to re-evaluate access permissions and roles ones migration to UXL-owned org is done.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In Progress
Development

No branches or pull requests

2 participants