Managing PCI DSS Requirement 4 for cardholder data in transit
Australian businesses process card payments through websites, mobile applications, point-of-sale terminals, call centres, subscription platforms and third-party marketplaces. Every transfer creates a potential exposure point, whether a customer taps a card in Melbourne, enters details into a Sydney-based ecommerce site or pays through an app while using public Wi-Fi at Brisbane Airport.
PCI DSS Requirement 4 focuses on protecting cardholder data during transmission over open, public networks. The central expectation is clear: payment data must be protected with strong cryptography and secure protocols while it travels between systems that could be observed, intercepted or manipulated.
Meeting the requirement involves more than enabling HTTPS on a checkout page. Organisations need to identify every payment data path, configure encryption correctly, control certificates and keys, protect APIs and wireless connections, and retain evidence that security settings remain effective. Continuous assurance can help security and engineering teams detect drift before an assessment exposes it.
What requirement 4 covers
Requirement 4 applies when cardholder data, including the primary account number, moves across an open or public network. This can include the public internet, public wireless services, cellular networks, shared hosting environments and other networks where the organisation cannot fully control who may observe traffic. A payment gateway connection, browser session, mobile API call or remote administrative session may fall within the assessment scope.
Strong cryptography should protect data in transit from interception and unauthorised modification. In practice, this means using current, securely configured versions of TLS for web traffic and APIs, validating certificates, disabling obsolete protocols and preventing users or systems from bypassing certificate errors. SSL and early TLS configurations should not remain as a fallback for older devices without a documented, risk-based treatment.
The requirement also reaches payment information sent through email, chat, file transfer, support tools and integrations. A business may secure its payment page yet expose a full card number in a support ticket or transmit it to a vendor through an unencrypted export. Mapping information flows is therefore essential. Document the source, destination, protocol, data type, encryption method, ownership and retention behaviour for each route.
Australian organisations should consider local operating conditions when mapping those flows. Tap-and-go payments are routine across Sydney and Perth, while retailers frequently connect cloud point-of-sale services through business broadband or mobile networks. A customer may also complete a purchase over café Wi-Fi in Melbourne or on a mobile device travelling between regional locations. These environments reinforce why public-network protections must be designed into the transaction rather than left to user behaviour.
Building a defensible encryption architecture
Start with a current data-flow diagram that shows where payment information enters the environment, how it reaches a payment processor, and what systems can observe or relay it. Include web servers, mobile back ends, APIs, reverse proxies, content delivery networks, service meshes, payment terminals, call-centre software and third-party providers. Mark every connection that carries a full PAN, token, payment authentication value or other cardholder data.
For internet-facing services, configure TLS using approved certificates, modern protocol versions and strong cipher suites. Automate certificate renewal and alert on impending expiry. Confirm that certificates match the correct hostnames and that the full trust chain is presented. A certificate that is technically valid but attached to the wrong endpoint can still create a serious security failure.
Encryption should be enforced at each meaningful connection rather than assumed because a front-end page uses HTTPS. For example, a browser may connect securely to an application, but the application’s connection to a payment gateway, fraud service or message broker may use a weaker setting. API gateways should reject plaintext requests, redirect behaviour should be controlled, and sensitive values should not appear in URLs because query strings often enter browser history, proxy logs and analytics platforms.
| Payment pathway | Appropriate protection | Evidence to retain |
|---|---|---|
| Customer browser to checkout | Current TLS, valid certificate, secure headers and no mixed content | TLS scan, configuration export, certificate inventory |
| Mobile application to payment API | TLS with certificate validation and controlled endpoints | API configuration, mobile release controls, test results |
| Application to payment processor | Strong TLS, authenticated integration and monitored failures | Vendor specification, connection settings, transaction test |
| Wireless point-of-sale device | Approved secure wireless configuration or managed private connection | Network standard, device inventory, wireless assessment |
| Support or operational transfer | Avoid full PAN; if unavoidable, approved encrypted channel and access controls | Procedure, transfer logs, approval records |
| Service provider connection | Contractual security requirements, encryption validation and monitoring | Attestation, contract, review record, monitoring alerts |
Wireless environments deserve specific attention. Payment terminals should use managed networks with strong authentication and segmentation, not an open guest network shared by customer devices. WPA2-Enterprise or WPA3-Enterprise may be appropriate depending on device compatibility and the organisation’s architecture. Network names, encryption settings, firmware versions and device ownership should be recorded, with rogue access point detection where relevant.
Controlling scope, vendors and operational access
A strong design reduces the amount of cardholder data that an organisation handles. Hosted payment pages, tokenisation and point-to-point encryption can limit exposure, although they do not automatically remove PCI DSS responsibilities. The business must still validate integration settings, protect credentials, manage redirects and confirm that payment data is not copied into logs, analytics tools, screenshots or customer records.
Third parties commonly operate important links in the payment chain. Acquirers, payment gateways, ecommerce platforms, managed service providers, call-centre suppliers and cloud services may transmit or handle cardholder data on the organisation’s behalf. Contracts should define security obligations, incident notification, permitted data flows, encryption expectations and evidence access. Review the provider’s relevant compliance documentation, but also verify how the service is configured in your own environment.
A useful control is continuous monitoring of privileged and vendor connections. Vendor access monitoring can help identify unexpected access paths, inactive accounts, unusual connection times and changes to integrations that transport sensitive data. This is especially valuable when a provider supports stores, warehouses or offices across different Australian time zones and business hours.
Remote administration also requires care. If a technician connects to a payment environment from home, a hotel or a shared office, the session should use an approved secure channel with strong authentication and appropriate device controls. Administrative tools must not silently downgrade encryption, and access should be limited to the systems and time period required. Keep records of approvals, session activity and changes made during support work.
Australian businesses should align this work with the Privacy Act 1988 and the Notifiable Data Breaches scheme. PCI DSS and privacy obligations are different, but an exposed PAN can create consequences under both regimes. Organisations regulated by APRA may also need to consider CPS 234 expectations around information security capability, control testing and incident response. A consistent encryption and evidence programme reduces duplicated effort across these obligations.
Turning technical settings into continuous evidence
Assessors generally need more than a policy statement saying that encryption is required. Evidence should demonstrate that the rule is implemented, tested and maintained. Useful records include an approved cryptographic standard, asset and certificate inventories, TLS scan results, firewall or gateway configurations, wireless assessments, change tickets, vendor attestations and remediation records.
Testing should cover external and internal service paths that carry cardholder data. An external scan can identify expired certificates, weak protocols, insecure renegotiation and exposed services. Application testing can find mixed content, insecure redirects, hard-coded endpoints and sensitive data in URLs. Packet inspection in a controlled test environment can confirm that PAN is unreadable while travelling across the relevant connection.
Configuration drift is a common weakness. A load balancer may be replaced, a development endpoint may be exposed temporarily, or a vendor may change its supported protocol without the security team noticing. Monitoring should compare actual settings with an approved baseline and create an alert when encryption is weakened, a certificate approaches expiry or a new payment-related endpoint appears.
Security and engineering teams can integrate these checks into delivery workflows. Policy-as-code rules can block a deployment that exposes a payment API without TLS, permits an unapproved cipher or creates a public endpoint connected to a cardholder-data service. Teams working with regulated defence customers may also find policy as code useful as a model for enforcing control requirements automatically across infrastructure and repositories.
Tauruseer’s continuous assurance approach can connect control requirements with live evidence from cloud environments, development tools and operational systems. The Secured Buy™ program is designed to place governance checks inside CI/CD and DevOps workflows, allowing product teams to identify control failures during delivery rather than waiting for an annual audit. This supports a clearer link between a PCI DSS policy, its technical implementation and the evidence an assessor can review.
Responding to failures and maintaining readiness
An encryption failure should trigger a defined response. Examples include a certificate expiry, a payment endpoint accepting HTTP, a processor connection reverting to an old protocol, a wireless terminal joining the wrong network or a support tool recording unmasked card data. The response should identify affected systems and transactions, contain the exposure, preserve relevant logs, remediate the cause and assess whether cardholder data was compromised.
Alert prioritisation matters when teams receive thousands of operational notifications. Signals from payment gateways, certificate monitors, cloud controls and application security tools should be correlated with asset criticality and data sensitivity. A practical approach to incident response alerts can help teams rank urgent indicators, although payment-specific context must remain central to the decision.
Maintain an inventory of certificates, cryptographic protocols, payment integrations, wireless devices and approved third parties. Assign an owner to each item and set review intervals based on risk. Test certificate renewal, gateway failover and incident escalation before a production event forces the team to discover that a contact, credential or runbook is outdated.
Finally, treat Requirement 4 as a living operational control rather than a one-off audit task. Review encryption standards when PCI DSS guidance, browser behaviour, processor requirements or platform architecture changes. For Australian companies expanding from a local customer base into international ecommerce, early discipline around TLS, payment tokenisation, vendor oversight and evidence collection can support safer growth while making future PCI DSS assessments more predictable.