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

Troubleshooting Security breaches document #33

Closed
wants to merge 1 commit into from

Conversation

pharar
Copy link

@pharar pharar commented Jun 4, 2020

Some advises of troubleshooting actions for hosting providers in the case of a Security scenario.
Any addition is more than welcome.

Some advises of troubleshooting actions for hosting providers.
@javiercasares javiercasares added this to To Do / Review in New Handbook (v2) Jun 6, 2020
@getsource
Copy link
Member

Initial thoughts (partially from Slack, from today's triage):

  • I like the idea of the content, thank you!
  • I think it’d be good to avoid recommending any specific commercial services.
  • Agreed with some others in the channel that security team review would be great.

@Crixu
Copy link
Member

Crixu commented Mar 3, 2021

Reached out to Ian Dunn from the security team to also get their review on this.

@iandunn
Copy link
Member

iandunn commented Mar 3, 2021

Hi 👋🏻

It seems like there's a lot of similarity between this and the My Site Was Hacked FAQ. Does this page have a different goal than that one?

If not, I'd recommend linking to that instead of creating a new one. You could then collaborate w/ Support to make improvements to that article.

Or maybe link to that for the "reactive", and have this focus on the "proactive" steps? Or link to that for user-focused tips, and make this focused on tips for hosting providers?

@pharar
Copy link
Author

pharar commented Jun 2, 2022

Hi 👋🏻

It seems like there's a lot of similarity between this and the My Site Was Hacked FAQ. Does this page have a different goal than that one?

If not, I'd recommend linking to that instead of creating a new one. You could then collaborate w/ Support to make improvements to that article.

Or maybe link to that for the "reactive", and have this focus on the "proactive" steps? Or link to that for user-focused tips, and make this focused on tips for hosting providers?

You are right. This is an old documentation proposal page, so I'm opening an issue to work in that article. Thanks!

@pharar pharar closed this Jun 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
New Handbook (v2)
  
To Do / Review
Development

Successfully merging this pull request may close these issues.

None yet

4 participants