<?xml version="1.0" encoding="UTF-8"?>
<mods xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.loc.gov/mods/v3" version="3.1" xsi:schemaLocation="http://www.loc.gov/mods/v3 http://www.loc.gov/standards/mods/v3/mods-3-1.xsd">
  <titleInfo>
    <title>PCI compliance</title>
    <subTitle>understand and implement effective PCI data security standard compliance</subTitle>
  </titleInfo>
  <name type="personal">
    <namePart>Williams, Branden R.</namePart>
  </name>
  <name type="personal">
    <namePart>Chuvakin, Anton.</namePart>
  </name>
  <typeOfResource>text</typeOfResource>
  <genre authority="marc">bibliography</genre>
  <originInfo>
    <place>
      <placeTerm type="code" authority="marccountry">mau</placeTerm>
    </place>
    <dateIssued encoding="marc">2012</dateIssued>
    <copyrightDate encoding="marc">2012</copyrightDate>
    <edition>Third edition.</edition>
    <issuance>monographic</issuance>
  </originInfo>
  <language>
    <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
  </language>
  <physicalDescription>
    <form authority="marcform">print</form>
    <extent>xviii, 337 pages : illustrations ; 24 cm</extent>
  </physicalDescription>
  <abstract>"There are a variety of regulatory mandates and industry guidelines that impact information security, but none have the virtually universal scope of PCI DSS (Payment Card Industry Data Security Standard). Every business around the world that accepts, processes, transmits, or stores credit card data is subject to compliance with PCI DSS"--</abstract>
  <tableOfContents>About PCI and this book -- Introduction to fraud, data theft, and related regulatory mandates -- Why is PCI here? -- Determining and reducing the PCI scope -- Building and maintaining a secure network -- Strong access controls -- Protecting cardholder data -- Using wireless networking -- Vulnerability management -- Logging events and monitoring the cardholder data environment -- PCI for the small business -- Managing a PCI DSS project to achieve compliance -- Don't fear the assessor -- The art of compensating control -- You're compliant, now what? -- Emerging technology and alternative payment schemes -- Myths and misconceptions of PCI DSS.</tableOfContents>
  <note type="statement of responsibility">Branden R. Williams, Anton Chuvakin.</note>
  <note>Authorship has changed from editon to edition.</note>
  <note>Includes bibliographical references and index.</note>
  <subject authority="lcsh">
    <topic>Data protection</topic>
    <topic>Standards</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Computer networks</topic>
    <topic>Security measures</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Credit cards</topic>
    <topic>Security measures</topic>
  </subject>
  <subject authority="lcsh">
    <topic>Liability for credit information</topic>
  </subject>
  <classification authority="lcc">QA76.9.A25 P414 2012</classification>
  <classification authority="ddc" edition="23">008.8 PCC</classification>
  <relatedItem type="otherVersion" displayLabel="Revision of:">
    <titleInfo>
      <title>PCI complaince / Tony Bradley, technical editor</title>
    </titleInfo>
    <originInfo>
      <publisher>Burlington, Mass. : Syngress, c2007</publisher>
    </originInfo>
  </relatedItem>
  <relatedItem type="otherVersion" displayLabel="Revision of:">
    <titleInfo>
      <title>PCI compliance / Anton A. Chuvakin, Branden R. Williams ; technical editor, Ward Spangenberg</title>
    </titleInfo>
    <originInfo>
      <publisher>Amsterdam ; Boston : Elsevier, 2010</publisher>
    </originInfo>
  </relatedItem>
  <identifier type="isbn">9781597499484 (pbk.)</identifier>
  <identifier type="isbn">159749948X (pbk.)</identifier>
  <identifier type="lccn">2012023454</identifier>
  <recordInfo>
    <recordContentSource authority="marcorg">DLC</recordContentSource>
    <recordCreationDate encoding="marc">120807</recordCreationDate>
    <recordChangeDate encoding="iso8601">20150408114201.0</recordChangeDate>
    <recordIdentifier source="OSt">17420548</recordIdentifier>
    <languageOfCataloging>
      <languageTerm authority="iso639-2b" type="code">eng</languageTerm>
    </languageOfCataloging>
  </recordInfo>
</mods>
