Home / Blogs

Reducing the Risks of BYOD with DNS-Based Security Intelligence; Part 1: Understanding the Risks

Pat Barnes

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?)

But BYOD comes with challenges. Personal devices can be infected with malware. Once they're connected to an enterprise's network, they can be controlled by a bot master to hijack enterprise resources and wreak havoc as part of a botnet. The biggest risk is data exfiltration which can have serious consequences: loss of valuable intellectual property, unauthorized disclosure of personal and confidential information, and more.

Having mentioned bot masters and botnets, here's a primer on what these terms are. Many cyber criminals employ bot networks, commonly known as "botnets", as the instrument of choice to implement their malicious activities. Bots are simply software that runs autonomously over the Internet. Devices can be infected with malware that operates as a "bot", autonomously exploiting the network to conduct malicious activities. A botnet is a collection of bots in the control of a cyber criminal (the "bot master"). Botnets are used by cyber criminals for a variety of malicious purposes. For example, they might rent their botnet to perform distributed denial of service (DDoS) attacks against websites or they're tasked with penetrating enterprise defenses and looking for valuable data. Bot masters control botnets by providing them with instructions that dictate the malicious activities the bot undertakes. Bots receive instructions by communicating with a server controlled by the bot master, known as command and control (C&C).

What can an enterprise do? Should BYOD be banned? Not without revolt, likely. In part two I'll discuss a DNS-based approach you can use to reduce the risks of allowing BYOD on your network.

By Pat Barnes, Product Manager of Security Solutions at Nominum

Related topics: DNS, Security

WEEKLY WRAP — Get CircleID's Weekly Summary Report by Email:

Comments

Way too short - you might put a bit more than just the teaser paragraphs in, next time. Suresh Ramasubramanian  –  Jan 22, 2013 8:14 PM PDT

That said, yes, DNS jails, device firewall policies etc (and metrics from those) are absolutely necessary for byod deployment.

To post comments, please login or create an account.

Related Blogs

Related News

Topics

Industry Updates – Sponsored Posts

New gTLDs and Best Practices for Domain Management Policies (Video)

Nominum Announces Future Ready DNS

New from Verisign Labs - Measuring Privacy Disclosures in URL Query Strings

DotConnectAfrica Delegates Attend the Kenya Internet Governance Forum

3 Questions to Ask Your DNS Host about Lowering DDoS Risks

Continuing to Work in the Public Interest

Verisign Named to the OTA's 2014 Online Trust Honor Roll

4 Minutes Vs. 4 Hours: A Responder Explains Emergency DDoS Mitigation

Dyn Acquires Internet Intelligence Company, Renesys

Tips to Address New FFIEC DDoS Requirements

Smokescreening: Data Theft Makes DDoS More Dangerous

Introducing getdns: a Modern, Extensible, Open Source API for the DNS

Why We Decided to Stop Offering Free Accounts

dotStrategy Selects Neustar's Registry Threat Mitigation Services for .BUZZ Registry

Tony Kirsch Announced As Head of Global Consulting of ARI Registry Services

24 Million Home Routers Expose ISPs to Massive DNS-Based DDoS Attacks

Dyn Acquires Managed DNS Provider Nettica

What Does a DDoS Attack Look Like? (Watch First 3 Minutes of an Actual Attack)

Joining Forces to Advance Protection Against Growing Diversity of DDoS Attacks

Why Managed DNS Means Secure DNS

Sponsored Topics