Tenant isolation
Every read and write is bound to a tenant and provider resolved server-side from the session.
SECURITY
Each control is listed with its real status. A roadmap item is never shown as live, and no certification is claimed that is not held.
Every read and write is bound to a tenant and provider resolved server-side from the session.
Role, plan, entitlement and approval requirements are evaluated on the server; the browser is never the authority.
Connector secrets are stored in a vault, referenced by handle, and never echoed into the UI or logs.
Public traffic and machine endpoints are served over TLS.
Scan targets are resolved before they reach the queue; private ranges, metadata endpoints and unsafe redirects are refused.
Scan budgets, rate limits and cost ceilings are enforced server-side.
Significant operations are appended with an actor, correlation id and record hash.
Approval queues for restricted write actions are being rolled out with the actions surface.
Sensitive operations require re-verification before they execute.
Operational backup and restore procedures are being formalised; status is published here as each is confirmed.
VENRAC holds no security certification today and does not claim one. Any future certification will be published with its scope and date.
To report a vulnerability, see /vulnerability-disclosure.