First, put checks and balances in place. One administrator can build code, but a second administrator must approve it before it can go live. Van Wyk also recommends limiting the number of root users and putting role-based privileges in place.
High-level access should be limited to as few people as possible, and everyone should have his or her own user ID and unique password to help keep a granular log of which users are making changes and issuing commands on the network, says Andi Mann, an analyst with Enterprise Management Associates.
Sending a clear message that people are watching also is a good deterrent, Paller says. "You need granular logging and log monitoring that gives people the feeling that somebody omniscient is out there watching them all the time," he says. "And you have to demonstrate that omniscience a few times. Somebody visits a porn site and you walk in and say, 'Do you really want to visit those sites from work?' Somebody else downloads something to a thumb drive and you ask them where the thumb drive is. Let these stories spread through the system."
UBS isn't an isolated case, prosecutor O'Malley says. "Sure it will happen again. And in all likelihood it will happen because of an insider. ... They always say, 'Oh, he was a trusted insider.' Bingo! That's the problem. He was a trusted insider."
By combining resources and expertise, the AI-Enabled ICT Workforce Consortium will offer a blueprint for how industries can adapt to an AI-dominated future.
IT leaders should heed the guidance of cybersecurity insurance providers who think businesses should prioritize security education, incident preparedness, regular internal audits, and ongoing vulnerability scanning and patching.
There are many network courses that can address your present job's priorities and help you gain the needed skills to keep pace with industry changes and new technologies.
