{"id":6365,"date":"2014-11-26T09:44:31","date_gmt":"2014-11-26T14:44:31","guid":{"rendered":"http:\/\/www.iri.com\/blog\/?p=6365"},"modified":"2026-02-23T14:43:29","modified_gmt":"2026-02-23T19:43:29","slug":"secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example","status":"publish","type":"post","link":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/","title":{"rendered":"Secure, Then Splunk – A Format-Preserving Encryption and Pseduonymization Example"},"content":{"rendered":"

Introduction: This example demonstrates an older method of using IRI FieldShield to protect sensitive data prior to indexing the data in Splunk. As you will read, FieldShield would process the data outside of Splunk and create a CSV file for Splunk’s ingestion. However, you can also use the Voracity (= FieldShield) add-on<\/strong> for seamless data preparation, indexing, and visualization in Splunk (details here<\/a>), or Splunk Universal Forwarder<\/strong> to send FieldShield targets and logs into Splunk automatically (details here<\/a>)!<\/em><\/p>\n

One of the concerns Splunk users have is that data they index is stored by,\u00a0and thus to some extent, under the control of, Splunk. Before they upload, however,\u00a0IRI FieldShield<\/a> users can protect their\u00a0data so Splunk (or potentially those hacking into Splunk servers) cannot compromise it. The user’s original data, FieldShield executables, job scripts, and encryption keys all remain inside user firewalls —\u00a0local to their machines, and not necessarily even connected to the internet\u00a0— where it is much harder to find, much less compromise, those things too.<\/p>\n

Splunk is a cloud-based analytic platform that indexes\u00a0and displays user data. The data uploaded to Splunk\u2019s can be searched and visualized\u00a0in an internet browser. Because your data that you analyze in Splunk is hosted on its servers, you\u00a0may have concerns about the security of that\u00a0data.<\/p>\n

Splunk does offer some encryption and certificate authentication when sending data back and forth, but not all types of communication are secured\u00a0by default. Enabling additional protection requires proper configuration by the admin. The table below defines the types of communication security and what is enabled by default.<\/p>\n

\"Configuration<\/a>
http:\/\/docs.splunk.com\/Documentation<\/figcaption><\/figure>\n

The default Splunk root certificate uses a private key that\u00a0is the same for every Splunk user, and can be easily accessed. Possession of a certificate authority\u2019s private key allows attackers to generate certificates signed by the trusted authority, which would defeat attempts to control authentication via public key infrastructure (PKI).<\/p>\n

When sensitive data needs to be stored by any third party, you may want to\u00a0secure your data before it reaches their network.\u00a0IRI FieldShield, and its parent IRI\u00a0CoSort<\/a> data manipulation and management package, apply\u00a0multiple\u00a0data masking functions prior to\u00a0Splunk indexing. Field-level protections like format-preserving encryption (FPE), redaction, and pseudonymization are among 12 categories of data-centric security functions supported by FieldShield in its Eclipse GUI<\/a> dialogs.<\/p>\n

FieldShield functions\u00a0can be applied to entire rows, or only those columns\/fields that need it. FPE\u00a0maintains the data in the same size and format, complete with separator characters, where numbers and letters are in the same places within the string.\u00a0This allows the data to be used in Splunk\u2019s charting and analytic capabilities, while keeping it\u00a0secure. FPE is also reversible, so that after data is used\u00a0or displayed by Splunk,\u00a0applicable fields can be decrypted by only those authorized to recover it.<\/p>\n

The example below shows how selected\u00a0fields can be protected, indexed, and stored securely in Splunk, then extracted\u00a0and\u00a0decrypted. Using FieldShield\u00a0FPE,\u00a0personal ID<\/strong> and Credit Card<\/strong> data are\u00a0encrypted in the same format as the original data. People’s names are\u00a0replaced with realistic, but not real, name data via\u00a0reversible pseudonymization.<\/p>\n

Original Data<\/strong><\/p>\n

\"image004\"<\/a><\/p>\n

Format-Preserved Encrypted (ID and CC_NUMBER) & Pseudonymized (NAME) Data\u00a0<\/strong><\/p>\n

\"image006\"<\/a><\/p>\n

ID and credit card values have the same length after encryption, each character\u00a0was\u00a0retained as either a number or letter, and separator characters are unchanged. Since the name data must adhere to the traditional naming conventions, pseudonymization was used. An external list of names substitutes\u00a0for the original names. Both sets get combined in a lookup file for pseudonymization, and an opposite\u00a0restore set for later\u00a0reversal outside Splunk.<\/p>\n

To prepare and secure your data\u00a0for Splunk indexing, use FieldShield specification files or job scripts to apply the functions you need to the fields in your data. You can write the source and target layouts and protections easily by hand or have the GUI do it automatically through job wizards and point-and-click dialogs.<\/p>\n

FieldShield inputs can be\u00a0database tables, files, or a combination of both. See this list<\/a> of IRI-supported data sources. Source formats are specified in the input section of a script, while protections and new formats are specified in the output section. Any number of targets and formats are supported.<\/p>\n

An\u00a0AES-256 FPE function applied to an “ID” field might look like this:<\/p>\n

\"image008\"<\/a><\/p>\n

Though the output field name is changed to reflect its newly encrypted state, the name of the input field “ID” is required, along with the name of the protection function and formatting attributes. Note that the encryption key, or “passphrase” in this case is maintained in a separate, securable file (called pass_id in this case), and not exposed in the script — though both an explicit key and\/or environment variables are also options.<\/p>\n

Pseudonymization in FieldShield uses\u00a0‘set’\u00a0files populated with values that fit the criteria associated with the original data field. In this case, names_first_last.set<\/strong>, contains first and last names. FieldShield creates a two-column lookup file, name_psuedo.set<\/strong>, that combines the original and substitute names\u00a0for pre-Splunk pseudonymization, and the converse\u00a0name_restore.set<\/strong>\u00a0file for post-Splunk restoration:<\/p>\n

\"image014\"<\/a><\/p>\n

These functions are both specified in our\u00a0FieldShield job’s output file, transactions_safe.csv<\/strong>, in a Splunk-ready layout:<\/p>\n

\"image016\"<\/a><\/p>\n

Once the partially encrypted and pseudonymized file is created, you can then index it into Splunk. Splunk will recognize the CSV format and\u00a0automatically\u00a0append a timestamp to each entry:<\/p>\n

\"image018\"<\/a><\/p>\n

Once in Splunk, you can search through the data and customize analytic functions and report displays. Meanwhile, the data you protected in FieldShield will be safe but not hinder the layout or appearance of the data.\u00a0Other users may not even know that the personalizing data was\u00a0encrypted or\u00a0psuedonymized.<\/p>\n

\"image020\"<\/a><\/p>\n

\"image022\"<\/a><\/p>\n

After filtering the data, use the pipe<\/strong> \u201c|\u201d character to start a function. Splunk’s\u00a0Chart <\/strong>function\u00a0allows you to create and customize graphics to your liking. You can then add those\u00a0graphics and statistics to a dashboard<\/strong> for fast and easy analysis.<\/p>\n

\"image027\"<\/a><\/p>\n

To recover the original data values, use Splunk to search for your files or indexed fields, and export them:<\/p>\n

\"image029\"<\/a><\/p>\n

A form will appear where you can designate the filename and format:<\/p>\n

\"image031\"<\/a><\/p>\n

The exported file will be sent to your Downloads <\/strong>folder with the fields ordered alphabetically. Use a FieldShield script like this to restore the field order, decrypt the ID and CC values using the corresponding algorithm and original key (passphrase\/file\/EV),\u00a0and reverse the pseudonyms via the restore set:<\/p>\n

\"image033\"<\/a>Running this job from the IRI Workbench<\/a> GUI or command line will restore your data and its field layout\u00a0to its original state:<\/p>\n

\"image035\"<\/a><\/p>\n

Note that multiple target files or tables could have been specified in this same job as well, with recovery scripts and keys provided only to the\u00a0authorized recipients of particular field values. You can also modify the sort order with CoSort’s SortCL<\/a> program, if you use it\u00a0instead, since SortCL is the parent engine that\u00a0runs FieldShield jobs while extended their capabilities.<\/p>\n

For\u00a0more information on the interaction between IRI Workbench software like FieldShield and Splunk, or other applications, email fieldshield@iri.com<\/a>, or submit your comment below.<\/p>\n","protected":false},"excerpt":{"rendered":"

Introduction: This example demonstrates an older method of using IRI FieldShield to protect sensitive data prior to indexing the data in Splunk. As you will read, FieldShield would process the data outside of Splunk and create a CSV file for Splunk’s ingestion. However, you can also use the Voracity (= FieldShield) add-on for seamless data<\/p>\n

Read More<\/a><\/div>\n","protected":false},"author":60,"featured_media":11683,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_exactmetrics_skip_tracking":false,"_exactmetrics_sitenote_active":false,"_exactmetrics_sitenote_note":"","_exactmetrics_sitenote_category":0,"footnotes":""},"categories":[32,8,2255],"tags":[13,15,203,98,97,585,546,520,584,586,574,582,583],"class_list":["post-6365","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-intelligence","category-data-protection","category-archived-articles","tag-data-protection-2","tag-data-security","tag-encryption","tag-format-preserving-encryption","tag-fpe","tag-indexing","tag-iri-cosort","tag-iri-fieldshield","tag-machine-generated-big-data","tag-reversible-pseudonymization","tag-splunk","tag-structured","tag-unstructured"],"acf":[],"yoast_head":"\nSecure, Then Splunk - A Format-Preserving Encryption and Pseduonymization Example - IRI<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Secure, Then Splunk - A Format-Preserving Encryption and Pseduonymization Example\" \/>\n<meta property=\"og:description\" content=\"Introduction: This example demonstrates an older method of using IRI FieldShield to protect sensitive data prior to indexing the data in Splunk. As you will read, FieldShield would process the data outside of Splunk and create a CSV file for Splunk’s ingestion. However, you can also use the Voracity (= FieldShield) add-on for seamless dataRead More\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/\" \/>\n<meta property=\"og:site_name\" content=\"IRI\" \/>\n<meta property=\"article:published_time\" content=\"2014-11-26T14:44:31+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-02-23T19:43:29+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"300\" \/>\n\t<meta property=\"og:image:height\" content=\"243\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Kyle Grosjean\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kyle Grosjean\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"9 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/\"},\"author\":{\"name\":\"Kyle Grosjean\",\"@id\":\"https:\/\/www.iri.com\/blog\/#\/schema\/person\/b1e7df4f0bc31c27408b601af27ba5dd\"},\"headline\":\"Secure, Then Splunk – A Format-Preserving Encryption and Pseduonymization Example\",\"datePublished\":\"2014-11-26T14:44:31+00:00\",\"dateModified\":\"2026-02-23T19:43:29+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/\"},\"wordCount\":1217,\"commentCount\":3,\"publisher\":{\"@id\":\"https:\/\/www.iri.com\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg\",\"keywords\":[\"data protection\",\"data security\",\"encryption\",\"format-preserving encryption\",\"FPE\",\"indexing\",\"IRI CoSort\",\"IRI FieldShield\",\"machine-generated big data\",\"reversible pseudonymization\",\"Splunk\",\"structured\",\"unstructured\"],\"articleSection\":[\"Business Intelligence (BI)\",\"Data Masking\/Protection\",\"Archived Articles\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/\",\"url\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/\",\"name\":\"Secure, Then Splunk - A Format-Preserving Encryption and Pseduonymization Example - IRI\",\"isPartOf\":{\"@id\":\"https:\/\/www.iri.com\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg\",\"datePublished\":\"2014-11-26T14:44:31+00:00\",\"dateModified\":\"2026-02-23T19:43:29+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#primaryimage\",\"url\":\"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg\",\"contentUrl\":\"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg\",\"width\":300,\"height\":243},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.iri.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Secure, Then Splunk – A Format-Preserving Encryption and Pseduonymization Example\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.iri.com\/blog\/#website\",\"url\":\"https:\/\/www.iri.com\/blog\/\",\"name\":\"IRI\",\"description\":\"Total Data Management Blog\",\"publisher\":{\"@id\":\"https:\/\/www.iri.com\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.iri.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.iri.com\/blog\/#organization\",\"name\":\"IRI\",\"url\":\"https:\/\/www.iri.com\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.iri.com\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2019\/02\/iri-logo-total-data-management-small-1.png\",\"contentUrl\":\"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2019\/02\/iri-logo-total-data-management-small-1.png\",\"width\":750,\"height\":206,\"caption\":\"IRI\"},\"image\":{\"@id\":\"https:\/\/www.iri.com\/blog\/#\/schema\/logo\/image\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.iri.com\/blog\/#\/schema\/person\/b1e7df4f0bc31c27408b601af27ba5dd\",\"name\":\"Kyle Grosjean\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.iri.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/5774edb367635439d5415b05885abf26?s=96&d=blank&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/5774edb367635439d5415b05885abf26?s=96&d=blank&r=g\",\"caption\":\"Kyle Grosjean\"},\"url\":\"https:\/\/www.iri.com\/blog\/author\/kyleg\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Secure, Then Splunk - A Format-Preserving Encryption and Pseduonymization Example - IRI","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/","og_locale":"en_US","og_type":"article","og_title":"Secure, Then Splunk - A Format-Preserving Encryption and Pseduonymization Example","og_description":"Introduction: This example demonstrates an older method of using IRI FieldShield to protect sensitive data prior to indexing the data in Splunk. As you will read, FieldShield would process the data outside of Splunk and create a CSV file for Splunk’s ingestion. However, you can also use the Voracity (= FieldShield) add-on for seamless dataRead More","og_url":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/","og_site_name":"IRI","article_published_time":"2014-11-26T14:44:31+00:00","article_modified_time":"2026-02-23T19:43:29+00:00","og_image":[{"width":300,"height":243,"url":"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg","type":"image\/jpeg"}],"author":"Kyle Grosjean","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kyle Grosjean","Est. reading time":"9 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#article","isPartOf":{"@id":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/"},"author":{"name":"Kyle Grosjean","@id":"https:\/\/www.iri.com\/blog\/#\/schema\/person\/b1e7df4f0bc31c27408b601af27ba5dd"},"headline":"Secure, Then Splunk – A Format-Preserving Encryption and Pseduonymization Example","datePublished":"2014-11-26T14:44:31+00:00","dateModified":"2026-02-23T19:43:29+00:00","mainEntityOfPage":{"@id":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/"},"wordCount":1217,"commentCount":3,"publisher":{"@id":"https:\/\/www.iri.com\/blog\/#organization"},"image":{"@id":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#primaryimage"},"thumbnailUrl":"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg","keywords":["data protection","data security","encryption","format-preserving encryption","FPE","indexing","IRI CoSort","IRI FieldShield","machine-generated big data","reversible pseudonymization","Splunk","structured","unstructured"],"articleSection":["Business Intelligence (BI)","Data Masking\/Protection","Archived Articles"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/","url":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/","name":"Secure, Then Splunk - A Format-Preserving Encryption and Pseduonymization Example - IRI","isPartOf":{"@id":"https:\/\/www.iri.com\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#primaryimage"},"image":{"@id":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#primaryimage"},"thumbnailUrl":"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg","datePublished":"2014-11-26T14:44:31+00:00","dateModified":"2026-02-23T19:43:29+00:00","breadcrumb":{"@id":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#primaryimage","url":"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg","contentUrl":"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg","width":300,"height":243},{"@type":"BreadcrumbList","@id":"https:\/\/www.iri.com\/blog\/data-protection\/secure-then-splunk-a-format-preserving-encryption-and-pseduonymization-example\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.iri.com\/blog\/"},{"@type":"ListItem","position":2,"name":"Secure, Then Splunk – A Format-Preserving Encryption and Pseduonymization Example"}]},{"@type":"WebSite","@id":"https:\/\/www.iri.com\/blog\/#website","url":"https:\/\/www.iri.com\/blog\/","name":"IRI","description":"Total Data Management Blog","publisher":{"@id":"https:\/\/www.iri.com\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.iri.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.iri.com\/blog\/#organization","name":"IRI","url":"https:\/\/www.iri.com\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.iri.com\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2019\/02\/iri-logo-total-data-management-small-1.png","contentUrl":"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2019\/02\/iri-logo-total-data-management-small-1.png","width":750,"height":206,"caption":"IRI"},"image":{"@id":"https:\/\/www.iri.com\/blog\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/www.iri.com\/blog\/#\/schema\/person\/b1e7df4f0bc31c27408b601af27ba5dd","name":"Kyle Grosjean","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.iri.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/5774edb367635439d5415b05885abf26?s=96&d=blank&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/5774edb367635439d5415b05885abf26?s=96&d=blank&r=g","caption":"Kyle Grosjean"},"url":"https:\/\/www.iri.com\/blog\/author\/kyleg\/"}]}},"jetpack_featured_media_url":"https:\/\/www.iri.com\/blog\/wp-content\/uploads\/2014\/11\/fieldshield-splunk.jpg","_links":{"self":[{"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/posts\/6365"}],"collection":[{"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/users\/60"}],"replies":[{"embeddable":true,"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/comments?post=6365"}],"version-history":[{"count":27,"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/posts\/6365\/revisions"}],"predecessor-version":[{"id":12810,"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/posts\/6365\/revisions\/12810"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/media\/11683"}],"wp:attachment":[{"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/media?parent=6365"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/categories?post=6365"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.iri.com\/blog\/wp-json\/wp\/v2\/tags?post=6365"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}