It could be tied to things like XML or JSON type data and then we've also taken the four learning capabilities that we've built for Salesforce as well and extended those to other applications. We can also support, generically, APIs so it's not just these ETL jobs that are tied to Salesforce. You can do different types of policies like only decrypt data for a finance person that's accessing a particular record but not for someone else that's maybe coming from an off-premises location or is in a different group. We support the ability to control the security level of the data. We also have an SDK as well that you can roll out for your own custom apps to encrypt data in structured databases if you like. While we can integrate with Salesforce on the fly, it's kind of a turnkey solution, and you get this capability, we've started porting over the solution to custom applications which you may have developed. What we've actually done from a technology perspective is, we've taken the technology that we built for Salesforce here and we actually extended this to support any application. It can pull data out through Bitglass, run reports, change it, augment it, and upload it back into Salesforce kind of on the fly here. Let's say you have a server over here that does some analysis, some ETL type job that does extract, transform, and loading of data. What this basically does is it can encrypt data on the fly, it can also encrypt with on-premises systems you might have. We encrypt it using your own keys and then we build a search index that you can maintain here either on premises or in your own instance of AWS. One is data that already exists in SalesForce – here, we use APIs to connect to data that might already exist and then actually encrypt it. There's a number of different ways that data can be put into Salesforce that we support from an integration perspective to encrypt the data on the fly. Sometimes, people will want to encrypt the data by maintaining their own keys while still being able to support searching and sorting.īitglass has a patented solution for this that actually supports connection to your own HSMs or KMS integrations and sits between users and the data. There could be really sensitive fields you put inside of these records, custom, created, or just in general. Inside this environment, you may want to protect that data. You can create custom objects, custom fields, and things like that. If you think about a contact object, for example, in Salesforce, it has a number of fields. ![]() So, I have a cloud application, the most common one that people typically talk about is Salesforce, and I have things like records inside of Salesforce, and there's all kinds of different tables and all kinds of different representations for various things. ![]() This is Mike from Product Management, and I wanted to talk a little bit about protecting data inside of the cloud from a structured data perspective.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |