Policy Evaluation Role

Go up to Terms and Definitions

Discussion

The Policy Evaluation Role identifies responsibility for evaluating policy constraints governing access, disclosure, safeguarding, release, redaction, transformation, marking, obligations, or the controlled movement of FX information.

This role includes receiving policy decision requests, evaluating requested release context, assessing policy constraints, producing FX Policy Decisions, and recording policy evaluation rationale and provenance.

The Policy Evaluation Role participates primarily in the FX Logical Policy and Release Plane. It also supports the FX Logical Audit and Provenance Plane when policy decisions preserve policy version, input references, decision rationale, obligations, and evidence expectations.

Definition

responsible for evaluating policy constraints governing access, disclosure, safeguarding, release, redaction, transformation, marking, obligations, or controlled movement of FX information

Source

Specialization of Logical Node Role from Part 2: Distributed Node-Based Logical Architecture, Section 6.4, Logical Policy Constraints from Part 2: Distributed Node-Based Logical Architecture, Section 11.7, and Policy and Release Plane from Part 1: Conceptual Architecture, Section 8.5; generalised from IEF policy-layer and policy-decision material in the original FX Demo Reference Architecture.

Note

The Policy Evaluation Role does not prescribe a policy language, policy engine, access-control product, rules engine, redaction tool, gateway, API, or service.

Example

The FX Policy and Release Node performs the Policy Evaluation Role when it evaluates whether selected FX information qualifies for disclosure to an External Oversight Participant.