Gazoo: *thank you*

Bleek: Actually, I have nothing to do with operations or site support. In fact, my title was SQL developer and I dealt with report development (where my innovative ideas to make 75 min reports run in 5 mins *were* squashed), and worked closely with the guys who did the Java front end stuff for the dialer. My work issued laptop was actually beefier than the one the guy was using. (My guess is he wanted our software licenses to do freelance work on the side, which he did.)

Asking someone to use a work issued laptop doesn't stifle innovation, at least I can't think of many cases where it would. What it *does* do is bring uncertainty into the realm of security and as I said we were dealing with credit card numbers and personal information. *THE* reason for disallowing personal machines is accountability. If anything happened the company would be held responsible and I don't think a certain credit card company whose cards live in many of our pockets would appreciate knowing the source of the breach was a personal laptop being used in the workplace. The company is accountable regardless, but the company should be accountable on it's own terms. There's also the issue of data security once said employee rolls out to greener pastures. How can you ensure your data doesn't reside on that machine?