![]() |
2007-12-12
, 16:24
|
Posts: 19 |
Thanked: 1 time |
Joined on Dec 2007
|
#32
|
![]() |
2007-12-12
, 16:35
|
Posts: 452 |
Thanked: 522 times |
Joined on Nov 2007
|
#33
|
djs: We had a developer with his own laptop PC. I'm not site support, so it's not my business... but I agreed with IT, it pissed them off to no end.
That said, depends on the business. This is a huge BPO, it *has* to be secure as there's credit card / personal info being dealt with. If it were a small design company or something (50-200 users), I'd have no qualms using my tablet for stuff.
(I'm seriously a huge proponent of Linux... but as much as I'd love to see it at work, I'd hate to as well.)
![]() |
2007-12-12
, 18:28
|
|
Posts: 1,361 |
Thanked: 115 times |
Joined on Oct 2005
@ Toronto, Ontario, Canada
|
#34
|
![]() |
2007-12-12
, 18:34
|
Posts: 452 |
Thanked: 522 times |
Joined on Nov 2007
|
#35
|
I will not, and have never written a 30 page diatribe to contain every possible angle to qualify things that I've said.
If you think you can sit back and tell me your Linux box is 100% secure and you're sure of that, then you're deluded
My IT regularly comes with me into the workplace. It only connects to the Wifi provided for clients that's solely an internet connection, nothing to do with our network.
Machines are locked with strict policies through AD to prevent agents from running anything that could conceivably help them scoop numbers/info.
And to the snotty developers getting their knickers in a knot.
1.) I resent the fact my work has to go to QA, I checked it myself.
2.) I argue a lot with QA
3.) When I get specs I try to improve them and sometimes that takes longer than the project initially allotted.
4.) I'm awesome, the organization couldn't survive without me.
5.) This is the only thing I'm good at, I suck in social situations, and I get my neck beard in a knot when people try to stymie my brilliant ideas. I know assembler you f*ck!!!
(P.S. I develop. I'm not site support. If you're going to make sweeping assumptions about me, let's at least get it in the right ballpark.)
![]() |
2007-12-12
, 18:39
|
|
Posts: 641 |
Thanked: 27 times |
Joined on Apr 2007
|
#36
|
![]() |
2007-12-12
, 19:16
|
Posts: 452 |
Thanked: 522 times |
Joined on Nov 2007
|
#37
|
I'm glad this took a turn for civility again. I'm actually not too paranoid about security, given the chance to use my tablet I would in a second. I'm arguing points on both side of the coin, and I'll (much to your dismay/mental health) regularly switch sides.(That's how I explore a topic fully.)
... but in your career paths, you've had to see the other side (which is what I was pointing my finger at). The developer who doesn't need admin rights for any reason but insists on them because it's an affront to his perceived intellect.
The one who wants to use his own machine for no other reason than to set his own standards and play by his own rules regardless of the impact it would have for another department
(say, the one charged with maintaining everything - - IT).
The one who comes up with ideas not because they're helpful but because they're grandiose and are a challenge as opposed to the usual daily code, and subsquently delays the project because rebuilding the wheel didn't work (like it didn't last time and the time before that).
It's been brought up before but in business it comes down to accountability. You might be frickin Linus Torvalds but if IT can't guarantee that your linux tablet is secure, they can't in good conscience allow it on the network.
(And in my specific case, all devs do have widescreen laptops which still kicked the crap out of that rogue machine specs-wise - - the guy was just being difficult and wanted to use the tools for his own on-the-side efforts.)
![]() |
2007-12-12
, 21:23
|
Posts: 19 |
Thanked: 1 time |
Joined on Dec 2007
|
#38
|
When it comes down to it, it's our (the IT folks) network. If there's an AUP stating you can't use a personal machine on the network, you're not using a personal machine on the network. If it states you can use a personal machine, but have to have one of our admin accounts installed on it and you don't want one of our accounts on it, it doesn't connect to the network. If we find that you have connected a personal machine to our network, it either gets confiscated, and you get to explain yourself to the director of technology, and/or, you find yourself a new job.
![]() |
2007-12-12
, 22:11
|
|
Posts: 574 |
Thanked: 166 times |
Joined on Oct 2007
@ BC, Canada
|
#39
|
It's not your network. It's the company's. Your job is making sure they can use the network to do theirs.
![]() |
2007-12-12
, 23:28
|
|
Posts: 1,361 |
Thanked: 115 times |
Joined on Oct 2005
@ Toronto, Ontario, Canada
|
#40
|
Hedge, thanks for initiating this discussion. It's a tough one certainly, but even the *difficult* posts are worth reading!
My 2cents: Security comes down to trusting people, and some businesses can 'afford' to do it, others simply can't. I work at a University where there are so many people, layers and devices that no 'security system' is sufficient for the whole. Breaches occur not just because people are malicious (which they can be) but because they are careless, lazy or both (which they are more likely to be