Conditional attribute exchange

What the clause says

The system should release an attribute only when the condition for releasing it is met, rather than releasing it by default.

What it supplies to a comparison

The comparison should test the condition and the default. A system that releases on request, without a policy check, fails the objective even if it logs the release.

Evidence to keep

• The release rule and the policy that authorises it.
• A refused request test showing the default is closed.

What the evidence looks like

For 7.1.7, the first artefact is The release rule and the policy that authorises it.. The second is A refused request test showing the default is closed.. If 7.1.7 has no first artefact, the practice is unproven at 7.1.7, and the report should record the absence rather than infer the practice from a policy.

Questions for the provider

1. What condition must be met before the attribute is released?
2. What happens when the requester is not entitled to it?

How it connects to the draft

Conditional attribute exchange belongs to 7 privacy objectives, and it gives the analysis one fixed point: The comparison should test the condition and the default. A system that releases on request, without a policy check, fails the objective even if it lo. A comparison that cannot place a result against 7.1.7 is measuring something the framework has not defined, and the report should say so.

In the register, 7.1.7 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.