Entity List Filter

The entity-list-filter policy checks content against blocked_entities. An empty list causes no checks. The policy returns allow and records a warning.

This policy matches customer-configured names. It is not a sanctions list, restricted-party database, or legal screening service.

Configuration

pack:
  name: entity-list-filter-example
  version: 1.0.0
  enabled: true

policies:
  chain:
    - entity-list-filter

policy:
  entity-list-filter:
    blocked_entities:
      - Example Restricted Entity
      - Northwind Export Group
      - Contoso Research Holdings
    fuzzy_matching: true
    max_distance: 2

Fields

Field	Type	Description	Default
blocked_entities	string[]	Entity names to examine. Add names for this policy to enforce a block.	[]
action	block	The only accepted and effective action.	block
fuzzy_matching	boolean	Enable near-match detection for spelling variations and transliterations.	false
max_distance	integer	Maximum edit distance used with fuzzy matching.	1

The policy always blocks when it finds a match. block is the only accepted action value.

How it works

1. Verdictan makes one text buffer from the message content.
2. It checks each configured entity with case-insensitive matching.
3. When fuzzy_matching is enabled, it also compares token windows with the configured entity strings.
4. On a match, the policy blocks the request with reason_code: entity_list.triggered.

Best practices

• Do not rely on this policy without populating blocked_entities.
• Prefer full names, not short fragments, to decrease false positives.
• Use fuzzy matching only for names that frequently have transliterations or spelling errors.
• Use Trail and Audit Evidence when stored check evidence is necessary. audit-logger only adds an audit marker.

Use with other policies

Combination	Effect
entity-list-filter + itar-ear-filter	Matches configured names and export-control terms in the same chain.
entity-list-filter + dual-use-filter	Adds configured topic terms beside entity-name matching.
entity-list-filter + audit-logger	Adds an audit marker to the decision stream. Configure evidence storage in its owning workflow.
entity-list-filter + data-routing-policy	Uses content screening with provider-side routing constraints.

Next steps

• Dual-Use Filter — Dual-use term controls
• ITAR/EAR Filter — Export-control blocking
• DLP Filter — Custom regex and term matching
• Audit Logger — Decision logging