Module 4: How Immuta makes Exceptions, Reporting, and Compliance easy

892 Judge Magnifying Glass Photos - Free & Royalty-Free Stock Photos from  Dreamstime

Owen, owner@immuta.com has successfully protected access to credit card transactions utilizing Masking and Row Filtering.

In this final module, we explore how Immuta streamlines work when there are Exceptions, Reporting, and Auditability requirements.

ABC Corp needs to be able to clearly understand how data sources, user attributes, and policies change over time. Also, since Anne will occasionally need to investigate a specific transaction, we will configure immuta to make the credit card number masked, but reversible by Manny.

Does Immuta support all of these scenarios? Let’s find out…

In this module you will:

  • Login to Immuta as Owen and run a report on who is subscribed to the credit_card_transaction table

  • While logged in as Owen, view the Audit log and see when the user Anne last queried credit_card_transactions.

  • While logged in as Owen modify the “Mask-cc-number Global Data Policy” so that masking can be reversible. Login as Anne and submit an unmask request that a particular value be unMasked by Owen.

  • Add a column to the table and view how this is masked by default.

4.0 Login to Immuta as Owen and run a report on who is subscribed to the credit_card_transaction table

Immuta Reports allow Data Governors to use a natural language builder to instantly create reports that detail user activity across Immuta.

Click select entity and choose the option you would like the report based on from the dropdown menu. Next choose Data Source and select the ‘Public Credit Card Transactions’ data source.

Select Entity

The Report shows the users who are currently subscribed to the data source.image-20211015140914822

4.1 While logged in as Owen, view the Audit log and see when the user Anne last queried credit_card_transactions.

Immuta provides access to all of the audit logs via the Audit page.

image-20211015141142155

If we use the filters, we can find the set of records that represent the activity of Manny (manager@immuta.com) against the Public Credit Card Transactions Data Source.

Are there any Failures?

Successful Activity Failed Activities
image-20211015141527522 image-20211015141601016

Click on the record and you will see the full details:

image-20211015141711964

4.2 While logged in as Owen modify the “Mask-cc-number Global Data Policy” so that masking can be reversible. Login as Anne and submit an unmask request that a particular value be unMasked by Manny.
  1. Edit the Mask-CC-Number Policy:

image-20211015141857740

Change the Masking Type to “with reversibility” 2021-10-15 14.20.44

  1. Log in as Anne and find a masked value and request that it be unmasked by Manny. Log in as Manny and view the request and the task on the data source. Click the eye icon. 2021-10-15 14.54.51
4.3 Add a column to the table and view how this is masked by default.
  1. Using the Amazon Redshift Query Editor, Alter the credit card table and add a new column: ( Use the following Alter Table statement)

    alter table public.credit_card_transactions add column New_column varchar default 'secret'

2021-10-15 15.10.23

  1. As Owen run “Column Detection ” on the Credit Card Transaction Data Source. Confirm that the new columns “secret data” is automatically masked by Immuta by running a query as Anne.

2021-10-15 15.18.53

  1. Owen removes the New Tag from that new column, how does that affect Anne’s Query?

image-20211015152935973