Skip to main content

Advertisement

Log in

An Information Security Performance Measurement Tool for Senior Managers: Balanced Scorecard Integration for Security Governance and Control Frameworks

  • Published:
Information Systems Frontiers Aims and scope Submit manuscript

Abstract

As organizations have become increasingly reliant on information systems, senior managers are keen in assessing the progress of implemented information security strategies. Although the balanced scorecard approach has been suggested for security governance, a critical issue affecting information security practitioners is complexity, as there are many standards and frameworks, with duplication and overlaps to adhere to when organizing the data. Consequently, the article attempts to develop a more inclusive framework for information security governance, a research gap recently identified in the literature. The article maps five governance and control frameworks (COBIT, SABSA, ISG, ITIL, and ISO 27000) to the information security balanced scorecard (InfoSec BSC) to develop a conceptual design of an effective information security performance measurement tool that can be used by senior managers. Using a real-life case application and interviews with a panel of experts, the article identifies IS initiatives, performance measures for each of the mapped objectives derived from governance and control frameworks that may provide guidance for practitioners.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Fig. 1
Fig. 2
Fig. 3
Fig. 4

Similar content being viewed by others

Notes

  1. “The current version is COBIT 5, which is the leading business framework for governance and management of enterprise IT (ISACA). COBIT 5 builds on the previous versions of COBIT (and Val IT and Risk IT), and without loss of information in this article, we focus on COBIT 4.1. COBIT 5 goals cascade stakeholder needs into specific actionable and customized goals within the context of enterprise, IT-related goals and enabler goals. The enterprise goals have been developed using the BSC dimensions and the list is not exhaustive (ISACA). COBIT 5 separates IT governance (evaluate stakeholder needs, set direction through prioritization, and monitor performance, compliance, and progress) and IT management (plan, build, run, and monitor activities with direction set by governance).

  2. We would like to thank the two anonymous reviewers for giving us in-depth feedback on the mappings as well as constructive feedback related to methodology.

References

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Tejaswini C. Herath.

Ethics declarations

Appropriate ethics approval was obtained through Research Ethics Board (REB) at Brock University.

The authors acknowledge generous financial support provided by the Institute for International Issues in Accounting (IIIA). Dr. Teju Herath acknowledges partial research funding from the Social Sciences and Humanities Research Council (SSHRC) of Canada (Grant no: 410–2010-1848). The usual disclaimers apply. The authors would like to acknowledge research support provided by Carla Avard, Dustin Secord, Farook Alyassin, and Hilary Elliott. The authors also thank Daniel Garcia, Michael Tisi, Russ Fisenko, and Andy Morgan for their assistance.

The authors have no other relevant financial or non-financial or competing interests to declare that are relevant to the content of this article.

Additional information

Publisher’s Note

Springer Nature remains neutral with regard to jurisdictional claims in published maps and institutional affiliations.

Appendices

Appendices

Table 6 COBIT4.1 Generic IT Goals Mapping to InfoSec BSC Perspectives. Referenced from COBIT Appendix 6, Table 2: Tables Linking Goals and Processes
Table 7 COBIT’s IT Processes Mapped to InfoSec BSC Perspectives. Referenced from COBIT 4.1 Framework
Table 8 Mapping of InfoSec BSC Perspectives and ITIL. ITIL (IT Infrastructure Library) Service Life Cycle Stages: Core Publications and Their Key Concepts, Processes, and Activities
Table 9 Mapping of InfoSec BSC Perspectives, SecSDLC and ISO 27001-2:2013. Source: Microsoft TechNet, 2007: Balanced Scorecard for Information Security Introduction
Table 10 Mapping of InfoSec BSC Perspectives, ISG Desired Outcomes, Benefits, and Programs
Table 11 SABSA Business Attributes and Metrics. Brothy, K (2009), Appendix Table 7: Business Attributes and Metrics
Table 12 Guide for semi-structured interviews

Appendix F: Notes for the Interviewer

A critical task in the measurement process- To assess and quantify what will be measured

  • Measurements collected from production statistics depend on the number of systems and the number of users of those systems

  • As the number systems/users changes, the effort to maintain the same level of service will vary

  • Once you know what to measure

  • The how, when, where, and who questions of metrics collection must be addressed

    • Measurements Development Approach

  • As the number systems/users changes, the effort to maintain the same level of service will vary

  • Macro-focus measurements: examine the performance of the overall security program

  • Micro-focus measurements: examine the performance of an individual control or group of controls within the InfoSec program

    • Organizations use three types of measurements:

  • Those that determine the effectiveness of the execution of the InfoSec policy

  • Those that determine the effectiveness and/or efficiency of the delivery of InfoSec services

  • Those that assess the impact of an incident or other security event on the organization or its mission

    • According to NIST, the following factors must be considered during development and implementation of an InfoSec performance management program:

  • Measurements must yield quantifiable information (percentages, averages, and numbers)

  • Data that supports the measurements needs to be readily obtainable

  • Only repeatable InfoSec processes should be considered for management

  • Measurements must be useful for tracking performance and directing resources

    • Before designing, collecting, and using measurements, the CISO should be prepared to answer:

  • Why should these measurements be collected?

  • What specific measurements will be collected?

  • How will these measurements be collected?

  • When will these measurements be collected?

  • Who will collect these measurements?

  • Where (at what point in the function’s process) will these measurements be collected?

    • Benefits of using InfoSec performance measurements:

  • Increasing accountability for InfoSec performance

  • Improving effectiveness of InfoSec activities

  • Demonstrating compliance with laws, rules, and regulations

  • Providing quantifiable inputs for resource allocation decisions

Table 13 Select Relevant Literature

Rights and permissions

Reprints and permissions

About this article

Check for updates. Verify currency and authenticity via CrossMark

Cite this article

Herath, T.C., Herath, H.S.B. & Cullum, D. An Information Security Performance Measurement Tool for Senior Managers: Balanced Scorecard Integration for Security Governance and Control Frameworks. Inf Syst Front 25, 681–721 (2023). https://doi.org/10.1007/s10796-022-10246-9

Download citation

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s10796-022-10246-9

Keywords

Navigation