Customize

Policies

Policies determine how vedSecure behaves on each endpoint. Good policy design keeps the product strict where it matters and flexible where work would otherwise be interrupted.

Start protectionRead quick start
Last updated: April 15, 2026

Policy scope and assignment

Policies can be assigned to individuals, teams, device classes, or staged cohorts. This makes it possible to handle very different endpoint roles without duplicating an entire security model for each group.

  • Executive policy
  • Engineering policy
  • Finance policy
  • Shared workstation policy

What a policy can control

Each vedSecure policy can shape exclusions, release cadence, ransomware folder protection, response automation, notification routes, and scan depth.

{
  "realtimeProtection": true,
  "behaviorEngine": "balanced",
  "scanMode": "smart-background",
  "protectedFolders": ["Finance", "Contracts", "Backups"],
  "exclusions": ["C:\\BuildCache"],
  "autoQuarantine": true
}

Policy review habits

Policies should be reviewed on a schedule, especially after internal tooling changes, department workflow changes, or new release-channel adoption. Unreviewed exclusions tend to become long-term risk debt.