![]()
Pop Quiz. Do you know how many USB flash drives and other non-sanctioned devices are plugged into your network at this precise moment? Do you know where they are? Where they’ve come from? Where they’ll go when they leave? Do you know what will be on them? Or what they might have left behind?
Thought not. And for the uninitiated, that’s the perfect business case for End-Point security – the first in iQ’s Piece of Cake series...
What’s the problem?
End-points – essentially all end-user devices and their ports – are a network’s frontier; the least guarded and therefore the most vulnerable places in the infrastructure.
are small (and so easy to conceal), cheap, and abundant; they can also hold huge amounts of data whilst arousing zero suspicion. In other words USB drives are ideal for smuggling data and applications out of – or even into – a business. Your customer database could leave the network, or a Trojan could enter it, completely undetected having simply bypassed your state-of-the-art and hugely expensive security perimeter, including firewall, IDS, IPS and everything else. It’s like closing, locking, dead-bolting, and alarming all your doors and windows but leaving your back door wide open.
part of their jobs.
and competitive edge there’s no business to protect in the first place. It is all too easy for security and operations departments to end up on opposite sides of this divide. What do I do about it? There are several immediate steps the concerned business should take to protect end-point desktops, laptops, and file servers.
1. Develop an end-point security policy -First get a clear picture of your potential threats and vulnerabilities by reviewing the status of all end-points, internal and remote. What’s running? What’s being accessed? What attacks are taking place, and where are you most vulnerable to them? 2. Decide on your approach I. Point solutions Deploying point solutions may solve the immediate problem, but it doesn’t constitute and end-point security policy. With IT forced implement and manage disparate, uncomplimentary solutions, it is often very time-consuming and costly too. II. Least possible user privileges This provides good short-term security benefits, but carries a number of drawbacks – particularly in terms of flexibility and administrative burden – with end-users often needing special assistance to meet even their most basic needs. Many blanket lock-down approaches fail for this reason. III. Build a real-world, business specific model based on live usage data. 3. Translate your policy into technical procedures and activities... ... which must then be constantly reviewed, refined, and adjusted. Administrators might not like it, but it’s good security practice. A one-size-fits-all approach rarely works however, especially with so many different devices now being used for network access. 4. Enforce and manage these centrally For true control, your strategy needs to be centrally managed and administered, but it must also be granular, malleable, wide reaching, and as automated as possible in order to reflect changes in the business and its threat profile. 5. Take a stance on user privileges... ... but don’t be too miserly. Managing the types of activities performed on a particular machine, and the apps and resources it can access is generally a more sensible approach than total lock down. It tends to be more secure because it actively manages rather than passively disables. It also drives greater asset utilisation and end user flexibility. 6. Enforce them |
|




