Supplierneeded
Junior Member
- Dec 4, 2012
- 101
- 5
What can you do to help prevent hacking of emails and your website???
GENERAL:
1) Strong passwords. I use anywhere between 14 and 36 character passwords with upper, low and number. PasswordSafe to generate and remember them
2) Disable root login.
FTP/SERVER:
3) For SSH login disable password authentication. Instead use key-based.
4) For SSH login, disable any IP login. Do a white-list method. Using a VPN to have a consistent IP is useful in this case
5) Disable FTP, FTPS, FTPES. Only use SFTP with key based auth.
6) Disable anonymous FTP
MySQL:
7) Disable remote MySQL management.
8) Only create MySQL users with the permissiosn needed. Giving blanket permissions is a security risk.
9) Only assign users to databases if they need it. Don't create one user for multiple databases.
10) Log all MySQL activity. This may create large logs but it can reveal hackers.
Email:
11) Make sure your SMTP server isnt an open relay
12) Force SSL/TLS and only use newer ciphers
Firewall:
13) If on linux, install CSF for a firewall and configure it to block unneeded ports/port+ip combos.
Server software:
14) Keep all software updated. This includes cPanel, WHM, Apache, PHP, exim, CSF, named etc.
15) Watch security lists for new exploits
16) Disable any software you do not use!
Website scripts:
17) Review any new installations. Make sure they dont have any current exploits.
18) Review any new module/plugin installations. Make they dont have any current exploits
19) Keep an eye on security lists for exploits for them...
20) Enable logging for all scripts.
21) Use strict access control. Don't give access to what isnt needed
22) Don't leave "archived" versions of your site! If it's not being used, delete it.
23) Review all work done on your site. Some freelancers may install backdoors.
24) Be wary of encrypted (ioncubed) scripts. You dont know what is in it.
25) use htaccess to block access to directories that admins use and consumers do not.
26) Disable errors from being shown to the user.
27) Do not allow file uploads unless the script has advanced security features for finding malicious files.
28) Store config files and error logs above the www directory so they can only be viewed via ftp.
GENERAL:
1) Strong passwords. I use anywhere between 14 and 36 character passwords with upper, low and number. PasswordSafe to generate and remember them
2) Disable root login.
FTP/SERVER:
3) For SSH login disable password authentication. Instead use key-based.
4) For SSH login, disable any IP login. Do a white-list method. Using a VPN to have a consistent IP is useful in this case
5) Disable FTP, FTPS, FTPES. Only use SFTP with key based auth.
6) Disable anonymous FTP
MySQL:
7) Disable remote MySQL management.
8) Only create MySQL users with the permissiosn needed. Giving blanket permissions is a security risk.
9) Only assign users to databases if they need it. Don't create one user for multiple databases.
10) Log all MySQL activity. This may create large logs but it can reveal hackers.
Email:
11) Make sure your SMTP server isnt an open relay
12) Force SSL/TLS and only use newer ciphers
Firewall:
13) If on linux, install CSF for a firewall and configure it to block unneeded ports/port+ip combos.
Server software:
14) Keep all software updated. This includes cPanel, WHM, Apache, PHP, exim, CSF, named etc.
15) Watch security lists for new exploits
16) Disable any software you do not use!
Website scripts:
17) Review any new installations. Make sure they dont have any current exploits.
18) Review any new module/plugin installations. Make they dont have any current exploits
19) Keep an eye on security lists for exploits for them...
20) Enable logging for all scripts.
21) Use strict access control. Don't give access to what isnt needed
22) Don't leave "archived" versions of your site! If it's not being used, delete it.
23) Review all work done on your site. Some freelancers may install backdoors.
24) Be wary of encrypted (ioncubed) scripts. You dont know what is in it.
25) use htaccess to block access to directories that admins use and consumers do not.
26) Disable errors from being shown to the user.
27) Do not allow file uploads unless the script has advanced security features for finding malicious files.
28) Store config files and error logs above the www directory so they can only be viewed via ftp.
^^ In other words, develop a passion for the vast field that is network security and never stop learning (or hire professionals).
You're only as strong as your weakest link. If someone else is calling the shots you're probably going to have very poor security.
strong password would be the first and most simple security element to take care of.
Sanitize your textboxes, have a strong PW & make sure you are not having an SQL injection prone website...I am use method but my website still hacked again and again. Can you share any other good way to stop hacking.
You are asking in wrong forum.I am use method but my website still hacked again and again. Can you share any other good way to stop hacking.