But sometimes your requirements demand protection across a broader range of connections, because sometimes you’ve got different kinds of work to do.į’rinstance? Some members of your team need to work from the road using public WiFi hotspots. SSH and SCP can protect data transferred through remote connections (chapter 3), file encryption can protect data at rest (chapter 8), and TLS/SSL certificates can protect data in transit between websites and client browsers (chapter 9). My Linux in Action book - from which this article is excerpted - talks a lot about encryption. Specifically, using encryption to build a virtual private network (VPN) tunnel to permit secure and invisible remote connections. So here’s where you’ll learn about _adding new_ layers of protection for your remote activities. In fact, there are all kinds of technologies devoted to securing network communication, and the principle of _defence in depth_ teaches us that you should never rely on just one. VPNs, by sharp contrast, focus on making sure that the data consumed by your remote clients is reliably transferred and invisible to anyone who might be lurking on the connecting network. Website encryption is about making sure that the data consumed by your remote clients is reliably transferred and invisible to anyone who might be lurking on the connecting network. And given that the public networks through which you access those remote locations are by their nature insecure, you’re going to want to carefully control those connections. Almost everyone whose work touches IT will access their professional tools from remote locations from time to time. But of course I only get to enjoy the comforts of my home office because all the server resources I could possibly need are available remotely.Īpparently I’m not alone. Not that I’d know: I rarely leave my home office. They tell us we live in a hyper-mobile world.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |