Sunday, November 14, 2010

HTTPS

“Going forward in 2011,” he says, “we are concentrating on some of the other technologies that will be a growing part of the payment-card industry, including point-to-point encryption, mobile-pay systems, and payment cards that have integrated chips.
In my previous blog, I talked about how unsafe it may be to provide personal information on the internet. But now, it is safer depending on what web site you go to. You want to look for “https” in the website. This is the use of a Secure Socket Layer or a Transport Layer Security. It was developed by Netscape to protect people from those people who like to steal personal information by “eavesdropping” on a person’s transactions that requires personal information be provided.

It has become a requirement for merchants who accept credit cards,
 online or offline, no matter how big or small their business is, to comply with the PCI Data Security standards. The reason being that there is nothing more important than keeping the customer’s information  private, this mostly applies to keeping the payment data secure. However, the compliance requirements may vary a little bit based on the size of the
 business. The PCI Security Standards Council was formed in 2006 by MasterCard, Visa, and other networks to manage the evolution of the payment-card industry.
In 2011, things will change a little bit when it comes to the use of credit and debit cards. Restaurants and other businesses who capture and store the customer’s credit and debit card data in their system will be required to meet the updated security standards. Unfortunately the update information is not provided yet. It will be discussed on November 16, 2010 (Tuesday). The latest standards were developed in response to thousands of comments from merchants, banks, processors, and others, and after a pair of community meetings in the U.S. and Europe.
If you are interested in learning more, visit:

“Today, if you are not PCI-compliant, you are considered to be backward”

Until Next week,
Elizabeth

This blog is prepared by a paralegal student as a class project, without compensation. The content of this blog contains my opinion, and is offered for personal interest without warranty of any kind. Comments posted by others on this blog are the responsibility of the posters of those messages. The reader is solely responsible for verifying the content of this blog and any linked information. Content, sources, information, and links will most likely change over time. The content of this blog may not be construed as legal, medical, business or personal advice 

One of the biggest things that merchants, including restaurants,
need to understand is where the cardholder data is on their
network.”

No comments:

Post a Comment