Keeping the Bank Happy: PCI DSS v4
summary
PCI DSS v4.0.1 (released March this year) requires concrete controls: annual internal and external penetration tests, ASV scans (Qualys or equivalent), continuous log monitoring, mandatory MFA and EDR, and vulnerability management that addresses all severities. Practical advice: avoid storing PANs, segment and encrypt anything you keep, scan code with ZAP and OpenVAS in CI/CD, and treat cloud as a shared responsibility. A redirect to WindCave can still hit the merchant and breaches cost an estimated $40 billion globally in 2023; merchants processing over 6 million transactions face full audits.
AI-written summary · about
chapters (10)
- 0:00PCI DSS introduction
- 3:12Why PCI DSS matters
- 7:12Credit card fraud impact
- 10:04PCI DSS terms explained
- 13:35PCI DSS v4 changes
- 16:25Six PCI focus areas
- 19:56Secure coding for PCI
- 23:01PCI compliance levels
- 25:07PCI DSS benefits
- 27:14PCI compliance resources
related talks
47mBreakout Session
48mPCI DSS 4.0: Evolution, Revolution, or an Omen of Extinction?
32mSecurity horror stories in payments
42mSecurity, Fraud, and Compliance Panel
06mLightning Talk: PCI DSS and
41mPerspectives on the transition to PQC in the financial sector
47mKey Trends in the Shifting Threats to Payments as Blended Commerce Returns
33mPKI PKI and PQC Strategy for Payment Card Industry
