* User has an important problem
* Central IT will not oblige for whatever good or bad reason
* User is both required and forbidden to resolve the problem, decides Central IT can stuff it, and writes a powerfull excel macro.
* Other have the same pain, so User's macro gets copied, cloned, weirdly mutated etc...
* At some point data has to be exchanged with another company, so they semi accidentally get the macro too. This introduces a required potentially malicious email atachment.
* In all of this, everybody conspires to get Central IT out of it, as they will stop the macro and cause much pain and delay for everyone involved. In a lot of cases, Central IT does its utmost best to not officially notice the macro.
This is generally good, as it allows big corporations to survive, even in spite of Central IT. But it also means things like this attack easily happen.
Almost every organisation with more than about 150 people will over time devolve to some kind of soviet state with all kinds of institutionalized insanity. As long as humanity has not solved that sociological problem, this attack is the kind of fallout to expect.
Well, a lot of times it's not that Central IT won't oblige, it's more that the business
1. The busines doesn't want to spend money on procuring or developing a reasonable solution
2. They prefer the organic growth pattern by having a non-IT asset run development instead of having to do the long arduous task of requirements gathering and all the political battles involved.
Hah yes we did this at the last company I worked for to categorize shipping info from our freight company’s api to an excel spreadsheet. Mostly did it because we didn’t want to check email all the time and IT did not want to give us a vps to run it on.
* User has an important problem * Central IT will not oblige for whatever good or bad reason * User is both required and forbidden to resolve the problem, decides Central IT can stuff it, and writes a powerfull excel macro. * Other have the same pain, so User's macro gets copied, cloned, weirdly mutated etc... * At some point data has to be exchanged with another company, so they semi accidentally get the macro too. This introduces a required potentially malicious email atachment. * In all of this, everybody conspires to get Central IT out of it, as they will stop the macro and cause much pain and delay for everyone involved. In a lot of cases, Central IT does its utmost best to not officially notice the macro.
This is generally good, as it allows big corporations to survive, even in spite of Central IT. But it also means things like this attack easily happen.
Almost every organisation with more than about 150 people will over time devolve to some kind of soviet state with all kinds of institutionalized insanity. As long as humanity has not solved that sociological problem, this attack is the kind of fallout to expect.