<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-li-saag-data-security-maturity-model-00"
     ipr="trust200902">
  <front>
    <title abbrev="scjwt">Data Security Maturity Model</title>
	
    <author fullname="Kepeng Li" initials="K." surname="Li">
      <organization>Alibaba Group</organization>

      <address>
        <email>kepeng.lkp@alibaba-inc.com</email>
      </address>
    </author>

    <date day="20" month="Mar" year="2016"/>

    <area>Security Area</area>

    <workgroup>SAAG Working Group</workgroup>

    <keyword>DSMM</keyword>

    <keyword>Draft</keyword>

    <abstract>
      <t>Data Security Maturity Model (DSMM) provides a multi-level maturity model 
to help organizations to measure their data security capability maturity 
level, identify issues related to data security capability, and improve 
their data security capability. </t>
    </abstract>

    <note title="Requirements Language">
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
      "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
      document are to be interpreted as described in <xref
      target="RFC2119">RFC 2119</xref>.</t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
      <t>The overall goal of Data Security Maturity Model (DSMM) is to provide a multi-level 
maturity model to help organizations solving the problems of data security management
 in big data era, including: </t>
       <t>
         <list style='symbols'>
  <t>How to build organizations data security capability </t>  <t>How to measure the data security capability maturity level of an organization </t>  <t>How to identify issues about data security capability </t>  <t>How to improve data security capability for organizations </t>
         </list>
       </t>

      <section title="Notational Conventions">
        <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
        "OPTIONAL" in this document are to be interpreted as described in RFC
        2119 [RFC2119]. </t>
      </section>

    </section>

    <section title="Overview">
      <t>The DSMM is a process management and improvement maturity model for the development 
and management of data security services. It consists of best practices that address
 the security issues in the lifecycle of data management from creation to delivery 
and maintenance.  The practices related to the DSMM model are extensible and 
applicable to any organization objectives. The model presents an organized set of 
practices and goals necessary for the data security.
      </t>
      <t>The DSMM defines the requirements for organization responsibilities, institution 
processes, technology tools, and staff skills, to ensure data security management 
in the organizations. It does not describe how organizations must do something, 
but rather what they must do in order to achieve high capabilities or maturity 
of data security management. By providing a structured and standard framework of 
practices, the DSMM can be used by organizations to build their own roadmap of 
data security maturity management. The DSMM has an accompanying standardized 
methodology for conducting objective appraisals of capability and maturity levels 
within the organizations data security management practice.
      </t>
      <t>The DSMM applies to all kinds of organizations, including industry enterprises, 
governments and research institutes. 
     </t>
    </section>

    <section title="Maturity Level">
      <t>Data Security Maturity Model can be indicated by 5 levels, as described below:
      </t>
      <t>
        <list style='symbols'>            <t>Level 1: Performed Informally </t>            <t>Level 2: Planned and Tracked </t>            <t>Level 3: Well Defined </t>            <t>Level 4: Quantitatively Controlled </t>
            <t>Level 5: Level 5: Continuously Improving </t>
       </list>
     </t>
    </section>
	
    <section title="Model Framework">
      <t> 

      </t>

      <figure>
        <preamble> </preamble>

        <artwork><![CDATA[ 
        /- - - - - - - - - - - - - - - - -/- - -/ - -/- -/ - /- - /|
       /              Staff Skil         /  D  / D  / D / D / D  / |
      /- - - - - - - - - - - - - - - - -/  a  / a  / a / a / a  /  |
     /           Technology Tools      /  t  / t  / t / t / t  /   |
    /- - - - - - - - - - - - - - - - -/  a  / a  / a / a / a  /    |
   /       Institution Process       /     /    /   /   /    /     |
  /_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _/     /    /   /   /    /      |
 /  Organization Responsibilities  /     /    /   /   /  D /       |
/_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _  /     |    |   |   |  e /        |                      
|Level 5: Continuously Improving   |    |    |   |   | s |        /
|_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ | C  |    |   | T | t |       /        
|Level 4: Quantitatively Controlled| r  | S  |   | r | r |      /
|- - - - - - - - - - - - - - - - - | e  | t  |   | a | u |     /       
|Level 3: Well Defined             | a  | o  |   | n | c |    /
|- - - - - - - - - - - - - - - - - | t  | r  | U | s | t |   /    
|Level 2: Planned and Tracked      | i  | a  | a | m | i |  /
|- - - - - - - - - - - - - - - - - | o  | g  | g | i | o | /   
|Level 1: Performed Informally     | n  | e  | e | t | n |/  |_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ |_ _ |_ _ |_ _| _ |_ _/ 
        ]]></artwork>

        <postamble>Figure 1 Model Framework</postamble>
      </figure>

    </section>

    <section title="Data Lifecycle">
       <t>
         The high-level descriptions for data lifecycle are:
       </t>
       <t>
         <list style='symbols'>            <t>1) Data Creation: Data creation is the generation of new digital content, or 
the significant alteration/updating of existing content, either structured or unstructured. 
            </t>            <t>2) Data Usage: Data usage refers to the combination of a series of activities 
towards active data. </t>            <t>3) Data Transmission: Data transition refers to the process that data flows from 
one entity to another through the network. </t>            <t>4) Data Storage: Data storage refers to inactive data, which is stored physically 
in any digital form. </t>
            <t>5) Data Sharing: Data sharing refers to data exchanging between organizations, 
customers and partners.</t>
            <t>6) Data Destruction: Data destruction refers to the process of permanently or 
temperately making the data unavailable using physical or digital means (e.g., 
crypto-shredding, freezing data under business context). </t>
        </list>
       </t>
     </section>

    <section title="Capability Dimension">
        <t>
           The DSMM model defines the organization capability in four dimensions, namely:
        </t>
        <t>
        <list style='symbols'>            <t>1) Organization Responsibilities: The first and most important capability 
the organization should build is its data security organization, including its 
function and responsibility, security consciousness. It addresses the need to 
drive organizational data security management from the top down effort, and in 
this way, organizations can be open and transparent, break down silos and get 
internal teams to collaborate. It is important to get executive support, to 
champion data security adoption from the top down.             </t>            <t>2)Institution Process: This capability involves the creation of process. 
This means that organizations need to put processes and frameworks in place 
to operationalize data security management internally and externally. It enables
 tight collaboration between different teams and entities like legal teams, IT, 
Crisis PR, various business units and external business parties.           </t>           <t>3)Technology Tools: Organizations have to invest in security technology 
to facilitate the data security controls it employed, especially under current 
big data era. Manual controls or management controls have been verified inefficient.
 One of the challenges within this capability is that there are various technologies 
available to choose thus organizations need to think strategically with proper 
assessment before investing. Ensuring that the technology can scale and integrate 
with existing applications that already exist in the enterprise is imperative.           </t>           <t>4)Staff Skills: Organizations have to educate their staffs, to get more 
security awareness training, and improve their security skills.           </t>
       </list>
      </t>
    </section>

    <section title="Assessment Method">
       <t>
The DSMM model uses bottom-up method to assess and determine the data security 
maturity level of an organization. Each domain in one data lifecycle phase should 
be assessed and be given a single maturity level as the assessment result of the 
domain. Then, take the minimum level of these domains as the assessment result 
of the data lifecycle phase. Finally, the minimum maturity level of all 6 data 
lifecycle phases is the overall maturity of the organization.
       </t>
    </section>

    <section title="Model Domains">
         <t>TBD</t>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t>This draft does not require any IANA registrations.</t>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>TBD. </t>
    </section>

    <section anchor="Acknowledgements" title="Acknowledgements">
      <t>TBD</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc include="reference.RFC.2119"?>
    </references>

  </back>
</rfc>
