# 8.3 The mutual exchange and what both parties learn

The mutual exchange is the clause that makes this family distinct. It gives both entities assurance of the other identity, and it does so with a sequence that has to be read as a whole. Splitting it into two unilateral runs is the classic implementation error.

## What it asks

Record the mutual sequence and mark the point at which each party is assured, and test that a party which stops early does not leave the other assured. Keep the evidence for both directions, because a mutual claim with one direction tested is a unilateral claim.

## What the revision does

The fourth edition will restate the mutual exchange. The revised sequence is not in the public record.

## Who it binds

The operator of the mutual service and the tester who signs it off.

## Evidence an auditor samples

- The mutual sequence with both assurance points marked (design note)
- The early stop test and its output (test report)
- The evidence for each direction, kept separately (test report)

## The test you can run

Stop the exchange after the first direction. If the second party still reports success, the mutual claim is false.

## Common failures

- The mutual exchange is implemented as two independent unilateral exchanges.
- Only one direction is tested and the other is assumed symmetric.

## How to close it

Test each direction separately and test the early stop. Mutual authentication is an ordering property, and an ordering property is only shown by breaking the order.

## Source

ISO/IEC 9798-5:2009(E), 8.3, publisher preview; replaced by ISO/IEC DIS 9798-5, stage 40.20. Read on 21 October 2026. Our wording, not the instrument's.
https://www.iso.org/standard/89516.html

Not legal advice; does not certify.