redhat - Drupal core - SQL injection aftermath procedures -


What we are running is likely compromised because we have seen a big spike in network traffic, Which brought the site down. / P>

Since the possibility of theft from our patching has already taken place, so what steps should we take to inform our customer? Do they need to change any password for admin login, etc., whatever is relevant? Do we need to change the DB password on our server etc?

Basically, all of the above

[a stream on Drupalgeddon project page] The chart is () which you can follow to help tackle a clean site.

Good luck


Comments

Popular posts from this blog

apache - 504 Gateway Time-out The server didn't respond in time. How to fix it? -

c# - .net WebSocket: CloseOutputAsync vs CloseAsync -

c++ - How to properly scale qgroupbox title with stylesheet for high resolution display? -