IT admins (and those involved in a company’s security) should be fired for deploying under-configured or misconfigured Windows installations on computers.
Microsoft in general should be fired from computers - their security is absolute garbage.
IT admins (and those involved in a company’s security) should be fired for deploying under-configured or misconfigured Windows installations on computers.
I kinda want to see you argue this one. With pop-corn.
There is a high skill level needed to configure Windows properly in enterprise settings. Regardless, I wouldn’t be working for an organization that trusts any Microsoft software.
Keep your popcorn ready though, it’s only a matter of time before Microsoft loses the security battle - unless Microsoft makes gigantic strides in a more sustainable direction.
I think their performance is relevant. Why would an employee be able to easily run an unknown binary from the internet to begin with? If the systems were properly configured to block this, there would be no issue. If I were an executive, I would absolutely be looking at my IT team in this case.
If the employee went entirely out of their way to run an unknown binary, bypassing OS-level restrictions, and sidestepping established procedures - then the employee should be fired.
You really are not familiar with the concepts of company policy and liability, are you? Whether there is an effective technical restriction in place is relevant to the question “can you run the thing”. It is irrelevant for the question “did you circumvent company policy?” and, subsequently, to the blame/firing that comes from it.
This is the exact same discussion people keep having about “government can’t block VPN” or “encryption can’t be broken” when the idea of a law forcing backdoors in services floats around. Sure, you can still use encryption, technically. But if there’s a law that say “encryption too strong to be broken is illegal”, then you’ll get arrested all the same, effective technical restriction or not.
I’m well-aware of how corporate policy, liability, and hierarchy works - the issue with your take is that you act like the IT team is innocent to somebody higher up on the ladder. My issue isn’t with the concept of policy itself (and the enforcement thereof) and the issue of liability, but with the misplaced absolution of IT teams from any responsibility when things go wrong.
IT teams are essentially the secret police in companies. I’m aware of how they usually function. I’ve heard many first-hand accounts from those behind the big screens making sure Bob doesn’t watch porn or that somebody doesn’t do something unauthorized with company computers. I’m unimpressed and it’s frankly a dystopian twist of what IT actually should be; which is best serving a company’s technical needs collaboratively - not roleplaying as the NSA.
It effectively shouldn’t be possible for Bob to watch porn on company devices/internet. It shouldn’t be possible or desirable for somebody to skirt policy to run binaries (even on a whim) for software they feel that they require for maximum productivity. There should be reasonable, timely, and accessible procedures for employees to request necessary software to be deployed.
If I recall correctly in another part of the thread, a user discussed a group of employees (including themselves) needing WSL for job duties and it being blocked without notice. This is an example of sheer incompetence of the IT team - blocking necessary software and failing to maintain/establish timely and accessible procedures to contest a block as an employee who needs specific software to function in their job.
Required software should never be blocked - so who is at fault? Who caused the most damage to the company? The people attempting to work? Or the people who have no idea what they’re doing; making employees feel they need to completely disregard them to function in their duties - the people sabotaging operations?
You’re free to fantasize about the little guy as the only one getting disciplined in these scenarios. I’m sure most corporate environments do work like that, but it just protects incompetency - unless, again, the employee went out of their way to run the binary in an abnormal way or otherwise had less than ideal intentions.
You’re free to fantasize about the little guy as the only one getting disciplined in these scenarios
I never, not once, implied that. And frankly speaking I have no idea why you would think that. I said that a user, circumventing a company policy, would be in a tight spot, and depending on the policy most likely fired, regardless of the actual effectiveness of these policies implementation.
At no point have I said that nobody else would be in hot water for failing to do their job, nor did I say that the IT teams is above all and always perfect. But, for the user that did go around the aforementioned policy, the fate of someone else on another team is pretty much irrelevant after they’re put down themselves.
That excuse won’t stop them from being fired. Just because you can does not mean you should.
Knowledge is knowing how to bypass work restrictions. Wisdom is knowing not to.
Just because I shouldn’t doesn’t mean I shouldn’t.
IT admins (and those involved in a company’s security) should be fired for deploying under-configured or misconfigured Windows installations on computers.
Microsoft in general should be fired from computers - their security is absolute garbage.
I kinda want to see you argue this one. With pop-corn.
There is a high skill level needed to configure Windows properly in enterprise settings. Regardless, I wouldn’t be working for an organization that trusts any Microsoft software.
Keep your popcorn ready though, it’s only a matter of time before Microsoft loses the security battle - unless Microsoft makes gigantic strides in a more sustainable direction.
Irrelevant. The defense of “they should do better” will do jack to prevent the firing of someone that willfully circumvented company policy.
I think their performance is relevant. Why would an employee be able to easily run an unknown binary from the internet to begin with? If the systems were properly configured to block this, there would be no issue. If I were an executive, I would absolutely be looking at my IT team in this case.
If the employee went entirely out of their way to run an unknown binary, bypassing OS-level restrictions, and sidestepping established procedures - then the employee should be fired.
You really are not familiar with the concepts of company policy and liability, are you? Whether there is an effective technical restriction in place is relevant to the question “can you run the thing”. It is irrelevant for the question “did you circumvent company policy?” and, subsequently, to the blame/firing that comes from it.
This is the exact same discussion people keep having about “government can’t block VPN” or “encryption can’t be broken” when the idea of a law forcing backdoors in services floats around. Sure, you can still use encryption, technically. But if there’s a law that say “encryption too strong to be broken is illegal”, then you’ll get arrested all the same, effective technical restriction or not.
I’m well-aware of how corporate policy, liability, and hierarchy works - the issue with your take is that you act like the IT team is innocent to somebody higher up on the ladder. My issue isn’t with the concept of policy itself (and the enforcement thereof) and the issue of liability, but with the misplaced absolution of IT teams from any responsibility when things go wrong.
IT teams are essentially the secret police in companies. I’m aware of how they usually function. I’ve heard many first-hand accounts from those behind the big screens making sure Bob doesn’t watch porn or that somebody doesn’t do something unauthorized with company computers. I’m unimpressed and it’s frankly a dystopian twist of what IT actually should be; which is best serving a company’s technical needs collaboratively - not roleplaying as the NSA.
It effectively shouldn’t be possible for Bob to watch porn on company devices/internet. It shouldn’t be possible or desirable for somebody to skirt policy to run binaries (even on a whim) for software they feel that they require for maximum productivity. There should be reasonable, timely, and accessible procedures for employees to request necessary software to be deployed.
If I recall correctly in another part of the thread, a user discussed a group of employees (including themselves) needing WSL for job duties and it being blocked without notice. This is an example of sheer incompetence of the IT team - blocking necessary software and failing to maintain/establish timely and accessible procedures to contest a block as an employee who needs specific software to function in their job.
Required software should never be blocked - so who is at fault? Who caused the most damage to the company? The people attempting to work? Or the people who have no idea what they’re doing; making employees feel they need to completely disregard them to function in their duties - the people sabotaging operations?
You’re free to fantasize about the little guy as the only one getting disciplined in these scenarios. I’m sure most corporate environments do work like that, but it just protects incompetency - unless, again, the employee went out of their way to run the binary in an abnormal way or otherwise had less than ideal intentions.
I never, not once, implied that. And frankly speaking I have no idea why you would think that. I said that a user, circumventing a company policy, would be in a tight spot, and depending on the policy most likely fired, regardless of the actual effectiveness of these policies implementation.
At no point have I said that nobody else would be in hot water for failing to do their job, nor did I say that the IT teams is above all and always perfect. But, for the user that did go around the aforementioned policy, the fate of someone else on another team is pretty much irrelevant after they’re put down themselves.