- 92
- Posts
- 20
- Years
- Vancouver,Richmond
- Seen Oct 28, 2007
TIPS:
Never use weak/obvious passwords. (i.e. your name, dates, password, or a variation of password. Use an alpha-numeric password with special characters as well. Such as N9j3-0.y
(Hint: you can use a phrase like 'i drink 2% milk')
Close all ports on your server that do not need to be open, ssl or ssh and such. Get a firewall to monitor the ports that are open and to monitor your ports activity. (Zone Alarm, or Black Ice, if you have XP just simply use the built-in firewall if you don?t want the others)
Get an Anti-Virus program like Norton; this will help prevent any applications that are virus-infected from slipping into your machine.
If you use a database like SQL make sure you?re defended against SQL injections. If you have login don't allow the user to see the password. Or get the file that the password could be in. or even encrypt the password in a file that they user should not have permission to view. Use a server side scripting language like php so the user can only see what you allow them to see in your code.
Look into the theories of Defense in Depth.... basically, setup several defense mechanisms so an attacker would have to go through many levels of defense.
Most people dont have servers but this is for the ones that do :)
such as me .
Never use weak/obvious passwords. (i.e. your name, dates, password, or a variation of password. Use an alpha-numeric password with special characters as well. Such as N9j3-0.y
(Hint: you can use a phrase like 'i drink 2% milk')
Close all ports on your server that do not need to be open, ssl or ssh and such. Get a firewall to monitor the ports that are open and to monitor your ports activity. (Zone Alarm, or Black Ice, if you have XP just simply use the built-in firewall if you don?t want the others)
Get an Anti-Virus program like Norton; this will help prevent any applications that are virus-infected from slipping into your machine.
If you use a database like SQL make sure you?re defended against SQL injections. If you have login don't allow the user to see the password. Or get the file that the password could be in. or even encrypt the password in a file that they user should not have permission to view. Use a server side scripting language like php so the user can only see what you allow them to see in your code.
Look into the theories of Defense in Depth.... basically, setup several defense mechanisms so an attacker would have to go through many levels of defense.
Most people dont have servers but this is for the ones that do :)
such as me .