Limitation of Use and Data Retention Policy

Sizing

ESET Inspect currently supports up to 25,000 endpoints per instance. If more endpoints require protection, consider dividing your environment into multiple ESET Inspect and ESET PROTECT instances. For example, based on multiple physical locations or branches of your organization. Alternatively, consider utilizing the ESET Inspect On-Prem, which supports a higher number of endpoints (use the calculator to scale the ESET Inspect On-Prem for your environment).

Data retention

ESET Inspect is running in lightweight mode. Thus the data collection type is set to Store most important data.

•The retention period for raw events is seven days. Older records are removed permanently.

•The retention period for detections is 31 days. Older records are removed permanently.

Backup and recovery

We back up the ESET Inspect databases using the built-in backup capability of Microsoft Azure. Backups are maintained solely for service continuity and disaster recovery purposes.

Backup scope and schedule

Backups cover both types of databases used by ESET Inspect:

•Azure Cosmos DB stores license and configuration data.

•Azure Database for MySQL flexible server stores customer data.

Both database types are backed up continuously. Backups are retained for seven days, and data can be restored to any point in time within this period.

Backup storage and integrity

•Backup data is encrypted at rest.

•All backup data is stored and maintained within the service region.

•Backup copies are managed by us and are not directly accessible to customers.

•We rely on the built-in mechanisms of Azure to verify the integrity of backup data.

Data restoration

Only a whole database server can be restored. Restoration of individual customer-deleted items or configurations is not supported.

The restore time depends on the database size and ranges from 30 minutes to approximately 12 hours for the largest databases. Manual operations, such as updating the configuration, require additional time.

Depending on the size of your environment, your data is stored on a dedicated database server or on a shared database server. The procedure to restore your data depends on the server type:

•Dedicated database server—We restore the server from backup and update the configuration.

•Shared database server—We restore the whole server from backup to a temporary server, move your data from the temporary server, update the configuration and remove the temporary server. This procedure takes longer.

For details about the shared responsibility for security, see How to securely use ESET Inspect.

Database limitations

Character limitations were implemented for all events to limit the database growth. These character limitations were set to 260.