Connector Policies

Connector policies let you define governance rules for the connectors used across your platform. Policies classify connectors as Allowed, Restricted, or Blocked, and Velnoro flags violations during scans.

Adding a Policy

1. Navigate to Governance > Policies tab
2. Click Add Policy
3. Enter the connector name (e.g., "HTTP", "SQL Server", "OpenAI")
4. Select the platform
5. Choose a status:
   • Allowed - approved for use, no violations generated
   • Restricted - generates violations requiring review (e.g., needs DLP approval before use)
   • Blocked - generates violations indicating prohibited use
6. Add a reason explaining why (e.g., "External data access requires DLP review")
7. Click Save

Editing a Policy

Click the edit button on any policy row to change its status or reason. Updated policies take effect on the next scan.

Deleting a Policy

Click the delete button and confirm. Removing a policy removes any associated violations from future scans. Existing violation records in the audit log are preserved.

How Violations Work

When a scan runs, Velnoro checks each asset's connectors against your policy set:

• Blocked and Restricted connectors both generate violations visible in the Assets tab under the "Violations" filter
• Allowed connectors pass without flags

Violations include the connector name, the policy reason, and a link to the asset.

Permissions

FAQ

Q: Do policies apply retroactively? Yes. After adding a new policy, run a scan. The scan re-evaluates all assets against the updated policy set.

Q: Can I create policies based on asset type or environment? Currently, policies match by connector name and platform. Condition-based rules (asset type, environment, ownership) are on the roadmap.

Q: Where can I see a history of policy changes? The Audit Log records all policy changes with timestamps and actor information.