Getting Started
  • Protecto Overview
    • Introduction
      • Quickstart Guide
      • Protecto Vault
        • What is a token?
        • Token customization
        • Authentication
        • Tokenization APIs
          • Masking
            • Mask with token
            • Mask with format and token
            • Identify and mask (Auto-detect)
          • Unmasking
          • What happens if an API fails?
        • Asynchronous API's
        • Bulk data
      • Add new data source
        • Snowflake
          • Create and grant access to Protecto
          • Add Snowflake to Protecto
        • Salesforce
          • Create connected app and user
            • Steps to create connected app
            • Steps to create Protecto user
          • Add Salesforce to Protecto
        • Azure SQL
          • Connect using AD Application credentials
          • Connect using database user credentials
        • Databricks
          • Add Service principal (Azure AD Application) to Databricks
          • Steps to create Azure Databricks Cluster
          • Steps to create Databricks python notebook and schedule job
        • Redshift
          • Create and grant access to Protecto user
          • Add Redshift to Protecto
      • Protecto FAQ's
        • 1. What are the steps after we sign up for a Protecto account?
        • 2. Can I sign up for a free account? How long is the trial period?
        • 3. What is Protecto license key? How can I get a new license key?
        • 4. How do I extend the trial period?
        • 5. What is the Protecto pricing model?
        • 6. How do I cancel my account?
        • 7. How do I unsubscribe / opt-out from emails?
      • Compliance User Guide
        • Risk Identification: Key Definitions
        • Understanding Risks
          • Find assets with severe breach risk
          • Filter assets by breach risk level
          • Find assets with other privacy risks
        • Understanding Usage
          • Find the data assets that were accessed
          • Find the data assets that are not used
        • Add Tags & Classification
          • Add tags globally
          • Classify tags to the categories
          • Add tags with category to the data assets
          • Remove tags with category from the data assets
        • Governance
          • Find all data assets
          • Add/delete purposes
          • Assign data owner for a data asset
          • Add/delete consent, data subject type and location for a data asset
          • Add/update retention time for a data asset
          • Add/update minor data for a data asset
        • Generate Compliance Reports
          • ROPA (Records of Processing Activities)
          • DPIA (Data Protection Impact Assessment)
Powered by GitBook
On this page
  1. Protecto Overview
  2. Introduction
  3. Protecto Vault
  4. Tokenization APIs

Unmasking

PreviousIdentify and mask (Auto-detect)NextWhat happens if an API fails?

Last updated 1 year ago

Unmasking in tokenization refers to the process of reversing the tokenization procedure to retrieve the original sensitive data from its tokenized form. It is the opposite of tokenization, where sensitive information is replaced with tokens to enhance security and privacy.

Note: To send a request with the authentication token, include the following in headers:

Headers: {"Authorization": "Bearer <AUTH_TOKEN>"}

Endpoint:

https://trail.protecto.ai/api/vault/unmask

Request Method: PUT

Request Payload:

{“unmask”:[{“token_value”:”2333”}]}

Parameters:

token_value (string): The token for which the original value needs to be retrieved.

Response:

{"data":[{“token_value”:”2333”,”value”:”George Williams}]}

Response Parameters:

  • token_value (string): The original token that was provided in the request.

  • value (string): The original sensitive data value retrieved from the token.

Advantage:

Authorized Data Access: Unmasking allows authorized personnel to access the original, unmasked data when needed, while still keeping the data protected during other stages of processing or storage.

Note : Unmasking should be performed under strict controls, only by authorized individuals, and in compliance with data protection policies and regulations. Organizations should carefully weigh the benefits and risks of unmasking, based on their specific use cases and security requirements.