Open Information Security Management Maturity Model: Difference between revisions

Revision as of 13:37, 4 February 2020

Latest revision as of 05:01, 11 March 2024

(16 intermediate revisions by 7 users not shown)

Line 1:

{{Short description|Framework for managing information security}}

{{multiple issues|

The '''[[The Open Group|Open informationGroup]] securityInformation managementSecurity maturityManagement modelMaturity Model''' ('''O-ISM3''') is Thea Open[[maturity Group frameworkmodel]] for managing [[information security, and wider still to managing information in the wider context]]. It aims to ensure that security processes in any organization are implemented so as to operate at a level consistent with that organization’s business requirements. O-ISM3 is technology-neutral. It defines a comprehensive but manageable number of information security processes sufficient for the needs of most organizations, with the relevant security control(s) being identified within each process as an essential subset of that process. In this respect, it is fully compatible with the well-established ISO/IEC 27000:2009, COBIT®, and ITIL® standards in this field. Additionally, as well as complementing the TOGAF® framework for Enterprise Architecture, O-ISM3 defines operational metrics and their allowable variances..<ref>O-ISM3 v2.0 2018 p6</ref>

{{more footnotes|date=September 2017}}

{{refimprove|date=July 2018}}

{{expert|date=July 2018}}

}}

The Open Group information security management maturity model ('''O-ISM3''') is The Open Group framework for managing information security, and wider still to managing information in the wider context. It aims to ensure that security processes in any organization are implemented so as to operate at a level consistent with that organization’s business requirements. O-ISM3 is technology-neutral. It defines a comprehensive but manageable number of information security processes sufficient for the needs of most organizations, with the relevant security control(s) being identified within each process as an essential subset of that process. In this respect, it is fully compatible with the well-established ISO/IEC 27000:2009, COBIT®, and ITIL® standards in this field. Additionally, as well as complementing the TOGAF® framework for Enterprise Architecture, O-ISM3 defines operational metrics and their allowable variances..<ref>O-ISM3 v2.0 2018 p6</ref>

== History ==

The original motivation behind O-ISM3 development was to narrow the gap between theory and practice for information security management systems, and the trigger was the idea of linking security management and maturity models. O-ISM3 strove to keep clear of a number of pitfalls with previous approaches.<ref name="mikko">Siponen, Mikko (2002-08-24). Designing Secure Information Systems and Software: Critical evaluation of the existing approaches and a new paradigm. ''OULU 2002'', 24 August 2002. Retrieved from http://jultika.oulu.fi/files/isbn9514267907.pdf.</ref>

The {{cite web|url=https://www.ism3opengroup.comorg/nodeforum/42|security/infosecmanagement|title=O-ISM3project}} website indicates that the project looked at [[Capability Maturity Model Integration]], [[ISO 9000]], [[COBIT]], [[ITIL]], [[ISO/IEC 27001:2013]], and other standards, and found some potential for improvement in several fields, such as linking security to business needs, using a process based approach, providing some additional details (who, what, why) for implementation, and suggesting specific metrics, while preserving compatibility with currentthe most popular IT and security management standards.

== Availability ==

[[The Open Group]] provides the standard {{cite web|url=https://publications.opengroup.org/c17b||title=O-ISM3 v.20}} free of charge.

==See alsoReferences ==

==References==

{{reflist|1}}

{{Open Group standards}}

== References ==

[[Category:Data security]]

[[Category:Computer security]]

[[Category:Security]]

[[Category:Information governance]]