O mercado está muito preocupado com os últimos ataques disparados por grupos como o Lulzsec e o Anonymous. Milhares de dados foram furtados e divulgados em menos de 3 meses e a tendência é que isso aumente.
Os principais alvos destes grupos são empresas governamentais, que estejam na mídia e grandes portais, mas quem sofre no final com isso tudo são pessoas como você e eu, aquelas que cuidam da administração destes servidores e acompanham as últimas novidades, tanto defensivas como de ataque. Precisamos saber onde estamos pisando, correto ?
Pois bem, acabei encontrando uma lista de recomendações /hardering/para servidores, principalmente para ambientes web.
Vale a dica:
- Deploy a Host Intrusion Detection System (HIDS) to help block and identify common attacks.
- Use an application proxy in front of web servers to filter out malicious requests.
- Ensure that the “allow URL_fopen” is disabled on the web server to help limit PHP vulnerabilities from remote file inclusion attacks.
- Limit the use of dynamic SQL code by using prepared statements, queries with parameters, or stored procedures whenever possible. Information on SQL injections is available here.
- Follow the best practices for secure coding and input validation, use the secure coding guidelines.
- Review US-CERT documentation regarding distributed DoS attacks here and here.
- Disable active scripting support in email attachments unless required to perform daily duties.
- Consider adding the following measures to your password and account protection plan.* Use a two factor authentication method for accessing privileged root level accounts.
- Use minimum password length of 15 characters for administrator accounts.
- Require the use of alphanumeric passwords and symbols.
- Enable password history limits to prevent the reuse of previous passwords.
- Prevent the use of personal information as password such as phone numbers and dates of birth.
- Require recurring password changes every 60-90 days.
- Deploy NTLMv2 as the minimum authentication method and disable the use of LAN Managed passwords.
- Use minimum password length of 8 characters for standard users.
- Disable local machine credential caching if not required through the use of Group Policy Object (GPO).
- Deploy a secure password storage policy that provides password encryption.
- If an administrator account is compromised, change the password immediately to prevent continued exploitation. Changes to administrator account passwords should only be made from systems that are verified to be clean and free from malware.
- Implement guidance and policy to restrict the use of personal equipment for processing or accessing official data or systems (e.g., working from home or using a personal device while at the office).
- Develop policies to carefully limit the use of all removable media devices, except where there is a documented valid business case for its use. These business cases should be approved by the organization with guidelines for there use.
- Implement guidance and policies to limit the use of social networking services at work, such as personal email, instant messaging, Facebook, Twitter, etc., except where there is a valid approved business case for its use.
- Adhere to network security best practices.
- Implement recurrent training to educate users about the dangers involved in opening unsolicited emails and clicking on links or attachments from unknown sources. Refer to NIST SP 800-50 for additional guidance.
- Require users to complete the agency’s “acceptable use policy” training course (to include social engineering sites and non-work related uses) on a recurring basis.
- Ensure that all systems have up-to-date patches from reliable sources. Remember to scan or hash validate for viruses or modifications as part of the update process.