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

Create SECURITY.md #5

Merged
merged 6 commits into from
Jan 20, 2023
Merged

Create SECURITY.md #5

merged 6 commits into from
Jan 20, 2023

Conversation

bmuenzenmeyer
Copy link
Contributor

@bmuenzenmeyer bmuenzenmeyer commented Nov 16, 2022

This was given to me by Ryan

Review

I've shared this now with the following stakeholders for review:

  • open source office staff
  • security staff

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

image

new issue ui

image

security policy ui

image

Copy link
Contributor Author

@bmuenzenmeyer bmuenzenmeyer left a 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 Show resolved Hide resolved
SECURITY.md Outdated Show resolved Hide resolved
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 _____.
Copy link
Contributor Author

@bmuenzenmeyer bmuenzenmeyer Nov 16, 2022

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?

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

Copy link
Contributor Author

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

Copy link
Contributor Author

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

SECURITY.md Outdated Show resolved Hide resolved
SECURITY.md Outdated Show resolved Hide resolved
SECURITY.md Outdated Show resolved Hide resolved
bmuenzenmeyer and others added 2 commits December 19, 2022 16:59
Co-authored-by: Jay Lindquist <jay.lindquist@gmail.com>
learned about this through our collaboration with security
SECURITY.md Outdated Show resolved Hide resolved
SECURITY.md Outdated Show resolved Hide resolved
@bmuenzenmeyer bmuenzenmeyer marked this pull request as ready for review January 12, 2023 20:43
Copy link

@djsudduth djsudduth left a 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!

@bmuenzenmeyer bmuenzenmeyer merged commit 160cddf into main Jan 20, 2023
@bmuenzenmeyer bmuenzenmeyer deleted the 4-security-md branch January 20, 2023 18:58
@bmuenzenmeyer bmuenzenmeyer mentioned this pull request Mar 1, 2023
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.

3 participants