Hi {{ session.user.profile.firstName }}

Internal Tokenization: A Strategy to Reduce Risks & Lock-in

Manage webcast
Brandon Dunlap, John Kindervag (Forrester), Blake Dournaee (Intel), and Ulf Mattsson (Protegrity).
This session will focus on the value of internal tokenization in reducing scope and potential audit costs at the datacenter, with a specific focus on post-payment applications, databases, loyalty tracking systems, data warehousing, and business applications. Internal tokenization contrasts with external tokenization, which involves third-parties, brands and additional vendors. Instead, internal tokenization allows enterprises to own and control their own tokens, avoiding migration issues and increasing choice. The presentation will focus on general concepts around internal tokenization, including specific examples of internal tokenization seen in different datacenter applications.

· Learn the difference between external and internal tokenization.
· Learn how to address more than 200 PCI DSS compliance requirements with a single solution.
· Maintain control over your own tokens and avoid payment processor lock-in.
· Tokenize customers’ credit card data to reduce PCI scope and risk
· Understand the controls and protection around the secure vault
· Maintain auditable security policies in a single, hardened form-factor, allowing for future review and change control.
May 12 2011
54 mins
Internal Tokenization: A Strategy to Reduce Risks & Lock-in
More from this community:

IT Governance, Risk and Compliance

  • Date
  • Rating
  • Views

Embed in website or blog

Successfully added emails: 0
Remove all
  • Title: Internal Tokenization: A Strategy to Reduce Risks & Lock-in
  • Live at: May 12 2011 3:00 pm
  • Presented by: Brandon Dunlap, John Kindervag (Forrester), Blake Dournaee (Intel), and Ulf Mattsson (Protegrity).
  • From:
Your email has been sent.
or close
You must be logged in to email this