
Outline the scope of the PCI DSS framework and the four areas of the course, covering fundamentals, assessment, the 12 requirements, and implementation.
Preview the PCI DSS fundamentals developed in the module, including key terms, payments, scope, requirement and goal overviews, and changes from v3.2.1.
Interpret core PCI DSS terminology—including CDE, CHD, SAD, requirements, and compliance artifacts—to correctly scope card-data environments and compliance obligations.
Explain what the PCI DSS require in practice by understanding their scope, structure, assessment mechanisms, and role in defining security controls for card-data environments.
Understand payment transaction flows and participants to contextualize where cardholder data appears and how PCI DSS controls apply across card-present and card-not-present scenarios.
Learn about Vasco's specific style of simulator Lab, and how these will work throughout the course
Explore how different payment architecture configurations affect vulnerabilities in a hands-on risk simulator. Adjust inputs like processor use, tokenization, and stored methods, run scenarios, and analyze weaknesses for online payments.
Explain why the PCI DSS exist and how they evolve by understanding their industry origins, version lifecycle, and response to changing fraud and security risks.
Plan a realistic PCI DSS implementation by sequencing controls, reducing scope, and prioritizing security improvements across data, systems, and processes.
Explore a PCI DSS timeline planner lab that uses a simple simulator to show how system size, resources, and time influence control implementation timelines through three steps.
Define and assess PCI DSS scope by classifying systems as CDE, security-impacting, or out-of-scope, and understanding how connectivity and access determine compliance obligations.
Interpret the twelve PCI DSS requirements by understanding their intent, control focus, and how they collectively protect cardholder data across technical and organizational domains.
Use PCI DSS goals to contextualize individual requirements, enabling a principle-driven understanding of how security controls work together to protect cardholder data.
Explore how PCI DSS scope expands or shrinks by adjusting network connections and cardholder data exposure in a hands-on scope explosion simulator.
Assess the impact of PCI DSS v4.0 changes by understanding requirement generalization, new sub-requirements, and the introduction of the customized approach to compliance.
Consolidate the PCI DSS fundamentals by reviewing key terms, requirements, goals, scope, and the reasons the standards exist.
Learn about Vasco's specific style of evaluation simulator Lab with 20 scenarios, and how these will measure your knowledge
Preview how organizations assess PCI DSS compliance, including the SAQ categories and the criteria used to select among them.
Distinguish merchant levels, ROCs, and the nine SAQ types, and explain how transaction volume, payment model, and card data handling determine which applies.
Engage in a hands-on lab for PCI-DSS v4.0.0 merchant classification. Simulate input changes, outputs, and rising transaction volume to see how decisions affect merchant risk levels.
Select the correct SAQ by working through questions on service provider status, card data storage, specific devices, and how payments are accepted or outsourced.
Experiment with a saq disclassifier simulator to see how choices like iframe payments, shared hosting, and storing account numbers affect scq categories and compliance complexity.
Consolidate how SAQ categories relate to payment models and how the SAQ selection criteria lead to the right assessment.
Preview the 12 PCI DSS requirements and how they group into network security, data protection, access control, monitoring, and policy.
Use a requirements spreadsheet to organize and track the 12 PCI DSS requirements and their sub-requirements.
Design and validate network security controls that isolate the cardholder data environment by restricting traffic, controlling trusted and untrusted connections, and mitigating risks from connected devices.
Work with a network segmentation simulator to explore risk and compliance. Tune vendor and inbound access, run the simulation, and craft a realistic security balance.
Reduce system vulnerabilities by applying secure configurations across system components, removing unsafe defaults, and hardening both wired and wireless environments.
This lab simulates default credential exposure to show how lax passwords and remote admin access affect PCI DSS compliance, and teaches adjusting inputs to mitigate vulnerabilities and preserve operator accounts.
Protect stored cardholder data by minimizing retention, enforcing unreadability through cryptography, restricting exposure of PANs, and managing encryption keys securely.
Run and analyze a data storage risk simulator to see how inputs like encryption and storing full personal account numbers influence security outcomes and PCI-DSS compliance.
Secure cardholder data during transmission by enforcing strong cryptography, trusted keys and certificates, and eliminating weak or deprecated encryption methods.
Explore how public wifi, tls, vpn use, and legacy protocols affect transmission security in a practical lab, then engineer scenarios to maximize safety under real-world constraints.
Prevent, detect, and respond to malicious software by deploying active, monitored anti-malware controls across systems and protecting PCI-relevant personnel from phishing attacks.
Explore a malware defense simulator to see how antivirus, anti-malware, and endpoint protection choices shape your cybersecurity posture and final security level, including phishing awareness and scenario engineering.
Maintain secure systems and software by embedding security into development practices, identifying and remediating vulnerabilities, protecting public-facing applications, and controlling system changes.
Engage in a secure software development lifecycle simulator to explore how patching cadence, third-party libraries, and code reviews shape cybersecurity posture under PCI-DSS v4.0.0.
Enforce least-privilege access to system components and cardholder data by defining role-based permissions, minimizing data exposure, and managing access through centralized control systems.
Explore how privilege creep affects security by running a simulator, adjusting permissions and input variables, and engineering a scenario to maximize security while preserving elevated access.
Ensure accountability and secure access to the cardholder data environment by managing user identities, enforcing strong authentication and MFA, and controlling system and application accounts.
Explore how multi-factor authentication, password complexity, and shared accounts shape authentication strength and PCI-DSS posture, and observe how input changes affect compliance outcomes through a hands-on simulator.
Protect cardholder data through physical security controls by managing facility access, visitor procedures, media handling, and safeguarding point-of-interaction devices from tampering.
Explore a physical security exposure simulator that varies CCTV, batch access, and visitor controls to observe how input changes shape final security outcomes through three guided steps.
Detect and investigate security incidents by implementing comprehensive logging, protecting log integrity, reviewing events, and ensuring accurate time synchronization across systems.
Engage with PCI-DSS v4.0 requirement 10 using a logging visibility simulator to adjust retention, SIEM integration, and alert thresholds, mapping inputs to cybersecurity posture and compliance.
Identify and remediate vulnerabilities by performing regular security testing, including wireless audits, vulnerability scanning, penetration testing, intrusion detection, and payment page integrity monitoring.
Explore testing coverage from internal, external, and penetration testing, and see how segmentation shapes the cybersecurity posture through variable inputs and simulated high-coverage scenarios.
Sustain PCI DSS compliance through governance by maintaining security policies, managing scope and risk, overseeing third-party providers, training personnel, and responding to security incidents.
Use a no-code policy maturity simulator to study cybersecurity policies. Adjust inputs like executive support, employee acknowledgement, and annual reviews to see how policy components shape quality and sophistication.
Consolidate the 12 PCI DSS requirements and the controls each one demands for protecting cardholder data.
Preview how PCI DSS compliance is put into practice through requirement recaps, checklists, implementation stages, best practices, weak points, and change handling.
Synthesize the 12 PCI DSS requirements into core implementation patterns, understand how requirements interrelate, and identify recurring control themes that drive effective compliance.
Translate each PCI DSS requirement into practical implementation checklists to support structured execution, progress tracking, and compliance gap identification.
Plan and sequence PCI DSS implementation using a phased timeline that prioritizes high-risk controls and progressively layers monitoring, governance, and supporting controls.
Explore allocating a PCI-DSS v4.0.0 compliance budget by simulating investments in training, multi-factor authentication, and logging, and observe the consequences of prioritizing one area.
Apply proven best practices to reduce PCI DSS scope, lower compliance effort, improve security outcomes, and increase organizational buy-in.
Identify common PCI DSS implementation failures, analyze their root causes, and apply targeted corrective actions to strengthen compliance posture.
Engage with a weak point identifier simulator to see how varying input areas—networks, shared accounts, segmentation, and logging—shape outputs, and practice reverse engineering, tinkering, and scenario planning in a sandbox.
Manage PCI DSS compliance over time by assessing the impact of organizational, technical, and regulatory changes and updating controls, scope, and documentation accordingly.
Explore how a single change can shift a stable PCI DSS scope and compliance, using inputs like new payment methods and remote workforce to test impact.
Consolidate how PCI DSS compliance is implemented, maintained, and kept current through best practices and attention to weak points and changes.
Recap the PCI DSS terms, requirements, assessment process, and implementation approach covered across the course.
Preview the range of security and privacy controls covered and how they protect data, systems, and physical assets.
Apply acquisition controls such as tamper-proof packaging, distribution tracking, supplier qualification, and supplier acceptance criteria and incentives to reduce tampering and supply chain attacks on purchased components.
Distinguish static and dynamic code analysis and choose the one suited to finding vulnerabilities such as SQL injection and buffer overflows, depending on whether source code is available.
Explain how digital signatures on software, firmware, updates, and drivers verify integrity and origin, and how code signing also supports digital rights management.
Apply security controls in proportion to data sensitivity, including multifactor authentication and the principle of least privilege for PII, privileged, and classified information.
Assess how critical a system is by weighing the consequences and likelihood of its failure, and reduce critical systems through redundancy or separation of functions.
Apply encryption to data in transit and at rest in proportion to sensitivity, accounting for protocol versions, key management, contingency planning, and access control.
Investigate possible compromise proactively using novelty threats, indicators of compromise, and machine learning models, following the steps of identification, investigation, and follow-up.
Apply masking, tokenisation, noise insertion, and synthetic data to remove personal information so that data can be processed safely.
Design data governance structures such as boards, ethics and integrity boards, and hierarchical councils, and distinguish Data Governance from Data Management.
Define the purposes for which users and roles may process PII at each stage of the data lifecycle, using access control and data classification to support compliance.
Minimise data retention and schedule secure disposal while balancing regulatory minimum retention periods such as those in the PCI-DSS.
Design layered, redundant controls across network, workstation, file integrity, and policy so that protection degrades gracefully when one control fails.
Distinguish passive and active information tainting for detecting data leaks from taint checking, which finds compromised inputs in source code.
Apply physical controls that lock or disable rooms, devices, and ports, supported by visitor logs and IT inventories, to prevent tampering and protect integrity.
Downgrade the sensitivity of media through redaction in a verified process, updating markings, inventories, and access controls to match.
Protect physical media at rest, in transit, and at destruction using sensitivity markings, physical access controls, and designated safe locations.
Assess external providers against your own security demands and monitor them continually for vulnerabilities and supply chain changes that could cause attacks or ruptures.
Define a security and privacy architecture integrated with the enterprise architecture, using baseline configurations, SDLC rules, inventories, defense-in-depth, and supplier diversity.
Explain how safe modes support protection and recovery, define their triggers, and weigh the trade-offs of entering them too often or too rarely.
Reduce device vulnerabilities by using thin or diskless clients, including virtualisation, to centralise data and security controls.
Define usage agreements for employees and vendors covering systems and data, including NDA, transport, monitoring, system use, conflict of interest, and acceptable behavior clauses.
Apply visitor controls such as ingress and egress logs, distinct badges, escorting, and short credential expirations, and avoid common visitor management mistakes.
Consolidate how the security and privacy controls covered work together to protect data, systems, and physical assets.
Apply Gen AI to fraud prevention modeling by comparing usual and Gen AI-assisted approaches across rules-based systems, anomaly detectors, and network algorithms.
Describe the fraud prevention modeling process, the models involved, and the expertise needed to build and judge them.
Prepare data and select features for fraud prevention models.
Design rules-based fraud detection using the usual modeling workflow.
Apply Gen AI to support the design and refinement of rules-based fraud detection.
Build an anomaly detector for fraud prevention using the usual modeling workflow.
Apply Gen AI to support the development and review of fraud anomaly detectors.
Apply network algorithms to fraud prevention using the usual modeling workflow.
Apply Gen AI to support the use and review of network algorithms for fraud prevention.
Consolidate how Gen AI complements the usual approaches to fraud prevention modeling.
Preview how AML models are built and how Gen AI can assist with transaction monitoring, risk scoring, and network models.
Describe the AML modeling process, the models involved, and the expertise needed to build and judge them.
Prepare data and select features for AML models.
Design transaction monitors for AML using the usual modeling workflow.
Apply Gen AI to support the design and refinement of AML transaction monitors.
Build a customer risk scoring model for AML using the usual modeling workflow.
Apply Gen AI to support the development and review of AML risk scoring models.
Apply network models to AML using the usual modeling workflow.
Apply Gen AI to support the use and review of network models for AML.
Consolidate how Gen AI complements the usual approaches to AML modeling.
Understand how generative AI enables modern fraud and implement practical defenses to detect, prevent, and respond to AI-driven attacks across systems and channels.
Preview the foundations of Gen AI and fraud needed to assess AI-enabled fraud risk.
Understand how generative AI creates new content, which models power it, and which systemic risks it introduces.
Explain how fraudsters misrepresent identities, manipulate systems, and exploit human and process weaknesses for financial gain.
Analyze how generative AI enables scalable, realistic, and evasive fraud—and how organizations adapt their defenses.
Consolidate the foundations of Gen AI-enabled fraud and its effect on fraud risk.
Preview the channels through which Gen AI-based fraud attacks are delivered.
Map the main generative media types used in social engineering and understand their creation and detection characteristics.
Recognize how AI-generated text enables scalable, context-aware fraud and how it is distributed and detected.
Understand how generative images support document forgery and synthetic identities, and how visual fraud is mitigated.
Analyze how AI-generated audio enables voice impersonation and vishing, and how organizations defend against it.
Explain how generative video supports high-impact impersonation and deepfake scams, and how these attacks are countered.
Consolidate how different attack mediums and channels are used in Gen AI-based fraud.
Preview the approaches attackers take when using Gen AI to commit fraud.
Understand how generative AI enables the creation of synthetic documents and identities, and how organizations detect and mitigate them.
Explain how generative AI is used to exploit payment workflows and how controls limit unauthorized transfers.
Identify how generative AI amplifies insurance and reimbursement fraud and how large-scale claim abuse is detected.
Recognize how generative AI enables large-scale account compromise and how continuous verification reduces impact.
Consolidate the main Gen AI attack approaches used in fraud.
Preview the techniques used to defend against Gen AI-based fraud.
Evaluate documents using layered forensic, consistency, and AI-based checks to detect generative forgeries.
Detect fraud by identifying deviations from established user behavior across transactions, devices, and interactions.
Strengthen fraud defenses by dynamically escalating authentication requirements based on assessed risk.
Validate identities by combining multiple verification channels to reduce reliance on any single, forgeable signal.
Consolidate the main defense techniques against Gen AI-based fraud.
Preview how fraud protection measures are put into practice in an organization.
Adapt existing fraud defenses to counter the scale, realism, and speed introduced by generative AI attacks.
Use large language models in parallel with traditional detection systems to identify complementary fraud signals and blind spots.
Enhance fraud model outputs with contextual validation, explanation, and prioritization using LLMs.
Prioritize and route generative-AI-enabled threats by risk, impact, and novelty across detection pipelines.
Contain generative-AI-driven attacks, investigate root causes, and reinforce systems to improve future resilience.
Consolidate the steps for implementing protection against Gen AI-based fraud.
Consolidate the course's approach to understanding, defending against, and responding to Gen AI-based fraud.
SECURE YOUR DATA, SECURE YOUR KNOWLEDGE
You may know that payment fraud has risen over time, and unfortunately is not slowing down.
The PCI-DSS, or Payment Card Industry Data Security Standards, are a set of strict standards for any organisation dealing with card data.
They tell you how to store and transmit these data.
However, you'll hardly find a course that both covers the technical knowledge, but also practical applications and examples.
In short, most PCI-DSS courses are either only about the tech, or about the business.
If only you could find a course that combined both...
Well... that's what this course aims to change.
LET ME TELL YOU... EVERYTHING
Some people - including me - love to know what they're getting in a package.
And by this, I mean, EVERYTHING that is in the package.
So, here is a list of everything that this course covers:
You'll learn about the clarification of all terms used in the PCI-DSS, including what is the CDE, what is CHD, SAD, whether an organisation must take an ROC or SAQ, as well as some "general" payment industry terms such as what is an issuing bank and an acquiring bank;
You'll learn about the history of the PCI-DSS since 2004, with several iterations and its own release lifecycle;
You'll learn about the merchant assessment process, based on their classification from Level 1-4, and how both SAQs and ROCs work, as well as the 8 different types of SAQs, and the types of machines/merchants they target, including the SAQ A and SAQ A-EP, the SAQ B and SAQ B-IP, the SAQ C and SAQ C-VT, the SAQ P2PE and SAQ SPoC, and finally, the most general SAQ-D;
You'll learn about the anatomy of a payment process, involving a cardholder and a merchant, from authorisation to authentication, clearing and settlement, and the role of the issuing bak, the acquiring bank and the card company;
You'll learn about an overview of all 12 PCI-DSS requirements, as well as their relationship with the 6 goals;
You'll learn all about Requirement 1 (Have a Firewall), including firewall configurations and standards, documentation on network topology and card data flows, setting up a DMZ, rejecting unsecured traffic, and more;
You'll learn all about Requirement 2 (No Defaults), about removing default passwords/accounts/strings from devices, but also isolating server functionality and removing unnecessary ports/services/apps that may present vulnerabilities;
You'll learn all about Requirement 3 (Protect Stored Data), about using strong encryption to protect cardholder data, as well as having proper data retention policies, data purging, as well as masking plaintext PANs, not storing SAD, and using proper key management and key lifecycle procedures;
You'll learn all about Requirement 4 (Protect Transmitted Data), about using strong encryption when transmitting CHD across public networks such as cellular or satellite, as well as masking plaintext PANs in transit, especially across IM channels;
You'll learn all about Requirement 5 (Prevent Malware), about having an antivirus solution on all commonly affected computers in order to prevent malware, as well as access control policies to prevent disabling AV software;
You'll learn all about Requirement 6 (Develop Securely), about doing vulnerability ranking and timely patch installation for both internal and 3rd-party applications, as well as including security requirements in the SDLC, as well as training developers to protect against common exploits such as code injections, buffer overflows and many others;
You'll learn all about Requirement 7 (Need-to-Know Access), about limiting access to CHD by personnel as much as possible, defining permissions by role, and having a formal mechanism for access control to consolidate this, such as LDAP, AD or ACLs;
You'll learn all about Requirement 8 (Identify Access), about tying each action to a unique user, including forcing unique IDs, automatic logouts on inactivity, lockouts on wrong password attempts, removing inactive accounts, limiting third-party access, forbidding the use of shared IDs, forcing physical security measures to be used only by the intended user, and more;
You'll learn all about Requirement 9 (Restrict Physical Access), about authorising and distinguishing visitors, enforcing access control to rooms with CHD, as well as the proper transport, storage and disposal of physical media containing CHD, with different sensitivity levels;
You'll learn all about Requirement 10 (Monitor Networks), about logging. Having a logging solution that is operating, logging specific events (such as all failed operations, all admin operations, all operations on CHD, etc), logging specific elements in each event (such as the user ID, the operation status, the affected resource, etc), as well as having a single time synchronisation mechanism for all logs, FIM (File Integrity Monitoring) on logs, frequent log review and proper log retention;
You'll learn all about Requirement 11 (Test Regularly), about performing regular scans for Access Points (APs), both authorised and non-authorised ones, as well as regular vulnerability scanning and regular penetration testing (from inside and outside, and multiple layers), as well as having FIM (File Integrity Monitoring) on all critical files, as well as having an IDS/IPS (Intrusion Detection/Prevention System) to prevent attacks;
You'll learn all about Requirement 12 (Have an InfoSec Policy), which covers roles, responsibilities and owners at levels of the organisation, including varied topics such as technology usage policies, employee screening, employee awareness, third-party selection criteria, regular risk and vulnerability assessments, among others;
You'll learn about a review of all 12 requirements and general patterns among them, such as "denying everything" by default, using common sense for certain parameters, enforcing change management on all changes, and always prioritising security (both logical and physical);
MY INVITATION TO YOU
Remember that you always have a 30-day money-back guarantee, so there is no risk for you.
Also, I suggest you make use of the free preview videos to make sure the course really is a fit. I don't want you to waste your money.
If you think this course is a fit and can take your fraud prevention knowledge to the next level... it would be a pleasure to have you as a student.
See you on the other side!