Security Reminder, or Who's That Looking Over Your Shoulder?

It doesn't matter which coffee shop -- Henry's, Z's, or the Bourgeois Pig -- I end up at, it's always the same ever since free WiFi came on the scene. There are more laptops than coffee mugs, and never enough places to sit. But I'm as bad as the rest. What with free wireless Internet access and a cell phone, well, I haven't been in the office for year or so now, and even the concept of a home-office is becoming more remote.

That said, I'm still careful about whose looking over my shoulder (especially at the Pig) and what kind of data I'm exchanging with whom. There's always a risk inherent in remote access, which is why the National Institute of Standards and Technology (NIST) has updated its guides for maintaining security while teleworking.

The updated draft version of Guide to Enterprise Telework and Remote Access Security is primarily intended for large organizations (like government agencies), while the Guide to Securing External Devices for Telework and Remote Access targets individual users on securing their own mobile devices. Both guides are prudent reading and good reminders for anyone telecommuting from public locations.

Most of the recommendations are common-sense suggestions, such as turning off or disabling not in use built-in wireless access points, changing the default SSID, or using strong encryption. But above all, says Karen Scarfone, a co-author of the guide and a member of NIST's Computer Security Division, you should be to expect trouble and plan for it.

"You should assume external environments contain hostile threats," explains Scarfone. Right. And know who is looking over your shoulder at the coffee shop.

Parallel Pattern 5: Stencil
All memory addresses used for reads are expressed as offsets
Distributing Work Across Cores Using .NET
A roll-your-own ThreadPool implementation
Looking For The Lost Packets: Part 2
Looking For The Lost Packets: Part 1

Real World Parallelism Webinar Series
  • February 18, 2010
    Lock Contention, Using Intel Parallel Studio to Improve Performance
    Speaker: Vasanth Tovinkere, Software Engineer, Intel Corporation (Bio)

    Vasanth Tovinkere is a software engineer in the Developer Products Division (DPD) at Intel. His current role involves defining novel approaches to understanding and visualizing parallel performance and consulting with strategic customers to help them prepare and deliver code for the multicore world. Vasanth has been involved in the development of automatic semantic event detectors for digital sports technologies in Intel Labs. He also has been awarded three patents and has two patents pending.

    Abstract:
    Discover how easy it is to use the power of Microsoft Visual Studio and Intel Parallel Studio to find performance issues due to lock contention in threaded applications. This ensures that shipped applications can take better advantage of multicore processors. In this webcast, we provide live demonstrations that show how to identify lock contentions issues with Visual Studio and Intel Parallel Studio, an add-in to Visual Studio that helps developers create fast, reliable code on multicore processors.t.