-
Notifications
You must be signed in to change notification settings - Fork 1
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
Create SECURITY.md #5
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
self-review
Derived from the provided source material
SECURITY.md
Outdated
|
||
Instead, please report them to the Target Cyber Security team at _____. | ||
|
||
If you prefer to submit without logging in, send an email to _____. If possible, encrypt your message with our PGP key; please download it from _____. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
opensource@target.com is already the reporting mechanism for code of conduct violations. should it continue to be that in this case, or perhaps security@target.com?
the security mailbox likely has fantastic monitoring in place already, but we need to coordinate
@djsudduth do you have thoughts?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agree that the security mailbox would be the appropriate contact mech. Jay L can confirm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
also reached out to our BISO
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also just now became aware of https://security.target.com/vdp which might be a great place to funnel everyone through - pending some internal alignment
Co-authored-by: Jay Lindquist <jay.lindquist@gmail.com>
learned about this through our collaboration with security
redundant with VDP docs
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've gone through every line - all looks good!
This was given to me by Ryan
Review
I've shared this now with the following stakeholders for review:
Effect
Merging this policy will apply the security policy documentation across all repositories within the organization (unless they have added their own):
right side nav on repos
new issue ui
security policy ui