Secured access to contacts

Oracle has adopted security controls and practices for Oracle Cloud Services that are designed to protect the confidentiality, integrity, and availability of customer data that is hosted by Oracle in the Oracle Cloud Services. Learn more about Oracle Cloud's hosting and delivery policies.

Oracle Eloqua has several mechanisms to help you secure contact data and maintain contact privacy.

Securing access to contacts

Oracle Eloqua allows you to secure access to contacts. Administrators apply labels to security groups and contacts. After labels are applied, users can only access contacts that are assigned the same labels as them. This functionality is also known as Label-Based Access Control (LBAC). Applying labels to contacts is managed using a specialized version of the program canvas.

Examples of common use include:

  • Separate contact data by business division.
  • Separate contact data by geography.
  • Restricted access to contact data for sales.
  • Shared access to contact data between divisions, geography, etc.

Learn more about contact security.

Securing contact data and contact communications

Oracle Eloqua enables marketers in regulated industries like financial services or healthcare to interact directly with consumers in a secure and compliant way. Oracle Eloqua has add-ons available that are designed to ensure personal identifiable information (PII), personal health information (PHI), or non-public information (NPI) is secured and appropriately protected.

The data privacy services are available with the following add-ons:

  • Oracle Eloqua Advanced Data Privacy Cloud Service.
  • Oracle Eloqua HIPAA Advanced Data Security Cloud Service.

With these add-ons, Oracle Eloqua ensures that:

  • User access to Oracle Eloqua is secured by a specific password policy that requires strong passwords and limited password resets.
  • If configured, contacts must opt-in to communications and cannot receive emails unless they have specifically opted-in or subscribed to communications via a form submission or by other means.
  • Contacts that have opted-in are added to an email group that can only be accessed by limited security groups. Your organization can have multiple email groups.
  • Communications with contacts can be secured using secure microsites and authenticated microsites. Secure content can only be viewed by users with the correct authentication.
  • Personal information about a contact such as personal identifiable information (PII), personal health information (PHI), or non-public information (NPI) is encrypted in the database. During bulk import and export operations, data is encrypted while held temporarily in a secure area.
  • Logging audit trails on the following activities: accessing contacts and accounts, accessing contacts and accounts via data export, subscriptions and unsubscribes to the restricted email groups, and accessing contact and account data via the Bulk API. All contact access and changes to email group members are tracked by the application.
  • Contact fields can be marked as protected, preventing access via web data lookups.
  • Operational reports that access contacts are limited to marketing users who have access to specific security groups.
  • Classic Insight reports that access contact and account data are disabled by default for all marketing users. However, your organization can request to have this changed.

Learn more about data privacy and HIPAA cloud services.

Securing contact data from web lookups

You can use data lookups to retrieve contact, visitor, or custom object data. Implementing a data lookup on your website allows you to personalize web pages with contact or visitor information. You help protect contact data, you can restrict which contact fields can be included in a data lookup. Learn more about securing contact data from web lookups.

Database encryption

Oracle Eloqua supports encrypting your database, transaction logs, and all database backups. Oracle Eloqua uses AES-256 encryption with our Transparent Data Encryption (TDE) implementation. The database encryption keys are backed up in our secure password server. This password server is encrypted and requires a two-factor RSA token code to access.

Database encryption is available with the following Oracle Eloqua trims and add-ons:

  • Oracle Eloqua Advanced Data Security Cloud Service
  • Oracle Eloqua HIPAA Advanced Security Add-on Cloud Service
  • Oracle Eloqua Marketing for Life Sciences Consumers Cloud Service

Learn more about database encryption.

Hashing identifier

Important: This feature is currently released under our Controlled Availability program. To request access to this feature, please log in to My Oracle Support and create a service request.

Hashing is a form of encryption used to anonymously share contact email addresses and phone numbers with an external data source without sending any Personal Identifiable Information (PII). An external data source could be a CRM, Oracle Data Cloud, or any other data sources

Once enabled, hashes are generated for the following fields using SHA256 and MD5 algorithms:

  • Email address
  • Business phone number
  • Mobile phone number

Learn more about hashing.

Learn more

Contact security

Data privacy

HIPAA

Database encryption

Hashing identifier