Welcome!

Industrial IoT Authors: Elizabeth White, Stackify Blog, Yeshim Deniz, SmartBear Blog, Liz McMillan

Blog Feed Post

Tokenization for De-Identifying APIs

De-identifying Data in APIs

I was catching up on my RSS feeds over the weekend, reading all the things I missed while I was at IDF, when I saw this great post from Kin Lane calling for “A Masking, Scrubbing, Anonymizing API“.  It reminded me of a conversation I had at IDF about Kaggle, which is a platform for crowdsourcing solutions to big data problems.  In both cases, the goal is to surface data in a way that protects personal information.  It got me thinking about how compliance intersects with API strategies.  With APIs being a universal tunnel into the enterprise, it’s important not to neglect security compliance in API content!  Fortunately, a Tokenization proxy or API Manager can be used to address these types of usage models.

Tokenization vs  Encryption vs Redaction

Tokenization is the process of replacing a string with another randomized string.  Expressway Tokenization Broker can perform this operation as a proxy for any API response, storing the PII in a secure vault.  The only way to recover the original data is through a detokenization routine performed by a system with access to the secure vault.  This is somewhat similar to the mechanism Kin describes (replacing actual values with fake values), except that the tokens are not likely to be human-readable (i.e. instead of replacing Kin Lane with John Doe it might wind up reading zAe N8fc).  On the other hand, tokenization preserves correlation – if you replace every instance of any name with “John Doe” you may lose the ability to do associations across data sets.  The Retail industry has been using this mechanism for years, adopting the tokenization of Payment Account Numbers (PAN) as a best practice for PCI compliance.  We have recently seen adoption of this tokenization capability for other types of PII, particularly where there are compliance and audit concerns.

Tokenization Process

Tokenization of Payment Account Numbers for PCI Compliance

Format-Preserving Encryption (FPE) is another mechanism for de-identifying data.  It is available in all of our Expressway products.  In this case, the data is encrypted using ciphertext that conforms to the same formatting as the input data.  For example, the SSN 123-45-1234 might encrypt to 789-12-3456.  This ensures that the ciphertext will pass any downstream format checking that may occur.  However, unlike tokenization, FPE is reversible — it is possible to decrypt the ciphertext to plaintext without access to a tokenization vault.  This makes the ciphertext behave more like encrypted data, enabling applications to use a shared secret to decrypt the data independently from the secure vault.

Finally, data can be anonymized using redaction, which is also supported in all of our products.  This is the process of eliminating PII entirely rather than replacing it.  This is the most surefire mechanism for keeping PII out of the wrong hands, but it comes with a potential downfall:  it may prevent records from being associated with the same owner, particularly across data sets.  This correlation can be the most valuable opportunity in many types of big data analysis.

De-Identification Using the Façade API Proxy Pattern

We have seen customers take advantage of regular expressions to identify personally identifiable information (PII).  There are standard policies that can pick out Social Security Numbers, email addresses, and other common types of PII in any API.  Nonstandard types of PII can be detected as well, provided that they conform to a well-defined structure (generally alphanumeric with a fixed length, although other patterns can be identified as well).  Once the PII has been identified, the data can be de-identified using tokenization or encryption (including format-preserving encryption).  Or the data can be anonymized completely via redaction. This policy can be generalized to proxy several APIs and replace any PII that passes through.  This works particularly well for credit card or social security numbers, both of which follow a very well-defined and relatively unique pattern.

Anonymization policies can also be tailored to specific APIs that have well-defined schemas (along the lines of the Swagger example that Kin suggested), matching based on the JSON or XML field information.  For example, a colleague and I were playing with the idea of stashing employee information in DynamoDB.  An employee record might look like:

{ 
  "Name": { "S": "Sally Rockstar" }, 
  "Email": { "S": "[email protected]acme.corp.us" },
  "City": { "S": "Mountain View" },
  "State": { "S": "CA" },
  "Zip": { "N": "90210" },
  "DriversLic": { "S": "A1234567" },
  "SSN": { "S": "123-45-1234" },
  "CurrentSalary": { "N": "60000" } 
}

Within this data set, email, SSNs, Drivers License numbers, and Zip Codes follow well-established rules that lend themselves to regular expressions.  However, the zip code rule (5 digit number) could match the salary field.  Obviously you could enforce Zip+4 and decimal inputs (XXXXX-XXXX for Zip Code, XXXXX.XX for CurrentSalary), but it would probably be safer to match the name rather than the value for this data set.

Another benefit of the anonymizing facade API pattern is that it can support conditional de-identification.  For example, I may want to allow the PII to be read within my network but have it de-identified for external clients.  Or I may want to tokenize internally but redact externally.  We can define a workflow that uses any of a number of factors to make the decision at API request time, allowing access to live data rather than a snapshot.

Summary

I’m excited about the potential for APIs to allow faster problem solving through crowdsourcing.  Kaggle looks like a very interesting platform for enabling this.  I’m also happy to see folks like Kin working to make government more open and accessible through the use of APIs.  API gateways can play a role in those transformations by sanitizing the data, reducing the risk of PII being compromised.  As Mark Silverberg pointed out in the comments on Kin’s blog, the safest way to protect PII is to scrub the data set before it goes out.  By using a tokenizing or encrypting proxy facade, the “scrubbing” is made internal, minimizing the risk of an escape.

As I noted above, our products are unique in the API management space, in that they support high-performance de-identification policies.  They also include powerful regular expression libraries that can be used to identify (and then de-identify) PII that is contained in an API response.  I did a webinar with John Kindervag recently that touched on many of these topics as well.  You can watch the replay to learn more, or try out FPE and redaction for yourself using Expressway API Manager on Amazon Web Services.

The post Tokenization for De-Identifying APIs appeared first on Application Security.

Read the original blog entry...

More Stories By Application Security

This blog references our expert posts on application and web services security.

IoT & Smart Cities Stories
The challenges of aggregating data from consumer-oriented devices, such as wearable technologies and smart thermostats, are fairly well-understood. However, there are a new set of challenges for IoT devices that generate megabytes or gigabytes of data per second. Certainly, the infrastructure will have to change, as those volumes of data will likely overwhelm the available bandwidth for aggregating the data into a central repository. Ochandarena discusses a whole new way to think about your next...
DXWorldEXPO LLC announced today that Big Data Federation to Exhibit at the 22nd International CloudEXPO, colocated with DevOpsSUMMIT and DXWorldEXPO, November 12-13, 2018 in New York City. Big Data Federation, Inc. develops and applies artificial intelligence to predict financial and economic events that matter. The company uncovers patterns and precise drivers of performance and outcomes with the aid of machine-learning algorithms, big data, and fundamental analysis. Their products are deployed...
Dynatrace is an application performance management software company with products for the information technology departments and digital business owners of medium and large businesses. Building the Future of Monitoring with Artificial Intelligence. Today we can collect lots and lots of performance data. We build beautiful dashboards and even have fancy query languages to access and transform the data. Still performance data is a secret language only a couple of people understand. The more busine...
All in Mobile is a place where we continually maximize their impact by fostering understanding, empathy, insights, creativity and joy. They believe that a truly useful and desirable mobile app doesn't need the brightest idea or the most advanced technology. A great product begins with understanding people. It's easy to think that customers will love your app, but can you justify it? They make sure your final app is something that users truly want and need. The only way to do this is by ...
CloudEXPO | DevOpsSUMMIT | DXWorldEXPO are the world's most influential, independent events where Cloud Computing was coined and where technology buyers and vendors meet to experience and discuss the big picture of Digital Transformation and all of the strategies, tactics, and tools they need to realize their goals. Sponsors of DXWorldEXPO | CloudEXPO benefit from unmatched branding, profile building and lead generation opportunities.
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Cell networks have the advantage of long-range communications, reaching an estimated 90% of the world. But cell networks such as 2G, 3G and LTE consume lots of power and were designed for connecting people. They are not optimized for low- or battery-powered devices or for IoT applications with infrequently transmitted data. Cell IoT modules that support narrow-band IoT and 4G cell networks will enable cell connectivity, device management, and app enablement for low-power wide-area network IoT. B...
The hierarchical architecture that distributes "compute" within the network specially at the edge can enable new services by harnessing emerging technologies. But Edge-Compute comes at increased cost that needs to be managed and potentially augmented by creative architecture solutions as there will always a catching-up with the capacity demands. Processing power in smartphones has enhanced YoY and there is increasingly spare compute capacity that can be potentially pooled. Uber has successfully ...
SYS-CON Events announced today that CrowdReviews.com has been named “Media Sponsor” of SYS-CON's 22nd International Cloud Expo, which will take place on June 5–7, 2018, at the Javits Center in New York City, NY. CrowdReviews.com is a transparent online platform for determining which products and services are the best based on the opinion of the crowd. The crowd consists of Internet users that have experienced products and services first-hand and have an interest in letting other potential buye...
When talking IoT we often focus on the devices, the sensors, the hardware itself. The new smart appliances, the new smart or self-driving cars (which are amalgamations of many ‘things'). When we are looking at the world of IoT, we should take a step back, look at the big picture. What value are these devices providing. IoT is not about the devices, its about the data consumed and generated. The devices are tools, mechanisms, conduits. This paper discusses the considerations when dealing with the...