<section title="17.10. Hardware Security Modules"><subsection title="Objective"><paragraph
    title="17.10.1."


><![CDATA[<p>Hardware Security Modules are used where additional security of cryptographic functions is desirable.</p>]]></paragraph>
 </subsection>
<subsection title="Context"> <block title="Scope"><paragraph
    title="17.10.2."


><![CDATA[<p>This section covers information relating to Hardware Security Modules (HSMs). &nbsp; &nbsp;Detailed key management guidance is provided in <a href="http://nzism.gcsb.govt.nz/ism-document#Section-16086">Section 17.9 – Key Management</a>.</p>]]></paragraph>
</block>
<block title="Hardware Security Module"><paragraph
    title="17.10.3."


><![CDATA[<p>Hardware Security Modules (HSMs) are defined as a hardware module or appliance which provides cryptographic functions.  HSM’s can be integrated into a design, installed in a host or be externally connected.  HSM’s can be packaged as discrete appliances, PCI cards, USB devices, smartcards or other form factors.</p>]]></paragraph>
<paragraph
    title="17.10.4."


><![CDATA[<p>Functions include (but are not limited to) encryption, decryption, key generation, signing, hashing and cryptographic acceleration.  The appliance usually also offers some level of physical tamper-resistance, has a user interface and a programmable interface for key management, configuration and firmware or software updates.</p>]]></paragraph>
</block>
<block title="Usage"><paragraph
    title="17.10.5."


><![CDATA[<p>HSMs are used in high assurance security solutions that satisfy widely established and emerging standards of due care for cryptographic systems and practices—while also maintaining high levels of operational efficiency.  Traditional use of HSMs is within automatic teller machines, electronic fund transfer, and point-of-sale networks.  HSMs are also used to secure CA keys in PKI deployments, SSL acceleration and DNSSEC (DNS Security Extensions) implementations.</p>]]></paragraph>
</block>
<block title="Physical Security"><paragraph
    title="17.10.6."


><![CDATA[<p>HSM’s usually describe an encapsulated multi-chip module, device, card or appliance, rather than a single chip component or device.  The nature of HSM’s requires more robust physical security, including tamper resistance, tamper evidence, tamper detection, and tamper response.</p>]]></paragraph>
</block>
<block title="Tamper Resistance"><paragraph
    title="17.10.7."


><![CDATA[<p>Tamper Resistance is designed to limit the ability to physically tamper with, break into or extract useful information from an HSM.  Often the boards and components are encased in an epoxy-like resin that will destroy any encapsulated components when drilled, scraped or otherwise physically tampered with.</p>]]></paragraph>
</block>
<block title="Tamper Evidence"><paragraph
    title="17.10.8."


><![CDATA[<p>The HSM is designed so that any attempts at tampering are evident.  Many devices use seals and labels designed break or reveal a special message when physical tampering is attempted.  Tamper evidence may require a regular inspection or audit mechanism.</p>]]></paragraph>
<paragraph
    title="17.10.9."


><![CDATA[<p>HSMs can include features that detect and report tampering attempts.  For example, embedding a conductive mesh within the epoxy-like package; internal circuitry monitored the electrical proper-ties of this mesh — properties which physical tamper would disrupt.  Devices can also monitor for temperature extremes, radiation extremes, light, air and other unusual conditions.</p>]]></paragraph>
</block>
<block title="Tamper Response"><paragraph
    title="17.10.10."


><![CDATA[<p>HSMs can include defensive features that activate when tampering is detected.  For example, cryptographic keys and sensitive data are deleted or zeroised.  A trade-off exists between availability and security as an effective tamper response essentially renders the HSM unusable.</p>]]></paragraph>
</block>
</subsection>
<subsection title="References"><paragraph
    title="17.10.11."


><![CDATA[<p>Further references can be found at:</p><table class="table-main">
<tbody>
<tr>
<td><strong>Reference</strong></td>
<td><strong>Title</strong></td>
<td><strong>Publisher</strong></td>
<td style="width: 33%;"><strong>Source</strong></td>
</tr>
<tr>
<td>&nbsp;</td>
<td><strong>Payment Card Industry (PCI) Hardware Security Module (HSM) - Security Requirements&nbsp;</strong></td>
<td style="text-align: center;">PCI</td>
<td style="width: 33%;">
<p><a rel="noopener noreferrer" href="https://docs-prv.pcisecuritystandards.org/PTS/Standard/PCI_HSM_Security_Requirements_v4.pdf" target="_blank">Official PCI Security Standards Council Site - Document</a></p>
<p><a href="https://listings.pcisecuritystandards.org/documents/PTS_HSM_Technical_FAQs_v3_May_2018.pdf">PCI HSM Frequently Asked Questions (pcisecuritystandards.org)</a></p>
</td>
</tr>
<tr>
<td>
<p><strong>FIPS PUB 140-2</strong></p>
</td>
<td>
<p><strong>FIPS PUB 140-2 Security Requirements for Cryptographic Modules</strong></p>
</td>
<td style="text-align: center;">NIST</td>
<td style="width: 33%;">
<p><a rel="noopener noreferrer" href="http://csrc.nist.gov/groups/STM/cmvp/standards.html" target="_blank"></a><a href="https://csrc.nist.gov/publications/detail/fips/140/2/final">FIPS 140-2, Security Requirements for Cryptographic Modules | CSRC (nist.gov)</a><a rel="noopener noreferrer" href="http://csrc.nist.gov/groups/STM/cmvp/standards.html" target="_blank"></a></p>
</td>
</tr>
</tbody>
</table>]]></paragraph>
 </subsection>
<subsection title="Rationale &amp; Controls"> <block title="Hardware Security Modules"><paragraph
    title="17.10.12.R.01."

    tags="Cryptography,Technical"


><![CDATA[<p>Where high assurance or high security is required or high volumes of data are encrypted or decrypted, the use of an HSM should be considered when designing the network and security architectures.</p>]]></paragraph>
<paragraph
    title="17.10.12.C.01."

    tags="Cryptography,Technical"


    classification="Top Secret, Confidential, Secret"
    compliance="Must"
    cid="3103"
><![CDATA[<p>Agencies MUST consider the use of HSMs when undertaking a security risk assessment or designing network and security architectures.</p>]]></paragraph>
<paragraph
    title="17.10.12.C.02."

    tags="Cryptography,Technical"


    classification="Confidential, Secret, Top Secret"
    compliance="Must"
    cid="3105"
><![CDATA[<p>Agencies MUST follow the product selection guidance in this manual. See <a href="http://nzism.gcsb.govt.nz/ism-document#Chapter-14397">Chapter 12 – Product Security</a>.</p>]]></paragraph>
<paragraph
    title="17.10.12.C.03."

    tags="Cryptography,Technical"


    classification="All Classifications"
    compliance="Should"
    cid="3108"
><![CDATA[<p>Agencies SHOULD consider the use of HSMs when undertaking a security risk assessment or designing network and security architectures.</p>]]></paragraph>
<paragraph
    title="17.10.12.C.04."

    tags="Cryptography,Technical"


    classification="All Classifications"
    compliance="Should"
    cid="3110"
><![CDATA[<p>Agencies SHOULD follow the product selection guidance in this manual. See <a href="http://nzism.gcsb.govt.nz/ism-document#Chapter-14397">Chapter 12 – Product Security</a>.</p>]]></paragraph>
</block>
</subsection>
</section>
