adobe captivate - oracle software downloads | oracle...

Adobe Captivate Sunday, May 07, 2023

Slide 3 - Oracle Sales Cloud Release 12

Slide notes

Hello, my name is Niranjan. Welcome to training for Release 12.

In this session we will talk about what’s coming in Oracle Sales Cloud for Blue Coat Related Data Security Enhancements.

Notes

of 20


Slide 4 - Agenda

Slide notesFor the enhancements covered in this training, we’ll give an overview, followed by more detail to explain how you can use them, and what business value they bring.

Then we’ll walk you through a demonstration.

Next we’ll explain what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

of 20


Slide 5 - Enhancements Overview

Slide notesCompanies are required to comply to a number of data privacy and compliance rules depending on the region and industry regimes they operate in.

In order to safeguard customer data in the cloud, Oracle offers wide variety of solutions to our customers. A few key ones are listed here.

Transparent Data Encryption protects data from physical breach by encrypting confidential data in the database. Database scripts use encryption keys to read and write data to the database, and the keys themselves are safely put away in oracle wallet.

Database Vault protects from insider attacks by using segregation of duties to restrict oracle database admin from viewing application data. Oracle database admins can continue to manage, patch and upgrade the instance; customer account admin acts as the gatekeeper for application data.

IP Whitelisting, VPN routing enable you to secure your data during transmission.

Certain set of our customers like to retain sensitive data on premise – this process is known as data residency. Drivers for data residency could be ”Data protection laws passed by nations”, or ”compliance rules in regulated industries”

Data Residency can be achieved through multiple options. In most cases, our customers are able to meet their compliance needs by hosting opting in for one of our global data centers.

An alternate way to achieve data residency is through use of a tokenization solution such as “Blue Coat Cloud Data Protection Gateway .. CDP” with Oracle Cloud. In previous releases, it was not possible to use Blue Coat CDP with Oracle Sales Cloud – starting Release 11 and 12, customers will be able to use Blue Coat CDP to protect their data with tokenization.

Notes

of 20


Slide 6 - Tokenization with Blue Coat

Slide notesPreviously, there was no option for our customers to leverage 3rd party data protection gateways such as Blue Coat to attain data residency for their Personal Data. This limitation acted as a roadblock for certain customers who wanted to comply to data residency requirements in their region or industry.

With the new enhancements we delivered in Release 11 and Release 12, customers can purchase Blue Coat Cloud Data Protection Gateway and use it to protect personal data in Sales Cloud.

With this solution, you get to enhance the data protection natively offered by Oracle with additional layer of security.

And because the protected data in your on-premise systems, managed by your personnel, there is ZERO risk of data breach for data protected by Blue Coat at the Oracle end.

Important to note is that the solution is co-architected by Oracle and Blue Coat teams enabling for maximum functionality preservation.

Finally, you get to pick the attributes for protection from the list of personally identifiable attributes that are enabled for protection by Oracle.

Notes

of 20


Slide 7 - Managing Contacts

Slide notesWhen an object and its attributes are protected using a tokenization solution such as Blue Coat, values of those attributes never persist in Oracle Sales Cloud tables. This can introduce limitations to core product functionality.

With our integrated solution, you can continue to manage protected objects including Contacts using our Simplified User Interface.

As an example, consider personal attributes in Contact such as Name, Address and Phone are protected – you can still continue to manage Contacts as you normally would without Blue Coat. This means that Sales Reps can create a new Contact, update protected values in the Contact and delete the contact when necessary using Sales Cloud application - not knowing that Blue Coat is securing that data on premise through the whole process.

Notes

of 20


Slide 8 - Searching Contacts

Slide notesSales Cloud provides robust search and filter capabilities in the product. It is one of the most commonly used features. In this integrated solution, we have made it possible to search for records using protected attributes. It is possible to use basic or advanced search with one or more search terms to search for records.

It is also possible to use suggestions that are shown in the form of Recent Items appearing in the Find box.

Due to non-existence of actual protected value in Sales Cloud, search on protected attributes is limited to exact match case sensitive search in Release 11 and Release 12.

Search using partial terms is not possible, therefore Alpha Bar and Auto Suggest features are disabled when tokenization using Blue Coat is enabled on the instance.

Notes

of 20


Slide 9 - Associating Contacts

Slide notesContacts is a core object, and one would want to associate contact to many different objects in Sales Cloud. In the integrated solution, we have made it possible to associate a protected value in Contact such as Contact Name to another object such as Account using existing pick lists.

It is also possible to search for Contacts in the context of Accounts, or create a new contact if necessary and associate it to an object such as Account or Opportunity.

Notes

of 20


Slide 10 - SOAP and REST APIs

Slide notesSales Cloud is among many different applications that our customers run and manage. We have made it possible to build integrations with other cloud and on-premise systems while keeping the data secure within Oracle Sales Cloud.

Sales Cloud SOAP and REST APIs are protected with Blue Coat. The policies that you create against a Sales Cloud object extends to its SOAP and REST interfaces as well with no additional setup.

Typically, in an inbound scenario, where you are pushing data into Sales Cloud form another system, no additional setup is required. Blue Coat would intercept SOAP and REST endpoints like it does for Sales Cloud web URLs, and transmit tokenized data into Sales Cloud.

In an outbound scenario, where one wants to push data from Sales Cloud into an external system, using groovy in conjunction with App Composer web services module, it is required to register the external service endpoint in Blue Coat Integration Component; also known as Reverse Proxy. Blue Coat ensures that protected data flowing out of Sales Cloud is detokenized on its way out.

If the other system is also protected with Blue Coat, it may not be required to route the calls through reverse proxy.

Notes

of 20


Slide 11 - File based Data Import and Export

Slide notesOne of the first step in any Sales Cloud implementation is data import. With the Blue Coat solution, we have made it possible to securely import data into Sales Cloud through our File Based Data Import feature. To import data in tokenized form it is required to embed protection keys as column headers metadata to ensure Blue Coat recognizes the column as protected column.

In the same way we support import, export of protected data is also supported with Blue Coat. Data exported via Blue Coat gateway will be detokenized into clear text values by the gateway.

Advanced import options such as recurring or scheduled import is restricted with Blue Coat.

Notes

of 20


Slide 12 - Reports and Analytics

Slide notesReports and Analytics is an valuable capability in our prodict. We have made it possible for customers to use both standard and custom reports containing protected values.

No additional setup is necessary for Blue Coat to detokenize values in a report. Although it is important to note that if protected values are truncated or concatenated, detokenization process may run into limitations. Also, reports that rely on protected value in filter criteria will see restrictions.

Notes

of 20


Slide 13 - Protection with Blue Coat

Slide notesWith this solution, customers get to enhance the data protection natively offered by Oracle with additional layer of data security.

And because the protected data in your on-premise systems, managed by your personnel, there is ZERO risk of data breach for data protected by Blue Coat at the Oracle end.

Notes

of 20


Slide 61 - Summary of Enhancement Capabilities

Slide notesHere is the summary of the features I have talked about today.

It is possible to use Blue Coat’s tokenization solution to protect Personally Identifiable Information(PII) attributes in Sales Cloud in order to meet data residency requirements.

It is possible to search and manage contacts in Sales Cloud with Blue Coat enabled.

It is possible to associate a protected object such as contact to other standard and custom objects using relationships and picklists.

It is possible to import data in a secure form, push or pull data at real time using Sales Cloud APIs, and report on that data when Blue Coat is enabled.

Notes

of 20


Slide 62 - Implementation Advice

Slide notesIn this implementation advice section we will go through what you need to consider before enabling these features in your business, and what you need to know to set them up.

Notes

of 20


Slide 63 - Feature Impact Guidelines

Slide notesBlue Coat Data Protection is not automatically available to all customers. After purchasing data protection gateway from Blue Coat, customers will have to configure the gateway pointing to their sales cloud instance. For prepare Sales Cloud to support Blue Coat gateway, follow the steps described in “ Implementing Oracle Sales Cloud with Blue Coat Cloud Data Protection (Doc ID 2097722.1) “ available on My Oracle Support.

Notes

of 20


Slide 64 - Implementation Decision Points

Slide notesDetermine which attributes you want to tokenize with Blue Coat as opposed to protecting them with other security offerings such as Transparent Data Encryption, as it could have potential impact on product functionality wherever that attribute is used.

Determine complete list of attributes you’d wish to protect with Blue Coat, as making modifications later could lead to exporting and re-importing data again into Sales Cloud.

Identify the integration touchpoints with Sales Cloud, the nature of data flow – inbound or outbound, and accordingly configure integration component (reverse proxy) to intercept API calls. This will have impact on whether data flowing out is tokenized or not.

Notes

of 20


Slide 65 - Setup Summary

Slide notesThe setup for tokenization with Blue Coat is achieved by first registering the Oracle Sales Cloud instance within Blue Coat Management Console which is part of the gateway that’s installed at a customer managed site.

Notes

of 20


Slide 66 - Registering Oracle Sales Cloud

Slide notesEach Oracle Sales Cloud Instance must be registered individually within the Management Console by providing credentials of the Sales Cloud admin user, and REST endpoints.

Every time a customization is made that involves an existing or adds a new protected attribute, green refresh icon next to the instance records must be invoked to refresh the metadata in console.

Notes

of 20


Slide 67 - Registering Oracle Sales Cloud

Slide notesIn order for Blue Coat to detect attributes in web and API channels, they must be configured as protected attributes in the console using protection policies. One or more protection policies can be created to group related attributes.

Attributes can be added or removed from a policy at any time, but may involve re-importing data as the original data may be unprotected.

Notes

of 20


Slide 68 - Job Roles

Slide notesUser with Sales Cloud Administrator role will be able to setup detection rules in Blue Coat Management Console.

All users will be able to access Sales Cloud features protected with Blue Coat.

Notes

of 20


Slide 69 - Business Process Information

Slide notesThe implementation business process involves configuring Blue Coat Proxy to intercept all traffic to Sales Cloud by defining appropriate data privacy and security rules in the management console. The process also involves following the guidelines described in Blue Coat support guide to identify the impacts and taking necessary actions as appropriate.

This concludes this presentation, thank you for listening. You can easily pause and rewind any of these slides if you require additional time to take in the detail.

Notes

of 20

adobe captivate - oracle software downloads | oracle...

Documents