Implementing the client-side masking for the DynamoDB data
Similar to the requirements from the previous recipe, there might be a need to mask data before saving it in DynamoDB. Masking is replacing real data with realistic data for sensitive information, such as names, dates of birth, Social Security number (SSN), credit/debit card numbers, and so on. Generally, when it comes to the security of testing data, people prefer masking over encryption. In this recipe, we will see how to mask such data before saving it in DynamoDB.
Getting ready
To perform this recipe, you should know how to use the AWS SDK for Java, especially its object persistence model. Refer to Chapter 5, Exploring Higher Level Programming Interfaces for DynamoDB, for more details.
How to do it…
Unlike encryption, AWS does not provide support for data masking, so we need to use custom solutions for masking the data before storing it in DynamoDB.
Consider our e-commerce website where we save our customer's credit card details....