{"product_id":11660,"v_id":11660,"product_name":"Cigent Software FDE version 1.2.1","certification_status":"Certified","certification_date":"2026-02-09T00: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 Software FDE version 1.2.1.&nbsp;&nbsp;</p>\r\n<p>The software TOE consists an OS-independent UEFI pre-boot authentication component (the &ldquo;AA&rdquo;) and an OS-specific file system driver component (the &ldquo;EE&rdquo;).</p>\r\n<p>The TOE&rsquo;s AA component accepts the user&rsquo;s authorization factors and if correct, unlocks the OS system partition, allowing the OS to boot.&nbsp; During the OS boot, the TOE&rsquo;s EE component allows the OS to decrypt and encrypt drive reads and writes (respectively).</p>\r\n<p>&nbsp;</p>","evaluation_configuration":"<p>The Target of Evaluation (TOE) is the Cigent Software FDE version 1.2.1.</p>\r\n<p>&nbsp;</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 Full Drive Encryption (FDE) Installation Guide and User Manual, Version 1.2.0, December 2025 document, satisfies all of the security functional requirements stated in the Cigent Software FDE Security Target, Version 1.5, February 4, 2026.&nbsp; The project underwent CCEVS Validator review.&nbsp; The evaluation was completed in February 2026.&nbsp; Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report (report number CCEVS-VR-VID11660-2026) prepared by CCEVS.</p>","environmental_strengths":"<p>The logical boundaries of the Software FDE 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 encrypt Data-At-Rest (including the generation and protection of keys and key encryption keys) used by the TOE.</p>\r\n<p><strong>User data protection:</strong></p>\r\n<p>The TOE performs Full Drive Encryption on all partitions on the drive (so that no plaintext exists) and does so without user intervention.</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 fail, the TOE will not go into an operational mode.</p>\r\n<p>&nbsp;</p>","features":[{"id":275,"feature_name":"Cryptographic Hashing"},{"id":274,"feature_name":"Cryptographic Signature Verification"},{"id":268,"feature_name":"Full Drive Encryption"},{"id":329,"feature_name":"Key Destruction"},{"id":277,"feature_name":"Keyed-hash message authentication"},{"id":272,"feature_name":"Symmetric Key Generation"}]}