Hi,
How to confirm of my dedicated server security is ok or not.
Can someone confirm my security is OK?
Server security is ok or not.
-
vivianepintoo21
- Posts: 10
- Joined: Wed Jan 21, 2015 4:44 pm
Re: Server security is ok or not.
Some checklists are here to confirm that your server security is ok .
>> set or change passwords
>> Install a firewall
>> Disable unnecessary services
>> Virus protection
>> Configure Backups
>> Update your Software's
Thanks
>> set or change passwords
>> Install a firewall
>> Disable unnecessary services
>> Virus protection
>> Configure Backups
>> Update your Software's
Thanks
-
mariaconcepcion1215
- Posts: 11
- Joined: Wed Jan 21, 2015 4:36 pm
Re: Server security is ok or not.
For better server security check list:
1. Use Strong Passwords
2. Protect Sensitive URLs
3. Limit User Accounts
4. Blocking Malicious Injections
5. Secure All Network Traffic
6. No Unnecessary Software
7. Get a Qualified Server Technician
1. Use Strong Passwords
2. Protect Sensitive URLs
3. Limit User Accounts
4. Blocking Malicious Injections
5. Secure All Network Traffic
6. No Unnecessary Software
7. Get a Qualified Server Technician
Re: Server security is ok or not.
1. Update your OS Updates for Linux systems are release almost daily. Many of these fix important security issues. At rack AID, we update systems daily (sometimes even more frequently). If you do not have a running service or auto-updates enabled, be sure to review your OS for any serious security updates.
2. Update your Control Panel. If you are using a hosting or server control panel, be sure to update it as well.
3. Check application updates. Most security problems we study are due to outdated web applications. After you have updated your server, be sure to check the web applications and update them as well.
4. Check for hardware errors. You may would like to check the logs for any signs of hardware problems. Overheating notices, disk read errors network failures could be early indicators of potential hardware failure.
5. Check server utilization “Review your server’s disk, CPU, RAM and network utilization. If you are nearing limits, you may need to plan on adding resources to your server or migrating to a new one.
6. Check RAID Alarms. If you are utilizing RAID (and you should be), check that your RAID’s error notification system is arranged properly and works as imagined.
7. Review user accounts. Storing old sites and users is both a security and legal risk. Depending on your service contracts, you may not have the right to retain a client’s data after they have terminated services.
8. Change passwords. I recommend changing passwords every 6 to 12 months, especially if you have given out passwords to others for maintenance.
9. Check system security. I suggest a periodic review of your server’s security using a remote auditing tool such as Nisus. Regular security audits serve as a check on system configuration, OS updates and other potential security risks
2. Update your Control Panel. If you are using a hosting or server control panel, be sure to update it as well.
3. Check application updates. Most security problems we study are due to outdated web applications. After you have updated your server, be sure to check the web applications and update them as well.
4. Check for hardware errors. You may would like to check the logs for any signs of hardware problems. Overheating notices, disk read errors network failures could be early indicators of potential hardware failure.
5. Check server utilization “Review your server’s disk, CPU, RAM and network utilization. If you are nearing limits, you may need to plan on adding resources to your server or migrating to a new one.
6. Check RAID Alarms. If you are utilizing RAID (and you should be), check that your RAID’s error notification system is arranged properly and works as imagined.
7. Review user accounts. Storing old sites and users is both a security and legal risk. Depending on your service contracts, you may not have the right to retain a client’s data after they have terminated services.
8. Change passwords. I recommend changing passwords every 6 to 12 months, especially if you have given out passwords to others for maintenance.
9. Check system security. I suggest a periodic review of your server’s security using a remote auditing tool such as Nisus. Regular security audits serve as a check on system configuration, OS updates and other potential security risks
Re: Server security is ok or not.
Your CGI script receives encrypted data from the safe server. On the local side, data "comes out" of the secure server unencrypted. There is no difference between secure and conventional Web servers as far as a CGI script can tell. The data is "safe" once it has been delivered. That why it'a important.
