Security

Topics:   Security

  • Email this page E-mail this page
  • Print this page Print this page
  • Bookmark and Share
  • icon

Security Is Not Insurance


Posted by Larry Greenemeier, Dec 14, 2005 05:47 PM

What's the hardest part of a chief security officer's job? Evaluating new technologies? Establishing policies for users to follow? Actually, it's more political than that, Jim Routh, chief security officer of Depository Trust & Clearing Corp., said during an Interop presentation Tuesday. "The hardest part of a CSO's job is influencing information security and practices that will be implemented throughout an organization," he said. "It's a delicate process, particularly when you're asking an IT or business manager to rethink how they operate. Education is probably the most important strategic tool for a CSO, without a doubt." And you thought wayward data tapes throwing themselves off of the back of delivery trucks were going to be your biggest challenge.


Security threats are changing all the time, based upon people, processes, and technology introduced into IT environments. CSOs have to take information about threats both within and outside their networks, figure out how they change from day to day and create a risk profile they can share with the business side of the house. "Once you have a risk profile, you have context for decision making," said Routh, whose company and its subsidiaries provide clearing, settlement, and custody of most U.S. securities transactions.

Chief security officers speak the language of risk management, which is statistics. The more information they have, the better they can secure a company. "Although there's no way to eliminate risk, companies can manage risk," noted Routh, a former chief information security officer with American Express.

Statistics are useful in another way; they help security executives justify investments in the products and services they buy. The old adage of security being like insurance won't fly anymore. "When you bring an umbrella, it usually doesn't rain," Routh said. That's why it's important for chief security officers to think in terms of how much money their companies could be spending on government fines, customer lawsuits, and contingency plans for when their systems get hacked.

« Daily News Podcast, Wednesday, December 14 | Main | "Dark" Traffic Dominates »



Sign Up Now
For InformationWeek News Alerts




This is a public forum. United Business Media and its affiliates are not responsible for and do not control what is posted herein. United Business Media makes no warranties or guarantees concerning any advice dispensed by its staff members or readers.

Community standards in this comment area do not permit hate language, excessive profanity, or other patently offensive language. Please be aware that all information posted to this comment area becomes the property of United Business Media LLC and may be edited and republished in print or electronic format as outlined in United Business Media's Terms of Service.

Important Note: This comment area is NOT intended for commercial messages or solicitations of business.