The data will be encrypted in DB therefore a DB Admin won’t be able to steal it.
Two possible implementations:
1.On AddQueueItem add a property SpecificDataEncrypted. SpecificData works exactly like now and won’t be Encrypted. SpecificDataEncrypted won’t be visible in the Orchestrator UI and only a robot can have access to it.
Pros: Full Flexibility to decide what data is Encrypted Cons: Pressure on the developer to decide which goes Encrypted and which not. He will need to work with two QueueItem properties.
2.In the Orchestrator you have the option to encrypt the queue. Encrypted Queue means the entire Specific Data get Encrypted and not available in UI.
Pros: Centralized governance - decide at the Orchestrator level (and not at the process design level) what queue goes encrypted Cons: Less flexibility. Everything will be encrypted or everything will be visible. Sometimes you need some data for debug, verify.
Note. This feature is dependent on the ItemIdentifier implementation.
I have tried to add a secure string in Queue collection and it throws JSON Error. Can you suggest how to encrypt specific items in queue collection in AddQueueItem. Also help me out to understand how the Specific Data Encrypted is to be set
For one thing, I saved your question as feedback for our product team to consider. I suppose @badita could share a bit of knowledge here, but I don’t think it is currently possible to automatically encrypt data that is saved in the queue.
Could you explain a bit how you would see this work practically in Studio with the Add Queue Item activity?
That’s something new, what changes are required from orchestrator point if we encrypt entire DB… Do we need to change web.config so that it can read encrypted data. Do you have any document or steps that needs to be followed
Support team has access to orchestrator and all the tenants. They can see all the customer data. Business doesn’t want their data to visible. We can go with Org units or give limited access to support team. But the team who owns Infra are admin of orchestrator and we cannot restrict that.
They want to encrypt all the data while storing in database.(which can be achieved by encrypting entire DB… ) Also they want to mask it from the UI so that apart from robot, no one else would see it.
Even if business team cant see it that fine, their main concern is they don’t want their data to seen outside their BU. Only robot should have access to it.
I tried to explain as much as I can.
Let me now if you want any more information.