{"product_id":11575,"v_id":11575,"product_name":"CAE MPIC v3.5","certification_status":"Certified","certification_date":"2025-06-05T00:00:00Z","tech_type":"Network Device,Remote Access","vendor_id":{"name":"CAE Inc.","website":"cae.com"},"vendor_poc":"Paula Mazzaferro","vendor_phone":null,"vendor_email":"paula.mazzaferro@cae.com","assigned_lab":{"cctl_name":"Lightship Security USA, Inc."},"product_description":"

The CAE MPIC is a standalone physical Network Device, used to transmit data from the hardware panels to a software-based flight simulation, processed by one or more Daughter Boards (DB). The simulation data is processed by the DB’s and then feedback is transmitted back to the hardware panels via the MPIC. It comes in a range of form factors MPIC, MPIC-PCMIP, MPIC-EMB, MPIC-ILAC, MPIC-SBC. The different form factors can be installed in combination or independently to Network data. All form factors provide a basic set of security functions such as, a secure remote management path, identification and authentication services to trusted administrators, and secure auditing of administrator actions.  The form factors are not security relevant and the claimed SFRs are supported across all TOE models.

\r\n

The MPIC-PCMIP form factor differs as it has a standard type slot for extensions compared to the custom interface on the MPIC. The MPIC-EMB differs as it is designed to be embedded and not mounted into systems. The MPIC-ILAC differs as its main function is to supply variable AC voltage to the cockpit integral lighting. The MPIC-SBC differs as its main function is to provide faster ethernet computing with a second ethernet port and a 48 pin daughterboard connector for demanding autopilot simulation.

","evaluation_configuration":"

The physical boundary of the TOE includes all software and hardware shown in the table below: 

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n
\r\n

Type/Model

\r\n		\r\n

CPU

\r\n		\r\n

Part Number

\r\n		\r\n

Software

\r\n		\r\n

Differences

\r\n
\r\n

MPIC

\r\n		\r\n

i.MX6 ARM Cortex-A9 (ARMv7-A) with CAAM

\r\n		\r\n

MA505400.61.2.268

\r\n		\r\n

cae-mx6qmpic-3.5.10
MPICLinuxDistributionXR 3.5

\r\n		\r\n

Form Factor

\r\n
\r\n

MPIC-PCMIP

\r\n		\r\n

i.MX6 ARM Cortex-A9 (ARMv7-A) with CAAM

\r\n		\r\n

MA505402.61.2.268

\r\n
\r\n

MPIC-EMB

\r\n		\r\n

i.MX6 ARM Cortex-A9 (ARMv7-A) with CAAM

\r\n		\r\n

MA505404.61.2.268

\r\n
\r\n

MPIC-EMB

\r\n		\r\n

i.MX6 ARM Cortex-A9 (ARMv7-A) with CAAM (quad-core)

\r\n		\r\n

MA505404.62.2.268

\r\n
\r\n

MPIC-ILAC

\r\n		\r\n

i.MX6 ARM Cortex-A9 (ARMv7-A) with CAAM

\r\n		\r\n

MA563540.61.2.268

\r\n
\r\n

MPIC-SBC

\r\n		\r\n

i.MX6 ARM Cortex-A9 (ARMv7-A) with CAAM (quad-core)

\r\n		\r\n

MA563510.61.2.268

\r\n
","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 MPIC v3.5 was evaluated are described in the Common Criteria for Information Technology Security Evaluation, Version 3.1 Rev. 5. The product, when configured as identified in the CAE MPIC v3.5 Common Criteria Guide, v1.2, May 2025, satisfies all of the security functional requirements stated in the CAE MPIC v3.5 Security Target, v1.11, May 2025. The project underwent CCEVS Validator review. The evaluation was completed in June 2025. Results of the evaluation can be found in the Common Criteria Evaluation and Validation Scheme Validation Report prepared by CCEVS.

","environmental_strengths":"

The TOE provides the following security functions:

\r\n
    \r\n
  1. Trusted Path/Channels. The TOE protects the integrity and confidentiality of communications as noted in the ST, and using cryptographic algorithms as claimed in the ST.
    2. \r\n
  2. Security Management. The TOE enables secure management of its security functions, including:\r\n
      \r\n
    1. Administrator authentication with passwords
      2. \r\n
    2. Configurable password policies
      3. \r\n
    3. Role Based Access Control
      4. \r\n
    4. Access banners
      5. \r\n
    5. Management of critical security functions and data
      6. \r\n
    6. Protection of cryptographic keys and passwords
      7. \r\n
    \r\n
    3. \r\n
  3. Protection of the TSF. The TOE performs a suite of self-tests to ensure the correct operation and enforcement of its security functions. The TOE performs diagnostic self-tests and cryptographic module self-tests during start-up.
    4. \r\n
  4. Identification and Authentication. The TOE ensures that all users must be authenticated before accessing its functions and data.
    5. \r\n
  5. TOE Access. TOE can be accessed directly via serial connection or remotely via SSH connection. When a user account has sequentially failed authentication the configured number of times, the account will be locked for a Security Administrator defined time period.
    6. \r\n
  6. Security Audit. The TOE generates audit records of user and administrator actions. The TOE includes the user identity in audit events resulting from actions of identified users. The Security Administrator can configure the TOE to send logs in real-time to a syslog server via SSH.
    7. \r\n
  7. Cryptographic Support. The TOE implements a cryptographic module. The cryptographic module has the ability to generate and destroy cryptographic keys. Relevant Cryptographic Algorithm Validation Program (CAVP) certificates are shown in Table 4 of the ST.
    8. \r\n
","features":[{"id":3248,"feature_name":"Asymmetric Key Generation"},{"id":3336,"feature_name":"Auditing"},{"id":3251,"feature_name":"Cryptographic Hashing"},{"id":3249,"feature_name":"Cryptographic Key Establishment"},{"id":3250,"feature_name":"Cryptographic Signature Verification"},{"id":3247,"feature_name":"DRBG"},{"id":3335,"feature_name":"Flaw Remediation"},{"id":3252,"feature_name":"Keyed-hash message authentication"},{"id":3245,"feature_name":"SSH Client"},{"id":3246,"feature_name":"SSH Server"}]}