Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

W-13160541 Tokenization/Detokenization EOL banner #313

Open
wants to merge 2 commits into
base: latest
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ endif::[]
:imagesdir: ../assets/images
:keywords: detokenization, api gateway, mule gateway, policy
:page-aliases: api-manager::policy-mule4-detokenization.adoc, policies::policies-included-detokenization.adoc
:page-support-status: eolScheduledFeature

[%autowidth.spread,cols="a,a"]
|===
Expand All @@ -28,6 +29,8 @@ Detokenization is the process of returning the previously masked sensitive data

For example, an application can require the bank account number or the credit card number for generating monthly credit card statements. Detokenized sensitive data must always be read under strict security controls.

This policy is designed to work only for Anypoint Runtime Fabric deployments.

== Prerequisites

To apply and manage the Detokenization policy, you must have:
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -5,11 +5,12 @@ endif::[]
:imagesdir: ../assets/images
:keywords: tokenization, api gateway, mule gateway, gateway, policy
:page-aliases: api-manager::policy-mule4-tokenization.adoc, policies::policies-included-tokenization.adoc
:page-support-status: eolScheduledFeature

[%autowidth.spread,cols="a,a"]
|===
>s| Policy name | Tokenization
>s| Summary | Transforms sensitive data into a nonsensitive equivalent, named token
>s| Summary | Transforms sensitive data into a nonsensitive equivalent, named token. This policy is designed to work only for Anypoint Runtime Fabric deployments.
>s| Category | Security
>s| First Mule version available | v4.1.1
.3+>.^s| Returned Status Codes |
Expand All @@ -24,12 +25,12 @@ endif::[]

== Summary

Tokenization is the process of masking a value or piece of information that can be considered sensitive data into a token that can be mapped back to its original value using detokenization concepts. If your API contains sensitive data, the tokenization policy is a highly effective way to protect it.

The data is displayed in the same format as the original value, but its actual value is not revealed initially. This policy is designed to work only for Anypoint Runtime Fabric deployments.
Tokenization is the process of masking a value or piece of information that can be considered sensitive data into a token that can be mapped back to its original value using detokenization concepts. If your API contains sensitive data, the tokenization policy is a highly effective way to protect it. The data is displayed in the same format as the original value, but its actual value is not revealed initially.

Tokenization minimizes the risk of matching the sensitive data to the original value, in case a third party accesses the data. For example, you can use this policy to hide credit card numbers, personally identifiable information (PII), protected health information (PHI), and similar sensitive data.

This policy is designed to work only for Anypoint Runtime Fabric deployments.

== Prerequisites

To apply and manage the Tokenization policy, you must have:
Expand Down