What is the best password policy for Encryption on Workbench
Options
We have a requirement to encrypt a few fields while uploading via workbench. What will be a good encryption password policy? Let's say we have ten fields that need to be encrypted, and 30 users need access to them that they can decrypt with a password.
- do you create 30 different encryption passwords
- how do you manage these passwords ( FOR forgotten password or periodically changing the password)
If you are encrypting your field in the workbench, please give us some pointers.
Tagged:
1
Answers
-
You can't use 30 different passwords to encrypt the data unless you have 30 different datasets which I highly recommend against as that's quite a bit of management overhead.
Typically using a password manager where you can grant or revoke access to the different accounts / passwords is good practice so you don't have passwords floating out in the wild.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 -
Thanks Grant
0
Categories
- All Categories
- Product Ideas
- 2.1K Ideas Exchange
- Data Connections
- 1.3K Connectors
- 309 Workbench
- 17 Cloud Integrations
- Data & ETL
- 2.3K Magic ETL
- 120 SQL DataFlows
- 667 Datasets
- Visualize & Apps
- 90 App Studio
- 198 Pro-code Components
- 2.6K Charting & Analyzer
- 873 Calculations & Variables (Beast Mode)
- AI & Data science
- 23 Domo AI & AI Chat
- 4 Managing AI
- 18 Jupyter Workspaces
- Automate
- 122 Workflows
- Alerts
- Distribute
- 118 Domo Everywhere
- 284 Reporting
- Manage
- 145 Governance & Security
- 489 APIs
- 11 Add-ins & Plugins
- 13 Domo Community Gallery
- 49 Product Releases
- 13 Domo University
- Community Forums
- 41 Getting Started
- 31 Community Member Introductions
- 118 Community Announcements
- 5K Archive