- WINDOWS SERVER 2008 SECURITY CENTER PATCH
- WINDOWS SERVER 2008 SECURITY CENTER SOFTWARE
- WINDOWS SERVER 2008 SECURITY CENTER WINDOWS 7
- WINDOWS SERVER 2008 SECURITY CENTER WINDOWS
WINDOWS SERVER 2008 SECURITY CENTER WINDOWS
WINDOWS SERVER 2008 SECURITY CENTER WINDOWS 7
Torvalds offers a thumbs-up to Windows 7.Are you ready for Windows 7 and Windows Server 2008 R2?.
WINDOWS SERVER 2008 SECURITY CENTER SOFTWARE
Windows Server 2008 R2: Security Changes and Additions Part III.The plot of this novella of a guide may not be gripping, but better Web security does promise a happy ending. This 85 page how-to guide is offers a nice overview of the entire process of setting up DNSSEC on Windows Server. To that end last week Microsoft released a Windows Server 2008 R2 deployment guide. If all this sounds complicated that's because it is. This technology is currently being tested to ensure the maximum compatibility with current Internet infrastructure and aims to play a continuing role in securing DNS data in the future." "Windows 7 is the first client operating system to include the necessary pieces to allow the client to verify that it is communicating securely with a DNS server and verify that the server has performed DNSSEC validation on its behalf. Basically, a server will be able to attach digital signatures to DNS data in responses as well as validate data received from other DNS servers. Windows Server 2008 R2 will allow the DNS Server to provide origin authority and data integrity artifacts. "Windows Server 2008 R2 and Windows 7 introduce support for DNSSEC as per the current standards (RFC 4033, RFC 4034, and RFC 4035). A TechNet article from May that lists all of the security features in Windows 7 puts it this way: Similarly, the Windows 7 client includes what it needs to validate that it is communicating with a server using DNSSEC and that said server has completed a validation process. With DNSSEC support, network administrators can use a Windows Server machine to generate keys and to validate that file being requested by servers over the Web are being sent by a trusted source. The previous version of Windows Server 2008 did artistically support this security protocol, but WS2008 R2 is the first Microsoft server operating system to be fully compliant the current standards (The IETF's RFC 4033, RFC 4034, and RFC 4035). ICANN is expected to start rolling out changes in January 2010 to the root zone that will let DNSSEC be applied, even in developing areas of the world, such as the countries of Africa, source of so much Nigerian spam, reports Computerworld.
Obviously, issues abound with rolling out such a fix, among them a lack of servers and clients that supported DNSSEC. DNSSEC applies the old public/private key cryptography trick to solve the DNS problem.
WINDOWS SERVER 2008 SECURITY CENTER PATCH
But even a year after that historic patch security experts said that DNS still needed to be more secure. In response to that flaw, for the first time, vendors such as Microsoft, Sun and Cisco banded together together to close the flaw. Better still, Windows 7 also supports DNSSEC, which Microsoft claims is a first among client operating systems.ĭNSSEC had been bandied about the IETF for years but came into the public eye in July, 2008, when security researcher Dan Kaminsky disclosed a serious flaw in the DNS that makes it possible for hackers to launch DNS cache poisoning attacks. DNSSEC is a security protocol that helps to verify that a Web address hasn't been hacked and redirected to a pretender.
As promised, the latest version of Windows Server 2008 R2 is the first Windows Server to fully support DNSSEC.
0 kommentar(er)
