RBAC for API authorization for all clusters
HTTPS encrypted endpoints for Kubelets
Pod security policies
Restricted access to etcd
Infrastructure credentials rotation
Telephone numbers are encrypted in the customer’s cloud and CSV call lists are generated with the encrypted data.
When Dasha places the call through the customer’s telephony, the hashed value is decrypted into a phone number.
It’s not personal data without phone numbers
A leak of employee phone numbers is a physical impossibility
We open a protected communication channel which is invisible to TCP/IP protocol.
An outside observer will not be able to fabricate data or eavesdrop on communications
Data is incorruptible in transit
Will require both parties working together to ensure proper set up
We use this service to encrypt physical hard drives at Azure instances
Even if the physical server is compromised, the data is safe
We work with our Azure account managers to get the Dasha instance set up in the same room of the same physical datacenter with our customer’s instance. We then open up an encrypted VPN communication channel between the two.
We avoid the open Internet, lowering the likelihood of malevolent outside actions, data loss or data corruption by an astronomical margin
May be a lengthy process to coordinate
Our Azure partners are already working with us to ensure the quickest timeframes
We can use asymmetric encryption (RSA) to encrypt the results of the conversation. The customer owns the private key used to decrypt the data and provides the public encryption key to Dasha.
While the AI is on the phone with the employee, each reply is encrypted using the public key and recorded in the Dasha Database as the encrypted value. The customer can decrypt the conversations on their servers
Full hands-off the data approach on behalf of team Dasha
Avoids any potential data leak
Dasha team will not be able to train the model to improve performance
Slower processing speeds for new records and time to decrypt them on the server
We can avoid storing recordings and transcripts on Dasha servers by pushing them directly to the customer’s Azure instances.
Full hands-off data approach on behalf of Dasha
Avoids potential data leaks
Only the customer has access to their data