Training requirements · PCI DSS

Is security awareness training mandatory under PCI DSS v4.0.1?

Yes, for organisations within PCI DSS scope. Version 4.0.1 requires a formal security awareness programme, training for personnel on hire and at least once every 12 months, content on phishing and social engineering, and a yearly acknowledgement of the security policy. PCI DSS is an industry standard, not a law; payment brands and acquirers require it.

Key facts

Applies to
Entities that store, process or transmit cardholder data or sensitive authentication data, or could affect the security of the cardholder data environment
Current version
PCI DSS v4.0.1; v4.0 was retired on 31 December 2024
Training frequency
On hire and at least once every 12 months
Programme review
At least once every 12 months, and updated for new threats
Mandatory topics
Phishing and related attacks, social engineering, and acceptable use of end-user technologies
Personnel acknowledgement
At least once every 12 months

Checked against the official text on 16 November 2026

Who does the PCI DSS awareness requirement apply to?

The requirement applies to every organisation that PCI DSS applies to: merchants, processors and service providers that store, process or transmit cardholder data or sensitive authentication data, and organisations that could affect the security of the environment where that data lives. A contact centre or BPO that takes card payments or handles refunds for a retailer is in scope on the same footing as the retailer itself.

Within the organisation, the programme must reach all personnel, because its purpose is to make everyone aware of the information security policy and procedures and of their own role in protecting cardholder data. Cashiers, agents, developers, system administrators and managers all fall inside it, each at the depth their access calls for.

PCI DSS is not legislation. It is maintained by the PCI Security Standards Council, and the compliance programmes that require merchants and service providers to meet it are run by the payment brands and by acquirers. How you validate compliance, and which parts of the standard you are assessed against, depends on the route your acquirer or payment brand sets.

What changed for security awareness in PCI DSS v4?

Version 4 added specific content and a review cycle to what had been a general awareness duty. Training must now cover threats and vulnerabilities that could affect the cardholder data environment, naming phishing and related attacks and social engineering, and it must cover acceptable use of end-user technologies under the entity’s own usage policies. The programme itself must be reviewed at least every 12 months and updated when new threats appear. These items were future-dated and became mandatory after 31 March 2025.

Version 4.0.1, published in June 2024, was a limited revision with no new or deleted requirements; it corrected errors and clarified some wording. Version 4.0 was retired at the end of 2024, leaving v4.0.1 as the only active version the Council supports. The standard also states that technical anti-phishing controls and phishing awareness training are separate requirements, and meeting one does not meet the other.

What must PCI DSS security awareness training cover?

The standard sets minimum content and leaves the depth to the entity. A programme that an assessor will accept typically includes the following, using more than one method of communication, as the standard requires:

  • The entity’s information security policy and procedures, and each person’s role in protecting cardholder data
  • Phishing and related attacks, including fake payment or refund requests, credential-harvesting links and malicious attachments
  • Social engineering by phone, chat and in person, such as callers posing as IT support or as a cardholder
  • Acceptable use of end-user technologies: laptops, mobile devices, removable media, email and internet use under the entity’s usage policies
  • Handling card data at the desk: the entity’s rules on writing down, storing and sharing card numbers, clean desks and screen locks
  • How and to whom to report a suspected incident, a tampered payment terminal or a suspicious contact

What will a QSA or internal assessor ask to see?

The testing procedures for this requirement are practical: examine the programme, its content and its records, interview personnel and examine their acknowledgements. Prepare the following before an assessment:

  • The documented security awareness programme and its scope
  • Evidence of the latest review of the programme, with the date and the changes made for new threats
  • Training content showing phishing, social engineering and acceptable-use topics
  • Records showing each person trained on hire and within the last 12 months
  • Signed or electronic acknowledgements that each person has read and understood the security policy and procedures in the last 12 months
  • Evidence of more than one communication method, such as courses, briefings, posters, email reminders or phishing simulations

Should PCI DSS awareness training differ by role?

Yes. The minimum topics apply to everyone, but the standard asks that people understand their own role in protecting cardholder data, and that role varies sharply across an organisation. One course for all, with no role depth, tends to leave the highest-risk people under-trained.

A practical split has three layers. Every person gets the common awareness base and the policy acknowledgement. People who touch card data directly, such as payment agents, refund teams and store staff, get scenario training on fraudulent requests, recorded calls, screen sharing and terminal tampering. People who run or change in-scope systems, such as developers and administrators, get the security awareness content plus technical training on the controls they operate.

Managers need one more element: what the programme requires of them. They sign off reviews, chase overdue training and decide what happens when someone ignores the rules, and an assessor interviewing them will expect clear answers.

How do you run a PCI DSS awareness programme that meets v4.0.1?

The cycle is annual, but the work is easier when training is tied to hiring and to the policy review rather than run as a single campaign.

  1. Define who is in scopeList the people who handle card data or can affect the cardholder data environment, including contractors and outsourced agents.
  2. Write the content planMap each mandatory topic to a course, briefing or reminder, and record which methods of communication you use.
  3. Train on hireMake awareness training and policy acknowledgement part of onboarding, before access to card data is granted.
  4. Repeat every 12 monthsSchedule refresher training and re-acknowledgement on a fixed cycle, and chase anyone overdue.
  5. Review the programmeAt least once every 12 months, review the content against current threats and incidents, update it and record the review.

Which PCI DSS awareness gaps should you check for before an assessment?

The awareness requirement is short and specific, so gaps tend to show up as missing evidence rather than missing intent. Work through these checks with the person who will face the assessor.

  • Training given at hire is recorded, not assumed because the person attended induction
  • No one in scope has gone more than 12 months since their last awareness training
  • Policy acknowledgements are current for every person, not only for new joiners
  • The training content visibly covers phishing and related attacks, social engineering and acceptable use of end-user technologies
  • The programme review is dated, and the content changed when new threats appeared
  • There is more than one communication method, and you can show each one
  • Outsourced agents and contractors are either in your programme or covered by evidence from their employer

How should a BPO or contact centre handle PCI DSS awareness?

A service provider that handles card data for clients usually faces the requirement twice: in its own assessment and in each client’s due diligence. One programme, run well, should answer both.

Agent turnover makes training on hire the pressure point. Build the awareness course and policy acknowledgement into the first days of onboarding, before a new agent takes live calls or chats with card data, and keep a per-agent record that a client can sample. Team leads and quality staff should be trained to recognise and escalate social engineering attempts, because they are the people agents turn to when a caller pushes back.

How does Sterling Academy help you meet the awareness requirement?

Sterling Academy’s PCI DSS and security awareness courses are written to PCI DSS v4.0.1 by industry experts, domain specialist trainers and globally renowned auditors with 30+ years in ISO and GRC. They are online and self-paced, but they follow the same content and format as Sterling’s classroom training, drawing on 20+ years and 8,100+ client engagements in 60+ countries.

Every learner completes an assessment designed on the principles of ISO/IEC 17024:2026 and receives a verifiable certificate with a QR code, which gives an assessor dated, per-person evidence of training. Learners have 12 months’ access, so the same course can carry them to the next annual refresher. Combine a course with your own policy acknowledgement and phishing exercises to cover the multiple-methods expectation.

Frequently asked questions

Questions about PCI DSS training

Ask a Sterling consultant

How often is PCI DSS security awareness training required?

On hire and at least once every 12 months. Personnel must also acknowledge, at least once every 12 months, that they have read and understood the security policy and procedures.

Is phishing training mandatory under PCI DSS v4.0.1?

Yes. Training must include awareness of threats and vulnerabilities that could affect the cardholder data environment, including phishing and related attacks and social engineering.

Do anti-phishing email filters meet the training requirement?

No. The standard treats technical anti-phishing controls and awareness training as separate requirements, and meeting one does not meet the other.

Is PCI DSS a legal requirement?

PCI DSS is an industry standard, not a law. Payment brands and acquirers run the compliance programmes that require merchants and service providers to meet it.

Does the training have to be classroom based?

No. The standard requires more than one method of communication, but it does not prescribe classroom delivery. Online courses, briefings, reminders and simulations can be combined.

Do outsourced agents need PCI DSS awareness training?

If they handle card data for you or can affect the security of your cardholder data environment, they should be inside your programme, or you should obtain evidence that their employer trains them.

Can the yearly acknowledgement be electronic?

The standard requires personnel to acknowledge that they have read and understood the security policy and procedures; it does not require a paper signature. An electronic acknowledgement with a date and the policy version is a clean record.

Does the awareness programme itself need reviewing?

Yes. It must be reviewed at least once every 12 months and updated as needed to address new threats and vulnerabilities, or changes in what personnel are told about protecting cardholder data.

Training your team?

Plan the training
with a Sterling consultant.

Discuss your training needs