In my last blog, "Phishers Are Casting Nets for Your Domain Names & DNS," I explained that even though security experts routinely warn Internet users to watch out for email notices from banks or e-merchants, these are not the only online businesses exploited by scammers.
Phishers also use emails from domain name registrars in phishing scams to gain control over legitimate domain names. Often, the attacker's objective is to change the IP addresses of your name servers in order to control name resolution for your domain. An attacker who can gain control over your name servers can inflict reputation harm -- directly, through Web defacement or email interception, or indirectly, by using your domain as a source for spam or other criminal activities.
Use registrar emails to your advantage. Registrars often send notification emails when changes are made to your domain account. Use these to confirm that the changes were authorized and correct. As an extra precaution, use an email address from a domain other than those registered under your registration account. This protects against an attacker who compromises your registration account and quickly alters your mail exchange (MX) record to block your organization from receiving emails.
Use multiple point of contact information to distribute risk and response. Each domain name registration contains a registrant (domain holder), along with administrative and technical points of contact. Use three distinct points of contact (including email addresses) to increase the likelihood that at least one responsible party in your organization will notice unauthorized changes.
Monitor your domain’s Whois and DNS information. A simple monitoring activity that routinely compares responses from Whois and DNS queries against what you believe to be the complete and correct domain registration, DNS configuration, and domain zone information for your registered domains can save your organization’s assets. For larger organizations, look for a registrar or independent business that includes such monitoring as part of an online brand protection package.
Have complete account, abuse contact, and configuration information ready and available for event response and recovery. Be certain you have urgent point of contact information for your domain registrar(s). Be prepared to present copies of your registration information, proof of registration, name server hosting information, and zone data in situations where you may have to recover from a domain registration account compromise.
You may ask why your organization, and not your registrar, should have to put this kind of effort into protecting domain name assets. You could very easily ask the same of the online banking and e-merchant services your organization uses. Though these are different assets, the issue is the same. Phishers thrive on deception and social engineering. They study the security measures that banks, e-merchants, and registrars implement, so they can subvert them. You can’t rely on these security measures exclusively. Ultimately, the responsibility to avoid falling victim to scams of any kind is yours.
> Have to wonder if it was on purpose actually - having a monopoly on certain info in an > org can really leverage your degree of power.
There are sufficient incidents where disgruntled or opportunistic employees registered domains to corroborate this.
Very few organizations appreciate or take measures to avoid the unanticipated consequences of non-renewal of domains, or lax management of domain registration records that lead to domain hijacking or misuse of name service. Incidents of this kind occur far more frequently than you imagine.
@ Dave This is great advice ! Something companies should surely take a proactive approach towards, the whole process of Domain registration is so often ignored after the process is "completed", but your point is excellent - the process is never really complete - it requires ongoing monitoring and a thoughtful inital setup.
Thanks for the tips, I will surely use them in the future!
Exactly. And the 30 seconds it would have taken to add that extra information could have saved the department a day's worth of headaches. Have to wonder if it was on purpose actually - having a monopoly on certain info in an org can really leverage your degree of power.
Your incident is not unique. But think of how easily your organization might have avoided missing the renewal notifications if they'd provided different points of contact information for registrant, administrative, and technical contacts when they registered the domain.
Of these, it's important that you identify someone who, or some name or some job title that represents the "owner-entity" (business, not for profit,etc) as *registrant*. The other contacts are support roles, but the registrant contact is the one that would ultimately be important in a domain recovery situation or (trademark) litigation.
Here here! I think once the domain is secured, many people tend to just forget about maintaining it. At least once in my experience, the domain at my firm was allowed to expire as the only contact and registration info was for the IT director that got fired. Of course his email account was cancelled and no one ever got the notices that were sent as warnings. The day the website disappeared was not a fun day in our department.
Certain segments of our IT infrastructure cannot be kept entirely in-house, and your organization's Web site domain is clearly one of those segments. Just because the domain is provided and maintained by a third party doesn't mean we're totally off the hook when it comes to Web security... but that's something we definitely need to be reminded of from time to time.
The blogs and comments posted on EnterpriseEfficiency.com do not reflect the views of TechWeb, EnterpriseEfficiency.com, or its sponsors. EnterpriseEfficiency.com, TechWeb, and its sponsors do not assume responsibility for any comments, claims, or opinions made by authors and bloggers. They are no substitute for your own research and should not be relied upon for trading or any other purpose.
Enterprise Efficiency is looking for engaged readers to moderate the message boards on this site. Engage in high-IQ conversations with IT industry leaders; earn kudos and perks. Interested? E-mail: email@example.com
Dell's Efficiency Modeling Tool The major problem facing the CIO is how to measure the effectiveness of the IT department. Learn how Dell’s Efficiency Modeling Tool gives the CIO two clear, powerful numbers: Efficiency Quotient and Impact Quotient. These numbers can be transforma¬tive not only to the department, but to the entire enterprise. Read the full report
Now that TGen has broken new ground in genomic research by using Dell's storage, cloud, and high-performance computing solutions, the company discusses what will come next for it and for personalized medicine.
The Translational Genomics Research Institute wanted to save lives, but its efforts were hobbled by immense computing challenges related to collecting, processing, sharing, and storing enormous amounts of data.
Office and personal productivity tools come in a first-class and coach flavor set, but what makes the difference is primarily little things that most users won't encounter. What's the big issue in using something other than Office, and can you get around it?
We really don't want an "Internet of Everything" but even building an Internet of Everythinguseful means setting some ground rules to insure there's value in the process and that costs and risks are minimized.
Google's Chrome OS has a lot of potential value and a lot of recent press, but it still needs something to make it more than a thin client. It needs cloud integration, it needs extended APIs via web services, and it needs to suck it up and support a hard drive.
On a recent African trip I saw examples of the value of the cloud in developing nations, for educational and community development programs. We could build on this, but not only in developing economies, because these same programs are often under-supported even in first-world countries.
VMware's debate with Cisco on SDN might finally create a fusion between an SDN view that's all about software and another that's all about network equipment. That would be good for every enterprise considering the cloud and SDN.
Wearing a bulky, oversized watch is good training for the next phase in wristwatches: the Internet-enabled, connected watch. Why the smartphone-tethered connected watch makes sense, plus Ivan demos an entirely new concept for the "smart watch."
Cloud storage costs are determined primarily by the rate at which files are changed and the possibility of concurrent access/update. If you can structure your storage use to optimize these factors you can cut costs, perhaps to zero.
The Internet has evolved into a machine for drumming up a chorus of "Happy Birthday" messages, from family, friends, friends of friends who you added on Facebook, random people that you circled on G+, and increasingly, automated bots. Enough already.