WIXLIB

FIPS 140-2 Non-Proprietary Security Policy: Aerospike Enterprise Database Federal Edition FIPS 186-4 RSAANSIX9.31Sig Gen 1024 using SHA-1PKCSI V1 5Sig Gen 1024 using SHA-1PSSSig Gen 1024 using SHA-1 FIPS 186-2 ECDSAKey Pair Generation: CurvesSig Gen Curves All P, K & BP-192, K-163 & B-163 FIPS 186-4 ECDSAKey Pair Generation: CurvesP-192, K-163 & B-163Sig Gen Curves P-224, P-256, P-384, P-521, K-233, K-283, K-409, K-571,B-233, B-283, B-409 & B-571) (using SHA-1)P-192-, K-163 & B-163 (any SHA size) CVL (ECC CDH KAS)The following algorithms are disallowed as of September 1, 2020 per the FIPS 186-2 transitions: FIPS 186-2 RSA (X9.31, PKCS #1.5, PSS)o ANSIX9.31 Key Gen: 2048-bit, 3072-bit & 4096-bit Sig Gen: 2048-bit, 3072-bit (any SHA size) Sig Gen: 4096-bit using SHA-1oPKCS1 V1 5 Sig Gen: 2048-bit, 3072-bit (any SHA size) Sig Gen: 4096-bit using SHA-1oPSS Document Version 1.0Sig Gen: 2048-bit, 3072-bit (any SHA size)Sig Gen: 4096-bit using SHA-1 Aerospike, Inc.Page 11 of 23

FIPS 140-2 Non-Proprietary Security Policy: Aerospike Enterprise Database Federal Edition2.2 Module InterfacesThe figure below shows the module’s physical and logical block diagram:Figure 1 – Module Boundary and Interfaces DiagramThe interfaces (ports) for the physical boundary include the computer keyboard port, mouse port,network port, USB ports, display and power plug. When operational, the module does not transmit anyinformation across these physical ports because it is a software cryptographic module. Therefore, themodule’s interfaces are purely logical and are provided through the Application Programming Interface(API) that a calling daemon can operate. The logical interfaces expose services that applications directlycall, and the API provides functions that may be called by a referencing application (see Section 2.3 –Roles, Services, and Authentication for the list of available functions). The module distinguishes betweenlogical interfaces by logically separating the information according to the defined API.The API provided by the module is mapped onto the FIPS 140-2 logical interfaces: data input, dataoutput, control input, and status output. Each of the FIPS 140-2 logical interfaces relates to the module’scallable interface, as follows:Document Version 1.0 Aerospike, Inc.Page 12 of 23

FIPS 140-2 Non-Proprietary Security Policy: Aerospike Enterprise Database Federal EditionFIPS 140-2 InterfaceData InputData OutputControl InputStatus OutputPowerLogical InterfaceInput parameters of API functioncallsOutput parameters of API functioncallsAPI function callsFor FIPS mode, function callsreturning status information andreturn codes provided by APIfunction calls.NoneModule Physical InterfaceNetwork InterfaceNetwork InterfaceKeyboard Interface, MouseInterfaceDisplay ControllerPower SupplyTable 4 – Logical Interface / Physical Interface MappingAs shown in Figure 1 – Module Boundary and Interfaces Diagram and Table 5 – Module Services, Roles,and Descriptions, the output data path is provided by the data interfaces and is logically disconnectedfrom processes performing key generation or zeroization. No key information will be output through thedata output interface when the module zeroizes keys.2.3 Roles, Services, and AuthenticationThe module supports a Crypto Officer and a User role. The module does not support a Maintenancerole. The User and Crypto-Officer roles are implicitly assumed by the entity accessing servicesimplemented by the module.2.3.1 Operator Services and DescriptionsThe module supports services that are available to users in the various roles. All the services aredescribed in detail in the module’s user documentation. The following table shows the services availableto the various roles and the access to cryptographic keys and CSPs resulting from services:ServiceModule ption/decryptionDigital signaturegenerationDigital SignatureverificationSymmetric keygenerationUserAES Key, Triple-DES KeyUserRSA Private Key, DSA Private Key, ECDSAPrivate KeyRSA Public Key, DSA Public Key, ECDSAPublic KeyAES Key, Triple-DES KeyDocument Version 1.0UserUserCSP / Algorithm Aerospike, ad/write/executePage 13 of 23

FIPS 140-2 Non-Proprietary Security Policy: Aerospike Enterprise Database Federal EditionServiceAsymmetric keygenerationKeyed Hash (HMAC)RolesUserCSP / AlgorithmDSA Private Key, ECDSA Private KeyUserMessage digest (SHS)UserRandom numbergenerationShow statusUserHMAC KeyHMAC SHA-1, HMAC SHA- 224, HMAC SHA256, HMAC SHA-384, HMAC SHA-512SHA-1, SHA-224, SHA-256, SHA-384, SHA512DRBG Internal State, DRBG EntropySelf serAll te/executeUser and ble 5 – Module Services, Roles, and DescriptionsThe operator is required to review the sections Approved Cryptographic Algorithms, Non-Approved butAllowed Cryptographic Algorithms, Non-Approved Cryptographic Algorithms, and Guidance and SecureOperation to ensure only approved algorithms are used.2.3.2 Operator AuthenticationAs required by FIPS 140-2, there are two roles (a Crypto Officer role and User role) in the module thatoperators may assume. As allowed by Level 1, the module does not support authentication to accessservices. As such, there are no applicable authentication policies. Access control policies are implicitlydefined by the services available to the roles as specified in Table 5 – Module Services, Roles, andDescriptions.2.4 Physical SecurityThis section of requirements does not apply to this module. The module is a software-only module anddoes not implement any physical security mechanisms.2.5 Operational EnvironmentThe module operates on a general purpose computer (GPC) running a general purpose operating system(GPOS). For FIPS purposes, the module is running on this operating system in single user mode and doesnot require any additional configuration to meet the FIPS requirements.The module was tested on the following platform:Document Version 1.0 Aerospike, Inc.Page 14 of 23

FIPS 140-2 Non-Proprietary Security Policy: Aerospike Enterprise Database Federal Edition CentOS 7.3 running on a Dell Optiplex 755 with an Intel Celeron 430 processorFIPS 140-2 validation compliance is maintained for other compatible operating systems (in single usermode) where the module source code is unmodified, and the requirements outlined in NIST IG G.5 aremet. No claim can be made as to the correct operation of the module or the security strengths of thegenerated keys when ported to an operational environment which is not listed on the validationcertificate.The GPC(s) used during testing met Federal Communications Commission (FCC) FCC ElectromagneticInterference (EMI) and Electromagnetic Compatibility (EMC) requirements for business use as definedby 47 Code of Federal Regulations, Part15, Subpart B.2.6 Cryptographic Key ManagementThe table below provides a complete list of Critical Security Parameters and keys used within themodule:Keys and CSPsAES Key (128,192, 256 tMethodAPI callparameterOutputMethodNoneZeroizationpower cyclecleanse()AccessCO: RWDU: RWDEncrypt/DecryptoperationsUsed to generateand verify MACswith AES as partof the CMACalgorithm.Triple-DES Key(168 bits)RAMPlaintextAPI callparameterNonepower cyclecleanse()CO: RWDU: RWDUsed forEncrypt/Decryptoperations.Used forgenerating andverifying MACswith Triple- DESas part of theCMAC algorithm.Document Version 1.0 Aerospike, Inc.Page 15 of 23

FIPS 140-2 Non-Proprietary Security Policy: Aerospike Enterprise Database Federal EditionKeys and CSPsRSA Public Key(1024, 1536,2048, 3072, 4096bits)RSApublic/privatekeys used to signand verify data.RSA Private Key(2048, 3072,4096 bits)RSApublic/privatekeys used to signand verify data.DSA Public Key(1024, 2048, and3072 bits)DSApublic/privatekeys used to signand verify data.DSA Private Key(2048, and 3072bits)DSApublic/privatekeys used to signand verify data.HMAC Key ( nputMethodAPI callparameterOutputMethodAPI callparameterZeroizationpower cyclecleanse()AccessCO: RWDU: RWDRAMPlaintextAPI callparameterAPI callparameterpower cyclecleanse()CO: RWDU: RWDRAMPlaintextAPI callparameterAPI callparameterpower cyclecleanse()CO: RWDU: RWDRAMPlaintextAPI callparameterAPI callparameterpower cyclecleanse()CO: RWDU: RWDRAMPlaintextAPI callparameterAPI callparameterpower cyclecleanse()CO: RWDU: RWDHMAC keys usedto generate andverify MACs ondata.Integrity KeyModuleBinaryPlaintextNoneNoneNoneCO: RWDU: RWDDocument Version 1.0 Aerospike, Inc.Page 16 of 23

FIPS 140-2 Non-Proprietary Security Policy: Aerospike Enterprise Database Federal EditionKeys and CSPsECDSA PrivateKey (PKG: Curves(P-224, P-256, P384, P-521, K233, K-283, K409, K-571, B233, B-283, B409 & B-571)PKV: Curves AllP, K & B)ECDSApublic/privatekeys used to signand verify data.ECDSA Public Key(PKG: Curves (P224, P-256, P384, P-521, K233, K-283, K409, K-571, B233, B-283, B409 & B-571)PKV: Curves AllP, K & B)ECDSApublic/privatekeys used to signand verify data.DRBG Internalstate (V,C , InputMethodAPI callparameterOutputMethodAPI callparameterZeroizationpower cyclecleanse()AccessCO: RWDU: RWDRAMPlaintextAPI callparameterAPI callparameterpower cyclecleanse()CO: RWDU: RWDRAMPlaintextNoneNonepower cyclecleanse()CO: RWDU: RWDV and key areused as part ofHMAC and CTRDRBG process. Vand C are used aspart of HASHDRBG process.Document Version 1.0 Aerospike, Inc.Page 17 of 23

FIPS 140-2 Non-Proprietary Security Policy: Aerospike Enterprise Database Federal EditionKeys and CSPsDRBG putMethodAPI r cyclecleanse()CO: RWDEntropy inputstrings used aspart of the DRBGprocess.U: RWDR Read W Write D DeleteTable 6 – Module Keys/CSPsPlease note that keys can be generated by the module for the services that require those keys, but thekeys will always be input via an API call.The application that uses the module is responsible for appropriate destruction and zeroization of thekey material. The module provides functions for key allocation and destruction which overwrite thememory that is occupied by the key information with zeros before it is deallocated.2.6.1 Random Number GenerationThe module uses SP 800-90A DRBGs for creation of asymmetric and symmetric keys.The module accepts input from entropy sources external to the cryptographic boundary for use as seedmaterial for the module’s Approved DRBGs. The calling application of the module shall use entropysources that meet the security strength required for the random bit generation mechanism as shown inNIST Special Publication 800-90A Table 2 (Hash DRBG, HMAC DRBG) and Table 3 (CTR DRBG). At aminimum, the entropy source shall provide at least 128 bits of entropy to the DRBG.The module performs continual tests on the random numbers it uses to ensure that the seed inputs tothe Approved DRBGs do not have the same value. The module also performs continual tests on theoutput of the Approved DRBGs to ensure that consecutive random numbers do not repeat.In accordance with FIPS 140-2 IG D.12, the cryptographic module performs Cryptographic KeyGeneration (CKG) for asymmetric keys as per NIST SP 800-133rev2 (vendor affirmed). The resultingsymmetric key or asymmetric seed is an unmodified output from a DRBG.The AES GCM IV generation is in compliance with the RFC5288 and RFC5289 and shall only be used forthe TLS protocol version 1.2 to be compliant with [FIPS 140-2 IG] IG A.5, provision 1 (“TLS protocol IVgeneration”); thus, the module is compliant with [SP 800-52]. Refer to Section 3.2.1 for additional detail.2.6.2 Key/Critical Security Parameter (CSP) Authorized Access and Use by Role andService/FunctionAn authorized application as user (the User role) has access to all key data generated during theoperation of the module.Document Version 1.0 Aerospike, Inc.Page 18 of 23

FIPS 140-2 Non-Proprietary Security Policy: Aerospike Enterprise Database Federal Edition2.6.3 Key/CSP StoragePublic and private keys are provided to the module by the calling process and are destroyed whenreleased by the appropriate API function calls or during power cycle. The module does not performpersistent storage of keys.2.6.4 Key/CSP ZeroizationThe application is responsible for calling

The Aerospike Enterprise Database Federal Edition may also be referred to as the "module" in this document. 1.3 External Resources The Aerospike website (aerospike.com) contains information on Aerospike services and products. The Cryptographic Module Validation Program website contains links to the FIPS 140-2 certificate Aerospike