A monitoring tool must be beyond reproach
VigilanceX handles security logs and detections: its own security is treated as a design requirement, not an option.
Read-only towards sources
VigilanceX never modifies Active Directory or Sophos Central. All queries towards sources and tenant data (including those from the AI agent) are read-only.
Least-privilege accounts
The installation kit uses a service account whose rights are limited to reading security logs. No administrator account is required, at any step of deployment or operations.
Encrypted secrets
Credentials and secrets required by connectors are stored encrypted. They are never displayed in clear text in the interface.
Data segregated per tenant
Each tenant has its own data, rules, retention and notifications. Permissions are granted per user: everyone only sees the tenants opened to them.
Controlled retention and archiving
Retention is configured per tenant. Monthly archiving produces compressed files to local or S3-compatible storage, restorable and downloadable from the interface.
Hosted at the service provider
The console is installed as containers, hosted at the service provider. Updates come from an image registry with built-in version checking.
Questions about VigilanceX security?
Discuss it directly with the publisher during a demonstration.
No public pricing: every deployment is scoped with you. Request a demonstration.
Get in touch