<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
   <channel>
      <title>Inside Privacy - Financial Institutions</title>
      <link>http://www.insideprivacy.com/financial-institutions/</link>
      <description>Washington DC Lawyer and Attorney for Data Security, FCC, HIPAA, Electronic Communications Privacy Act</description>
      <language>en</language>
      <copyright>Copyright 2013</copyright>
      <lastBuildDate>Tue, 14 May 2013 11:05:51 -0500</lastBuildDate>
      <pubDate>Tue, 14 May 2013 11:05:51 -0500</pubDate>
      <generator>http://www.sixapart.com/movabletype/?v=4.32-en</generator>
      <docs>http://blogs.law.harvard.edu/tech/rss</docs> 

      
      <item>
         <title>SEC and CFTC Issue Final Identity Theft Rule</title>
         <description><![CDATA[<p>Last week, the Securities and Exchange Commission (SEC) and Commodity Futures Trading Commission (CFTC)&nbsp;published in the Federal Register&nbsp;a <a href="http://www.gpo.gov/fdsys/pkg/FR-2013-04-19/pdf/2013-08830.pdf">joint rule</a> requiring entities regulated by the agencies to adopt programs to detect and prevent identity theft.&nbsp; The rule is referred to as the &ldquo;red flags rule&rdquo; and applies to certain broker-dealers, mutual funds, investment advisers, futures commission merchants, retail foreign exchange dealers, commodity trading advisors, commodity pool operators, introducing brokers, swap dealers, major swap participant, and certain other entities regulated by the SEC and CFTC that qualify as a &ldquo;financial institution&rdquo; or &ldquo;creditor&rdquo; under the Fair Credit Reporting Act.&nbsp; The SEC and CFTC promulgated the rule pursuant to the Dodd-Frank Act, which amended the Fair Credit Reporting Act to require the SEC and CFTC to adopt the red flags rule.&nbsp; Prior to the Dodd-Frank Act, only the federal banking regulators and the Federal Trade Commission were required to adopt red flags rules applicable to the entities under their jurisdiction.&nbsp; Entities will be expected to comply with the rule by November 20, 2013.&nbsp;&nbsp;&nbsp;&nbsp;</p>
<p>The SEC and CFTC&rsquo;s final rule requires affected entities offering or maintaining a &ldquo;covered account&rdquo; (generally, an account for personal, family, or household purposes that is designed to permit multiple transactions, such as a broker-dealer brokerage account) to develop and implement a written identity theft prevention program that is designed to detect, prevent, and mitigate identity theft in connection with the opening of a covered account or any existing covered account.&nbsp; The program should be appropriate to the size and complexity of the entity and the nature and scope of its activities.&nbsp;</p>
<p>The program is required to include reasonable policies and procedures to:</p>
<p>(1)&nbsp;Identify relevant Red Flags (activities that indicate the possible existence of identity theft) for the covered accounts that the entity offers or maintains, and incorporate those Red Flags into its program;</p>
<p>(2)&nbsp;Detect Red Flags that have been incorporated into the entity&rsquo;s program;</p>
<p>(3)&nbsp;Respond appropriately to any Red Flags that are detected to prevent and mitigate identity theft; and</p>
<p>(4)&nbsp;Ensure the program is updated periodically, to reflect changes in risks to customers and to the safety and soundness of the entity from identity theft.&nbsp;&nbsp;</p>
<p>The SEC and CFTC&rsquo;s red flags rule is nuanced, particularly in defining the entities that are subject to its requirements.&nbsp; SEC- and CFTC-regulated entities should review the rule carefully to determine whether they are required to develop identity theft prevention programs.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/sec-and-cftc-issue-final-identity-theft-rule/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/sec-and-cftc-issue-final-identity-theft-rule/</guid>
         <category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/financial-privacy">Red Flags</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Thu, 25 Apr 2013 11:46:37 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>Federal Reserve Releases Report of Mobile Banking and Mobile Payments Use</title>
         <description><![CDATA[<p>On March 27, 2013, the Federal Reserve released a&nbsp;<a href="http://www.federalreserve.gov/econresdata/consumers-and-mobile-financial-services-report-201303.pdf">report</a> on consumers&rsquo; use of mobile banking and mobile payments.&nbsp; The report follows a similar report issued by the Federal Reserve last year.&nbsp; The report found that use of mobile banking has increased significantly in the past year while use of mobile payments has increased as well.&nbsp;</p>
<p>As of November 2012, 28 percent of all mobile phone users (compared to 21 percent in December 2011) and 48 percent of smartphone users (compared to 42 percent in December 2011) had used mobile banking in the past 12 months.&nbsp; The recent report found that 15 percent of all smartphone users have made a payment from their phone in the past 12 months, compared to 12 percent of users from the prior report.&nbsp; In addition, the use of mobile phones to deposit checks has doubled in the past year, rising from approximately 10 percent to 21 percent.&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</p>
<p>The most common uses of mobile banking are to check account balances or recent transactions (87 percent of users) and to transfer money between accounts (53 percent of users).&nbsp; The most common use of mobile payments is to make online bill payments (42 percent of users).&nbsp; Six percent of all smartphone users have made a point-of-sale payment using their phone in the past 12 months, which represents a sizable increase from the one percent of users in December 2011.&nbsp;</p>
<p>&nbsp;</p>]]><![CDATA[<p>The primary reason consumers have not adopted mobile banking services is that they feel as though their banking needs are being met without mobile banking. The primary reason consumers have not adopted mobile payments is the concern over security. This concern also is the second most prevalent reason why consumers have not adopted mobile banking services.</p>
<p>The report reiterated the reliance of the underbanked on mobile banking and mobile payments. In the past 12 months, almost 50 percent of underbanked consumers reported use of mobile banking and more than 30 percent reported use of mobile payments.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/federal-reserve-releases-report-of-mobile-banking-and-mobile-payments-use/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/federal-reserve-releases-report-of-mobile-banking-and-mobile-payments-use/</guid>
         <category domain="http://www.insideprivacy.com/">Data Security</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Tue, 09 Apr 2013 11:43:17 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>House Passes Legislation Eliminating Annual GLBA Privacy Notice Requirement </title>
         <description><![CDATA[<p>Earlier this week, the House of Representatives passed&nbsp;<a href="http://beta.congress.gov/bill/113th-congress/house-bill/749">H.R. 749, the Eliminate Privacy Notice Confusion Act</a>.&nbsp; The bill is sponsored by Rep. Blaine Leutkemeyer (R-MO) and Rep. Brad Sherman (D-CA).&nbsp; An earlier version of the bill passed the House in December but was never taken up by the Senate.&nbsp; We <a href="http://www.insideprivacy.com/united-states/proposed-bill-would-limit-annual-privacy-notice-requirement-under-glba/">previously covered</a> similar legislation introduced by Representative Leutkemeyer.</p>
<p>The bill provides that a financial institution subject to the requirement in the Gramm-Leach-Bliley Act (GLBA) to send annual privacy notices to customers is excluded from this requirement if the institution (1) only discloses customers&rsquo; nonpublic personal information to nonaffiliated third-parties pursuant to an exception in GLBA (e.g., for processing or servicing a customer&rsquo;s account or to a service provider) from the overall opt-out framework and (2) has not changed its policies and practices with regard to disclosing nonpublic personal information from the policies and practices that were disclosed in the most recent notice sent to customers.&nbsp; If either of these requirements ceases to apply, the institution would be required to send an annual privacy notice.&nbsp; The legislation is intended to lessen the regulatory burden on financial institutions and potential for customer confusion in sending to customers privacy notices that have not changed over time and that are generally available on institutions&rsquo; websites.&nbsp;</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/house-adopts-legislation-eliminating-annual-glba-privacy-notice-requirement/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/house-adopts-legislation-eliminating-annual-glba-privacy-notice-requirement/</guid>
         <category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Thu, 14 Mar 2013 14:01:04 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>FTC Study Details Inaccuracies in Credit Reports</title>
         <description><![CDATA[<p>This week, the Federal Trade Commission released a&nbsp;<a href="http://www.ftc.gov/os/2013/02/130211factareport.pdf">study</a> of the U.S. credit reporting industry and credit report accuracy.&nbsp; The study found that five percent of consumers had errors on one of their three nationwide credit reports that could lead them to pay more for financial products.&nbsp; The study is required under section 319 of the Fair and Accurate Credit Transactions Act of 2003.</p>
<p>The study evaluated 1,001 consumers and 2,968 credit reports.&nbsp; Of these totals, the study found that as many as 206 consumers identified material errors in their credit reports.&nbsp; The most common errors identified were errors in tradeline data (consumer accounts) and collections information.&nbsp; Another common error was inaccuracies in the header information such as current and previous address, age, and employment.</p>
<p>The FTC study is the first major study to take into consideration all of the primary groups that play a role in the credit reporting industry:&nbsp; consumers; furnishers of information to consumer reporting agencies, including creditors, debt collection agencies, and courts; the Fair Isaac Corporation; and the national consumer reporting agencies.&nbsp; The FTC will issue a final report on credit report accuracy in 2014.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/ftc-study-details-inaccuracies-in-credit-reports/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/ftc-study-details-inaccuracies-in-credit-reports/</guid>
         <category domain="http://www.insideprivacy.com/united-states">Federal Trade Commission</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Thu, 14 Feb 2013 22:07:31 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>President Obama Issues Cybersecurity Executive Order</title>
         <description><![CDATA[<p>In his State of the Union message on Tuesday, President Obama announced that he had signed an <a href="http://www.whitehouse.gov/the-press-office/2013/02/12/executive-order-improving-critical-infrastructure-cybersecurity">Executive Order</a> addressing the cybersecurity of&nbsp; critical infrastructure. &nbsp;President Obama <a href="http://www.whitehouse.gov/state-of-the-union-2013">emphasized</a> that in the face of threats to corporate secrets, the power grid, and financial institutions, among others, &ldquo;We cannot look back years from now and wonder why we did nothing in the face of real threats to our security and our economy.&rdquo;</p>
<p>The Executive Order follows legislative efforts in the last Congress to pass comprehensive cybersecurity bills.&nbsp; After the Cybersecurity Act of 2012 (S. 3414) failed to pass in August 2012, Deputy National Security Adviser John Brennan mentioned in an <a href="http://www.insideprivacy.com/data-security/cybersecurity/white-house-considers-cybersecurity-executive-order/">appearance</a> at the Council on Foreign Relations that the President was considering issuing an Executive Order to implement portions of the cybersecurity legislation. &nbsp;In the subsequent months, the White House sought <a href="http://thehill.com/blogs/hillicon-valley/technology/270429-white-house-draft-cyber-order-adds-changes-to-mollify-tech-industry">industry input</a> on the Order.</p>
<p>The Order has two main components: increasing information sharing from the government to the private sector and establishing a Cybersecurity Framework to buttress the security of critical infrastructure.<span id="_marker">&nbsp;</span></p>]]><![CDATA[<p>Section 4 of the Order addresses information sharing and aims to &ldquo;increase the volume, timeliness, and quality of cyber threat information shared with U.S. private sector entities.&rdquo;&nbsp; The Order directs the Attorney General, Secretary of Homeland Security, and Director of National Intelligence to issue instructions to &ldquo;ensure the timely production of unclassified reports of cyber threats to the U.S. homeland that identify a specific targeted entity.&rdquo;&nbsp; The officials are also charged with establishing a process to disseminate classified reports to critical infrastructure entities with the requisite security clearances.&nbsp; In support of this direction, the Order directs the Secretary of Homeland Security to expedite security clearances for personnel employed by critical infrastructure owners and operators.&nbsp; In addition, Section 4 directs the Secretary of Homeland Security, in coordination with the Secretary of Defense, to &ldquo;establish procedures to expand the Enhanced Cybersecurity Services program to all critical infrastructure sectors&rdquo; within 120 days of the Order&rsquo;s issuance.&nbsp; The program &ldquo;will provide classified cyber threat and technical information from the Government to eligible critical infrastructure companies or commercial service providers that offer security services to critical infrastructure.&rdquo;</p>
<p>Section 7 of the Order turns to the Cybersecurity Framework.&nbsp; Section 7 requires the Director of the National Institute of Standards and Technology to lead the development of a Cybersecurity Framework &ldquo;to reduce cyber risks to critical infrastructure.&rdquo;&nbsp; The Framework will include &ldquo;a set of standards, methodologies, procedures and processes that align policy, business, and technological approaches to address cyber risks&rdquo; and &ldquo;shall incorporate voluntary consensus standards and industry best practices to the fullest extent possible.&rdquo;&nbsp; The Framework&rsquo;s guidance to critical infrastructure owners and operators will be &ldquo;technology neutral&rdquo; and preserve &ldquo;a competitive market for products and services that meet the standards, methodologies, procedures and processes developed to address cyber risks.&rdquo;&nbsp; The Framework will be subject to &ldquo;an open public review and comment process,&rdquo; with a preliminary version to be published within 240 days and a final version to be issued within one year of the Order.</p>
<p>Section 8 of the Order directs the Secretary of Homeland Security and sector-specific agencies to establish a &ldquo;voluntary program to support the adoption of the Cybersecurity Framework by owners and operators of critical infrastructure.&rdquo;&nbsp; The Secretary of Homeland Security is further directed to &ldquo;coordinate establishment of a set of incentives&rdquo; to promote participation by owners and operators of critical infrastructure in the Framework program.</p>
<p>The Order also contemplates regulation by sector-specific agencies based on the Cybersecurity Framework.&nbsp; Section 10 directs sector-specific agencies that regulate critical infrastructure to report to the President on &ldquo;whether the agency has clear authority to establish requirements based upon the Cybersecurity Framework to sufficiently address current and projected cyber risks to critical infrastructure&rdquo; and &ldquo;any additional authority required.&rdquo;</p>
<p>For additional details and analysis, please see our <a href="http://www.cov.com/files/Publication/f918cf61-d856-49d5-b824-3ac3c8714a8a/Presentation/PublicationAttachment/140660bd-e448-4979-b45c-4b62a7abb8d3/President_Obama_Issues_Executive_Order_on_Improving_Critical_Infrastructure_Cybersecurity.pdf">client alert</a> on the Executive Order.</p>]]></description>
         <link>http://www.insideprivacy.com/data-security/cybersecurity/president-obama-issues-cybersecurity-executive-order/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/data-security/cybersecurity/president-obama-issues-cybersecurity-executive-order/</guid>
         <category domain="http://www.insideprivacy.com/">Cloud Computing</category><category domain="http://www.insideprivacy.com/data-security">Cybersecurity</category><category domain="http://www.insideprivacy.com/united-states/congress">Department of Commerce</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Thu, 14 Feb 2013 11:44:47 -0500</pubDate>
         <dc:creator>Kristen Eichensehr</dc:creator>

      </item>
      
      <item>
         <title>FFIEC Proposes Social Media Guidance</title>
         <description><![CDATA[<div>
<p>On January 22, 2013, the Federal Financial Institutions Examination Council proposed <a href="http://www.ffiec.gov/press/Doc/FFIEC%20social%20media%20guidelines%20FR%20Notice.pdf">guidance</a> on the applicability of consumer protection and compliance laws, regulations, and policies to activities conducted via social media by depository institutions.&nbsp; The proposed guidance would not impose additional compliance obligations on institutions.&nbsp; Instead, the guidance is intended to help financial institutions understand potential consumer compliance, legal, reputation, and operational risks associated with the use of social media, along with expectations for managing those risks.&nbsp;</p>
<p>The proposed guidance defines &ldquo;social media&rdquo; as &ldquo;a form of interactive online communication in which users can generate and share content through text, images, audio, and/or video.&rdquo;&nbsp; The FFIEC warns that social media can impact a depository institution&rsquo;s risk profile by increasing the risk of harm to consumers, compliance and legal risk, operational risk, and reputational risk.&nbsp;</p>
</div>]]><![CDATA[<p>To further mitigate these risks, the federal banking agencies expect an institution to have a risk management program that allows the institution to identify, measure, monitor, and control risks related to social media. The size and complexity of the program must be commensurate with the breadth of the institution&rsquo;s involvement in social media, but in any event the program&rsquo;s components should include:</p>
<ol>
<li>A governance structure with clear roles and responsibilities for the Board of Directors or senior management to direct how social media contributes to the strategic goals of the institution, establish controls, and assesses risk on an ongoing basis;</li>
<li>Policies and procedures regarding the use of social media and monitoring for compliance with consumer protection laws and regulations;</li>
<li>Due diligence for selecting and managing third-party service provider relationships in social media;</li>
<li>An employee training program for official, work-related use of social media and other uses of social media;</li>
<li>An oversight process for monitoring information posted to proprietary social media sites administered by the institution;</li>
<li>Audit and compliance functions to ensure ongoing compliance with internal policies and applicable laws and regulations; and</li>
<li>Parameters for appropriate reporting to the Board of Directors or senior management regarding the effectiveness of the risk management program. </li>
</ol>
<p>The guidance also highlights the unique privacy risks raised by social media to institutions and their customers. In particular, the guidance notes the Gramm-Leach-Bliley Act, CAN-SPAM Act and Telephone Consumer Protection Act, Children&rsquo;s Online Privacy and Protection Act, and Fair Credit Reporting Act as all posing unique compliance challenges to institutions using social media to advertise and provide financial products and services.</p>
<p>Comments to the proposed guidance must be submitted within 60 days of the guidance&rsquo;s publication in the Federal Register. The FFIEC is requesting specific comment on the following three questions:</p>
<ol>
<li>Are there other types of social media, or ways in which financial institutions are using social media, that are not included in the proposed guidance but that should be included?</li>
<li>Are there other consumer protection laws, regulations, policies or concerns that may be implicated by financial institutions&rsquo; use of social media that are not discussed in the proposed guidance but that should be discussed?</li>
<li>Are there any technological or other impediments to financial institutions&rsquo; compliance with otherwise applicable laws, regulations, and policies when using social media of which the Agencies should be aware?</li>
</ol>]]></description>
         <link>http://www.insideprivacy.com/united-states/ffiec-proposes-social-media-guidance/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/ffiec-proposes-social-media-guidance/</guid>
         <category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">Social Media</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Sat, 26 Jan 2013 15:03:24 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>FDIC Highlights Mobile Payment Technologies and Related Risks</title>
         <description><![CDATA[<p>In its most recent issue of the <a href="http://www.fdic.gov/regulations/examinations/supervisory/insights/siwin12/SIwinter12.pdf">Supervisory Insights</a> newsletter, the Federal Deposit Insurance Corporation (FDIC) describes mobile payment technologies, the risks they pose to depository institutions, and the regulatory framework applicable to such technologies.&nbsp; The FDIC notes the widespread use of smartphones as a payment technology and the increasing availability of point-of-sale terminals equipped to process payments using near-field communications.&nbsp; Both of these factors require institutions to understand and adopt controls to mitigate risk from mobile payment technologies.</p>]]><![CDATA[<p>The FDIC identified the following risks associated with mobile payment technologies:</p>
<ul>
<li><em>BSA/AML risk</em> &ndash; risk that mobile payment technologies will violate the Bank Secrecy Act or other anti-money laundering requirements.</li>
<li><em>Fraud risk</em> &ndash; risk that mobile payment technologies will fail to prevent or deter unauthorized transactions.</li>
<li><em>Compliance risk</em> &ndash; risk that mobile payment technologies will  be used in a manner that violates applicable consumer protection laws,  disclosure requirements, and supervisory guidance.</li>
<li><em>Credit/liquidity risk</em> &ndash; risk that a loss will occur from a  failure by a mobile payment technology to collect on a credit obligation  or failure to meet a payments-based contractual commitment.</li>
<li><em>Operations/IT risk</em> &ndash; risk that mobile payment technologies will fail to protect confidential financial information.</li>
<li><em>Reputation risk</em> &ndash; risk that negative consumer experience from  mobile payment technologies or from an incident resulting from mobile  payment technologies will reflect poorly on the institution.</li>
<li><em>Vendor management risk</em> &ndash; risk that a third-party providing  mobile payment technologies to an institution will fail to meet  expectations or suffer bankruptcy.&nbsp; </li>
</ul>
<p>The article also describes the laws and regulations applicable to  mobile payment technologies, including the Electronic Fund Transfer Act;  Truth in Lending Act; truth in billing requirements; unfair, deceptive,  or abusive acts or practices (UDAAP) requirements; Gramm-Leach-Bliley  Act; and deposit insurance requirements.&nbsp; The FDIC concludes by  reminding institutions to consistently apply fundamentals of payments  risk management, in particular with regard to oversight of third-party  relationships.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/fdic-highlights-mobile-payment-technologies-and-related-risks/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/fdic-highlights-mobile-payment-technologies-and-related-risks/</guid>
         <category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Fri, 18 Jan 2013 10:31:30 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>FTC Announces Amended Rule on Identity Theft &quot;Red Flags&quot;</title>
         <description><![CDATA[<p>On Friday, November 30, the Federal Trade Commission (FTC) issued an <a href="http://www.ftc.gov/os/2012/11/121130redflagsrule.pdf">Interim Final Rule</a> to amend its Red Flags Rule, which requires certain financial institutions and creditors to establish programs to detect, prevent and mitigate identity theft in connection with consumer accounts. &nbsp;The Interim Final Rule narrows the definition of &ldquo;creditor&rdquo; in response to legislation passed by Congress in December 2010 (as covered in previous <a href="http://www.insideprivacy.com/united-states/congress/president-to-sign-into-law-legislation-narrowing-scope-of-red-flags-rule/">blog posts</a>), excluding from the definition most doctors, lawyers, and other professionals who do not receive full payment at the time their service is furnished.&nbsp; The rule is effective on February 11, 2013, and the FTC is seeking comments on the rule until that time.&nbsp; &nbsp;&nbsp;&nbsp;</p>
<p>The Interim Final Rule narrows the circumstances under which creditors are covered by the Rule in an attempt to be consistent with Congress&rsquo;s legislation. The amended Rule now provides that a creditor is covered only if, in the ordinary course of business, it regularly: (1) obtains or uses consumer reports in connection with a credit transaction; (2) furnishes information to consumer reporting agencies in connection with a credit transaction; or (3) advances funds to or on behalf of a person (except for a creditor who advances funds on behalf of the person for expenses incidental to a service provided by the creditor to that person). &nbsp;&nbsp;</p>
<p>Under the Rule, covered entities&rsquo; Red Flag programs must: (1) include reasonable policies and procedures to identify signs &ndash; or &ldquo;red flags&rdquo; &ndash; of identity theft in the day-to-day operations of the business; (2) be designed to detect the red flags of identity theft known to the business; (3) set out the actions the business will take upon detecting red flags; and (4) re-evaluate its program periodically to reflect new risks.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/ftc-announces-amended-rule-on-identity-theft-red-flags/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/ftc-announces-amended-rule-on-identity-theft-red-flags/</guid>
         <category domain="http://www.insideprivacy.com/united-states">Congress</category><category domain="http://www.insideprivacy.com/united-states/congress">Creditors</category><category domain="http://www.insideprivacy.com/">Data Security</category><category domain="http://www.insideprivacy.com/united-states">Federal Trade Commission</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/financial-privacy">Red Flags</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Tue, 04 Dec 2012 12:00:36 -0500</pubDate>
         <dc:creator>Kristi Cercone</dc:creator>

      </item>
      
      <item>
         <title>CFPB Offers Assistance for Consumer Credit Reporting Complaints</title>
         <description><![CDATA[<p>Last week, the Consumer Financial Protection Bureau (CFPB)&nbsp;<a href="http://www.consumerfinance.gov/blog/headline-now-accepting-credit-reporting-complaints/">announced</a> that it had established a process for assisting consumers with credit reporting complaints.&nbsp; The CFPB previously had implemented similar processes for complaints relating to credit cards, mortgages, bank accounts and services, private student loans, vehicle, and other consumer loans.&nbsp; The complaint process is intended to complement the CFPB&rsquo;s recent initiatives to supervise the consumer reporting industry, including the&nbsp;CFPB&rsquo;s <a href="http://www.gpo.gov/fdsys/pkg/FR-2012-07-20/pdf/2012-17603.pdf">final rule</a> establishing its authority to supervise consumer reporting agencies and&nbsp;<a href="http://files.consumerfinance.gov/f/201209_cfpb_Consumer_Reporting_Examination_Procedures.pdf">examination manual</a> for consumer reporting agencies.</p>
<p>The announcement makes clear that consumers should not file complaints with the CFPB in lieu of or before disputing inaccurate credit reporting information with the applicable consumer reporting agency.&nbsp; Disputing inaccurate information with the applicable reporting agency preserves certain rights under the Fair Credit Reporting Act and serves as the most immediate way of resolving inaccurate information.&nbsp; However, if the consumer is dissatisfied with the reporting agency&rsquo;s resolution of the dispute, the announcement encourages the consumer to contact the CFPB.&nbsp; The Federal Trade Commission has a similar process for assisting consumers with credit reporting complaints.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/cfpb-offers-assistance-for-consumer-credit-reporting-complaints/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/cfpb-offers-assistance-for-consumer-credit-reporting-complaints/</guid>
         <category domain="http://www.insideprivacy.com/united-states">Federal Trade Commission</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Fri, 02 Nov 2012 13:59:03 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>CFPB Study Assesses Differences in Credit Scores Sold to Consumers and Creditors</title>
         <description><![CDATA[<p>Last week, the Consumer Financial Protection Bureau (CFPB) released a&nbsp;<a href="http://files.consumerfinance.gov/f/201209_Analysis_Differences_Consumer_Credit.pdf">study</a> comparing credit scores sold to creditors and those sold to consumers.&nbsp; The study found that approximately 1 in 5 consumers would, upon purchasing their credit score from a consumer reporting agency, receive a different credit score than the score provided to creditors for use in determining eligibility for products or services.&nbsp; The study was required by section 1078 of the Dodd-Frank Wall Street Reform and Consumer Protection Act.</p>
<p>The study also found that differences in the scores provided to consumers versus creditors could harm consumers and that most consumers would never find out that the credit score given to them may not be the score in fact used by creditors.&nbsp; To address these findings, the CFPB recommended that consumers shop around for credit and carefully review their credit reports.&nbsp;</p>
<p>The CFPB commenced supervision of consumer reporting agencies on September 30, 2012.&nbsp; The differences highlighted in the study will be one of the CFPB&rsquo;s focal points during supervisory examinations.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/cfpb-study-assesses-differences-in-credit-scores-sold-to-consumers-and-creditors/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/cfpb-study-assesses-differences-in-credit-scores-sold-to-consumers-and-creditors/</guid>
         <category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Tue, 02 Oct 2012 15:02:50 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>FDIC Official Discusses Implementation of FFIEC Authentication Guidance</title>
         <description><![CDATA[<p>In an&nbsp;<a href="http://www.bankinfosecurity.com/interviews/fdic-ffiec-guidance-progress-report-i-1638">interview</a> with Information Security Media Group, William Henley, Associate Director of the Federal Deposit Insurance Corporation&rsquo;s (FDIC) Technology Supervision Branch, discussed the status of the banking industry&rsquo;s implementation of <a href="http://www.ffiec.gov/pdf/Auth-ITS-Final%206-22-11%20(FFIEC%20Formated).pdf">FFIEC authentication guidance</a> released in July 2011.&nbsp; Henley generally said that the industry was working towards compliance and offered that FDIC examiners at this stage were looking for good faith efforts to comply:&nbsp; &ldquo;What the examiners were looking for were reasonable, good faith efforts that an institution was working toward compliance&hellip;.If any institution was working toward a compliance plan, that's all they needed to do.&rdquo;</p>
<p>He also described the federal banking agencies&rsquo; move away from &ldquo;controls-based oversight&rdquo; to &ldquo;governance-based oversight.&rdquo;&nbsp; The agencies do not want to be in the position of constantly reacting to the newest form of technology through the issuance of internal controls guidance tailored to the technology.&nbsp; Instead, the agencies would prefer to address emerging technology risks through requirements relating to robust risk management, board oversight, and broader risk mitigation strategies that can address any form of emerging technology.</p>
<p>The federal banking agencies have prioritized information security highly.&nbsp; We will continue to monitor and report on developments.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/fdic-official-discusses-implementation-of-ffiec-authentication-guidance/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/fdic-official-discusses-implementation-of-ffiec-authentication-guidance/</guid>
         <category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Wed, 05 Sep 2012 11:00:57 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>FTC Obtains Second Largest Civil Penalty Under FCRA</title>
         <description><![CDATA[<p>An employment background screening company will pay a $2.6 million civil penalty to <a href="http://www.ftc.gov/os/caselist/1023130/120808hirerightstip.pdf">settle</a> Federal Trade Commission charges under the Fair Credit Reporting Act.&nbsp; &nbsp;The FTC <a href="http://www.ftc.gov/os/caselist/1023130/120808hirerightcmpt.pdf">alleged </a>that HireRight Solutions, Inc., which compiles background reports to assist employers in making hiring and other employment-related decisions, is a consumer reporting agency since its reports &ldquo;bear on . . . consumers&rsquo; general reputation and personal characteristics; and are used as a factor in determining eligibility for employment.&rdquo;&nbsp; The FTC charged that, as a consumer reporting agency, HireRight had an obligation to follow reasonable procedures to assure the maximum possible accuracy of the information in its consumer reports -- an obligation that the FTC says HireRight violated.</p>
<p>In addition to a $2.6 million civil penalty, the consent decree enjoins HireRight from failing to follow reasonable procedures to:</p>
<ul>
<li>Ensure that its consumer reports reflect the current status of criminal records that have been expunged; </li>
<li>Prevent the inclusion of multiple entries for a single criminal offense; and</li>
<li>Prevent the inclusion of information about individuals other than the person about whom a consumer report pertains.&nbsp; </li>
</ul>
<p>The consent decree also enjoins HireRight from failing to provide consumers full access to records maintained about them or failing to investigate&nbsp;or respond promptly to consumer disputes about the accuracy of HireRights&rsquo; consumer reports. &nbsp;&nbsp;</p>
<p>According to press reports, this is the second largest civil penalty that the FTC has obtained under the FCRA.&nbsp; In 2006, ChoicePoint, Inc. agreed to pay $10 million to settle claims under the FCRA.&nbsp;</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/ftc-obtains-second-largest-civil-penalty-under-fcra/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/ftc-obtains-second-largest-civil-penalty-under-fcra/</guid>
         <category domain="http://www.insideprivacy.com/united-states">Federal Trade Commission</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Mon, 13 Aug 2012 17:03:41 -0500</pubDate>
         <dc:creator>Libbie Canter</dc:creator>

      </item>
      
      <item>
         <title>CFPB Issues Rule to Supervise Larger Participants in Consumer Reporting Market</title>
         <description><![CDATA[<p style="text-align: left;">The Consumer Financial Protection Bureau (CFPB) has issued a <a href="http://files.consumerfinance.gov/f/201207_cfpb_final-rule_defining-larger-participants-consumer-reporting.pdf">final rule</a> to implement its authority under section 1024 of Dodd-Frank to subject &ldquo;larger participants&rdquo; in the consumer reporting market to CFPB supervision.&nbsp; The rule will have significant consequences for companies in the consumer reporting industry.&nbsp; The final rule follows a proposed rule issued in February 2012 indicating that the CFPB intended to supervise the consumer reporting market as part of the CFPB&rsquo;s authority to supervise nonbank providers of consumer financial products and services.&nbsp; The final rule is effective September 30, 2012.&nbsp;</p>
<p>The final rule defines a &ldquo;larger participant&rdquo; in the consumer reporting market as a nonbank covered person that offers or provides consumer reporting and has annual receipts from consumer reporting in excess of $7 million.</p>]]><![CDATA[<ul>
<li>A &ldquo;nonbank covered person&rdquo; generally is any person that is not a bank and that is engaged in offering or providing a consumer financial product or service.&nbsp; The term also includes certain affiliates of such a person.&nbsp; </li>
<li>&ldquo;Consumer reporting&rdquo; means &ldquo;collecting, analyzing, maintaining, or providing consumer reporting information or other account information used or expected to be used in any decision by another person regarding the offering or provision of any consumer financial product or service.&rdquo;&nbsp; Notably, this definition is different from the comparable definition in the Fair Credit Reporting Act.&nbsp; </li>
<li>&ldquo;Annual receipts&rdquo; generally are total income plus the cost of goods sold, as reported on Internal Revenue Service tax return forms.&nbsp; Annual receipts are computed over a three-year period by totaling receipts from the covered person&rsquo;s three most recently completed fiscal years and dividing by three.&nbsp; The final rule requires a covered person to include in its annual receipts the annual receipts of affiliates from consumer reporting.&nbsp; </li>
</ul>
<p>A larger participant in the consumer reporting market will be notified if the CFPB intends to initiate a supervisory activity (<em>e.g.</em>, examination) with respect to the participant.&nbsp; The participant may contest the supervisory activity on the grounds that the participant does not meet the definition of &ldquo;larger participant&rdquo; by submitting a response to the CFPB.&nbsp;</p>
<p>The CFPB&rsquo;s final rule makes clear that supervision of larger participants will be &ldquo;probabilistic&rdquo; in nature.&nbsp; The CFPB will examine certain larger participants on a periodic basis while other larger participants may be examined less frequently.&nbsp; The CFPB&rsquo;s supervisory decisions, including decisions regarding the frequency and extent of examinations, will be informed by statutory factors including the size and transaction volume of individual participants, the risks posed to consumers, and the extent of state consumer protection oversight.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/cfpb-issues-rule-to-supervise-larger-participants-in-consumer-reporting-market/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/cfpb-issues-rule-to-supervise-larger-participants-in-consumer-reporting-market/</guid>
         <category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Wed, 18 Jul 2012 11:19:12 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>FFIEC Issues Risk Management Guidance for Cloud Computing</title>
         <description><![CDATA[<p>On July 10,&nbsp;the Federal Financial Institutions Examination Council (FFIEC) issued&nbsp;<a href="http://ithandbook.ffiec.gov/media/153119/06-28-12_-_external_cloud_computing_-_public_statement.pdf">risk management guidance</a> for depository institutions&rsquo; use of cloud computing.&nbsp; The guidance defines cloud computing generally as &ldquo;a migration from owned resources to shared resources in which client users receive information technology services, on demand, from third-party service providers via the Internet &lsquo;cloud.&rsquo;&rdquo;&nbsp; The guidance also considers cloud computing to be a form of outsourcing subject to the risk management requirements set forth in the <em><a href="http://ithandbook.ffiec.gov/ITBooklets/FFIEC_ITBooklet_OutsourcingTechnologyServices.pdf">FFIEC Information Technology Examination Handbook for Outsourcing Technology Services</a></em>.</p>]]><![CDATA[<p>The key risk management controls for cloud computing identified in the guidance are:</p>
<ul>
<li>Due Diligence &ndash; Institutions should conduct due diligence with respect to the cloud computing provider to assess the provider&rsquo;s controls to protect the confidentiality and integrity of data stored in the cloud, to determine whether data will be stored on servers used by other clients of the provider and, if so, the provider&rsquo;s access controls, and to evaluate the provider&rsquo;s disaster recovery and business continuity plans.</li>
<li>Vendor Management &ndash; Institutions may require additional controls to manage cloud computing providers that have little experience with financial institution clients and may determine that retention of a particular provider is unacceptable due to the provider&rsquo;s unwillingness or inability to satisfy bank regulators&rsquo; supervisory guidance.</li>
<li>Audit &ndash; Institutions&rsquo; audit coverage should include outsourced cloud computing.&nbsp; </li>
<li>Information Security &ndash; Institutions should incorporate cloud computing services in existing information security policies, standards, and practices and ensure that data is protected and access to data is properly restricted.&nbsp; An institution also should effectively monitor data security threats to the institution&rsquo;s systems and to the provider&rsquo;s systems and develop incident response methodologies.&nbsp; </li>
<li>Legal, Regulatory, and Reputational Considerations &ndash; Institutions should assess the extent to which cloud computing services increase the complexity of complying with applicable legal and regulatory requirements.&nbsp; In addition, contracts with cloud computing providers should specify the providers&rsquo; obligations with respect to institutions&rsquo; responsibilities for compliance with privacy laws, for responding to and reporting security incidents, and for fulfilling regulatory requirements to notify customers and regulators of any breaches.</li>
<li>Business Continuity &ndash; Institutions should determine whether the provider and the provider&rsquo;s network carriers have adequate plans and resources to ensure institutions&rsquo; continuity of operations, as well as the ability to recover and resume operations if an unexpected disruption occurs.</li>
</ul>]]></description>
         <link>http://www.insideprivacy.com/united-states/ffiec-issues-risk-management-guidance-for-cloud-computing/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/ffiec-issues-risk-management-guidance-for-cloud-computing/</guid>
         <category domain="http://www.insideprivacy.com/">Cloud Computing</category><category domain="http://www.insideprivacy.com/">Data Security</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Tue, 17 Jul 2012 14:15:52 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>First Circuit Finds Bank&apos;s Online-Security Procedures &apos;Commercially Unreasonable&apos;</title>
         <description><![CDATA[<p>A bank that required a commercial customer to answer &ldquo;challenge questions&rdquo; for virtually all online payments and that did not implement other common security measures failed to provide a commercially reasonable level of security, the U.S. Court of Appeals for the First Circuit <a href="http://www.ca1.uscourts.gov/pdf.opinions/11-2031P-01A.pdf">ruled</a> this week.</p>
<p>The case arose when unknown hackers were able to make large electronic transfers over the course of seven days from Patco Construction&rsquo;s accounts at Ocean Bank, a southern Maine community bank owned by People&rsquo;s United Bank. &nbsp;Patco lost more than $345,000. Patco sued People&rsquo;s United, alleging that Ocean Bank&rsquo;s security procedures were not &ldquo;commercially reasonable,&rdquo; and therefore the bank was liable for Patco&rsquo;s loss under the Uniform Commercial Code.</p>]]><![CDATA[<p>Ocean Bank&rsquo;s automated monitoring system assigned risk scores to online transactions based on customers&rsquo; patterns of use. Transactions with risk scores above a set threshold would require users to answer additional &ldquo;challenge questions,&rdquo; which were security questions and answers that the accountholder had chosen when setting up the online-banking account. However, Ocean Bank set up its system so that users would have to answer the challenge questions for any payment or transfer over $1. Patco used Ocean Bank&rsquo;s online-banking feature for routine tasks such as making weekly payroll payments, and thus had to answer the challenge questions frequently. In May 2009, unknown hackers were able to use the online-banking system to transfer money from Patco&rsquo;s account to numerous individuals whom Patco had never before paid.&nbsp; The hackers apparently had obtained the answers to Patco&rsquo;s challenge questions. The bank&rsquo;s automated monitoring system flagged the fraudulent transactions as &ldquo;high risk,&rdquo; based on &ldquo;the timing, value, and geographic location of Patco&rsquo;s regular payment orders,&rdquo; but &ldquo;Ocean Bank neither [manually] monitored that transaction nor provided notice to customers before allowing the transaction to be completed.&rdquo;</p>
<p>Patco argued that by asking users to answer the challenge questions so frequently, the bank increased the risk of fraud&nbsp; by providing more opportunities for hackers to intercept the information using keyloggers or other malware that might have infected a customer&rsquo;s computer. Patco later found remnants of the Zeus/Zbot malware on its computers, although it could not determine whether that malware had captured Patco&rsquo;s banking credentials. The First Circuit agreed that lowering the dollar threshold for challenge questions without implementing additional, compensating security measures &ldquo;rendered Ocean Bank&rsquo;s security procedures commercially unreasonable.&rdquo; Accordingly, the First Circuit reversed the district court&rsquo;s decision to grant summary judgment to the bank.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/first-circuit-finds-banks-online-security-procedures-commercially-unreasonable/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/first-circuit-finds-banks-online-security-procedures-commercially-unreasonable/</guid>
         <category domain="http://www.insideprivacy.com/data-security">Cybersecurity</category><category domain="http://www.insideprivacy.com/">Data Security</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/united-states">Litigation</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Fri, 06 Jul 2012 13:48:26 -0500</pubDate>
         <dc:creator>Michael Beder</dc:creator>

      </item>
      
      <item>
         <title>Settlement Reached in Data Security Breach Lawsuit Against Bank</title>
         <description><![CDATA[<p>Yesterday, Village View, Inc. reached a settlement with Professional Business Bank, a California state-chartered bank subject to regulation by the Federal Deposit Insurance Corporation (FDIC), over the company&rsquo;s lawsuit against the bank arising from a data security breach.&nbsp; In March 2010, Village View lost nearly $400,000 after the company&rsquo;s bank account was compromised by hackers.&nbsp; The company brought&nbsp;<a href="http://www.villageviewescrow.com/documents/2011-03-15%201st-Amend-Complaint.pdf">suit</a> against Professional Business Bank alleging, among other claims, that the bank failed to comply with the Federal Financial Institutions Examination Council&rsquo;s (FFIEC) authentication guidance from 2005 and other FDIC guidance on identify theft.&nbsp; Specifically, Village View&rsquo;s complaint alleged that the bank used only single factor authentication as opposed to multifactor authentication required by the FFIEC guidance.&nbsp; The company announced that the settlement amount included the full amount of lost funds plus interest from the bank.&nbsp;&nbsp;&nbsp;</p>
<p>The lawsuit and settlement are noteworthy insofar they underscore the potential significance of the FFIEC guidance, including the FFIEC&rsquo;s release in 2011 of a&nbsp;<a href="http://www.ffiec.gov/pdf/Auth-ITS-Final%206-22-11%20(FFIEC%20Formated).pdf">supplement</a> to its authentication guidance, to mitigate both regulatory and litigation risk.&nbsp;&nbsp;&nbsp;</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/litigation/settlement-reached-in-data-security-breach-lawsuit-against-bank/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/litigation/settlement-reached-in-data-security-breach-lawsuit-against-bank/</guid>
         <category domain="http://www.insideprivacy.com/data-security">Data Breaches</category><category domain="http://www.insideprivacy.com/">Data Security</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/united-states">Litigation</category>
         <pubDate>Wed, 20 Jun 2012 11:39:30 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>PCI Council Issues Guidance for Mobile Payment Acceptance</title>
         <description><![CDATA[<p>Yesterday, the Payment Card Industry Council issued&nbsp;<a href="https://www.pcisecuritystandards.org/documents/accepting_mobile_payments_with_a_smartphone_or_tablet.pdf">guidance</a> for merchants using smartphones or tablets to accept payments from customers.&nbsp; The guidance follows up on the PCI Council Chairman&rsquo;s pledge in February,&nbsp;<a href="http://www.insideprivacy.com/united-states/new-pci-council-chairman-establishes-mobile-payments-as-top-priority-for-2012/">as reported in this blog</a>, to make mobile payments a top priority.&nbsp; Payment card readers that can be attached to a smartphone or tablet have become popular in recent years due to portability and cost efficiencies.&nbsp;</p>
<p>The guidance urges merchants to secure account data at the point of capture using validated point-to-point (P2PE) solutions in order to maintain data security throughout the payment lifecycle.&nbsp; A validated P2PE solution ensures that cardholder data is encrypted before it enters the mobile payment acceptance device.&nbsp; These solutions also reduce the scope of merchants&rsquo; PCI compliance obligations.</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/pci-council-issues-guidance-for-mobile-payment-acceptance/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/pci-council-issues-guidance-for-mobile-payment-acceptance/</guid>
         <category domain="http://www.insideprivacy.com/">Data Security</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Thu, 17 May 2012 11:55:44 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>Fiserv Releases White Paper on Multi-Channel Banking</title>
         <description><![CDATA[<p>On April 4, 2012, Fiserv, one of the largest payment processing service providers for the banking industry, released a <a href="http://www.fiserv.com/documents/en/resources/wp-mobile-reshaping-every-banking-channel.pdf?rdeResponseMimetype=application/force-download">white paper</a> analyzing the current state of multi-channel banking, which is a consumer&rsquo;s use of more than one channel to conduct banking activities.&nbsp; The white paper, titled &ldquo;Snacking, Lunching and Fine Dining: How Mobile is Reshaping Every Banking Channel,&rdquo; argues that mobile banking&rsquo;s evolution from informational services, such as balance inquiries and ATM locations, to transactional services, such as bill payment and funds transfers, impacts all three of the primary banking channels: branch banking, online banking, and mobile banking.&nbsp;</p>
<p>The white paper analogizes mobile banking to snacking, online banking to lunching, and branch banking to fine dining based on the consumer&rsquo;s level of interaction with the bank.&nbsp; A consumer&rsquo;s use of mobile banking is akin to snacking because the consumer&rsquo;s interaction is quick and may have a sense of urgency.&nbsp; For example, a consumer may use mobile banking to check his or her balance or pay a bill immediately before its due date.&nbsp; Online banking is similar to lunching in that the interaction is more structured and routine than mobile banking.&nbsp; Online banking is conducive to in-depth and periodic self-service banking activities, including managing budgets and finances.&nbsp; Branch banking is comparable to fine dining because consumers now only rarely visit their local bank branches to conduct banking activities.&nbsp; Typically, consumers visit their bank branches for infrequent consultative services that require substantial interaction.&nbsp;</p>
<p>Optimizing consumers&rsquo; multi-channel banking experiences ultimately will provide a number of benefits to banks and consumers, including increased efficiency from focusing on the delivery of specific services in the particular channel that is the most used by consumers.&nbsp; Privacy and security&nbsp;are one&nbsp;<a href="http://www.insideprivacy.com/united-states/congress/federal-reserve-official-testifies-before-congress-on-mobile-financial-services/">impediment</a>&nbsp;to consumers' adoption&nbsp;of mobile banking services.&nbsp; Accordingly, banks' ability to enhance privacy and security in connection with&nbsp;services delivered&nbsp;through the mobile channel ultimately will&nbsp;help determine the extent to which&nbsp;they profit from multi-channel&nbsp;banking.&nbsp; &nbsp;&nbsp;&nbsp;</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/fiserv-releases-white-paper-on-multi-channel-banking/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/fiserv-releases-white-paper-on-multi-channel-banking/</guid>
         <category domain="http://www.insideprivacy.com/">Data Security</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Fri, 06 Apr 2012 09:22:58 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>Federal Reserve Official Testifies Before Congress on Mobile Financial Services</title>
         <description><![CDATA[<p>On March 29, 2012, Director of the Federal Reserve&rsquo;s Division of Consumer and Community Affairs Sandra Braunstein <a href="http://banking.senate.gov/public/index.cfm?FuseAction=Files.View&amp;FileStore_id=35f312df-40b9-4305-b400-97939358ad54">testified</a>&nbsp;before the Senate Banking Committee on consumers&rsquo; use of mobile financial services.&nbsp; Ms. Braunstein distinguished between &ldquo;mobile banking,&rdquo; which is a consumer&rsquo;s use of a mobile device to interact with a financial institution, including checking balances and transferring funds, and &ldquo;mobile payments,&rdquo; which are purchases, bill payments, charitable donations, or payments to other persons using a mobile device.&nbsp; After making this distinction, she referred to the Federal Reserve&rsquo;s recent <a href="http://banking.senate.gov/public/_files/BraunsteinAddendummobiledevicereport201203.pdf">survey</a>&nbsp;of consumers&rsquo; adoption of mobile banking and mobile payments.</p>
<p>The survey found that the most common reasons for consumers not adopting mobile banking were satisfaction with traditional banking services and concerns over security, including potential hackers and the perceived inadequacy of existing technology.&nbsp; Consumers do not use mobile payments because of security concerns and because traditional payment forms such as cash or credit card can be regarded as being simpler or easier to use.&nbsp;</p>
<p>These findings highlight the progress depository institutions must make to advance consumers&rsquo; use of mobile financial services: namely, enhance information security technology and inform consumers of the effectiveness of such technology.&nbsp; Indeed, the survey concludes that &ldquo;consumers&rsquo; perception that mobile banking and mobile payments are unsecure is currently one of the primary impediments to adoption.&nbsp; If consumers&rsquo; perception of security issues changes&mdash;whether due to actual or perceived improvements&mdash;adoption rates may significantly increase.&rdquo;</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/congress/federal-reserve-official-testifies-before-congress-on-mobile-financial-services/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/congress/federal-reserve-official-testifies-before-congress-on-mobile-financial-services/</guid>
         <category domain="http://www.insideprivacy.com/united-states">Congress</category><category domain="http://www.insideprivacy.com/">Data Security</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/advertising-marketing">Mobile</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Sun, 01 Apr 2012 23:03:09 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
      <item>
         <title>FFIEC Authentication Guidance to be a Hot Topic in 2012</title>
         <description><![CDATA[<p>Last year, the Federal Financial Institutions Examination Council (FFIEC) released a much-anticipated <a href="http://www.ffiec.gov/press/pr062811.htm">supplement</a> to its <em>Authentication in an Internet Banking Environment</em> guidance.&nbsp; The supplement updates the FFIEC&rsquo;s supervisory expectations regarding depository institutions&rsquo; customer authentication, layered security, and other controls for Internet banking.&nbsp; Starting this year, FFIEC information technology examinations will include reviews for compliance with the supplement.&nbsp;</p>
<p>A <a href="http://www.guardiananalytics.com/researchandresources/ffiec-onlinebanking-request.php">study</a> released by Guardian Analytics suggests that institutions are moving towards compliance with the supplement but may not be completely prepared for FFIEC IT examinations to be conducted in 2012.&nbsp; The Guardian Analytics study polled executives at 100 U.S.-based financial institutions in November 2011.&nbsp; The study found that 43 percent of institutions had not yet completed a risk assessment of online banking, and 41 percent had not developed a plan for addressing online banking security gaps.&nbsp; Further, 22 percent of institutions had not reviewed the FFIEC supplement.&nbsp; It is expected that the supplement will be a hot topic throughout 2012 as FFIEC IT examinations reveal the agencies&rsquo; stance on the supplement as well as institutions&rsquo; compliance with the supplement.&nbsp;&nbsp;&nbsp;&nbsp;</p>]]></description>
         <link>http://www.insideprivacy.com/united-states/ffiec-authentication-guidance-to-be-a-hot-topic-in-2012/</link>
         <guid isPermaLink="false">http://www.insideprivacy.com/united-states/ffiec-authentication-guidance-to-be-a-hot-topic-in-2012/</guid>
         <category domain="http://www.insideprivacy.com/">Data Security</category><category domain="http://www.insideprivacy.com/">Financial Institutions</category><category domain="http://www.insideprivacy.com/">Financial Privacy</category><category domain="http://www.insideprivacy.com/">United States</category>
         <pubDate>Tue, 10 Jan 2012 10:16:27 -0500</pubDate>
         <dc:creator>Mike Nonaka</dc:creator>

      </item>
      
   </channel>
</rss>