In part 1, I talked about some of the risks associated with BYOD. But there are actions you can take to greatly reduce this risk. One effective method for limiting the risk of BYOD is to employ DNS-based security intelligence techniques. DNS-based security intelligence makes use of an enterprise’s caching DNS server to monitor and block DNS queries to known botnet command and control (C&C) domains. These domains are the domain names of the servers that are in the control of the bot master for purposes of botnet command and control. Bots will perform a DNS query for one or more of these domains in an attempt to connect to these servers in order to receive their instructions. By monitoring queries to these domains, all infected clients, including BYOD, can be identified on the network. Moreover, by subsequently blocking access to the domains, malware responsible for the bot infection is denied the critical instructions it needs to function.
Ah, BYOD. How I love thee.
BYOD, or “Bring Your Own Device”, gives me choices. I can use a device at work I actually like and am most effective with. (How did I ever get by without my iPad?)
The number of ‘things’ connected to the internet is already bypassing the number of people on the planet. This Internet of ‘things’ is changing the way we live and work: from the way food is grown and produced on farms through automated temperature and feeding controls, to the way we check prices and buy through connected terminals, to the vehicles we drive, the security cameras at work, and automated gates at the entrance. Connected ‘things’ are everywhere. All these ‘things’ are helping us to be more productive and efficient while also offering more and more convenience.
Last month Microsoft led an effort to take control of a domain – 3322.org – in order to disrupt more than 500 different strains of malware affecting millions of innocent people around the world. Using a surgical approach implemented with software from Nominum, Microsoft was able to sinkhole traffic to malware subdomains hosted on 3322.org without impacting queries to legitimate subdomains. Numerous articles covered the effort; some of the better ones are below:
One of the challenges network operators face is responding quickly to market requirements. Agility is the new normal, competitive leadership is based on moving quickly. But progress can be slowed by the disparate interests of marketing or business teams, and technical or operational teams. Marketing can spot trends and identify new services, but it can be difficult to get them implemented quickly in the network when stability is rightfully paramount.
Ten years ago everyone evaluating DNS solutions was always concerned about performance. Broadband networks were getting faster, providers were serving more users, and web pages and applications increasingly stressed the DNS. Viruses were a factor too as they could rapidly become the straw that broke the camel’s back of a large ISP’s DNS servers. The last thing a provider needed was a bottleneck, so DNS resolution speed became more and more visible, and performance was everything.
The transition to IPv6 is top of mind for most service providers. Even in places where there are still IPv4 addresses to be had surveys we’ve run suggest v6 is solidly on the priority list. That’s not to say everyone has the same strategy. Depending where you are in the world transition options are different – in places such as APAC where exhaustion is at hand one of the many NAT alternatives will likely be deployed since getting a significant allocation of addresses is not going to happen and other alternatives for obtaining addresses will prove expensive. Ditto the European region, who is next on the list to find the IPv4 shelves bare.
With IPv6 World Launch coming up it’s worth pausing to consider the collective efforts of the Internet industry in enabling and deploying an essential evolutionary technology at what will become truly massive scale. It’s easy to be a detractor and believe there has been little progress – but the Internet hasn’t melted down and there is no evidence it is about to. Perhaps the issue is that progress occurred in a different way than was predicted or preferred by the experts. The reality is providers everywhere have developed coping mechanisms for IPv4 exhaustion. Innovation, operational sweat, and perhaps some tough negotiating make it happen. But isn’t that the essence of the Internet?