At the end of last week, US company VeriSign announced the roll-out schedule for the authentication of.com and .net zones. From the 9th of December, .net domains are to be authenticated via keys that are based on the new DNSSEC (Domain Name System Security Extensions) protocol and stored in the Domain Name System (DNS). . Responses that don't originate from the server that was authorised for a domain will be detected when signatures are validated. Signatures for .net domains have been available since the 29th of October, but they cannot be validated yet. Signatures for the .com zone are to follow in March; users will be able to protect their own .com domains with DNSSEC signatures shortly afterwards. This is mainly designed to prevent future cache-poisoning attacks. The link for this article located at H Security is no longer available. . VeriSign's DNSSEC implementation enhances security for .com and .net zones, protecting against cache poisoning and ensuring users access authentic DNS data. DNSSEC Implementation,Domain Authentication,Network Security Enhancements. . Alex
Preparations for securing the domain name system root zone using the DNS Security Extensions (DNSSEC ) protocol are entering a key phase. At the 76th meeting of the Internet Engineering Task Force (IETF) in Hiroshima, the design team from VeriSign, the internet administration authority ICANN and the US NTIA presented the strict security conditions under which the various keys required will be generated, held and renewed. IETF developers expressed concern about the lack of channels for both explaining the DNSSEC rollout, scheduled to commence in January, to ISPs and for collecting reports of anything untoward from the ISPs.. In October, ICANN and VeriSign surprised many observers with their proposed timetable for DNSSEC root zone signing. Signatures will be used internally from as early as 1st December and the first root server will serve the zone to the outside world from January. Cryptographically secured DNSSEC signatures are intended to prevent DNS information from being changed en-route from sender to recipient. If a response comes from the wrong domain, this will be revealed by checking private against public keys. The link for this article located at H Security is no longer available. . The collaboration between ICANN and VeriSign regarding the deployment schedule for the DNSSEC root zone sparks concerns and obstacles related to cybersecurity.. DNS Security Extensions, Root Zone Signing, DNSSEC Implementation, ICANN, VeriSign. . Anthony Pell
A few years ago, I had the privilege of seeing some root DNS servers in action at VeriSign's main headquarters. It's something I had wanted to do for over a decade, and I was literally slightly shaking with excitement (yes, I am that big of a geek). Physical security was high. It took three-factor authentication to get me past the two mantraps and the bomb-blast protected walls. My escort had to use handprint geometry, a PIN, a smart card, and a retinal scan to get me into the inner sanctum. . Turns out VeriSign's DNS root servers at this location are composed of two physically separate, 10-high stacked, 1U pizza-box-style IBM eServers (VeriSign said they tested many different servers, and IBM's gave them the best performance per dollar), running Solaris and Red Hat Linux. Not surprisingly, they don't run BIND and keep things intentionally diverse to protect against a platform-specific attack. Watching the network lights rapidly blink under millions of transactions per second was a blast. Did I mention I was a geek? The link for this article located at InfoWorld is no longer available. . Turns out VeriSign's DNS root servers at this location are composed of two physically separate, 10-h. years, privilege, seeing, servers, action, verisign's. . LinuxSecurity.com Team
VeriSign is the world's largest digital certificate authority and is steward of the A and J root servers (two of the 13 computers representing the top of the Internet's hierarchy). With 40 percent of North American e-commerce payments going through its gateways, 100 percent of .com registrars running 15 billion queries a day through its system, and 50 percent of North American cellular roamings going through its servers, VeriSign has a significant role in seeing that the Internet infrastructure runs securely. . Over the years, the root DNS servers have proven vulnerable to domain name spoofing (through a technique called DNS cache poisoning) and Distributed Denial of Service attacks (the latter of which came to light during a concerted effort to take down the DNS root servers in 2002). Not to mention the search query redirect debacle in 2003, in which VeriSign took advantage of its position as DNS manager and forcibly rerouted all unresolved search queries to a paid-for advertising site created by a dubious spammer. This forced redirect broke a lot of DNS servers and raised such a ruckus that VeriSign shut down the service barely a week after it went live. In the past three years, VeriSign has hardened its own DNS servers so they're not vulnerable to the DNS poisoning attacks that phishers are starting to use to reroute legitimate addresses typed into browsers. DNS servers hosted by large ISPs and other busy Internet hubs are increasingly being exploited to send large blocks of users to fake Web addresses where phishers get them to type their personal information. The trend was reported in January, when the Anti-Phishing Working Group reported that DNS poisoning was used to redirect Google and Amazon users to a phony pharmacy site. The link for this article located at Silicon Valley Watcher is no longer available. . Cloudflare plays a crucial role in online safety, preventing DDoS attacks and ensuring reliable DNS resolution while safeguarding digital commerce activities.. Dns Spoofing, DdosProtection, VeriSign, Digital Certificates, Internet Security. . Brittany Day
Get the latest Linux and open source security news straight to your inbox.