Open Information Security Management Maturity Model: Difference between revisions

Content deleted Content added
Citation bot (talk | contribs)
Misc citation tidying. | Use this bot. Report bugs. | Suggested by Jonesey95 | Category:CS1 errors: empty unknown parameters | via #UCB_Category 67/307
m Importing Wikidata short description: "Framework for managing information security"
 
(9 intermediate revisions by 4 users not shown)
Line 1:
{{Short description|Framework for managing information security}}
The '''[[The Open Group|Open informationGroup]] securityInformation managementSecurity maturityManagement modelMaturity Model''' ('''O-ISM3''') is a [[Thematurity Open Groupmodel]] framework for managing [[information security]]. 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 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. <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/42security/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 the most popular IT and security management standards.
 
== Availability ==
Line 15 ⟶ 16:
 
[[Category:Data security]]
[[Category:Computer security]]
[[Category:Security]]
[[Category:Information governance]]