Illustration of a cargo dock with stacks of blue and pink shipping containers, some bearing the logo Upwind. The scene includes overhead structures and rows of containers along a dock under bright lighting.

Automatically Discover API Sensitive Data Flows

Joshua Burgin October 22, 2024

Automatically Discover API Sensitive Data Flows

We are excited to announce a significant new addition to Upwind’s API Security capability – the automatic discovery and classification of sensitive data flows.

Upwind automatically tracks sensitive data routes and classifies sensitive data as PCI, PII, and PHI by analyzing API samples recognized by the Upwind sensor, making it easy to identify where you are at elevated risk.

Screenshot-2024-08-30-at-9.50.26%E2%80%AFAM-1024x656

Examples of sensitive data that Upwind identifies include:

  • PHI data: patient information, medical records & insurance information
  • PII data: SSNs, IDs and emails
  • PCI data: credit cards and billing information
Screenshot-2024-08-30-at-9.50.02%E2%80%AFAM-1024x732

How Upwind Identifies Sensitive Data Flows

In order to identify sensitive data flows, Upwind searches for patterns at the packet level and then masks any data found, ensuring it remains secure and is never sent outside of your environment. When an API request for sensitive data  is detected, Upwind labels it with a sensitive data tag and classifies it by its type and category, such as PCI for a MasterCard number. We are continuing to extend this capability, and customers will soon be able to create their own custom regular expression (regex) to classify sensitive data.

Screenshot-2024-09-04-at-6.13.58%E2%80%AFAM-1024x483

Use Upwind’s automated sensitive data flow tracking to easily understand API data security risks, prioritize remediation efforts for APIs with sensitive data flows, and ensure a proactive approach to data security. 

Learn More

To learn more about Upwind API Security, visit the Upwind Documentation Center (login required), or schedule a demo.

Contents

Further Reading

behind-the-curtain-part-02

What’s Behind the Curtain? AWS Bedrock AgentCore Runtime Tear Down – Part II

Recap In Part I, we explored the AgentCore Runtime microVM from the inside and discovered we weren't alone - four platform binaries were running alongside our code, and one of them was quietly shipping logs to an AWS-internal S3 bucket. We left off with a question: what can we learn from these internal components, and…
behind-the-curtain-part-01

What’s Behind the Curtain? AWS Bedrock AgentCore Runtime Tear Down – Part I

Introduction When you deploy an AI agent to AWS Bedrock AgentCore Runtime, your code runs inside a Firecracker microVM - but it doesn't run alone. In this three-part series, we tear down the platform internals, document what we found, and assess how well the isolation holds up. Setting the Stage AWS Bedrock AgentCore Runtime is…
upwind-code

Upwind Code Expands Enterprise Coverage to Azure DevOps and Bitbucket Cloud

Modern development organizations rarely keep all their code in one place. Teams may use different version control platforms because of acquisitions, business-unit preferences, regional requirements, or existing development workflows. But when code is spread across multiple providers, application security coverage can become fragmented too. Today, Upwind Code adds support for Azure DevOps and Bitbucket Cloud.…
Add the Upwind RSS Feed to Slack
Connect the Upwind RSS Feed to your Slack.
Follow the how-to here.
Threat RSS
Add the Upwind RSS Feed to Slack
Connect the Upwind RSS Feed to your Slack.
Follow the how-to here.
Main RSS