Both Linux and Windows are here to stay. The decision to deploy a Linux or a Windows server should be based on a careful evaluation of both technical and business needs. For smaller companies with in-house Windows skills, moving to Linux or implementing Linux alongside Windows could cause more headaches and staff issues than value. For larger companies with sufficient staff and training budgets, implementing Linux-based servers may prove cost-effective in the long-term. . An important consideration for any Linux implementation is the availability of support, documentation, and third-party conversion and interoperability tools. Without these, firms face increased costs and exposure to increased downtime as staff struggle to find fixes and solutions. It is also important to remember that creating a more secure Linux environment will probably involve the purchase of third-party security products to augment Linux's security features. And if Linux is being installed with existing Windows servers, third-party integration tools also may be required. The link for this article located at SecuritySearch is no longer available. . Assessing the choice between Unix-like systems and Microsoft Windows for server implementation involves analyzing aspects like compatibility, financial factors, and protection protocols.. Linux Implementation, Windows Servers, IT Support Costs. . LinuxSecurity.com Team
DNSSEC, which stands for DNS Security Extensions, is a method by which DNS servers can verify that DNS data is coming from the correct place, and that the response is unadulterated. In this article we will discuss what DNSSEC can and cannot do, and then show a simple ISC Bind 9.3.x configuration example. . DNSSEC is a public/private key system. This means that the owner of a DNS zone has a private key and a public key. Using the private key to digitally sign a zone will allow anyone with the zone's public key to verify that the data is authentic. As with all public key crypto systems, the method by which the entire world obtains your public key is a problem. If an attacker can intercept the transmission of your public key, the entire zone is compromised, so sending keys via email or other Internet vehicles probably isn't a good idea. The proposed solution to the basic key management problem is to have Network Solutions sign everyone's public key. For example; myname.com will create a key, sign it, and then send it to Network Solutions for signing. DNS servers around the world who have Network Solutions' key are now able to reject DNS records about myname.com that aren't accompanied by the appropriate signatures. This is the proposed method for global DNSSEC. It hasn't happened. There is no Network Solutions key that everyone knows, and Network Solutions has no mechanism to gather *.com keys. The highest level domain, '.' (dot), also needs to be under some administrative control. IANA or ICANN can hold this key, and sign all TLD's (.com, .org, etc), but the political mess this would create puts the implementation a long ways off. Whether the U.S. holds the key to the entire Internet or not, someone must before DNSSEC can work globally. Until this is in place, DNSSEC cannot protect anything outside your administrative control or access; meaning you have to manually distribute keys. The link for this article located at Enterprise Networking Planet is no longer available. . DNSSEC is apublic/private key system. This means that the owner of a DNS zone has a private key and. which, dnssec, stands, security, extensions, method, servers, verify. . Brittany Day
DNS is a heavily used protocol on the Internet yet has numerous security considerations. This paper whilst containing nothing new on DNS security brings together in one document many strands of DNS security which has been published and reported in many . . . . DNS is a heavily used protocol on the Internet yet has numerous security considerations. This paper whilst containing nothing new on DNS security brings together in one document many strands of DNS security which has been published and reported in many separate publications before. As such this document intends to act as a single point of reference for DNS security. The link for this article located at Help Net Security is no longer available. . The Domain Name System (DNS) is vital for internet functionality but poses various security risks to networks. This guide details DNS security threats and effective mitigation strategies. DNS Security, Network Threats, Security Protocols. . Anthony Pell
Get the latest Linux and open source security news straight to your inbox.