So, just to wrap this up.
You can create a Ruleset using the Masking API. If you are clever then you can build all sorts of capability and build your Rulesets dynamically. We have developed in-house a way of extracting massive lists of databases and their connection strings to dynamically and automatically profile your database estate for sensitive data. This will automatically build an inventory on which you can also automatically run a masking job. Obviously you will need to check your inventory for false positives and false negatives using a human or artificial intelligence...
In this case Pankaj sent me a list of tables and I sent him back a list of curl commands that will update his ruleset, with all the tables that are relevant to profile/mask.
As I'm not proficient at bash programming, I simply used the
http://<your masking engine>:8282/masking/api-client to guide me. To login to that client and get an authentication code you need to read the documentation or follow this
video that I created.
The curl command syntax to add tables to a ruleset is shown below - download a sample file
here.
# 1. You need to change 47eba9e5-3ee3-4d3d-8299-2c0700a1a619 to your
# authorisation code.
# 2. You need to change the “rulesetId”: 1 to the correct number for the
# ruleset you want to change. You can see that in the UI.
# 3. You need to change the Engine IP Address and port to your
# engine ID and port
#
# Before running this you should login and get the authorisation code.
# You could do that on the masking/client-api
# You just need to run this on a command line like ./Table_names_json.txt
# You will need curl installed on your machine that you run this from.
# You could run a script that will take the table_name from an Excel or
# CSV file but I don’t have much recent experience with something like
# that.
#
curl -s -X POST --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: 47eba9e5-3ee3-4d3d-8299-2c0700a1a619' -d '{ "tableName": "TABLE_17”, "rulesetId": 1 }' 'http://192.13.12.100:8282/masking/api/table-metadata'
Regards,
Gary