-
Notifications
You must be signed in to change notification settings - Fork 227
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
More security incident details? #34
Comments
Awesome! I know @richadams is working on a few updates regarding Security, so let's keep this Issue open for the moment, and once those updates are out we can take a look, sound like a plan? |
any updates? Thanks |
Hi @juju4, I'm just catching up on this, sorry that it got missed for so long! I'd definitely like to include some of your changes! I'd like to organize them a certain way to fit the style of our documentation, but I want to make sure you get the appropriate credit for the changes. Normally I'd ask you to raise the PR, but I feel it'll be quicker for me to organize all of the changes into a PR first, rather than us going back and forth a lot (since I don't want to waste your time with silly nitpicky stuff). Would you be OK with me taking your changes and organizing them into a PR first myself? Then you can take the patch and raise your own PR with those changes so you get the credit as the committer (I definitely don't want to claim credit for your work!) Does that sound OK? |
No worries @richadams ! Good for me. |
Hello,
I found great that you share your incident response docs. Thanks for it.
I use it as a base to detail more on security incident response and a few typical cases.
https://github.com/juju4/incident-response-docs/tree/devel
I decide to keep it simple so not with overload of details and more with good references set.
If it's something you would be interested in, I can push a PR
The text was updated successfully, but these errors were encountered: