<!doctype html>

<html>



<?php define('BASE_URL', 'https://merchantproinc.com'); ?>



<head>
 <?php

        include("includes/header.php");

        ?>

        

<div class="bannerSub">

  <div class="container">

    <div class="row">

      <div class="col position-relative h-100">          

        <h1>PCI security<br> standards council<br> fact sheets</h1> 

      </div>        

    </div>

  </div>

  <img src="assets/images/PCI-security-standards.jpg" class="w-100" alt="">

</div>



<div class="container sub-page-contr">



  <div class="container for-gap"></div>



  <div class="row">

    <div class="col">

      <!-- my content start -->

      <div class="list-pci">

        <ul>

         <li>



           <a href="https://www.pcisecuritystandards.org/pdfs/pci_lifecycle_for_changes_to_pts.pdf" target="_blank"><h4><i class=" fa fa-file-pdf-o "></i> Lifecycle for changes to the PTS</h4> </a>

           <p> The Payment Card Industry PIN Transaction Security (PTS) requirements are used primarily by ATM and point-of-sale equipment manufacturers to secure cardholder data at the physical point of interaction. Changes to the standard follow a defined 36-month lifecycle with eight stages. The lifecycle ensures a gradual, phased use of new versions of the standard without invalidating current implementations of PTS. It also prevents organizations from becoming noncompliant when changes are published and allows vendors to complete existing product development. Throughout the lifecycle, the Council will continuously evaluate evolving technology and threats, and provide ongoing guidance about these standards.</p>



         </li>







         <li>



           <a href="https://www.pcisecuritystandards.org/pdfs/pci_lifecycle_for_changes_to_dss_and_padss.pdf" target="_blank"><h4><i class=" fa fa-file-pdf-o "></i> 

           Lifecycle for changes to the PCI DSS and PA DSS</h4> </a>



           <p> The Payment Card Industry Data Security Standard (PCI DSS) secures cardholder data that is stored, processed or transmitted by merchants and other organizations. Changes to the PCI standards follow a defined 36-month lifecycle with eight stages. The lifecycle ensures a gradual, phased introduction of new versions of the standard in order to prevent organizations from becoming noncompliant when changes are published. This lifecycle also applies to the Payment Application Data Security Standard (PA-DSS), which covers validation requirements for applications used to process payment cards. During the lifecycle, the Council will continuously evaluate evolving technology and threats, and if necessary, make mid-lifecycle changes to the standards or provide ongoing supplemental guidance about these issues.</p>



         </li>





         <li>

           <a href="https://www.pcisecuritystandards.org/pdfs/skimming_prevention_overview_one_sheet.pdf" target="_blank"><h4><i class=" fa fa-file-pdf-o "></i> 

           Overview of the PCI SSC Skimming Prevention: Best Practices for Merchants</h4> </a>



           <p> Skimming is the unauthorized capture and transfer of payment data to another source. Its purpose is to commit fraud, the threat is serious, and it can hit any merchant's environment. PCI Security Standards currently contain a number of requirements and recommendations to guard against skimming. This “At-a-Glance” provides a snapshot of skimming and introduces areas requiring countermeasures to ensure an appropriate level of security for cardholder data.</p>



         </li>



         <li>

           <a href="https://www.pcisecuritystandards.org/pdfs/pci_dss_wireless_guideline_info_sup.pdf" target="_blank"><h4><i class=" fa fa-file-pdf-o "></i> 

           Overview of the PCI DSS Wireless Guideline</h4> </a>



           <p>The goal of this document is to help organizations understand how PCI DSS applies to wireless environments, how to limit the PCI DSS scope as it pertains to wireless, and provide practical methods and concepts for deployment of secure wireless in payment card transaction environments.</p>



         </li>



         <li>

           <a href="https://www.pcisecuritystandards.org/pdfs/pci_fs_data_storage.pdf" target="_blank"><h4><i class=" fa fa-file-pdf-o "></i> 

           PCI Data Storage Do's and Don'ts</h4> </a>



           <p>Requirement 3 of the Payment Card Industry’s Data Security Standard (PCI DSS) is to "protect stored cardholder data." For merchants who have a legitimate business reason to store cardholder data, it is important to understand what data elements PCI DSS allows them to store and what measures they must take to protect those data.</p>



         </li>



         <li>

           <a href="https://www.pcisecuritystandards.org/pdfs/pcissc_overview.pdf" target="_blank"><h4><i class=" fa fa-file-pdf-o "></i> 

           Payment Card Industry Security Standards Overview</h4> </a>



           <p>PCI security standards are technical and operational requirements set by the Payment Card Industry Security Standards Council to protect cardholder payment data.</p>



         </li>



         <li>

           <a href="https://www.pcisecuritystandards.org/pdfs/pcissc_getting_started_with_pcidss.pdf" target="_blank"><h4><i class=" fa fa-file-pdf-o "></i> 

           Getting Started with PCI Data Security Standard</h4> </a>



           <p>PCI security for merchants and payment card processors is the vital byproduct of applying information security best practices in the Payment Card Industry Data Security Standard (PCI DSS).</p>



         </li>





         <li>

           <a href="https://www.pcisecuritystandards.org/pdfs/pciscc_ten_common_myths.pdf" target="_blank"><h4><i class=" fa fa-file-pdf-o "></i> 

           Ten Common Myths of PCI DSS</h4> </a>



           <p>The Payment Card Industry Data Security Standard (PCI DSS) secures cardholder payment data that is stored, processed or transmitted by merchants and processors.</p>



         </li>







         <li>

           <p> <b>Reports and Blog Resources </b></p>

           <a href="http://www.verizonenterprise.com/resources/reports/rp_2010-data-breach-report_en_xg.pdf" target="_blank"><h4><i class=" fa fa-file-pdf-o "></i> 

           Verizon Business 2010 Data Breach Investigations Report</h4> </a>



           <a href="https://securityblog.verizonenterprise.com/" target="_blank"><h4><i class=" fa fa-file-pdf-o "></i> 

           Verizon Business Security Blog</h4> </a>

         </li>

       </ul>

     </div>

     <!-- my content end -->

   </div>

 </div>





</div>









<?php

    include("includes/footer.php");

    ?>

	

</body>

</html>