<section title="17.3. Approved Cryptographic Protocols"><subsection title="Objective"><paragraph
    title="17.3.1."


><![CDATA[<p>Classified information in transit is protected by an Approved Cryptographic Protocol implementing an Approved Cryptographic Algorithm.</p>]]></paragraph>
 </subsection>
<subsection title="Context"> <block title="Scope"><paragraph
    title="17.3.2."


><![CDATA[<p>This section covers information on the cryptographic protocols that the GCSB recognises as being approved for use within government.  Implementations of the protocols in this section need to have successfully completed a GCSB recognised cryptographic evaluation before they can be approved for implementation.</p>]]></paragraph>
<paragraph
    title="17.3.3."


><![CDATA[<p>High assurance cryptographic protocols are <strong>not</strong> covered in this section.</p>]]></paragraph>
</block>
<block title="Approved cryptographic protocols"><paragraph
    title="17.3.4."


><![CDATA[<p>In general, the GCSB only recognises the use of cryptographic products that have passed a formal evaluation.  However, the GCSB may approve the use of some commonly available cryptographic protocols even though their implementations within specific products have not been formally evaluated.  This approval is limited to cases where they are used in accordance with the requirements in this manual.</p>]]></paragraph>
<paragraph
    title="17.3.5."


><![CDATA[<p>The Approved Cryptographic Protocols are:</p><ul>
<li>TLS;</li>
<li>SSH;</li>
<li>S/MIME;</li>
<li>OpenPGP Message Format; and</li>
<li>IPSec.</li>
</ul>]]></paragraph>
</block>
</subsection>
<subsection title="Rationale &amp; Controls"> <block title="Using Approved Cryptographic Protocols"><paragraph
    title="17.3.6.R.01."

    tags="Approved Cryptographic Algorithms,Cryptography,Technical"


><![CDATA[<p>If a product implementing an Approved Cryptographic Protocol has been inappropriately configured, it is possible that relatively weak cryptographic algorithms or implementations could be inadvertently selected.  In combination with an assumed level of security confidence, this can represent a significant level of security risk.</p>]]></paragraph>
<paragraph
    title="17.3.6.R.02."

    tags="Approved Cryptographic Algorithms,Cryptography,Technical"


><![CDATA[<p>When configuring unevaluated products that implement an Approved Cryptographic Protocol, agencies can ensure that only the Approved Cryptographic Algorithm can be used by disabling the unapproved algorithms within the products (which is preferred).  Alternatively a policy can be put in place to advise system users not to use the non-approved algorithms.</p>]]></paragraph>
<paragraph
    title="17.3.6.R.03."

    tags="Approved Cryptographic Algorithms,Cryptography,Technical"


><![CDATA[<p>While many Approved Cryptographic Protocols support authentication, agencies should be aware that these authentication mechanisms are not foolproof. To be effective, these mechanisms MUST be securely implemented and protected. <br>This can be achieved by:</p><ul>
<li>providing an assurance of private key protection;</li>
<li>ensuring the correct management of certificate authentication processes including certificate revocation checking; and</li>
<li>using a legitimate identity registration scheme.</li>
</ul>]]></paragraph>
<paragraph
    title="17.3.6.C.01."

    tags="Approved Cryptographic Algorithms,Cryptography,Technical"


    classification="All Classifications"
    compliance="Must"
    cid="2520"
><![CDATA[<p>Agencies using a product that implements an Approved Cryptographic Protocol MUST ensure that only Approved Cryptographic Protocols can be used.<br><br></p>]]></paragraph>
</block>
</subsection>
</section>
