PCI-DSS Compliance or an Insurance for the Card Companies

Is PCI-DSS enough to ensure security of personnel data. Is it the minimum required to protect user information. But the way the standard has been prescribed, it looks more like a system designed to transfer the incidence from the card issuing organization to the organization handling information for the card issuers.

If the controls are adequate, why are there breaches. Is the system designed to protect the end user sufficient and complete enough to warrant a certification. What does the certification achieve. If you look at the issues in hand, it is clear that the problem is not with the organization handling the data but the protection afforded by such systems to personnel information.

Is it not that the card industry to protect itself have an publicly available standard that has gone through peer reviews and public scrutiny imposed on organizations which process credit/debit card information inadequate?

The balance between what is prescribed in the standard and what is required to achieve a level of security commensurate with the sensitivity of the data in mind, looks more designed to transfer the incidence of breach to the online vendor rather than the card companies. By doing this the card companies can mandate and prescribe a set of standards and certify them " as ready to process personnel information" but the onus of actually protecting the data is with the online trader or shop.

This is not to belittle the standard, but to ensure that a standard is more complete and instead of pushing the incidence and address the security question in earnest

Comments

Malware Damage - It is real and you need to be ready ...

Malware, short for "malicious software," is any software intentionally designed to cause harm to computer systems, networks, or devices. Malware can take many forms, including viruses, trojan horses, worms, ransomware, spyware, and adware, among others. The dangers of malware are numerous, and it is crucial to protect yourself from malware to avoid serious consequences, such as: Data theft: Malware can be designed to steal personal information, such as bank account details, social security numbers, and login credentials. Once this information is stolen, it can be used for identity theft, financial fraud, and other malicious activities. System damage: Some malware can damage your computer system, causing it to crash or malfunction. This can result in lost data, system downtime, and costly repairs. Financial loss: Malware can also be used to extort money from victims. For example, ransomware can lock down a victim's computer and demand payment in exchange for the decrypti...

CIO Questions answered - Your comments welcome - The reflections of the inner self

Briefly describe the typical size and organization of an IT team that you have managed. Include the division of responsibilities, how you track progress, etc. My experience ranges from me working independently, mainly to maintain my independence when I perform audits to managing a team of more than 25 - 100 consultants in various roles. I have handled multiple projects simultaneously where we have multiple consultants (typically from five to ten) working on multiple projects. We have used a set of tools to specifically monitor progress as well as the milestones. The projects involved were simple roll out of products (Microsoft Active Directory Domain Builds, Log Consolidation, Vulnerability Management) in line with product specifications to complex integration of systems that involves building multiple SoA interfaces for healthcare applications. For a successful project there needs to be proper delegation, personally I believe a person can deliver if he is not micromanaged, identifyi...

A Roadmap to move from Cloud to In premise - The reverse migration -- Is Cloudflation at myth?

Cloudflation as a term is being used and talks on the spiralling cost of cloud bills for an organization. The easily available and provisioning options leads to workloads that run for no reasons, orphaned accounts and a gamut of costs that are accrued by multiple departments without much of an oversight. There is a trend to reduce the workloads and have a semblance of order. It is imperative that we have plans that helps to reverse the migration to cloud and bring back some of the workloads that might work cheaper to run local. Is there a roadmap to achieve this goal? A few pointers in this direction A roadmap for moving from the cloud to in-premise computing should include the following steps: Assess current workloads: Assess the current workloads that are running on the cloud and determine which workloads would be most suitable for in-premise computing. Identify in-premise infrastructure: Identify the in-premise infrastructure that will be needed to run the identified workloads....

Aardvarks to Zorillas - Anything goes

Search This Blog