PropelZ™ for PCI DSS 4.0: Accelerating Evidence Collection with Splunk

PCI DSS 4.0 raises the bar for monitoring, logging, and auditable evidence across all platforms — including IBM Z. In this session, we’ll show how PropelZ™ helps mainframe teams quickly deliver the right operational data to Splunk (and JDBC targets) as part of a broader PCI program — without brittle scripts or one-off data moves.

You’ll see how the PropelZ Splunk Log Connector exposes z/OS console message traffic as a governed input and publishes to Splunk for centralized analysis and alerting. We’ll also cover when to persist events to databases or archives via JDBC outputs for retention and investigations. We’ll be clear about scope: PropelZ isn’t a one-stop compliance product — it’s a powerful accelerator that streamlines the “data-in/SIEM-out” cog many security and audit teams struggle to implement and maintain.

What we’ll cover

• Where PCI DSS 4.0 increases expectations for logging, monitoring, and evidence — and why mainframe platforms are in scope.
• How PropelZ + Splunk Log Connector moves z/OS console messages into Splunk; what’s included on the input and output sides.
• When to route events to JDBC-compatible targets (Oracle, SQL Server, PostgreSQL, Snowflake, BigQuery, Redshift) for retention and reporting.
• Realistic boundaries: why some PCI controls still require application-level logging and broader controls — and how PropelZ fits as an accelerator.
• Live demo: set up, configure, and verify event flow to Splunk — plus patterns for archival.

Who should attend

• Security & compliance leaders, SIEM engineers (Splunk), mainframe platform teams, data engineers supporting audit/forensics, and MSP/partner architects.