<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Information Defense &#187; PCI Compliance</title>
	<atom:link href="http://www.cybersecurityinformation.com/tag/pci-compliance/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cybersecurityinformation.com</link>
	<description>Cyber Security and Risk Management Blog</description>
	<lastBuildDate>Fri, 27 Aug 2010 13:53:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Managing Your PCI Audit (Part 2)</title>
		<link>http://www.cybersecurityinformation.com/2009/11/09/pci-audit-compliance-qsa-visit-part-2/</link>
		<comments>http://www.cybersecurityinformation.com/2009/11/09/pci-audit-compliance-qsa-visit-part-2/#comments</comments>
		<pubDate>Mon, 09 Nov 2009 11:15:35 +0000</pubDate>
		<dc:creator>Information Defense Corporation</dc:creator>
				<category><![CDATA[IT Security Technology News]]></category>
		<category><![CDATA[Information Security News]]></category>
		<category><![CDATA[Risk Management News]]></category>
		<category><![CDATA[Managing Audits]]></category>
		<category><![CDATA[PCI Compliance]]></category>

		<guid isPermaLink="false">http://www.cybersecurityinformation.com/?p=606</guid>
		<description><![CDATA[Welcome back to our Managing Your PCI Audit &#38; Compliance Blog! By Michael Nelson – PCI Practice Manager See here for Managing your PCI Audit &#38; Compliance blog part 1 By now your organization has chosen a Qualified Security Assessor (QSA) who will be performing PCI compliance assessments, but now when do you schedule the [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Welcome back to our Managing Your PCI Audit &amp; Compliance Blog!</strong> By Michael Nelson – PCI Practice Manager</p>
<p>See here for <a href="http://www.cybersecurityinformation.com/2009/09/22/managing-your-pci-audit-part-1/" target="_self">Managing your PCI Audit &amp; Compliance blog part 1</a></p>
<p>By now your organization has chosen a Qualified Security Assessor (QSA) who will be performing PCI compliance assessments, but now when do you schedule the on site visit for the QSA? The answer is simple; once the organization is prepared. As discussed prior in Managing Your PCI Audit (Part 1), without appropriate preparation the PCI audit process can rapidly deteriorate.</p>
<p>Now this may seem shocking, but it is not unusual for some very large organizations, and smaller ones too, to not understand or have documented all of the ways in which the company accepts and processes credit card information.  For the purpose of this blog lets assume your company does know and has documented comprehensive credit card information flows throughout the network.  We will detail these requirements in a later blog.</p>
<p>From the large organization and data center to the mid level business, assigning the key participants for the PCI audit is crucial and must occur before scheduling the onsite review with your QSA.   Key stakeholders depending on the size and complexity of the company may include among others:</p>
<ul>
<li>Management</li>
<li> Infrastructure Engineering</li>
<li> Systems Administration</li>
<li> Applications Development</li>
<li> Information Security</li>
</ul>
<p>Coordinating with the appropriate resources from the participating departments and discussing the upcoming PCI audit is key.  This includes making certain participants are informed of their roles, time requirements and availability requirements.  Once complete, it is time to reach out and schedule the QSA.</p>
<p>Request that your QSA send an itinerary and schedule one-week prior to arrival. This will help set schedules and necessary arrangements for your key personnel.  Depending on your company size and complexity the QSA may be onsite for a week or more.</p>
<p>Once onsite the QSA will want to schedule a meeting to coordinate activities, meet the key participants, layout the schedule, establish management rapport, and answer any questions.   It is important that your key participants are effective communicators and clear on their roles.  As the main point of contact for the organization you should plan on dedicating your time to participate in all QSA meetings and interviews.</p>
<p>I would like to point out that almost all QSA firms (an auditor) also offer PCI consulting (advisor).  This is however a very fine line to have one firm in both the role of advisor and auditor.  It is best to separate these functions obtaining a PCI consultant to advise your company on identifying the necessary actions to achieve compliance and a QSA to measure the organizations compliance.</p>
<p>A typical QSA itinerary might be as follows:</p>
<ul>
<li> Project kickoff meeting</li>
<li> Network Diagram and CDE review</li>
<li> Credit card flow review</li>
<li> Key Personnel Interviews</li>
<li> Supporting documentation review</li>
<li> Remediation review</li>
</ul>
<p>Always remember that while the QSA is providing the itinerary you the customer need to maintain control. Participating in all meetings and interviews will eliminate audits going off track and insure that each key participant is focused on their area of responsibility and expertise and maintain the scope as defined in the organizations pre-assessment meetings. I cannot stress enough that preparation, knowledge and management oversight are key to an effective and efficient audit.</p>
<p>In my next blog I will go into details an exactly what needs to be done around Network Diagrams, Credit Card Flow, and Documentation. Until then contact us <strong><a href="http://www.cybersecurityinformation.com/contact-us/">here</a></strong> to see how we can advise your organization on reaching PCI Compliance.  See you soon!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cybersecurityinformation.com/2009/11/09/pci-audit-compliance-qsa-visit-part-2/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Preparing for the FACTA Red Flags Rule</title>
		<link>http://www.cybersecurityinformation.com/2009/10/07/preparing-for-the-red-flags-rule/</link>
		<comments>http://www.cybersecurityinformation.com/2009/10/07/preparing-for-the-red-flags-rule/#comments</comments>
		<pubDate>Wed, 07 Oct 2009 20:16:05 +0000</pubDate>
		<dc:creator>Marty Schmidt</dc:creator>
				<category><![CDATA[IT Security Technology News]]></category>
		<category><![CDATA[Risk Management News]]></category>
		<category><![CDATA[PCI Compliance]]></category>
		<category><![CDATA[Red Flags Rule]]></category>
		<category><![CDATA[Red Flags Rule Assistance]]></category>

		<guid isPermaLink="false">http://www.cybersecurityinformation.com/?p=496</guid>
		<description><![CDATA[Perhaps you have heard about new regulations that the Federal Trade Commission (FTC) has proposed for some time now called the Red Flags Rule.  The Red Flags Rule stems from The Fair and Accurate Credit Transaction Act of 2003 (FACTA).  As of this writing the mandate will be enforced beginning November 1, 2009. FACTA added [...]]]></description>
			<content:encoded><![CDATA[<p>Perhaps you have heard about new regulations that the Federal Trade Commission (FTC) has proposed for some time now called the Red Flags Rule.  The Red Flags Rule stems from The Fair and Accurate Credit Transaction Act of 2003 (FACTA).  As of this writing the mandate will be enforced beginning November 1, 2009.</p>
<p>FACTA added sections to the Federal Fair Credit Reporting Act intended primarily to help consumers fight the growing crime of identity theft.  In adopting FACTA, Congress recognized that consumers were unable to prevent identity theft and could only react long after the event had occurred.  In order to stop the fraud at its source businesses that offer credit need to address the events that signal a potential fraud.</p>
<p>Six agencies were involved in drafting the red flag rules: the Treasury Department&#8217;s Office of Thrift Supervision, Office of Comptroller of the Currency, Federal Deposit Insurance Corp., Federal Trade Commission, National Credit Union Administration and the Federal Reserve System. The Red Flags Rule identifies 26 “ Red Flags” which may be indicators of attempted fraud.</p>
<p>According to FTC statistics nearly 10 million people were victims of identity theft in 2008 in the US.   In the broadest sense identity theft is the act of someone assuming the identity of another individual to gain access to the victim’s personal resources.  Last year over 35 million known data records containing sensitive personally identifiable information (PII) were stolen.</p>
<p>While some perpetrators know their victims, having stolen their wallets, credit cards, checkbooks or other personal items, the vast majority of perpetrators do not.  Identity theft comes in many forms and most victims learn their fate long after the initial event occurs, often months to years after the fact.</p>
<p>Most data theft is primarily due to poor controls surrounding PII.  This can range from sensitive records being thrown in dumpsters to electronic records being improperly secured online and breached by hackers.</p>
<p>Personal resources accessed by data thieves may include use of credit cards, establishment of credit under the victims identity, access to utilities, healthcare benefits, banking, employment, loans, government benefits, and many other acts limited only by the imagination of the perpetrator.  The common element is the use of defrauded individuals persona to gain credit or access to established resources.</p>
<p>The Red Flags Rule applies to both financial institutions and creditors.   The definition of “creditor” is broad and includes businesses or organizations that regularly defer payment for goods or services or provide goods or services and bill customers later.  These companies may not traditionally be thought of as extending credit and include utility companies, health care providers, telecommunications companies, cable and satellite providers, and others, depending on how and when they collect payment for their services.</p>
<p>The Rule also defines a “creditor” as one who regularly grants loans, arranges for loans or the extension of credit, or makes credit decisions. Examples include finance companies, mortgage brokers, real estate agents, automobile dealers, and retailers that offer financing or help consumers get financing from others by processing credit applications.  Additionally, the definition includes anyone who regularly participates in the decision to extend, renew, or continue credit, including setting the terms of credit – for example, a third-party debt collector who regularly renegotiates the terms of a debt.</p>
<p>Organizations that are covered under the Red Flags Rule must create written plans that are reviewed and signed off by the organizations board of directors that:</p>
<ul>
<li>Create Policies and Procedures that Identify Red Flags Which Pertain to their Business</li>
<li>Create Policies and Procedures that Detect the Identified Red Flags</li>
<li>Create Policies and Procedures that define the Actions to be take when Red Flags are Detected</li>
<li>Monitor changing Red Flags, Train Employees and Monitor 3rd party contractors</li>
</ul>
<p>An appropriately designed and managed plan depending on the business may require considerable skill and effort.  Most organizations will do well to reach out to experts in designing their programs.  Is your organization subject to the Red Flags Rule?</p>
<p>Information Defense is prepared to assist in evaluating whether your organization is subject to the FTC ruling and assist in defining and developing the necessary steps to reach compliance.  Contact us <strong><a href="http://www.cybersecurityinformation.com/contact-us/">here</a></strong> for further information.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cybersecurityinformation.com/2009/10/07/preparing-for-the-red-flags-rule/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Managing Your PCI Audit (Part 1)</title>
		<link>http://www.cybersecurityinformation.com/2009/09/22/managing-your-pci-audit-part-1/</link>
		<comments>http://www.cybersecurityinformation.com/2009/09/22/managing-your-pci-audit-part-1/#comments</comments>
		<pubDate>Tue, 22 Sep 2009 15:37:31 +0000</pubDate>
		<dc:creator>Information Defense Corporation</dc:creator>
				<category><![CDATA[IT Security Technology News]]></category>
		<category><![CDATA[Information Security News]]></category>
		<category><![CDATA[Risk Management News]]></category>
		<category><![CDATA[Managing Audits]]></category>
		<category><![CDATA[PCI Compliance]]></category>

		<guid isPermaLink="false">http://www.cybersecurityinformation.com/?p=475</guid>
		<description><![CDATA[Managing Your PCI Audit &#38; Compliance Blog! By Michael Nelson – PCI Practice Manager PCI DSS compliance has now become a household name for security and IT departments worldwide, potentially having significant impact on those organizations that store or process credit cards. According to the PCI Security Standards Council “All merchants, whether small or large, [...]]]></description>
			<content:encoded><![CDATA[<p><strong>Managing Your PCI Audit &amp; Compliance Blog!</strong> By Michael Nelson – PCI Practice Manager</p>
<p>PCI DSS compliance has now become a household name for security and IT departments worldwide, potentially having significant impact on those organizations that store or process credit cards.  According to the PCI Security Standards Council <strong><em>“All merchants, whether small or large, need to be PCI compliant.”</em></strong></p>
<p>While the security requirements are the same for all covered organizations, the method of proving compliance depends on the number and value of annual credit card transactions.  For merchants processing more than 6 million transactions a year, this means an on-site audit by a Qualified Security Assessor (QSA).  For more information on PCI DSS please visit <a href="https://www.pcisecuritystandards.org" target="_blank">https://www.pcisecuritystandards.org</a>.</p>
<p>For many organizations the term “PCI Audit” seems to be shrouded in mystery.  Having facilitated many PCI audits for large organizations, I have probably been asked every question imaginable in regards to PCI.  What exactly is involved? What is my Cardholder Data Environment?  How much information must I provide?</p>
<p>As an adviser I have always tried to impress upon my clients the need to understand and proactively manage the PCI Audit process, and in particular to be prepared for onsite interviews by the QSAs.  Many of the staff members that the auditor will be interviewing (e.g. office PC users, call center operators, systems administrators) may view the auditor; either as an adversary, from whom as much information should be withheld as possible, or as a friend, to whom all information should be provided when requested.  In fact, neither of these positions is appropriate and both can lead to trouble for the organization being audited.</p>
<p>Proactive PCI Audit management is the cornerstone to a successful audit process.  While many businesses simply do not have the time, staff, or trained personnel to prepare for all aspects of a PCI audit, I recommend finding qualified external resources to help the organization down this path.  It is important to remember that while most QSAs are reasonable and professional organizations they are not employees and maintain significantly different roles, responsibilities, and organizational insight.</p>
<p>Managing the PCI audit carefully will help reduce time, costs, and operational impacts to the organization.  At a minimum audit management will refine the scope and keep answers to audit questions on point.  Keys to a successful audit and meaningful results are to appropriately prepare staff, set expectations, and sharpen scope.   Expert resources to manage the process can add significant benefit to the organization and potentially reduce the cost of compliance.</p>
<p>The PCI audit process consists of many areas, however we will be focusing on the “on-site Interview” portion.  The first step in the onsite interview is preparation. Once you have chosen your QSA find out exactly when the auditor will be on site, what activities the auditor will be conducting, and what documentation they will require.  Knowing all of this will help you to understand exactly what level of detail the auditor is looking for, as well as which team members will be asked to take part in onsite interviews.  Make sure to schedule the auditor’s on-site presence when there is the minimum impact on your business operations.</p>
<p>PCI audits may become less effective and minimally productive due to a lack of preparation on the client side.  Inappropriate preparations may lead to a host of issues including the over exposure of information, withholding or attempts to hide information by well intended but ill advised staff, or as well as inaccurate and or inconsistent answers.   Theses issues among others can cause significant problems and expense down the road for the organization under audit.  Preparing each staff member before the onsite meeting is vital to a successful, efficient, and effective audit.</p>
<p>Some examples of staff interview preparation includes understanding exactly what is meant by “Cardholder Data Environment” and what this actually means to the organization.  The organization and the auditor must agree on the scope prior to the commencement of the audit.  Only information directly related to the CDE should be provided in interviews.  Auditors should be expected to provide their interview questions for review beforehand, comply with an interview schedule, and should not interview additional staff members who may confuse the issues or provide inappropriate answers.  It is the responsibility of the individual managing the audit process to ensure the interview is on topic, within scope, and with the appropriate staff.</p>
<p>My next blog I will cover actual questions that have been asked as well as the proper way to answer them. I will also dive deeper into the audit process.  Until then please contact us <strong><a href="http://www.cybersecurityinformation.com/contact-us/">here</a></strong> to learn more about how we can assist your organization to manage the compliance process.</p>
<p>See my next blog post here &#8211; <a href="http://www.cybersecurityinformation.com/2009/11/09/pci-audit-compliance-qsa-visit-part-2/" target="_self">Managing Your PCI Audit &amp; Compliance part 2 &#8211; preparing for the QSA visit</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.cybersecurityinformation.com/2009/09/22/managing-your-pci-audit-part-1/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
