This article is intended primarly for enterprises who use the features provided by our Team edition.
To assist with selecting the appropriate data source, here is a set of concerns and the list of data sources that can serve in such a context.
When choosing a non-on-premises data source, it is important to account for the security of data both at rest and in transit. It is strongly recommended to further encrypt data using a master key for file-based solutions or a security providerfor advanced data sources, ensuring that only authorized parties can access the data.
| CONCERN | Devolutions Server | Devolutions Hub Business |
|---|---|---|
| Self-hosted data | ||
| Cloud-hosted data | ||
| Unaccessible database to end users | ||
| Encryption at rest and in transit | ||
| Zero-knowledge on sensitive data | ||
| Privileged Access Management (PAM) module | Note 1 | |
| AD accounts used for authentication | ||
| AD group membership used to assign permissions | ||
| Activity logs | ||
| Data accessible globally | Note 2 | |
| Just-in-time (JIT) connections via Devolutions Gateway |
Notes
Note 1
The Privileged Access Management module in Devolutions Hub Business is currently in beta development. For further details, please contact our sales department.
Note 2
Exposing a Devolutions Server instance to the Internet without protection from DDoS attacks is not recommended. It is essential to use strong passwords and obscure account names that cannot be easily deduced through social data mining techniques.
Give us Feedback