The TOE is the INTEGRITY Enterprise OS – Archon Edition, which provides a secure computing environment for mobile platforms. The TOE provides end users with the ability to install their own custom user software in a high security sandbox, while maintaining a secure operating system enclave logically isolated from the end user’s application.
","evaluation_configuration":"","security_evaluation_summary":"The evaluation was carried out in accordance with the Common Criteria Evaluation and Validation Scheme (CCEVS) process and scheme. The criteria against which the INTEGRITY Enterprise OS – Archon Edition was evaluated are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 rev 5. The evaluation methodology used by the evaluation team to conduct the evaluation is the Common Methodology for Information Technology Security Evaluation, Version 3.1 rev 5. Acumen Security determined that the evaluation assurance level (EAL) for the product is EAL 1. The product, when delivered configured as identified in the INTEGRITY Enterprise OS – Archon Edition Common Criteria User Guidance, satisfies all of the security functional requirements stated in the INTEGRITY Enterprise OS Security Target. The project underwent CCEVS Validator review. The evaluation was completed in May 2022. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.
","environmental_strengths":"The TOE implements the following security functional requirements from [OSPP]:
\r\nThe TOE audits the following events and details:
\r\n· Audit all administrative functions.
\r\n· Audit all security-relevant functions of the OS.
\r\n· Audit the causing user, calling process, and specific error messages for any logged events.
\r\nThe TOE includes the INTEGRITY Crypto Library v1.0 (ICL). Functions implemented with ICL are in service of all cryptographic functionality required by the SFRs. The TOE supports the following cryptographic functions:
\r\n| \r\n SFR \r\n | \r\n\r\n Cryptographic Algorithm \r\n | \r\n\r\n Operating Env. \r\n | \r\n\r\n Modes & Key Sizes \r\n | \r\n\r\n CAVP \r\n | \r\n
| \r\n FCS_CKM.1 \r\n | \r\n\r\n ECC KeyGen in accordance with FIPS 186-4 Appendix B.4 \r\n | \r\n\r\n SWIC Operating System 1.0 on INTEGRITY-IoT-2020.24 RTOS Microkernel \r\n | \r\n\r\n NIST Curves P-256, P-384, P-521 \r\n | \r\n\r\n C1871 \r\n | \r\n
| \r\n FCS_CKM.2 \r\n | \r\n\r\n Elliptic Curve key establishment in accordance with NIST SP 800-56A \r\n | \r\n\r\n SWIC Operating System 1.0 on INTEGRITY-IoT-2020.24 RTOS Microkernel \r\n | \r\n\r\n NIST Curves P-384 \r\n | \r\n\r\n C1871 \r\n | \r\n
| \r\n FCS_COP.1(1) \r\n | \r\n\r\n AES-XTS in accordance with NIST SP 800-38E \r\n | \r\n\r\n SWIC Operating System 1.0 on INTEGRITY-IoT-2020.24 RTOS Microkernel \r\n | \r\n\r\n 256-bit \r\n | \r\n\r\n C1871 \r\n | \r\n
| \r\n AES-GCM in accordance with NIST SP 800-38D \r\n | \r\n\r\n SWIC Operating System 1.0 on INTEGRITY-IoT-2020.24 RTOS Microkernel \r\n | \r\n\r\n 256-bit \r\n | \r\n\r\n C1871 \r\n | \r\n|
| \r\n FCS_COP.1(2) \r\n | \r\n\r\n SHA-1, SHA-256, SHA-384, SHA-512 in accordance with FIPS Pub 180-4 \r\n | \r\n\r\n SWIC Operating System 1.0 on INTEGRITY-IoT-2020.24 RTOS Microkernel \r\n | \r\n\r\n 160 bits for SHA-1, 256 bits for SHA-256; 384 bits for SHA-384; 512 bits for SHA-512 \r\n | \r\n\r\n C1871 \r\n | \r\n
| \r\n FCS_COP.1(3) \r\n | \r\n\r\n ECDSA SigGen and SigVer in accordance with FIPS Pub 186-4 Section 5 \r\n | \r\n\r\n SWIC Operating System 1.0 on INTEGRITY-IoT-2020.24 RTOS Microkernel \r\n | \r\n\r\n NIST curve P-384 \r\n | \r\n\r\n C1871 \r\n | \r\n
| \r\n RSA SigGen and SigVer in accordance with FIPS Pub 186-4 \r\n | \r\n\r\n SWIC Operating System 1.0 on INTEGRITY-IoT-2020.24 RTOS Microkernel \r\n | \r\n\r\n 2048-bit \r\n | \r\n\r\n C1871 \r\n | \r\n|
| \r\n FCS_COP.1(4) \r\n | \r\n\r\n SHA-1, SHA-256, SHA-384, SHA-512 in accordance with FIPS Pub 198-1 and FIPS Pub 180-4 \r\n | \r\n\r\n SWIC Operating System 1.0 on INTEGRITY-IoT-2020.24 RTOS Microkernel \r\n | \r\n\r\n For SHA-256, a 256-bit key size and message size. \r\nFor SHA-384, a 384-bit key size and message size. \r\nFor SHA-512, a 512-bit key size and message size. \r\n | \r\n\r\n C1871 \r\n | \r\n
| \r\n FCS_RBG_EXT.1 \r\n | \r\n\r\n HMAC_DRBG in accordance with NIST SP 800-90A \r\n | \r\n\r\n SWIC Operating System 1.0 on INTEGRITY-IoT-2020.24 RTOS Microkernel \r\n | \r\n\r\n Random number generation for all cryptography \r\n | \r\n\r\n C1871 \r\n | \r\n
The TOE protects all user data on disk via always-on encryption. All data on the disk, including the OS files and all user data, are automatically encrypted. This includes all Protection Profile-defined Sensitive Data, including:
\r\n· User application private keys, secrets, and key material.
\r\n· Certificates and keys used for trusted path establishment, trusted channel establishment, and trusted update verification.
\r\nThe TOE implements user identification and authentication, including authentication failure limiting, at all administrative interfaces. No more than three consecutive unsuccessful authentication attempts on any given power cycle. The TOE requires that the administrator successfully authenticate prior to performing any management or configuration functions.
\r\nThe TOE supports the use of X.509v3 certificates, including revocation and validity checking. The administrator may choose which certificate is used for any given trusted path or trusted channel.
\r\nThe TOE permits authorized and authenticated administrators to perform the following management functions:
\r\n· Set the inactivity timeout.
\r\n· Configure trusted paths and channels.
\r\n· Configure the networking parameters.
\r\n· Configure automatic updates.
\r\n· Management of user accounts.
\r\nThe TOE implements protection of the kernel, audit logs and functions, and credential repositories. The TOE implements Address Space Layout Randomization and Stack-Based Buffer Overflow protection. The TOE performs self-tests of the cryptographic functions prior to operation and implements security checking prior to installing updates.
\r\nThe TOE provides a TLS trusted communication path to both administrators and trusted IT entities that protects the channel data from modification or compromise.
","features":[]}