{"product_id":11638,"v_id":11638,"product_name":"Cigent PBA Software v2.0","certification_status":"Certified","certification_date":"2025-09-05T00:00:00Z","tech_type":"Encrypted Storage","vendor_id":{"name":"Cigent Technology, Inc.","website":"https://www.cigent.com/"},"vendor_poc":"Conner Crisafulli","vendor_phone":"609-618-3765","vendor_email":"conner.crisafulli@cigent.com","assigned_lab":{"cctl_name":"Gossamer Security Solutions"},"product_description":"<p>The Target of Evaluation (TOE) is the Cigent PBA Software v2.0. The TOE is software that provides pre-boot authentication (PBA) suitable for authenticating users and passing a Border Encryption Value (BEV) to a Self-Encrypting Drive (SED), which encrypts data written to and decrypts data read from the SED.</p>\r\n<p>The TOE&rsquo;s Pre-Boot user Authentication (PBA) for Opal 2.0 compliant SEDs supporting MBR Shadowing. &nbsp;It has been evaluated with the Cigent M.2 2230 SED in order to exercise all functionality.</p>\r\n<p>The TOE&rsquo;s PBA software is installed on a 128MB read-only Shadow partition on the storage device. After installation, the PBA allows the user to authenticate, which unlocks the SED and boots to the protected OS environment.</p>\r\n<p>The Cigent M.2 2230 SED provides encrypted storage to protect data until the SED has successfully received the Border Encryption Validation (BEV) from an Authorization Acquisition component (like Cigent&rsquo;s PBA).</p>\r\n<p>The Cigent PBA Software acts as an Authorization Acquisition component that supplies the Border Encryption Validation (BEV) to an Encryption Engine component (like Cigent&rsquo;s M.2 2230).&nbsp; The PBA software can interoperate with any FDE EE certified SSD supporting Opal 2.0 and MBR shadowing.</p>","evaluation_configuration":"<p>The Target of Evaluation (TOE) is the Cigent PBA Software v2.0.</p>","security_evaluation_summary":"<p>The evaluation was carried out in accordance to the Common Criteria Evaluation and Validation Scheme (CCEVS) requirements and guidance.&nbsp; The evaluation demonstrated that the TOE meets the security requirements contained in the Security Target.&nbsp; The criteria against which the TOE was judged are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1, Revision 5, April 2017. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Evaluation Methodology, Version 3.1, Revision 5, April 2017.&nbsp; The product, when delivered and configured as identified in the Cigent Cigent Single and Multidrive PBA Installation Guide and User Manual June 2025, PBA Version 2.0.0 document, satisfies all of the security functional requirements stated in the Cigent PBA Software v2.0 Security Target, Version 1.4, August 27, 2025.&nbsp; The project underwent CCEVS Validator review.&nbsp; The evaluation was completed in August 2025.&nbsp; Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11638-2025) prepared by CCEVS.</p>","environmental_strengths":"<p>The logical boundaries of the PBA Software are realized in the security functions that it implements. Each of these security functions is summarized below.</p>\r\n<p><strong>Cryptographic support:</strong></p>\r\n<p>The TOE includes cryptographic functionality for key management, user authentication, and block-based encryption including: symmetric key generation, encryption/decryption, cryptographic hashing, keyed-hash message authentication, and password-based key derivation. These functions are supported with suitable random bit generation, key derivation, salt generation, initialization vector generation, secure key storage, and key destruction. These primitive cryptographic functions are used to protect key chain keys related to validating and transforming user supplied authorization factors.</p>\r\n<p><strong>Security management:</strong></p>\r\n<p>The TOE provides each of required management services to manage the full drive encryption using a graphical user interface.</p>\r\n<p><strong>Protection of the TSF:</strong></p>\r\n<p>The TOE implements a number of features to protect itself to ensure the reliability and integrity of its security features. It protects key and key material, and includes functions to perform self-tests and software/firmware integrity checking so that it might detect when it is failing or may be corrupt.&nbsp; If any of the self-tests fails, the TOE will not go into an operational mode</p>","features":[{"id":319,"feature_name":"Cryptographic Hashing"},{"id":317,"feature_name":"Cryptographic Signature Verification"},{"id":314,"feature_name":"DRBG"},{"id":311,"feature_name":"Full Drive Encryption"},{"id":323,"feature_name":"Key Destruction"},{"id":320,"feature_name":"Keyed-hash message authentication"},{"id":316,"feature_name":"Symmetric Key Generation"}]}