While we at CDW are in the business of providing IT solutions and services to our customers, behind the scenes we deal with the same operational issues that other enterprises face. Earlier this year, our leadership made the decision to close our offices and arrange for all non-essential CDW coworkers to start working remotely.

Over the course of a weekend, our Information Technology teams gained firsthand knowledge of what our customers were either already going through or soon going to be. It was a tall order to tackle the enterprise networking, storage, security, collaboration and communication needs to allow 7,100 coworkers to work from home, but our teams rose to the task. Now, we’re sharing our experience with our customers.

As organizations across the country have moved to remote work models, many have reported an increase in cyberattacks. Cybercriminals, it seems, are taking advantage of the public health crisis to exploit security vulnerabilities in home-based computer systems. What can organizations do to minimize the chances that their shift to remote work results in an expensive breach? We recommend a multipronged approach that combines the use of security tools and end-user education.

The fact that compliance efforts can be challenging is no surprise to IT professionals and managers. Today’s regulatory environment is full of security and privacy regulations that place strict limits on the collection, handling and storage of sensitive information, and IT teams often find themselves responsible for the heavy lifting of compliance programs.

I recently had the opportunity to visit with a retailer that operates a large contact center to support its international chain of stores. The company was in the early stages of reviewing its compliance obligations and asked us to find ways to modify business practices to reduce the scope of its compliance efforts. After reviewing the company’s activities, we discovered a few small changes in the way the company handles information that could dramatically reduce its compliance burden. Organizations across industries can draw lessons from this experience as they seek to reduce their own costs of compliance.

The global pandemic and social distancing measures have redefined the office for many people. Industries that never would have considered allowing their office employees to work from home were forced to rethink decades of business as usual.

This change has also brought new technology needs. Since these businesses had built technology infrastructures that relied on traditional network and application architecture, a shift had to occur. Suddenly, IT departments were dealing with overloaded VPNs or having to deploy a VPN that they never had to maintain before. Compound that with the fact that users are now accessing company resources from networks or assets that corporate IT has no control over, that most home routers are still vulnerable to exploitation and that, in many cases, the network gates were flung open in the name of productivity ― it’s enough to give any CISO an ulcer.

So how can companies mitigate these risks? Now that everyone is settling into a routine and we’re adjusting to this “new normal,” it’s an ideal time to reach out to your users and talk about security.

In my work with CDW customers, I often come across technology leaders who want to improve their cybersecurity posture but aren’t really sure where to start. They might recognize that their organizations need to improve their cybersecurity controls but don’t know where their investments will pay off the most.

When I hear concerns like this, I immediately look to the Cybersecurity Framework (CSF) developed by the National Institute of Standards and Technology (NIST). While there are many different cybersecurity standards out there, I prefer this one because it uses plain language to describe the five most important activities in cybersecurity. I’d like to walk you through this framework using two different examples.

Is Microsoft a security company? The idea has been on my mind for a while. I think back to the days of my early Microsoft experiences. For me, that would be Windows 3.1 and DOS 5.0 up to DOS 6.22. It was the base of my conquest for co-sysop on a few dial-up BBSs (bulletin boards), getting really good download ratios, and finding all the sweet “warez”. I was also digging through every inch of my computer. Today, in my role as a Microsoft 365 pre-sales architect, I give even more thought to the security aspects of Microsoft’s environment.