Hi there Jay007. We have been talking about a lot of simliar things. A few of the things we recently talked about that relate to you may be these things...
1.) many of us use this little drive adaptor thing, you can plug it into the usb port of a linux/windows machine, then the other end has like 3 heads on it for different types of hard drives, like sata, versus IDE, etc. It has a power supply. What we do is leave the customers drive in the pc, and just reach in and unplug the power connector from the customers psu to the customers hard drive, and the data cable. Then we attach our device, and we can scan the drive from linux.
2.) If you can get the pc on the network. Some of us use switches & routers that have advanced capabilities, like setting up vlan's, and pvlans. All this means, is that if you buy one nice router, with say 24, 36, 48 ethernet connectors (or however many), that the nicer switches & routers let you stick like certain 'connections' in 'groups' and if you like, you can have multiple vlan's. Like accounting, lab, and internet. In my switch, I have the lab vlan set up so that ... one port is promiscuous and is attached to a lab server running linux with fprot for linux on it. This linux server has thousands of utilities on a partition. Now the customer computers are set up on 'isolated' ports (you click on this in the web interface of the switch, just select the port and click isolated). Anyway what winds up happening is that you can have say 5 or 10 client pc's all powered up on the net, and they can't cross infect each other. They can only talk to the linux server which of course is pretty much immune to windows virus and trojans.
so say on one switch have a vlan for (accounting/business) , another vlan for (internet), and a vlan for (lab). None of them can talk to each other, even though they are on the same switch. B/c I have put them in their own groups. The lab vlan is the part that has the linux server with utilities on it. so if I hook up 10 pc's from customers, each one of those pc's that is on the (lab) vlan is special case. Each customer pc cannot talk to any other customers pc. Each customers pc cannot talk to the (accounting vlan) or to the (internet vlan). The only computers are on the (lab) vlan are the linux server with all the utilities running a linux antivirus, and then there are connections of course for hooking up customers pc's. Customers pc's are on pvlans where the port for each customer pc is 'isolated' but the linux server with the utilities is marked as the 'promiscuous' port (in the switch web page), which means i can access whatever i need to fix each pc, without worrying that one customers pc will infect another customers pc, and etc...
Isolated ports in a vlan cant talk to each other, they can only talk to ethernet ports on the switch in the same vlan designated as community or as promiscuous
**In the unlikely event a very good hacker broke through your firewall, into your router, and launched a very sophisticated attack against you that would send isolated traffic to a different isolated port, this can be easily stopped by simply setting up a vlan access control list. According to cisco that causes the isolated ports to disregard all ip nat external traffic.