Abstract

http://ssrn.com/abstract=1979796
 


 



Developing a Common Language About IT Risk Management


George F. Westerman


Massachusetts Institute of Technology (MIT) - Center for Information Systems Research (CISR)

Richard Hunter


affiliation not provided to SSRN

June 1, 2009

MIT Sloan Research Paper No. 4933-11

Abstract:     
Although IT risks can have wide-ranging business consequences, few executives feel comfortable discussing IT risk management. It doesn’t have to be this way. Executive-level tradeoffs around IT risk are managerial, not technical. The Four A Framework of Availability, Access, Accuracy, and Agility risks provides a common language that business and IT managers can use to manage IT risks without getting bogged down in technical complexity. Then you can build a risk management capability — by improving the IT foundation, installing a risk governance process, and creating a risk aware culture — that increases the returns from your IT risk management investments.

Number of Pages in PDF File: 15

Keywords: IT risk, Non-IT executive viewpoint, IT governance, alignment, oversight, risk aware culture, architecture, business continuity, security, agility, regulatory compliance, privacy

working papers series


Download This Paper

Date posted: January 10, 2012  

Suggested Citation

Westerman, George F. and Hunter, Richard, Developing a Common Language About IT Risk Management (June 1, 2009). MIT Sloan Research Paper No. 4933-11. Available at SSRN: http://ssrn.com/abstract=1979796 or http://dx.doi.org/10.2139/ssrn.1979796

Contact Information

George F. Westerman (Contact Author)
Massachusetts Institute of Technology (MIT) - Center for Information Systems Research (CISR) ( email )
Sloan School of Management
5 Cambridge Center, NE25-780
Cambridge, MA 02142
United States
617-253-2939 (Phone)
Richard Hunter
affiliation not provided to SSRN ( email )
Feedback to SSRN


Paper statistics
Abstract Views: 1,037
Downloads: 294
Download Rank: 56,058

© 2014 Social Science Electronic Publishing, Inc. All Rights Reserved.  FAQ   Terms of Use   Privacy Policy   Copyright   Contact Us
This page was processed by apollo8 in 0.281 seconds