Complicate requirement are kind of out of date. They keep adding requirements to them but then don’t often take them away. So if a requiment made sense 20 years ago it’s still there even though there are better strategies to protect your environment.
You could skip a requiment if you can establish a compensatinh control and show that the threat the requirements is intended to address is addressed. For example skipping antivirus by reimagining the devices every morning, this is an absurd example but would work.
Doesn’t help that IT is outsourced to the lowest bidder, which typically means the IT contractor enslaving corporate IT to microsoft and playing a game of “forward the ticket”.
Then “IT managers” in the organisation responsible for the contract typically know jack shit about IT and are busy trying to save face over protecting their users from incompetent contractors.
Complicate requirement are kind of out of date. They keep adding requirements to them but then don’t often take them away. So if a requiment made sense 20 years ago it’s still there even though there are better strategies to protect your environment.
You could skip a requiment if you can establish a compensatinh control and show that the threat the requirements is intended to address is addressed. For example skipping antivirus by reimagining the devices every morning, this is an absurd example but would work.
Doesn’t help that IT is outsourced to the lowest bidder, which typically means the IT contractor enslaving corporate IT to microsoft and playing a game of “forward the ticket”. Then “IT managers” in the organisation responsible for the contract typically know jack shit about IT and are busy trying to save face over protecting their users from incompetent contractors.