FIPS 140-2 Non-Proprietary Security Policy

Kernel Crypto API Cryptographic Module version 1.0 FIPS 140-2 Non-Proprietary Security Policy Version 1.3 Last update: 2020-03-02 Prepared by: atsec information security corporation 9130 Jollyville Road, Suite 260 Austin, TX 78759 <a href="/goto?url=http://www.atsec.com" target="_blank">www.atsec.com </a>© 2020 Canonical Ltd. / atsec information security This document can be reproduced and distributed only whole and intact, including this copyright notice. <ul style="display: flex;"><li style="flex:1">Kernel Crypto API Cryptographic Module </li><li style="flex:1">FIPS 140-2 Non-Proprietary Security Policy </li></ul>Table of Contents <a href="#5_0">1. Cryptographic</a><a href="#5_0"> </a><a href="#5_0">Module Specification .....................................................................................................5 </a><a href="#5_1">1.1. Module</a><a href="#5_1"> </a><a href="#5_1">Overview .....................................................................................................................................5 </a><a href="#9_0">1.2. Modes</a><a href="#9_0"> </a><a href="#9_0">of Operation .................................................................................................................................9 </a><a href="#10_0">2. Cryptographic</a><a href="#10_0"> </a><a href="#10_0">Module Ports and Interfaces ........................................................................................10 </a><a href="#11_0">3. Roles,</a><a href="#11_0"> </a><a href="#11_0">Services and Authentication .....................................................................................................11 </a><a href="#11_1">3.1. Roles</a><a href="#11_1"> </a><a href="#11_1">.......................................................................................................................................................11 </a><a href="#11_2">3.2. Services...................................................................................................................................................11 </a><a href="#13_0">3.3. Algorithms</a><a href="#13_0"> </a><a href="#13_0">..............................................................................................................................................13 </a> <a href="#13_1">3.3.1. </a><a href="#17_0">3.3.2. </a><a href="#0_0">3.3.3. </a><a href="#0_1">3.3.4. </a> <a href="#13_1">Ubuntu 16.04 LTS 64-bit Little Endian Running on POWER System...............................................13 </a><a href="#17_0">Ubuntu 16.04 LTS 64-bit Running on Intel® Xeon® Processor .......................................................17 </a><a href="#0_0">Ubuntu 16.04 LTS 64-bit Running on z System...............................................................................24 </a><a href="#0_1">Non-Approved Algorithms..............................................................................................................27 </a> <a href="#0_2">3.4. Operator</a><a href="#0_2"> </a><a href="#0_2">Authentication ........................................................................................................................29 </a><a href="#0_0">4. Physical</a><a href="#0_0"> </a><a href="#0_0">Security ................................................................................................................................30 </a><a href="#0_0">5. Operational</a><a href="#0_0"> </a><a href="#0_0">Environmen</a><a href="#0_0">t</a><a href="#0_0">...................................................................................................................31 </a><a href="#0_3">5.1. Applicability</a><a href="#0_3"> </a><a href="#0_3">............................................................................................................................................31 </a><a href="#0_4">5.2. Policy.......................................................................................................................................................31 </a><a href="#0_0">6. Cryptographic</a><a href="#0_0"> </a><a href="#0_0">Key Management.........................................................................................................32 </a><a href="#0_5">6.1. Random</a><a href="#0_5"> </a><a href="#0_5">Number Generatio</a><a href="#0_5">n</a><a href="#0_5">.</a><a href="#0_5">................................................................................................................32 </a><a href="#0_0">6.2. Key</a><a href="#0_0"> </a><a href="#0_0">Generatio</a><a href="#0_0">n</a><a href="#0_0">.</a><a href="#0_0">......................................................................................................................................33 </a><a href="#0_6">6.3. Key</a><a href="#0_6"> </a><a href="#0_6">Agreement / Key Transport / Key Derivation ..................................................................................33 </a><a href="#0_7">6.4. Key</a><a href="#0_7"> </a><a href="#0_7">Entry / Output..................................................................................................................................33 </a><a href="#0_8">6.5. Key</a><a href="#0_8"> </a><a href="#0_8">/ CSP Storage....................................................................................................................................33 </a><a href="#0_9">6.6. Key</a><a href="#0_9"> </a><a href="#0_9">/ CSP Zeroization..............................................................................................................................33 </a><a href="#0_0">7. Electromagnetic</a><a href="#0_0"> </a><a href="#0_0">Interference/Electromagnetic Compatibility (EMI/EMC) ............................................34 </a><a href="#0_0">8. Self-Test</a><a href="#0_0">s</a><a href="#0_0">.</a><a href="#0_0">..........................................................................................................................................35 </a><a href="#0_10">8.1. Power-Up</a><a href="#0_10"> </a><a href="#0_10">Tests.......................................................................................................................................35 </a> <a href="#0_11">8.1.1. </a><a href="#0_12">8.1.2. </a> <a href="#0_11">Integrity Test</a><a href="#0_11">s</a><a href="#0_11">.</a><a href="#0_11">................................................................................................................................35 </a><a href="#0_12">Cryptographic Algorithm Test</a><a href="#0_12">s</a><a href="#0_12">.</a><a href="#0_12">......................................................................................................35 </a> <a href="#0_13">8.2. On-Demand</a><a href="#0_13"> </a><a href="#0_13">Self-Test</a><a href="#0_13">s</a><a href="#0_13">.</a><a href="#0_13">...........................................................................................................................37 </a><a href="#0_14">8.3. Conditional</a><a href="#0_14"> </a><a href="#0_14">Tests ....................................................................................................................................37 </a>© 2020 Canonical Ltd. / atsec information security <ul style="display: flex;"><li style="flex:1">This document can be reproduced and distributed only whole and intact, including this copyright notice. </li><li style="flex:1">2 of 46 </li></ul><ul style="display: flex;"><li style="flex:1">Kernel Crypto API Cryptographic Module </li><li style="flex:1">FIPS 140-2 Non-Proprietary Security Policy </li></ul><a href="#0_0">9. Guidance</a><a href="#0_0"> </a><a href="#0_0">...........................................................................................................................................38 </a><a href="#0_15">9.1. Crypto</a><a href="#0_15"> </a><a href="#0_15">Officer Guidanc</a><a href="#0_15">e</a><a href="#0_15">.</a><a href="#0_15">........................................................................................................................38 </a> <a href="#0_16">9.1.1. </a><a href="#0_17">9.1.2. </a> <a href="#0_16">Module Installation.........................................................................................................................38 </a><a href="#0_17">Operating Environment Configuratio</a><a href="#0_17">n</a><a href="#0_17">.</a><a href="#0_17">..........................................................................................38 </a> <a href="#0_18">9.2. User</a><a href="#0_18"> </a><a href="#0_18">Guidance ........................................................................................................................................39 </a> <a href="#0_19">9.2.1. </a><a href="#0_0">9.2.2. </a><a href="#0_20">9.2.3. </a><a href="#0_21">9.2.4. </a> <a href="#0_19">AES GCM IV.....................................................................................................................................39 </a><a href="#0_0">AES XTS ...........................................................................................................................................40 </a><a href="#0_20">Triple-DES encryptio</a><a href="#0_20">n</a><a href="#0_20">.</a><a href="#0_20">....................................................................................................................40 </a><a href="#0_21">Handling FIPS Related Errors ..........................................................................................................40 </a><a href="#0_0">10. Mitigation</a><a href="#0_0"> </a><a href="#0_0">of Other Attack</a><a href="#0_0">s</a><a href="#0_0">.</a><a href="#0_0">...............................................................................................................41 </a>© 2020 Canonical Ltd. / atsec information security <ul style="display: flex;"><li style="flex:1">This document can be reproduced and distributed only whole and intact, including this copyright notice. </li><li style="flex:1">3 of 46 </li></ul><ul style="display: flex;"><li style="flex:1">Kernel Crypto API Cryptographic Module </li><li style="flex:1">FIPS 140-2 Non-Proprietary Security Policy </li></ul>Copyrights and Trademarks Ubuntu and Canonical are registered trademarks of Canonical Ltd. Linux is a registered trademark of Linus Torvalds. © 2020 Canonical Ltd. / atsec information security <ul style="display: flex;"><li style="flex:1">This document can be reproduced and distributed only whole and intact, including this copyright notice. </li><li style="flex:1">4 of 46 </li></ul><ul style="display: flex;"><li style="flex:1">Kernel Crypto API Cryptographic Module </li><li style="flex:1">FIPS 140-2 Non-Proprietary Security Policy </li></ul>1. Cryptographic Module Specification This document is the non-proprietary FIPS 140-2 Security Policy for version 1.0 of the Ubuntu Kernel Crypto API Cryptographic Module. It contains the security rules under which the module must operate and describes how this module meets the requirements as specified in FIPS PUB 140-2 (Federal Information Processing Standards Publication 140-2) for a Security Level 1 software module. The following sections describe the cryptographic module and how it conforms to the FIPS 140-2 specification in each of the required areas. 1.1. Module Overview The Ubuntu Kernel Crypto API Cryptographic Module (hereafter referred to as “the module”) is a software module running as part of the operating system kernel that provides general purpose cryptographic services. The module provides cryptographic services to kernel applications through a C language Application Program Interface (API) and to applications running in the user space through an AF_ALG socket type interface. The module utilizes processor instructions to optimize and increase the performance of cryptographic algorithms. For the purpose of the FIPS 140-2 validation, the module is a software-only, multi-chip standalone cryptographic module validated at overall security level 1. The table below shows the security level claimed for each of the eleven sections that comprise the FIPS 140-2 standard. <ul style="display: flex;"><li style="flex:1">FIPS 140-2 Section </li><li style="flex:1">Security </li></ul>Level 123456789 Cryptographic Module Specification Cryptographic Module Ports and Interfaces Roles, Services and Authentication Finite State Model 1111<ul style="display: flex;"><li style="flex:1">Physical Security </li><li style="flex:1">N/A </li></ul><ul style="display: flex;"><li style="flex:1">1</li><li style="flex:1">Operational Environment </li></ul>Cryptographic Key Management EMI/EMC 11<ul style="display: flex;"><li style="flex:1">Self-Tests </li><li style="flex:1">1</li></ul>10 Design Assurance 11 Mitigation of Other Attacks Overall Level 1N/A 1Table 1 - Security Levels © 2020 Canonical Ltd. / atsec information security <ul style="display: flex;"><li style="flex:1">This document can be reproduced and distributed only whole and intact, including this copyright notice. </li><li style="flex:1">5 of 46 </li></ul><ul style="display: flex;"><li style="flex:1">Kernel Crypto API Cryptographic Module </li><li style="flex:1">FIPS 140-2 Non-Proprietary Security Policy </li></ul>The cryptographic logical boundary consists of all kernel objects and the integrity check files used for Integrity Tests. The table below enumerates the components that comprise the module with their location in the target platform. <ul style="display: flex;"><li style="flex:1">Description </li><li style="flex:1">Components </li></ul><ul style="display: flex;"><li style="flex:1">Integrity test utility </li><li style="flex:1">/usr/bin/sha512hmac </li></ul>Integrity check HMAC file for the integrity test utility. /usr/bin/.sha512hmac.hmac <ul style="display: flex;"><li style="flex:1">Static kernel binary </li><li style="flex:1">On Power system: </li></ul>/boot/vmlinux-4.4.0-1002-fips On x86_64 and z system: /boot/vmlinuz-4.4.0-1002-fips Integrity check HMAC file for static kernel binary On Power system: /boot/.vmlinux-4.4.0-1002-fips.hmac On x86_64 and z system: /boot/.vmlinuz-4.4.0-1002-fips.hmac Cryptographic kernel object files On Power system: /lib/modules/4.4.0-1002-fips/kernel/crypto/*.ko /lib/modules/4.4.0-1002-fips/kernel/arch/powerpc/crypto/*.ko /lib/modules/4.4.0-1002-fips/kernel/drivers/crypto/vmx/*.ko On x86_64 system: /lib/modules/4.4.0-1002-fips/kernel/crypto/*.ko /lib/modules/4.4.0-1002-fips/kernel/arch/x86/crypto/*.ko On z system: /lib/modules/4.4.0-1002-fips/kernel/crypto/*.ko /lib/modules/4.4.0-1002-fips/kernel/arch/s390/crypto/*.ko Table 2 - Cryptographic Module Components © 2020 Canonical Ltd. / atsec information security <ul style="display: flex;"><li style="flex:1">This document can be reproduced and distributed only whole and intact, including this copyright notice. </li><li style="flex:1">6 of 46 </li></ul><ul style="display: flex;"><li style="flex:1">Kernel Crypto API Cryptographic Module </li><li style="flex:1">FIPS 140-2 Non-Proprietary Security Policy </li></ul>The software block diagram below shows the module, its interfaces with the operational environment and the delimitation of its logical boundary, comprised of all the components within the BLUE box. Figure 1 - Software Block Diagram © 2020 Canonical Ltd. / atsec information security <ul style="display: flex;"><li style="flex:1">This document can be reproduced and distributed only whole and intact, including this copyright notice. </li><li style="flex:1">7 of 46 </li></ul><ul style="display: flex;"><li style="flex:1">Kernel Crypto API Cryptographic Module </li><li style="flex:1">FIPS 140-2 Non-Proprietary Security Policy </li></ul>The module is aimed to run on a general purpose computer (GPC); the physical boundary of the module is the tested platforms. Figure 2 shows the major components of a GPC. Figure 2 - Cryptographic Module Physical Boundary The module has been tested on the test platforms shown below. <ul style="display: flex;"><li style="flex:1">Test Platform </li><li style="flex:1">Processor </li><li style="flex:1">Processor </li><li style="flex:1">Test Configuration </li></ul>Architecture IBM Power System S822L (PowerNV 8247-22L) <ul style="display: flex;"><li style="flex:1">POWER8 </li><li style="flex:1">Power system </li></ul>Power system Power system Ubuntu 16.04 LTS 64-bit Little Endian with/without Power ISA 2.07 (PAA) IBM Power System S822LC (PowerNV 8001-22C) POWER8 POWER8 Ubuntu 16.04 LTS 64-bit Little Endian with/without Power ISA 2.07 (PAA) IBM Power System S822LC (PowerNV 8335-GTB) Ubuntu 16.04 LTS 64-bit Little Endian with/without Power ISA 2.07 (PAA) © 2020 Canonical Ltd. / atsec information security <ul style="display: flex;"><li style="flex:1">This document can be reproduced and distributed only whole and intact, including this copyright notice. </li><li style="flex:1">8 of 46 </li></ul><ul style="display: flex;"><li style="flex:1">Kernel Crypto API Cryptographic Module </li><li style="flex:1">FIPS 140-2 Non-Proprietary Security Policy </li></ul><ul style="display: flex;"><li style="flex:1">Test Platform </li><li style="flex:1">Processor </li><li style="flex:1">Processor </li><li style="flex:1">Test Configuration </li></ul>Architecture Supermicro SYS-5018R-WR IBM z13 Intel® Xeon® CPU x86_64 E5-2620v3 Ubuntu 16.04 LTS 64-bit with/without AES-NI (PAA) <ul style="display: flex;"><li style="flex:1">z13 </li><li style="flex:1">z System </li></ul>x86_64 Ubuntu 16.04 LTS 64-bit running on LPAR with/without CPACF (PAI) Supermicro A1SAi Supermicro SMX11SPL-F <ul style="display: flex;"><li style="flex:1">Intel®Atom™ </li><li style="flex:1">Ubuntu 16.04 LTS 64-bit with/without </li></ul><ul style="display: flex;"><li style="flex:1">AES-NI (PAA) </li><li style="flex:1">C2750 </li></ul>Intel® Xeon® Silver 4216 <ul style="display: flex;"><li style="flex:1">x86_64 </li><li style="flex:1">Ubuntu 16.04 LTS 64-bit with/without </li></ul>AES-NI (PAA) Table 3 - Tested Platforms Note: Per [FIPS 140-2_IG] G.5, the Cryptographic Module Validation Program (CMVP) makes no statement as to the correct operation of the module or the security strengths of the generated keys when this module is ported and executed in an operational environment not listed on the validation certificate. 1.2. Modes of Operation The module supports two modes of operation: FIPS mode (the Approved mode of operation): only approved or allowed security functions with sufficient security strength can be used. non-FIPS mode (the non-Approved mode of operation): only non-approved security functions can be used. The module enters FIPS mode after power-up tests succeed. Once the module is operational, the mode of operation is implicitly assumed depending on the security function invoked and the security strength of the cryptographic keys. Critical security parameters used or stored in FIPS mode are not used in non-FIPS mode, and vice versa. © 2020 Canonical Ltd. / atsec information security <ul style="display: flex;"><li style="flex:1">This document can be reproduced and distributed only whole and intact, including this copyright notice. </li><li style="flex:1">9 of 46 </li></ul><ul style="display: flex;"><li style="flex:1">Kernel Crypto API Cryptographic Module </li><li style="flex:1">FIPS 140-2 Non-Proprietary Security Policy </li></ul>2. Cryptographic Module Ports and Interfaces As a software-only module, the module does not have physical ports. For the purpose of the FIPS 140-2 validation, the physical ports are interpreted to be the physical ports of the hardware platform on which it runs. The logical interfaces are the API through which kernel modules request services, and the AF_ALG type socket that allows the applications running in the user space to request cryptographic services from the module. The following table summarizes the four logical interfaces: FIPS Interface Data Input <ul style="display: flex;"><li style="flex:1">Physical Port </li><li style="flex:1">Logical Interface </li></ul>Keyboard Display API input parameters from kernel system calls, AF_ALG type socket. Data Output Control Input API output parameters from kernel system calls, AF_ALG type socket. <ul style="display: flex;"><li style="flex:1">Keyboard </li><li style="flex:1">API function calls, API input parameters for </li></ul>control from kernel system calls, AF_ALG type socket, kernel command line. Status Output Power Input <ul style="display: flex;"><li style="flex:1">Display </li><li style="flex:1">API return codes, AF_ALG type socket, </li></ul>kernel logs. <ul style="display: flex;"><li style="flex:1">PC Power Supply Port </li><li style="flex:1">N/A </li></ul>Table 4 - Ports and Interfaces © 2020 Canonical Ltd. / atsec information security <ul style="display: flex;"><li style="flex:1">This document can be reproduced and distributed only whole and intact, including this copyright notice. </li><li style="flex:1">10 of 46 </li></ul><ul style="display: flex;"><li style="flex:1">Kernel Crypto API Cryptographic Module </li><li style="flex:1">FIPS 140-2 Non-Proprietary Security Policy </li></ul>3. Roles, Services and Authentication 3.1. Roles The module supports the following roles: User role: performs cryptographic services (in both FIPS mode and non-FIPS mode), key zeroization, show status, and on-demand self-test. Crypto Officer role: performs module installation and initialization. The User and Crypto Officer roles are implicitly assumed by the entity accessing the module services.

FIPS 140-2 Non-Proprietary Security Policy

Details

Download

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

Support