How we protect your data
Encryption in transit. All connections to the Zerov platform, including from the Zerov sensor, use TLS with certificate verification.
Encryption at rest. Stored data, including findings and inventory, is encrypted at rest.
Multi-factor authentication. Every user account must use multi-factor authentication.
Customer isolation. Each customer's data is stored separately and is reachable only by that customer's authenticated users. The customer is determined from the signed-in user's authentication, never from information a request supplies.
Credential protection. Credentials for the cloud and software accounts you connect are kept in encrypted secret storage and are never shown back in the platform. Sensor credentials and installation tokens are stored only as keyed hashes.
Audit logging. Administrative actions in the platform are logged with the acting user and source IP address.
How we handle personal data is described in our Privacy Policy and Data Processing Agreement.
Reporting a vulnerability
If you believe you have found a security vulnerability in Zerov, email security@zerov.io with the steps to reproduce it. We acknowledge reports within 5 business days.
- Do not access, change, or delete data that does not belong to you, and stop testing once you have confirmed a vulnerability.
- Do not degrade the service for other users, and do not use social engineering or physical attacks.
- Give us reasonable time to fix the issue before you disclose it publicly.
Safe harbor. We will not pursue legal action against you for good-faith security research that follows this policy.
Security incidents
If a security incident affects your data, we notify you without undue delay and no later than 72 hours after becoming aware of it.