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

Adding Incident Page to Docs #420

Merged
merged 1 commit into from
Apr 18, 2022
Merged

Adding Incident Page to Docs #420

merged 1 commit into from
Apr 18, 2022

Conversation

lreading
Copy link
Collaborator

Summary
What does Threat Dragon do when we are impacted by a security incident?

Description for the changelog
closes #419

Other info
Updated gems, fixed link that had incorrect syntax, added jekyll installation instructions to readme.

…nstructions, fixed typo in link to env page, added security incident/response page
@lreading lreading self-assigned this Apr 17, 2022
@codecov-commenter
Copy link

codecov-commenter commented Apr 17, 2022

Codecov Report

Merging #420 (3888007) into main (cacfc23) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #420   +/-   ##
=======================================
  Coverage   96.54%   96.54%           
=======================================
  Files         127      127           
  Lines        1826     1826           
  Branches      116      116           
=======================================
  Hits         1763     1763           
  Misses         56       56           
  Partials        7        7           

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update cacfc23...3888007. Read the comment docs.

@lreading
Copy link
Collaborator Author

@jgadsden @ShubhamPalriwala - These are my initial thoughts on how we should handle high-profile incidents moving forward. It's a bit off effort to keep up with, but I think it's a worthwhile exercise to earn trust from our community. Happy to hear your thoughts on this!

Copy link
Collaborator

@jgadsden jgadsden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Superb, this is a very good page to have, thanks
@lreading please go ahead and merge as soon as you can, given that this is a security response

@lreading lreading merged commit 8768acd into main Apr 18, 2022
@lreading lreading deleted the chore/incident-docs branch April 18, 2022 04:59
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.

Heroku Security Incident / Threat Dragon's Response
3 participants