> If I was this “IT” person, I would explain to the individual that there was a critical vulnerability found which will not be patched and then print up a liability waver form for them to sign and date, stating that they are doing this on their own terms and I cannot be held responsible should anything go wrong.
That's even worse advice than what I was responding to. Great way to anger a high-ranking executive and probably get fired.
Frankly a lot of the advice in this thread seems to be coming from people who are very junior or otherwise don't have experience dealing with high-ranking executives. Heck, even mid-ranking executives would respond very poorly to the kinds of actions advised in this thread.
Here's the situation: a high-ranking person in the company is so powerful that she can disobey IT policy by refusing to update her computer. This person is also powerful enough to demand that changes be made to a corporate website to make it compatible with her older computer. This is a problem for the head of IT, and the head of IT either lost that battle or decided it was not worth fighting.
This is not the right place for a more junior IT person or developer to stick their nose in by going directly to that executive with some bogus "liability waiver" or appeals to wasted money or whatever else. It won't go well, and it's wrong to do it in the first place because it bypasses layers of management and the historical and political context that led to this outcome. If the head of IT couldn't solve this problem, a stunt like what you are suggesting won't solve it either.