What do you do when a network administrator goes bad? That's the question IT staffers for the city of San Francisco are facing this week. One of their own, a net admin named Terry Childs, was arrested for sabotaging the city government's new fiber backbone network (see story).

Now he's in jail. But he's not the only one who will pay the price.

Until recently, Childs was well regarded in his IT shop. But last month, that all began to unravel. On June 20, Childs reportedly went after the IT department's newly hired head of security, chasing her with a camera until she locked herself in an office to escape.

The security chief was auditing who had password access to the new network. According to the San Francisco Chronicle, that audit soon turned up the fact that Childs had changed passwords so that only he had administrative access to the network. Childs also reportedly installed software to monitor his managers' e-mails related to his job performance.

Childs was suspended on July 9 for insubordination. When police asked Childs for the passwords, first he gave them phony information, then he refused to divulge the real passwords. On July 14, Childs was arrested for felony computer tampering.

Because prosecutors feared for the security of law enforcement documents, jail inmate bookings, payroll files and other city, Childs was jailed with bail set at a whopping $5 million.

To date, Childs hasn't explained why he allegedly locked up the network -- and he hasn't coughed up the passwords.

Meanwhile, his co-workers are now facing the possibility of having to rebuild the network and verify everything stored on it -- about 60% of all government data in San Francisco.

Oh, and also having to live under a cloud for as long as they work in that IT shop. Because someone in their department was trusted too much, they'll be distrusted. By users, managers -- and one another.

Is that fair? Of course not. They're not the ones who sabotaged the network and created a huge mess. They're not the ones who should have acted more quickly and effectively when it looked like there was a problem employee on the loose.

But they're the ones who'll pay.

So what to do in the wake of that net admin gone bad? First, there's the fiber backbone to unlock and sanitize, or rebuild if necessary. Then, no doubt, new technology and new layers of auditing will be added to increase security scrutiny.

For more enterprise computing news, visit Computerworld. Story copyright Computerworld, Inc.