What the clause says
The system should allow an age attribute to be forwarded to another provider only where the person or the policy permits it.
What it supplies to a comparison
Forwarding spreads the data beyond the tested boundary. The comparison should map every onward transfer and its authority.
Evidence to keep
- The transfer map, naming each recipient and the basis.
- The consent or policy record for each transfer.
What the evidence looks like
For 8.1.5, the first artefact is The transfer map, naming each recipient and the basis.. The second is The consent or policy record for each transfer.. If 8.1.5 has no first artefact, the practice is unproven at 8.1.5, and the report should record the absence rather than infer the practice from a policy.
Questions for the provider
- Where does the attribute go after the relying party receives it?
- Is each onward transfer permitted, and by whom?
How it connects to the draft
Forwarding only where allowed belongs to 8 security objectives, and it gives the analysis one fixed point: Forwarding spreads the data beyond the tested boundary. The comparison should map every onward transfer and its authority. A comparison that cannot place a result against 8.1.5 is measuring something the framework has not defined, and the report should say so.
In the register, 8.1.5 is read beside the unit that tests it, and where it sets an objective rather than a number, that unit turns the objective into a question and an evidence artefact.
Source for this page
Sources: ISO/IEC 27566-1:2025 official record. The published framework record, free from ISO. ISO/IEC JTC 1/SC 27/WG 5 N3927, AWI 27566-1 working draft WD2.0. Public working draft WD2.0 of the framework, at the ETSI document box. Retrieved 2026-10-21. 8.1.5 is our statement of the working draft; the published edition is authoritative.