Considerations before implementing CSO position

Considerations before implementing CSO position

What should an organization consider before implementing the Chief Security Officer position?

    Requires Free Membership to View

    SearchSecurity.com members gain immediate and unlimited access to breaking industry news, virus alerts, new hacker threats, highly focused security newsletters, and more -- all at no cost. Join me on SearchSecurity.com today!

    Michael S. Mimoso, Editorial Director

    By submitting your registration information to SearchSecurity.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchSecurity.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

At a bare minimum, the organization should conduct a thorough security audit and perform a risk assessment to identify systems, networks and assets at potential risk. Based on the evaluation of the risks and potential related losses, you could formulate a security policy and a set of plans to remediate or avoid such risks. During that process a consultant can help, but once the process is nearing completion or already done that would be the right time to think about designating a CSO.


For more information on this topic, visit these other SearchSecurity.com resources:
  • News & Analysis: Does your CSO need to be a techie?
  • News & Analysis: TCO model prioritizes security in the enterprise
  • IT Career Expert: The rise of the CSO


    This was first published in April 2003