<section title="5.4. System Security Plans"><subsection title="Objective"><paragraph
    title="5.4.1."


><![CDATA[<p>System Security Plans (SSPs) specify the information security measures for systems.</p>]]></paragraph>
 </subsection>
<subsection title="Context"> <block title="Scope"><paragraph
    title="5.4.2."


><![CDATA[<p>This section relates to the development of SSPs. Information relating to other mandatory documentation can be found in <a title="Documentation fundamentals" href="http://nzism.gcsb.govt.nz/ism-document#Section-12683">Section 5.1 - Documentation Fundamentals</a>.</p>]]></paragraph>
<paragraph
    title="5.4.3."


><![CDATA[<p>Further information to be included in SSPs relating to specific functionality or technologies that could be implemented for a system can be found in the applicable areas of this manual.</p>]]></paragraph>
</block>
<block title="Stakeholders"><paragraph
    title="5.4.4."


><![CDATA[<p>There can be many stakeholders involved in defining a SSP including representatives from the:</p><ul>
<li>project, who MUST deliver the capability (including contractors);</li>
<li>owners of the information to be handled;</li>
<li>system users for whom the capability is being developed;</li>
<li>management audit authority;</li>
<li>CISO, ITSM and system owners;</li>
<li>system certifiers and accreditors;</li>
<li>information management planning areas; and</li>
<li>infrastructure management.</li>
</ul>]]></paragraph>
</block>
</subsection>
<subsection title="Rationale &amp; Controls"> <block title="Contents of System Security Plans (SSPs)"><paragraph
    title="5.4.5.R.01."

    tags="Governance,Information Security Documentation"


><![CDATA[<p>The NZISM provides a list of controls that are potentially applicable to a system based on its classification, its functionality and the technology it is implementing. Agencies will need to determine which controls are in scope of the system and translate those controls to the SSP. These controls will then be assessed on their implementation and effectiveness during an information security assessment as part of the accreditation process.</p>]]></paragraph>
<paragraph
    title="5.4.5.R.02."

    tags="Governance,Information Security Documentation"


><![CDATA[<p>In performing accreditations against the latest baseline of this manual, agencies are ensuring that they are taking the most recent threat environment into consideration. GCSB continually monitors the threat environment and conducts research into the security impact of emerging trends. With each release of this manual, controls can be added, rescinded or modified depending on changes in the threat environment.</p>]]></paragraph>
<paragraph
    title="5.4.5.C.01."

    tags="Governance,Information Security Documentation"


    classification="All Classifications"
    compliance="Must"
    cid="828"
><![CDATA[<p>Agencies MUST select controls from this manual to be included in the SSP based on the scope of the system with additional system specific controls being included as a result of the associated SRMP. Encryption Key Management requires specific consideration; refer to <a title="Cryptography" href="http://nzism.gcsb.govt.nz/ism-document#Chapter-15745">Chapter 17 – Cryptography</a>.</p>]]></paragraph>
<paragraph
    title="5.4.5.C.02."

    tags="Governance,Information Security Documentation"


    classification="All Classifications"
    compliance="Should"
    cid="829"
><![CDATA[<p>Agencies SHOULD use the latest baseline of this manual when developing, and updating, their SSPs as part of the certification, accreditation and reaccreditation of their systems.</p>]]></paragraph>
<paragraph
    title="5.4.5.C.03."

    tags="Governance,Information Security Documentation"


    classification="All Classifications"
    compliance="Should"
    cid="831"
><![CDATA[<p>Agencies SHOULD include a Key Management Plan in the SSP.</p>]]></paragraph>
</block>
</subsection>
</section>
