As Gen AI tools become increasingly crucial for driving innovation and efficiency, I'm curious about your approach to managing concerns around proprietary data while embracing the benefits of these tools. How do you strike a balance between leveraging Gen AI technologies and mitigating the risks of sharing proprietary information?

273 views2 Comments
Sort By:
Oldest
Global Head of AI, Data & Analytics in Softwarea year ago
I like to think about 4 approaches to generative AI adoption (or lack)
0: 'No gen ai' - your people will use it anyway and you'll probably be opening yourself up to data leaks
1: 'use it if you want, with these rules' - Your people have their own accounts with chatgpt (or other) directly , you might say no copying confidential data in, but it will likely happen. 
2: 'internally deployed chatbot' - You deploy a llm in your own tenant and control data privacy at the system level. Eliminate the need to use chatGPT or other, because they can access a free model by their company. lower risk of data leaks
3:  bespoke tuning on top of internally hosted models - the gold nugget, get responses specific to your enterprise data, full controls over privacy, very unlikely to have accidental data leaks because your users wont need to copy paste data into a chatbot, as your enterprise bot already had access to the data in question.
lock icon

Please join or sign in to view more content.

By joining the Peer Community, you'll get:

  • Peer Discussions and Polls
  • One-Minute Insights
  • Connect with like-minded individuals
Chief Information Security Officer in Healthcare and Biotecha year ago
I would suggest implementing a CASB solution and start tracking your user's behaviour and take action as per the data

Content you might like

TCO19%

Pricing26%

Integrations21%

Alignment with Cloud Provider7%

Security10%

Alignment with Existing IT Skills4%

Product / Feature Set7%

Vendor Relationship / Reputation

Other (comment)

View Results
5.7k views3 Upvotes1 Comment
196 views

Human Factors (fears, mental health, physical spacing)85%

Technical / IT Factors (on-premise tools, pivoting back away from remote)14%

3.7k views3 Upvotes2 Comments