Review updates to CON_ topic

### 6.7.3 CON_INGEST-3

**Objective:** Protect the ingested data confidentiality.

**Objective:** The ingested data confidentiality is maintained during their transmission.

**Preparation:**

#### 6.7.1.2 CON_CRYPTO-2

**Objective:** Prevent attackers from modifying the connectivity to a more favorable cipher suite.

**Objective:** Attackers cannot version-rollback, downgrade or shorten key length of the actually deployed cipher suite.

**Preparation:**

**Activities:**

1. Study the product operation.

1. Study the product operation;

2. Try to rollback to an older cryptographic version.

**Verdict:**

1. Pass, if the listed requirements are implemented.

2. Fail otherwise.

1. Pass, if the listed requirements are implemented

2. and if the rollback trial is rejected with corresponding log entry.

3. Fail otherwise.

**Supporting Evidence:**

* Relevant vendor or design documentation describing the applied measures;

* Test reports showing the steps performed and results obtained;

* Screenshots, captures, or console outputs confirming the correct execution or protection behaviour;

* Screenshots, captures, or console outputs confirming the rejection of the rollback trial;

* Logs, configuration files, or audit traces demonstrating the implementation of the requirement.

### 6.7.2.2 CON_CHANNEL-2

**Objective:** Mutual authentication ensures that blind trust is not part of the system design.

**Objective:** All communicating entities are mutually authenticated with cryptographic means.

**Preparation:** None