Protect Your Servers: Follow these Steps

If you're a small business, you may not have more than a server or two. But no matter how few or how many servers you are running, your network relies on them. They serve the applications or web pages or e-mail your team needs to do their jobs. They store valuable and/or confidential information resources. They provide a means for your customers to communicate with you, perhaps even purchase goods or services from you.

Basic Steps You Can Take

Many of the procedures already discussed will help protect your servers too. So if you haven't yet taken care of the following, make these steps a priority:

Step 1: Protect Your Desktops and Laptops

Step 2: Keep Your Data Safe

Step 3: Use the Internet Safely

Step 4: Protect Your Network

Even with those security measures addressed, there is more you can do to protect your servers.

1. Keep your servers in a safe place. Businesses must make sure that their servers are not vulnerable to physical calamities. Locate these machines in a secure, well-ventilated room, not in a hallway or under a desk where someone might inadvertently kick or spill coffee on them. Or mischievously tinker with them. Your server room should have no windows and a single door you can lock. Server cases should also be locked to prevent tampering with internal components. Know which employees have keys to the server room. You should also keep a record of the serial numbers of your servers, and mark them with your company information, so they can be identified and recovered if stolen.

2. Practice least privilege. With Windows 2000 Server, Windows Server 2003 and Small Business Server 2003, it is possible to assign users different permission levels. Rather than giving all users "Administrator" access - which is not a best practice for maintaining a secure environment for PCs or servers - you should use your servers to manage client PCs. Windows Servers can be configured to give individual users access to specific programs only, and to define which user privileges are allowed on the server. This ensures users can't make changes in areas that are critical to the server or client PC operation. It also prevents them from installing software that may introduce a virus or otherwise compromise the integrity of your network.

3. Understand your security options. Today's servers are more secure than ever, but the powerful security settings you find in Windows server products are only good if they are used appropriately and monitored aggressively. If your team doesn't have an IT specialist and/or expertise in security issues, consider hiring an outside consultant to work with you to appropriately protect your servers.

Source: Microsoft

Microsoft Fixed Windows 7 Holes with Security Updates

Microsoft stated that the critical fix was for just about every version of Windows, including Windows 2000, XP, Vista, Server 2003 and Server 2008. However, the software giant failed to mention that the update also was intended for Windows 7 under its "Affected Software" heading.

Microsoft did, however, mention that the update affected Windows 7 under the "Frequently Asked Questions" section. In addition to Windows 7, the patch repaired critical flaws in Windows Server 2008 Service Pack 2 Beta and Windows Vista Service Pack 2 Beta.

Altogether, the patch bundle resolved a total of four image vulnerabilities in the Windows kernel, the most serious of which could allow hackers to install malicious code on users' computers without any user intervention by enticing a victim to view a maliciously crafted EMF or WMF image file. The user could then download a Trojan or other piece of malware that would enable hackers to take complete control of the machine and steal sensitive data. Other vulnerabilities repaired by the update could leave the user susceptible to a denial of service attack.

Microsoft's March security update addressed two other security flaws, both deemed "important," that could allow hackers to spoof Web sites in identify theft schemes.

One of the flaws, occurring in the Windows DNS server and the Windows WINS server, could allow a remote attacker to redirect Web traffic to his or her own malicious Web site. Once users opened the maliciously crafted page, attackers could then entice users to submit sensitive password, credit card or bank account information for identity theft activities. Hackers also could infuse the page with malware designed to record keystrokes and steal information, security experts said.

The other "important" fix repaired a bug in the Windows Secure Channel security package that could allow miscreants to spoof a Web site by gaining access to the authentication credentials utilized by the end user.

Source: http://www.crn.com/security/215801984