PCI/DSS Data Compliance with Streamdal

We're updating our documentation, so the presented info might not be the most recent.

The data compliance features of Streamdal are currently in beta, and being tested with a select group of contributors, companies, and design partners. If you would like to participate in the beta, please reach out to us.

The Payment Card Industry Data Security Standard (PCI DSS), initially introduced in 2004, is a global set of security standards designed to ensure that all companies that accept, process, store, or transmit credit card information maintain a secure environment.

Streamdal can help keep your PCI data in compliance.

Streamdal’s Approach

You can leverage Streamdal for:

Data Flow Diagram: An integral part of the Console UI is the Data Graph. It will show the flow of data throughout your entire system in a single view, and give you instant compliance with this requirement of PCI DSS.

No maintenance on the Data Graph is required because of how the Streamdal SDK works. The view it provides in the Console UI) is dynamic, and so long as new and existing services are instrumented with the SDK, the Data Graph will always give an up-to-date representation of data flow.

Enforcing Data Policies: You can physically apply your requirements to producers and consumers of cardholder data by creating rules in the Console UI. From there (or the Streamdal CLI), you can periodically audit real-time data with Tail to ensure data is flowing within the necessary compliance parameters.

Data Minimization & PII Protection: Rules can be created into a matrix of pipelines that data must validate through in order to continue flowing through your systems.

For example: you could set up rules to obfuscate or block cardholder data, and restrict access by IP address or time fields to ensure data minimization and more scrutiny over hours of use

Coming Soon: A visual guide on setting up PCI DSS-specific rules in the Console UI.

Regulatory Insights

We wanted to make researching the relevant data regulations easier and give a better idea of where Streamdal could be the most impactful for your organization. In most cases, the combination of the observability and data governance capabilities will ensure successful compliance.

While more PCI requirements could be applicable, below are some (abbreviated) sections taken from various requirements established in the PCI DSS v4.01 along with how Streamdal can help with data compliance:

PCI RequirementsHow Streamdal helps comply
1.2.4 An accurate data-flow diagram(s) is maintained that meets the following:

• Shows all account data flows across systems and networks.

• Updated as needed upon changes to the environment.
Once the Streamdal core components have been fully instrumented, the Data Graph will ensure all services that handle account data are in a single view.

Since the Data Graph is dynamic, it will not require maintenance like many contemporary solutions, and will always be accurate so long as new services instrument the SDK or utilize our Shims.
2.1.1 All security policies and operational procedures that are identified in Requirement 2 are:

• In use.
You can ensure your data policies are in use by adding them to rules in the Console UI and then attaching those rules as pipelines to any service that requires it.

For example, you can set up rules to reject data that might populate too much card data in one environment or storage destination, causing potential security and compliance issues. Pipelines can be attached and detached in real time to help with easier policy adjustments.
3.2.1 Account data storage is kept to a minimum through implementation of data retention and disposal policies, procedures, and processes…The Streamdal SDK can filter for cardholder data, and ensure only the minimum amount of data required is being transmitted.

Rules can also be set up to approve/reject data based on time fields to prevent data past its retention period from being accidentally reintroduced into critical environments. The full contents of any track are not retained upon completion of the authorization process.Rules can be set up to enforce data content requirements, and the SDK can block data transmission that would result in potentially retaining more information than necessary.
7.2.5 All application and system accounts and related access privileges are assigned and managed…You can set up rules on the movement of data for applications, such as only accepting data during certain windows of time throughout the day (week, month, etc). Rules also allow you to restrict access and movement of data to specific IP addresses.

Did you know:

Among the good practices outlined for ensuring your software is developed securely, PCI DSS states that “…understanding how sensitive data is handled by the application—including when stored, transmitted and in memory—can help identify where data needs to be protected2.”


  1. PCI Security Standards Council. (2022). PCI DSS Requirements and Testing Procedures Version 4.0 [Requirement sections: 1.2.4, 2.1.1, 3.2.1,, 7.2.5]. https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0.pdf ↩

  2. PCI Security Standards Council. (2022). PCI DSS Requirements and Testing Procedures Version 4.0 [6.2 Bespoke and custom software are developed securely: Good Practice, p. 127]. https://docs-prv.pcisecuritystandards.org/PCI%20DSS/Standard/PCI-DSS-v4_0.pdf ↩