LinuxSecurity.com
Share your story
The central voice for Linux and Open Source security news
Home News Topics Advisories HOWTOs Features Newsletters About Register

Welcome!
Sign up!
EnGarde Community
Login
Polls
What is the most important Linux security technology?
 
Advisories
Community
Linux Events
Linux User Groups
Link to Us
Security Center
Book Reviews
Security Dictionary
Security Tips
SELinux
White Papers
Featured Blogs
All About Linux
DanWalsh LiveJournal
Securitydistro
Latest Newsletters
Linux Advisory Watch: August 15th, 2014
Linux Advisory Watch: August 8th, 2014
Subscribe
LinuxSecurity Newsletters
E-mail:
Choose Lists:
About our Newsletters
RSS Feeds
Get the LinuxSecurity news you want faster with RSS
Powered By

  
Letting The Telecommuters Into The Network Print E-mail
User Rating:      How can I rate this item?
Source: Rebecca Rohan - Posted by Joe Shakespeare   
Network Security Locking down the network and patrolling the perimeter is a never-ending job. Still, it feels good to get through another shift on the Forbidden Planet without an invisible force penetrating your shield and setting off alarms. But there's a change: now, other humans want to work from their home worlds -- but by mind alone, over the computer screen. It's up to you to create for them a safe passage (one that won't have Robby the Robot all stirred up and carrying Anne Francis around like a rag doll) and to make sure the Krell don't come sneaking in, under the fence, behind the newcomers.

In other words, you need to let the right people into your network -- telecommuters and other people working remotely -- while continuing to protect the company from criminals. What to do?

The Number One Answer: A Sit-Down VPN
The answer that helps administrators sleep most securely is a fixed Virtual Private Network (VPN). A VPN uses end-to-end encryption to carve out a private tunnel over the public network.

The most secure VPN is the traditional arrangement with the telecommuter coming from a fixed site, ideally using a managed, corporate device, and terminating in a secure, private network on either side. Quite a bit of effort can go into setting up this arrangement; you need to see that hardware, software, and settings, as well as authentication, are set up perfectly and maintained on both ends, despite user changes to software, firmware, and hardware, but the security can be worth the trouble.

Don't let this next bit scare you away: After the act with all the acronyms, you'll have the secret of the monster sneaking past the alarms, and everything lightens up.

Let's throw out some protocols -- literally. There are three or four at this end of the pool. Only one from this group is secure enough to take seriously: IPSec, especially in conjunction with L2TP.

Read this full article at Rebecca Rohan

Only registered users can write comments.
Please login or register.

Powered by AkoComment!

 
< Prev   Next >
    
Partner

 

Latest Features
Peter Smith Releases Linux Network Security Online
Securing a Linux Web Server
Password guessing with Medusa 2.0
Password guessing as an attack vector
Squid and Digest Authentication
Squid and Basic Authentication
Demystifying the Chinese Hacking Industry: Earning 6 Million a Night
Free Online security course (LearnSIA) - A Call for Help
What You Need to Know About Linux Rootkits
Review: A Practical Guide to Fedora and Red Hat Enterprise Linux - Fifth Edition
Yesterday's Edition
Google Fixes 12 Vulnerabilities in Chrome 36
Partner Sponsor

Community | HOWTOs | Blogs | Features | Book Reviews | Networking
 Security Projects |  Latest News |  Newsletters |  SELinux |  Privacy |  Home
 Hardening |   About Us |   Advertise |   Legal Notice |   RSS |   Guardian Digital
(c)Copyright 2014 Guardian Digital, Inc. All rights reserved.