Dealing with coworkers who ask for support of their home computing setups is a hazard or working in IT. It is difficult particularly to answer an executive who wants help with their home computer or network and asks you for help. There's no good answer for those issues, unless you have a written company policy that addresses them. But regarding connecting a home computer to the company network, here's what I have worked out.
I work for a large nonprofit that is affected by HIPAA, as well as California's SB1386 law. The legal requirements of those laws (and others) make the connection of a HOME network/computer a security policy matter. As of now, my response is that any computer that connects to the network, either remotely or locally, is subject to the same restrictions, and we do not support home computers per se. We have a tiny IT department (myself and 2 others) to support almost 300 computers at 25 sites, spread out over a geographical area from Monterey to Menlo Park, California. So we can't afford to have a large, widespread outbreak that could occur if a home computer connected to our network and allowed malware to infect our servers. We also can't afford to support home systems with such a small staff. It is the responsibility of any staff person who wants to connect their home computer to our network, to bring it up to organizational security standards. And it is a simple matter to say to any user asking for home support that since the organization doesn't own the computer, we can't charge the cost of support to a cost center. Another reason is as follows.
We are fairly well protected by Symantec Antivirus Corporate from Viruses, but that does not prevent spyware, adware, and trojans from infecting machines, as most IT people are aware by now. We now have Pestpatrol Corporate, to clean a wide variety of this malware from machines remotely.
The danger in connecting home machines is this: since home machines are often used by everyone in the household for random internet browsing, they pick up a great deal of spyware, adware and trojans. My nightmare is to have a home machine bring down the network by connecting and infecting our central servers. That would fall under the category of the 60%-90% (depending on who is talking) of security issues that are internally caused, rather than external hackers trying to break into the network. I regard "internal" issues as including those where the user has bypassed the firewall & antivirus by bringing in malware by their internet use.
To summarize, the danger of connecting home computers to a corporate network is fairly high, without strict standards, and support of home computers must be a cost-related issue. Hope this helps.
Thanks
So in the interests of preventing infection of our network servers by home users, I insist on having any user with a home computer that they want to remotely connect to the network make it as well-protected and cleaned up as we try to keep the organization's business desktops. I have found that a good demonstration of how much spyware has taken hold of a user's computer goes a long way to overcoming objections to