Skip to main content

PCI DSS


With over 257 billion card transactions for goods and services worldwide, the payment cards (credit or debit cards) serve as one of the most preferable modes of payment. In fact, many surveys show that over 70% people prefer card payments over cash.


PCI DSS
Payment Card - PCI DSS

While alternate modes of payment are catching up (such as IBAN in Europe, UPI in India etc.), the card industry will continue to thrive for several years, on account of its worldwide acceptance, transaction success rate and ease of use.


Of course, like all other electronic media, security is of paramount importance when it comes to payment cards. While there is a legal structure for protecting the interests of the card users, the underlying security (both infrastructure and application) is governed by PCI DSS compliance.


So what is PCI DSS?

It stands for Payment Cards Industry - Data Security Standards. Five different companies Visa, MasterCard, American Express, Discover and JCB International - each of them who already had their individual security policies - aligned together to form PCI DSS compliance, with the aim:


" To protect their interests by making merchants (e-commerce websites etc.) comply with minimum (acceptable) level of security while storing, processing and transmitting card holder data."


There have been several revisions to these standards and the latest version 3.2.1 was ratified and released in May 2018.


The complete PCI DSS checklist can be found here.


PCI Stake Holders

Payment Brands - The financial institutions viz. Visa, MasterCard, American Express, Discover and JCB who are responsible for advancing and promoting the PCI DSS

Acquirer - Bank or a financial institution that maintains the account of the merchant and which processes transactions.

Approved Scanning Vendor (ASV) - Company approved by PCI SSC to conduct external vulnerability scanning services. The list of ASVs can be found here:

Merchant - This is the e-commerce website that accepts card payments


Workflow:

  1. The customer purchases goods or avails services from an e-commerce website. Here, the owner of the e-commerce website is the "Merchant"
  2. The customer uses his credit / debit card to pay for the goods or services. The credit / debit card is issued to the customer by an "Issuing Bank". To simplify, if you used ABN AMRO's credit card to pay for the goods (i.e. if the card reads ABN AMRO), the "Issuing Bank" here, will be ABN AMRO.
  3. The transaction details are immediately processed by the merchant's Acquirer. The acquirer sends the transaction details to the Credit Card Network (Visa, MasterCard etc.)
  4. The credit card network clears the payment and requests payment authorization from the issuing bank. The authorization request includes the following:
    • Payment Amount
    • Credit card Number
    • Card Expiration date
    • Billing address - for Address Verification System (AVS) validation
    • Card security code such as CVV
  5. The issuing Bank checks the above authorization, checks for the account balance and clears the transaction.

Next we will check the PCI DSS compliance checklist.


Comments

Popular posts from this blog

Checkpoint - Exporting Objects in CSV format

Be it a Network Operations Manager, Security Architect or a Security Auditor, the people up the hierarchy always harangue the Security Engineers to compile the list of firewall objects or rules or policies or the traffic statistics and so on.. This can turn out to be quite hectic especially if there are no built in features to systematically provide the output in a "layman-readable" format. Come, Checkpoint's "Object Explorer..."  which not only provides the output in the "layman-readable" format, but also provides in-built filtering mechanisms, thereby ensuring that the Security Engineer doesn't have to rely on Google for building his scarce Microsoft Excel data filtering skills. The following screenshots will show how easy it is, with Checkpoint R80.10 to generate the firewall configuration inventory. On the SmartConsole Unified Portal, navigate to Menu >> Open Object Explorer... Select the Categories you wish to see in your output: Click o

Tejas Jain - GCP Constraints & Random Facts

1.  Google Cloud Interconnect Security Cloud Interconnect does not encrypt the connection between your on-premises network and Google's network. Cloud VPN cannot be used with Dedicated Interconnect For additional security, use application-level encryption or your own VPN 2. While using Cloud CDN, the default time-to-live (TTL) for content caching is 3600 seconds = 60 mins 3. Cloud NAT sends only the translation logs and error logs to Cloud Logging service. 4. GCP Dedicated Interconnect - On Premises network device requirements:     10-Gbps circuits, single mode fiber or 100-Gbps circuits, single mode fiber     IPv4 link local addressing     LACP, even if you are using single circuit     EBGP-4 with multi-hop     802.1Q VLANs 5. While using Cloud VPN, the recommended MTU to be configured on the peer VPN  gateway = 1460 bytes 6. Each instance must have at least one network interface. The maximum number of network instances per instance is 8, depending on the instance's machine

MITRE ATT&CK - Kerberos Vulnerabilities and Security

From the previous post, the summary of Kerberos authentication process is as below: For the initial authentication, the user’s client machine sends a request to the KDC  Authentication Service (AS) . The request includes details like the user’s username, and the date and time. All information except the username is encrypted using the hash of the user’s password. The KDC AS uses the username to look up its copy of the user’s password hash and uses it to decrypt the rest of the request. If the decryption is successful, that means the client used the correct password hash and the user has successfully authenticated. Once the user is authenticated, the KDC AS sends the user’s client a  ticket granting ticket   (TGT) . The TGT includes a unique session key and a timestamp that specifies how long that session is valid (normally 8 or 10 hours). Importantly, before sending the TGT, the KDC encrypts it using the password hash for a special account, the  KRBTGT account.  That password hash is s