Course Dashboard

-

Explain how API keys and short-lived tokens are used to authenticate payment API requests, and describe how each should be stored Apply the principle of least privilege to the components of a POS integration Identify common authentication vulnerabilities in payment integrations and describe how to prevent them

-

Explain how TLS protects data in transit between POS components and how to verify it is configured correctly Describe what point-to-point encryption does and why it removes card data from your integration's scope Explain how tokenization works and why a card token is safe to store where a card number is not

-

Identify the main attack vectors targeting POS systems: skimming, man-in-the-middle, injection, and insider threat Describe how each attack vector exploits a specific weakness in the POS architecture from Course 2 Explain why mapping the attack surface is the first step in securing any integration

-

Describe the PCI-DSS requirements most relevant to a developer building a POS integration in Kenya Identify the regulatory requirements from the Central Bank of Kenya that apply to payment system operators Describe the immediate steps to take when a POS security breach is suspected