Welcome Guest. | Log In | Register | Membership Benefits

New Tokenization White Paper Answers Merchant Questions On PCI DSS Guidelines And Scope Reduction

Paper provides practical guidance to merchants on how to use tokenization to reduce scope

Dec 22, 2011 | 12:08 PM | 


ATLANTA — December 16, 2011 — Liaison Technologies, a global provider of secure cloud-based integration and data management services and solutions, is offering a free download of a new white paper from Securosis that answers questions on tokenization left unaddressed by the PCI Council’s “Information Supplement: PCI DSS Tokenization Guidelines” released earlier this year. Co-sponsored by Liaison and written by Securosis Analyst & CTO Adrian Lane, the new paper, titled “Tokenization Guidance: How to Reduce PCI Compliance Costs,” explains exactly how to implement tokenization to meet Payment Card Industry Data Security Standards (PCI DSS), reduce scope and lower compliance costs.

The paper is the product of hundreds of hours of research and interviews with nearly a hundred merchants, payment processors, tokenization vendors and qualified security assessors (QSAs). It provides answers to the most commonly asked questions on tokenization readers have after reviewing the PCI Council’s tokenization guidelines. Foremost among these questions: “What falls out of scope?” and “What are the audit guidelines?,” both of which the Securosis paper answers in full.

“Tokenization is highly effective for lowering both risk and the cost of PCI compliance through scope reduction, as evidenced by forward-thinking retailers that have already reaped the benefits of this relatively new data security model,” said Christopher Hale, VP Product Marketing at Liaison. “The new guide from Securosis succinctly spells out for merchants the ‘whys’ and ‘hows’ of tokenization in no-nonsense language. We encourage merchants, auditors and QSAs to download it today to clearly understand what steps they should take to start reaping the unique benefits of tokenization, as well.”

In the white paper, the author draws on his extensive research to provide sound and practical guidance to merchants on how to use tokenization to reduce scope. He also offers advice to both internal auditors going through a self-assessment questionnaire, and to external auditors. The paper includes a comprehensive tokenization audit checklist.

In April 2009, Liaison Technologies introduced Liaison Protect™ Token Manager, the industry’s first tokenization solution to combine universal Format Preserving TokenizationTM, strong encryption and unified key management in one platform-agnostic package. Liaison Protect™ Tokenization as a Service (TaaS), the first cloud-based tokenization service for national and multi-national companies that want to protect Personally Identifiable Information (PII) and Electronic Health Records (EHR), was introduced in February 2011.

To download “Tokenization Guidance: How to Reduce PCI Compliance Costs,” go tohttp://liaison.com/resource-center/analyst-reports/tokenization-guidance-report.

To learn more about Liaison’s on-premise and cloud-based tokenization solutions, visit http://liaison.com/solutions/data-security.

About Liaison Technologies

Liaison Technologies is a global integration and data management company providing unique and high-value solutions to securely move, transform and manage business information on-premise or in the cloud. With a comprehensive array of business-to-business and application-to-application integration and data transformation services, Liaison's practitioners implement data management infrastructures adapted to specific business requirements. Headquartered in Atlanta, Liaison has offices in the Netherlands, Finland, Sweden and the United Kingdom. For more information, visit www.liaison.com.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Compliance Reports

report How To Boost Security Via FFIEC Compliance
With just a smartphone, users can conduct nearly all their banking business at any time of the day or night. However, all this flexibility and convenience opens up new avenues for fraud and cybercrime. Guidelines laid out by the FFIEC several years ago predate many of the capabilities-and vulnerabilities-that are in place today. In this report, we examine the latest guidelines and provide advice on how you can extend the work done to comply with FFIEC guidelines to strengthen your organization's overall security posture and keep customers and their data safe.

report Keeping Compliance In Check
Configuration mistakes, access control gaffes, poor documentation--it doesn?t take much for a compliance audit to go all wrong. In this special retrospective of recent news coverage, Dark Reading takes a look at the costs, common missteps and best practices for compliance, as well as the day the Internet nearly went dark due to the threat of new regulations.

report FISMA Lifts All Compliance Boats
FISMA may not be on your radar now, but it likely will be at some point. Geared specifically toward the federal government and its affiliate agencies and third parties, FISMA is a very specific set of requirements aimed at establishing and maintaining at least a baseline level of computer and network security. FISMA requires unique categorization and classification of information assets, not to mention a boatload of documentation to prove compliance. But once your organization achieves FISMA compliance, it will likely be compliant with just about every security mandate out there.

Other reports from the Compliance Tech Center:

Related Content

Log Management in 2012 and Beyond
2012 brings interesting changes to the log management world. Now, more than ever, it is critical to understand the impact to your log infrastructure and the solutions that will better prepare you to manage your security posture.

SANS Log Management Survey Report
Organizations are increasingly dependent on log management to support core business functions, including cost management, service level and line-of-business application monitoring, as well as traditional IT- and security-focused activities.

Cut the Time and Effort of Troubleshooting and Reporting
Organizations generate millions of logs a day and struggle with centralized collection, storage and analysis of those logs. ArcSight Logger is a universal log management solution that unifies searching, reporting, alerting and analysis across any type of IT data. It consolidates silos of logs into a single indexed repository for fast detection and mitigation of operational issues.

Get Turnkey and Automated PCI Compliance
PCI compliance monitoring is seamless with the self-contained ArcSight PCI Logger solution for log collection, storage and analysis. No database administration expertise is required and a web-based interface simplifies deployment and ongoing management.

Swiss Bank Meets Compliance Requirements and Protects Customer Data
Due to long-term data retention requirements, Swiss bank EFG needed a cost-effective way to collect, secure and store audit-quality log data in an easily accessible log repository. ArcSight Logger helps EFG meet key requirements of Switzerland?s banking laws fast and cost-effectively.




Featured Webcasts
Featured Whitepapers
Featured Reports