Neurobyte Technologies

PCI DSS Certification in Kenya: What Compliance Really Requires

PCI DSS certification in Kenya explained: who must comply, PCI DSS v4.0.1, SAQ vs QSA report on compliance, scans, penetration testing and reducing scope.

· Reviewed by Danstan Akwiri, CISSP, CISA

The Payment Card Industry Data Security Standard (PCI DSS) applies to any organisation that stores, processes or transmits payment card data, or that can affect the security of that data. In Kenya that includes banks and card issuers, payment service providers and aggregators, merchants that accept cards online or in store, and the technology and hosting companies that serve them. If your business touches card data, your acquiring bank or the card brands will expect you to show you meet the standard.

Searches for "PCI DSS certification in Kenya" assume there is a certificate to obtain. There is not, in the way there is for ISO 27001. This guide explains what compliance actually means, how it is validated, what changed with version 4, and how to reduce the amount of your business the standard applies to.

There is no PCI DSS certificate

PCI DSS is maintained by the PCI Security Standards Council, which was founded by the major card brands. The Council publishes the standard but does not certify organisations. What exists instead is validation: evidence, in a format the card brands and your acquiring bank accept, that you meet the requirements for the environment that handles card data.

That evidence takes one of two main forms. Smaller merchants and some service providers complete a Self-Assessment Questionnaire (SAQ) and sign an Attestation of Compliance. Larger organisations, and anyone their acquirer or the card brands require it of, are assessed by a Qualified Security Assessor (QSA), who produces a Report on Compliance (ROC) and an Attestation of Compliance. Which one applies to you depends on your transaction volumes and role, and is confirmed by your acquiring bank or the card brands, not chosen freely.

Version 4.0.1 is now the only standard

PCI DSS version 3.2.1 was retired on 31 March 2024 and version 4.0 on 31 December 2024. Since 1 January 2025, version 4.0.1 is the only active version. It is a limited revision of 4.0 that clarified wording without adding or removing requirements.

The bigger change came from version 4.0 itself. It introduced new requirements, most of which were future-dated and became mandatory on 31 March 2025. They include a targeted risk analysis to justify how often certain controls run, stronger authentication with multi-factor authentication for all access into the cardholder data environment, controls against skimming scripts on payment pages, and more rigorous scoping. An organisation that last validated under 3.2.1 should expect real gaps.

What the twelve requirements cover

The standard is organised into twelve requirements: secure network controls, secure configurations, protecting stored account data, encrypting card data in transit, protecting systems from malicious software, developing and maintaining secure systems and software, restricting access by business need to know, identifying users and authenticating access, restricting physical access, logging and monitoring all access, testing security regularly, and supporting security with organisational policies and programmes.

Two testing obligations surprise many organisations. External vulnerability scans must be run by an Approved Scanning Vendor (ASV) at least quarterly and passed. Penetration testing, internal and external, is required at least annually and after significant changes, and where segmentation is used to reduce scope, the segmentation controls themselves must be tested. These are recurring obligations, not a one-off project.

Reduce scope before you do anything else

The single most effective way to make PCI DSS manageable is to shrink the cardholder data environment. Every system that stores, processes or transmits card data, and every system connected to those, is in scope. If card data never touches your servers, much of the standard stops applying to you.

For online merchants that usually means using a payment provider's hosted payment page or iframe so card details go straight to the provider, which can move you to the shortest questionnaire. In store, it means validated point-to-point encryption terminals. Tokenisation lets systems use a token instead of the card number. Network segmentation isolates what remains. Mobile money such as M-Pesa does not involve card data and is outside PCI DSS, although it carries its own security and data protection obligations.

Where Neurobyte fits

We are not a QSA or an Approved Scanning Vendor, and we will not issue a Report on Compliance or a passing ASV scan. Keeping implementation separate from assessment is what gives the validation its value, the same principle that applies to ISO 27001.

What we do is the work in between: scoping and segmentation design, a gap assessment against version 4.0.1, remediation of technical findings, secure development of payment pages and applications, the internal and external penetration tests and segmentation tests the standard requires, policies and procedures, and preparation of the evidence your QSA or your questionnaire needs.

Key takeaways

  • PCI DSS is validated, not certified: you produce an SAQ or a QSA Report on Compliance, plus an Attestation of Compliance.
  • Version 4.0.1 has been the only active version since 1 January 2025, and the future-dated v4 requirements have applied since 31 March 2025.
  • Your acquiring bank or the card brands decide which validation applies to you.
  • Quarterly ASV scans and at least annual penetration testing are recurring obligations.
  • Reducing scope with hosted payment pages, tokenisation and segmentation is the cheapest control there is.

Frequently asked questions

Is there such a thing as PCI DSS certification in Kenya?

Not as a certificate issued to your organisation. Compliance is validated through a Self-Assessment Questionnaire or a Report on Compliance by a Qualified Security Assessor, each with an Attestation of Compliance. Your acquiring bank or the card brands tell you which applies.

Who needs to comply with PCI DSS in Kenya?

Any organisation that stores, processes or transmits payment card data, or can affect its security: banks, payment service providers, merchants accepting cards, and service providers such as hosting and software companies that handle card data for them.

Does M-Pesa fall under PCI DSS?

No. PCI DSS covers payment card data. M-Pesa transactions do not involve card numbers, so they are outside its scope, although they still carry security, data protection and fraud risks that must be managed.

How often is penetration testing required for PCI DSS?

Internal and external penetration testing is required at least once a year and after significant changes, and segmentation controls used to reduce scope must also be tested. External vulnerability scans by an Approved Scanning Vendor are required at least quarterly.

What is the difference between PCI DSS and ISO 27001?

ISO 27001 is a certifiable management system covering all of an organisation's information risks. PCI DSS is a prescriptive set of controls for card data specifically. They overlap and support each other, but one does not replace the other.

Can Neurobyte make us PCI DSS compliant?

We can do most of the work: scoping, gap assessment, remediation, secure development, the required penetration and segmentation testing, and evidence preparation. Validation itself comes from a QSA or your own questionnaire, and scans from an Approved Scanning Vendor.