Table of Contents

Search

  1. Preface
  2. Part 1: Introduction
  3. Part 2: Configuring Hub Console Tools
  4. Part 3: Building the Data Model
  5. Part 4: Configuring the Data Flow
  6. Part 5: Executing Informatica MDM Hub Processes
  7. Part 6: Configuring Application Access
  8. Appendix A: MDM Hub Properties
  9. Appendix B: Viewing Configuration Details
  10. Appendix C: Row-level Locking
  11. Appendix D: MDM Hub Logging
  12. Appendix E: Table Partitioning
  13. Appendix F: Collecting MDM Environment Information with the Product Usage Toolkit
  14. Appendix G: Informatica Platform Staging
  15. Appendix H: Informatica Platform Mapping Examples
  16. Appendix I: Glossary

Data Encryption Architecture

Data Encryption Architecture

You can store sensitive data in the database in encrypted form and transfer it to the
Hub Server
, the
Process Server
, and
Data Director
in the encrypted form. Data encryption ensures that sensitive data in the
MDM Hub
implementation is secure.
Encrypted data is decrypted in
Data Director
or other
Services Integration Framework
(
SIF
) clients before it is shown to users. Also, the encrypted data in the database is decrypted before the cleanse process.
The
MDM Hub
performs each
SIF
API call through a SiperianClient object. Each call comprises a request and a response. The request that goes out must be encrypted and the response that comes in must be decrypted.
The
MDM Hub
can encrypt the following data exchanges over a network:
  • Between the
    Hub Server
    and the database
  • Between the
    Hub Server
    and the
    Process Server
    during cleanse operations
  • Between
    Data Director
    and the
    Hub Server

0 COMMENTS

We’d like to hear from you!