Templates

The GDPR baseline and Financial services (DORA) policy templates, what rules each one starts with, and how to use them.

Enterprise. A template is a starting set of rules for a new policy. On Community the template cards are shown locked; a Blank policy is available on every edition.

+ New policy offers the two templates and a blank policy. A policy from a template starts as a draft in Monitor. Its rules are then the policy's own: edit them like any draft. A template adds no compliance mapping.

A template is a starting point that assists with a framework. It is not a certification, and Elizon does not check that your Organization meets any regulation.

Rule	GDPR baseline	Financial services (DORA)
Personal data, before non-Local models	Replaced with placeholders	Replaced with placeholders
Financial data	Replaced with placeholders before non-Local models	Local models only: the run is routed to a capable Local configuration
Confidential business data	No rule	Local models only, routed the same way
Credentials, at the model call	Denied before every model, Local included	Denied before every model, Local included
Name recognition	PERSON, at 80 % confidence	PERSON, at 80 % confidence
Content above the name-recognition size cap	Patterns only, logged `partial_scan`	Blocked
Real values in the answer the user sees	Yes	No: the user sees placeholders

Both are written with routing.data_rules, so the draft shows the rules instead of relying on the defaults.

Under Financial services (DORA):

With no capable Local configuration, a call carrying financial or confidential business data is denied. Set one up before you switch to Enforce.
A routed run's tool calls that carry a routed value wait for review unless the tool is marked for it. See the 0.26.1 change.

Monitor shows you what either template would do on your traffic. See Monitor and enforce.