{"id":242,"date":"2020-09-17T23:53:09","date_gmt":"2020-09-17T23:53:09","guid":{"rendered":"https:\/\/machine-learning.webcloning.com\/2020\/09\/17\/detecting-and-redacting-pii-using-amazon-comprehend\/"},"modified":"2020-09-17T23:53:09","modified_gmt":"2020-09-17T23:53:09","slug":"detecting-and-redacting-pii-using-amazon-comprehend","status":"publish","type":"post","link":"https:\/\/salarydistribution.com\/machine-learning\/2020\/09\/17\/detecting-and-redacting-pii-using-amazon-comprehend\/","title":{"rendered":"Detecting and redacting PII using Amazon Comprehend"},"content":{"rendered":"
\n

Amazon Comprehend<\/a> is a natural language processing (NLP) service that uses machine learning (ML) to find insights and relationships like people, places, sentiments, and topics in unstructured text. You can now use Amazon Comprehend ML capabilities to detect and redact personally identifiable information (PII) in customer emails, support tickets, product reviews, social media, and more. No ML experience required. For example, you can analyze support tickets and knowledge articles to detect PII entities and redact the text before you index the documents in the search solution. After that, search solutions are free of PII entities in documents. Redacting PII entities helps you protect privacy and comply with local laws and regulations.<\/p>\n

Customer use case: TeraDact Solutions<\/u><\/strong><\/h3>\n

TeraDact Solutions has already put this new feature to work. TeraDact Solutions\u2019 software offers a robust alternative for secure information sharing in a world of ever-increasing compliance and privacy concerns. With its signature Information Identification & Presentation (IIaP\u2122) capabilities, TeraDact\u2019s tools provide the user with a safe information sharing environment. \u201cUsing Amazon Comprehend for PII redaction with our tokenization system not only helps us reach a larger set of our customers but also helps us overcome the shortcomings of rules-based PII detection which can result in false alarms or missed details. PII detection is critical for businesses and with the power of context-aware NLP models from Comprehend we can uphold the trust customers place in us with their information. Amazon is innovating in ways to help push our business forward by adding new features which are critical to our business thereby providing enhanced service to 100% of customers able to access Comprehend in AWS.\u201d said Chris Schrichte, CEO, TeraDact Solutions, Inc.<\/p>\n

In this post, I cover how to use Amazon Comprehend to detect PII and redact the PII entities via the AWS Management Console<\/a> and the AWS Command Line Interface<\/a> (AWS CLI).<\/p>\n

Detecting PII in Amazon Comprehend<\/h2>\n

When you analyze text using Amazon Comprehend real-time analysis, Amazon Comprehend automatically identifies PII, as summarized in the following table.<\/p>\n\n\n\n\n\n\n\n\n
PII entity category<\/strong><\/td>\nPII entity types<\/strong><\/td>\n<\/tr>\n
Financial<\/strong><\/td>\n\n

BANK_ACCOUNT_NUMBER<\/p>\n

BANK_ROUTING<\/p>\n

CREDIT_DEBIT_NUMBER<\/p>\n

CREDIT_DEBIT_CVV<\/p>\n

CREDIT_DEBIT_EXPIRY<\/p>\n

PIN<\/p>\n<\/td>\n<\/tr>\n

Personal<\/strong><\/td>\n\n

NAME<\/p>\n

ADDRESS<\/p>\n

PHONE<\/p>\n

EMAIL<\/p>\n

AGE<\/p>\n<\/td>\n<\/tr>\n

Technical security<\/strong><\/td>\n\n

USERNAME<\/p>\n

PASSWORD<\/p>\n

URL<\/p>\n

AWS_ACCESS_KEY<\/p>\n

AWS_SECRET_KEY<\/p>\n

IP_ADDRESS<\/p>\n

MAC_ADDRESS<\/p>\n<\/td>\n<\/tr>\n

National<\/strong><\/td>\n\n

SSN<\/p>\n

PASSPORT_NUMBER<\/p>\n

DRIVER_ID<\/p>\n<\/td>\n<\/tr>\n

Other<\/strong><\/td>\nDATE_TIME<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

For each detected PII entity, you get the type of PII, a confidence score, and begin and end offset. These offsets help you locate PII entities in your documents for document processing to redact it at the secure storage or downstream solutions.<\/p>\n

Analyzing text on the Amazon Comprehend console<\/h2>\n

To get started with Amazon Comprehend, all you need is an AWS account<\/a>. To use the console, complete the following steps:<\/p>\n

    \n
  1. On the Amazon Comprehend console, in the Input text<\/strong> section, select Built-in<\/strong>.<\/li>\n
  2. For Input text<\/strong>, enter your text.<\/li>\n
  3. Choose Analyze<\/strong>.<\/li>\n<\/ol>\n

    \"\"<\/p>\n

      \n
    1. On the Insights<\/strong> page, choose the PII<\/strong>\n<\/li>\n<\/ol>\n

      \"\"<\/p>\n

      The PII<\/strong> tab shows color-coded text to indicate different PII entity types, such as name, email, address, phone, and others. The Results<\/strong> section shows more information about the text. Each entry shows the PII entity, its type, and the level of confidence Amazon Comprehend has in this analysis.<\/p>\n

      Analyzing text via the AWS CLI<\/h2>\n

      To perform real-time analysis using the AWS CLI, enter the following code:<\/p>\n

      \n
      aws comprehend detect-pii-entities \r\n--language-code en \r\n--text \r\n\" Good morning, everybody. My name is Van Bokhorst Serdar, and today I feel like sharing a whole lot of personal information with you. Let's start with my Email address SerdarvanBokhorst@dayrep.com. My address is 2657 Koontz Lane, Los Angeles, CA. My phone number is 818-828-6231. My Social security number is 548-95-6370. My Bank account number is 940517528812 and routing number 195991012. My credit card number is 5534816011668430, Expiration Date 6\/1\/2022, my C V V code is 121, and my pin 123456. Well, I think that's it. You know a whole lot about me. And I hope that Amazon comprehend is doing a good job at identifying PII entities so you can redact my personal information away from this document. Let's check.\"<\/code><\/pre>\n<\/div>\n
      To view the output, open the JSON response object and look at the detected PII entities. For each entity, the service returns the type of PII, confidence score metric, BeginOffset, and EndOffset. See the following code:<\/p>\n
      \n
      {\r\n    \"Entities\": [\r\n        {\r\n            \"Score\": 0.9996334314346313,\r\n            \"Type\": \"NAME\",\r\n            \"BeginOffset\": 36,\r\n            \"EndOffset\": 55\r\n        },\r\n        {\r\n            \"Score\": 0.9999902248382568,\r\n            \"Type\": \"EMAIL\",\r\n            \"BeginOffset\": 167,\r\n            \"EndOffset\": 195\r\n        },\r\n        {\r\n            \"Score\": 0.9999983310699463,\r\n            \"Type\": \"ADDRESS\",\r\n            \"BeginOffset\": 211,\r\n            \"EndOffset\": 245\r\n        },\r\n        {\r\n            \"Score\": 0.9999997615814209,\r\n            \"Type\": \"PHONE\",\r\n            \"BeginOffset\": 265,\r\n            \"EndOffset\": 277\r\n        },\r\n        {\r\n            \"Score\": 0.9999996423721313,\r\n            \"Type\": \"SSN\",\r\n            \"BeginOffset\": 308,\r\n            \"EndOffset\": 319\r\n        },\r\n        {\r\n            \"Score\": 0.9999984502792358,\r\n            \"Type\": \"BANK_ACCOUNT_NUMBER\",\r\n            \"BeginOffset\": 347,\r\n            \"EndOffset\": 359\r\n        },\r\n        {\r\n            \"Score\": 0.9999974966049194,\r\n            \"Type\": \"BANK_ROUTING\",\r\n            \"BeginOffset\": 379,\r\n            \"EndOffset\": 388\r\n        },\r\n        {\r\n            \"Score\": 0.9999991655349731,\r\n            \"Type\": \"CREDIT_DEBIT_NUMBER\",\r\n            \"BeginOffset\": 415,\r\n            \"EndOffset\": 431\r\n        },\r\n        {\r\n            \"Score\": 0.9923601746559143,\r\n            \"Type\": \"CREDIT_DEBIT_EXPIRY\",\r\n            \"BeginOffset\": 449,\r\n            \"EndOffset\": 457\r\n        },\r\n        {\r\n            \"Score\": 0.9999997615814209,\r\n            \"Type\": \"CREDIT_DEBIT_CVV\",\r\n            \"BeginOffset\": 476,\r\n            \"EndOffset\": 479\r\n        },\r\n        {\r\n            \"Score\": 0.9998345375061035,\r\n            \"Type\": \"PIN\",\r\n            \"BeginOffset\": 492,\r\n            \"EndOffset\": 498\r\n        }\r\n    ]\r\n}<\/code><\/pre>\n<\/div>\n
      Asynchronous PII redaction batch processing on the Amazon Comprehend console<\/h2>\n
      You can redact documents by using Amazon Comprehend asynchronous operations. You can choose redaction mode Replace with PII entity<\/strong> to replace PII entities with PII entity type, or choose to mask PII entity with redaction mode Replace with character <\/strong>and replace the characters in PII entities with a character of your choice (!, #, $, %, &, *, or @).<\/p>\n
      To analyze and redact large documents and large collections of documents, ensure that the documents are stored in an Amazon Simple Storage Service<\/a> (Amazon S3) bucket and start an asynchronous operation to detect and redact PII in the documents. The results of the analysis are returned in an S3 bucket.<\/p>\n
        \n
      1. On the Amazon Comprehend console, choose Analysis jobs<\/strong>.<\/li>\n
      2. Choose Create job<\/strong>.<\/li>\n<\/ol>\n
        \"\"<\/p>\n
          \n
        1. On the Create analysis job<\/strong> page, for Name<\/strong>, enter a name (for this post, we enter comprehend-blog-redact-01).<\/li>\n
        2. For Analysis type<\/strong>, choose Personally identifiable information (PII)<\/strong>.<\/li>\n
        3. For Language<\/strong>, choose English<\/strong>.<\/li>\n<\/ol>\n
          \"\"<\/p>\n
            \n
          1. In the PII detection settings<\/strong> section, for Output mode<\/strong>, select Redactions<\/strong>.<\/li>\n
          2. Expand PII entity types<\/strong> and select the entity types to redact.<\/li>\n
          3. For Redaction mode<\/strong>, choose Replace with PII entity type<\/strong>.<\/li>\n<\/ol>\n
            Alternatively, you can choose Replace with character<\/strong> to replace PII entities with a character of your choice (!, #, $, %, &, *, or @).<\/p>\n
            \"\"<\/p>\n
              \n
            1. In the Input data<\/strong> section, for Data source<\/strong>, select My documents<\/strong>.<\/li>\n
            2. For S3 location<\/strong>, enter the S3 path for pii-s3-input.txt.<\/li>\n<\/ol>\n
              This text file has the same example content we used earlier for real-time analysis.<\/p>\n
                \n
              1. In the Output data<\/strong> section, for S3 location<\/strong>, enter the path to the output folder in Amazon S3.<\/li>\n<\/ol>\n
                Make sure you choose the correct input and output paths based on how you organized the document.<\/p>\n
                \"\"<\/p>\n
                  \n
                1. In the Access permissions<\/strong> section, for IAM<\/strong> role, select Create an IAM role<\/strong>.<\/li>\n<\/ol>\n
                  You need an AWS Identity and Access Management<\/a> (IAM) role with required permissions to access the input and output S3 buckets for the job that is created and propagated.<\/p>\n
                    \n
                  1. For Permissions to access<\/strong>, choose Input and Output S3 buckets<\/strong>.<\/li>\n
                  2. For Name suffix<\/strong>, enter a suffix for your role (for this post, we enter ComprehendPIIRole).<\/li>\n
                  3. Choose Create job<\/strong>.<\/li>\n<\/ol>\n
                    \"\"<\/p>\n
                    You can see the job comprehend-blog-redact-01<\/code> with the job status In progress<\/code>.<\/p>\n
                    When the job status changes to Completed<\/code>, you can access the output file to view the output. The pii-s3-input.txt<\/code> file has the same example content we used earlier, and using redaction mode replaces PII with its PII entity type. Your output looks like the following text:<\/p>\n
                    \n
                    Good morning, everybody. My name is [NAME], and today I feel like sharing a whole lot of personal information with you. Let's start with my Email address [EMAIL]. My address is [ADDRESS] My phone number is [PHONE]. My Social security number is [SSN]. My Bank account number is [BANK-ACCOUNT-NUMBER] and routing number [BANK-ROUTING]. My credit card number is [CREDIT-DEBIT-NUMBER], Expiration Date [CREDIT-DEBIT-EXPIRY], my C V V code is [CREDIT-DEBIT-CVV], and my pin [PIN]. Well, I think that's it. You know a whole lot about me. And I hope that Amazon comprehend is doing a good job at identifying PII entities so you can redact my personal information away from this document. Let's check.<\/code><\/p>\n<\/div>\n
                    If you have very long entity types, you may prefer to mask PII with a character. If you choose to replace PII with the character *, your output looks like the following text. :<\/p>\n
                    \n
                    Good morning, everybody. My name is *******************, and today I feel like sharing a whole lot of personal information with you. Let's start with my Email address ****************************. My address is ********************************** My phone number is ************. My Social security number is ***********. My Bank account number is ************ and routing number *********. My credit card number is ****************, Expiration Date ********, my C V V code is ***, and my pin ******. Well, I think that's it. You know a whole lot about me. And I hope that Amazon comprehend is doing a good job at identifying PII entities so you can redact my personal information away from this document. Let's check.<\/code><\/p>\n<\/div>\n
                    Asynchronous PII redaction batch processing via the AWS CLI<\/h2>\n
                    To perform the PII redaction job using the AWS CLI, enter the following code:<\/p>\n
                    \n
                    aws comprehend start-pii-entities-detection-job \r\n --input-data-config S3Uri=\"s3:\/\/ai-ml-services-lab\/public\/labs\/comprehend\/pii\/input\/redact\/pii-s3-input.txt\"  \r\n --output-data-config S3Uri=\"s3:\/\/ai-ml-services-lab\/public\/labs\/comprehend\/pii\/output\/redact\/\"  \r\n --mode \"ONLY_REDACTION\" \r\n --redaction-config PiiEntityTypes=\"BANK_ACCOUNT_NUMBER\",\"BANK_ROUTING\",\"CREDIT_DEBIT_NUMBER\",\"CREDIT_DEBIT_CVV\",\"CREDIT_DEBIT_EXPIRY\",\"PIN\",\"EMAIL\",\"ADDRESS\",\"NAME\",\"PHONE\",\"SSN\",MaskMode=\"REPLACE_WITH_PII_ENTITY_TYPE\" \r\n --data-access-role-arn \"arn:aws:iam::<ACCOUNTID>:role\/service-role\/AmazonComprehendServiceRole-ComprehendPIIRole\" \r\n --job-name \"comprehend-blog-redact-001\" \r\n --language-code \"en\"\r\n<\/code><\/pre>\n<\/div>\n
                    The request yields the following output:<\/p>\n
                    \n
                    {\r\n    \"JobId\": \"e41101e2f0919a320bc0583a50f86b5f\",\r\n    \"JobStatus\": \"SUBMITTED\"\r\n}\r\n<\/code><\/pre>\n<\/div>\n
                    To monitor the job request, enter the following code:<\/p>\n
                    \n
                    aws comprehend describe-pii-entities-detection-job --job-id \" e41101e2f0919a320bc0583a50f86b5f \"<\/code><\/pre>\n<\/div>\n
                    The following output shows that the job is complete:<\/p>\n
                    \n
                    {\r\n    \"PiiEntitiesDetectionJobProperties\": {\r\n        \"JobId\": \"e41101e2f0919a320bc0583a50f86b5f\",\r\n        \"JobName\": \"comprehend-blog-redact-001\",\r\n        \"JobStatus\": \"COMPLETED\",\r\n        \"SubmitTime\": <SubmitTime>,\r\n        \"EndTime\": <EndTime>,\r\n        \"InputDataConfig\": {\r\n            \"S3Uri\": \"s3:\/\/ai-ml-services-lab\/public\/labs\/comprehend\/pii\/input\/redact\/pii-s3-input.txt\",\r\n            \"InputFormat\": \"ONE_DOC_PER_LINE\"\r\n        },\r\n        \"OutputDataConfig\": {\r\n            \"S3Uri\": \"s3:\/\/ai-ml-services-lab\/public\/labs\/comprehend\/pii\/output\/redact\/<AccountID>-PII-e41101e2f0919a320bc0583a50f86b5f\/output\/\"\r\n        },\r\n        \"RedactionConfig\": {\r\n            \"PiiEntityTypes\": [\r\n                \"BANK_ACCOUNT_NUMBER\",\r\n                \"BANK_ROUTING\",\r\n                \"CREDIT_DEBIT_NUMBER\",\r\n                \"CREDIT_DEBIT_CVV\",\r\n                \"CREDIT_DEBIT_EXPIRY\",\r\n                \"PIN\",\r\n                \"EMAIL\",\r\n                \"ADDRESS\",\r\n                \"NAME\",\r\n                \"PHONE\",\r\n                \"SSN\"\r\n            ],\r\n            \"MaskMode\": \"REPLACE_WITH_PII_ENTITY_TYPE\"\r\n        },\r\n        \"LanguageCode\": \"en\",\r\n        \"DataAccessRoleArn\": \"arn:aws:iam::<AccountID>:role\/ComprehendBucketAccessRole\",\r\n        \"Mode\": \"ONLY_REDACTION\"\r\n    }\r\n}\r\n<\/code><\/pre>\n<\/div>\n
                    After the job is complete, the output file is plain text (same as the input file). Other Amazon Comprehend asynchronous jobs (start-entities-detection-job<\/code>) have an output file called output.tar.gz<\/code>, which is a compressed archive that contains the output of the operation. Start-pii-entities-detection-job<\/code> retains the folder and file structure as input. Our comprehend-blog-redact-001<\/code> job input file pii-s3-input.txt<\/code> has the respective pii-s3-input.txt.out<\/code> file with the redacted text in the jobs output folder. You can find the Amazon S3 location in the output from monitoring the job; the JSON element PiiEntitiesDetectionJobProperties.OutputDataConfig.S3uri<\/code> has the file pii-s3-input.txt.out<\/code> and the redacted content with PII entity type.<\/p>\n
                    Conclusion<\/h2>\n
                    As of this writing, the PII detection feature in Amazon Comprehend is available for US English in the following Regions:<\/p>\n