<?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>Ludwig &#38; Robinson PLLC &#187; FDIC</title>
	<atom:link href="https://www.ludwigrobinson.com/blog/?feed=rss2&#038;tag=fdic" rel="self" type="application/rss+xml" />
	<link>https://www.ludwigrobinson.com/blog</link>
	<description>Blog</description>
	<lastBuildDate>Fri, 29 Jan 2021 20:22:53 +0000</lastBuildDate>
	<language>en-US</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>https://wordpress.org/?v=3.8.41</generator>
	<item>
		<title>Banking Regulators Issue Joint Statement on Heightened Cybersecurity Risk</title>
		<link>https://www.ludwigrobinson.com/blog/?p=180</link>
		<comments>https://www.ludwigrobinson.com/blog/?p=180#comments</comments>
		<pubDate>Wed, 29 Jan 2020 22:35:31 +0000</pubDate>
		<dc:creator><![CDATA[Ludwig &#38; Robinson PLLC]]></dc:creator>
				<category><![CDATA[BANKING & FINANCE]]></category>
		<category><![CDATA[CORPORATE]]></category>
		<category><![CDATA[INSURANCE]]></category>
		<category><![CDATA[INTERNATIONAL]]></category>
		<category><![CDATA[LITIGATION]]></category>
		<category><![CDATA[Business Continuity Plans]]></category>
		<category><![CDATA[Cyber Insurance]]></category>
		<category><![CDATA[Cybercrime]]></category>
		<category><![CDATA[Cybersecurity]]></category>
		<category><![CDATA[Data Breach]]></category>
		<category><![CDATA[Data Protection]]></category>
		<category><![CDATA[Data Recovery]]></category>
		<category><![CDATA[FDIC]]></category>
		<category><![CDATA[Funds Transfer]]></category>
		<category><![CDATA[Identity Management]]></category>
		<category><![CDATA[IT]]></category>
		<category><![CDATA[Malware]]></category>
		<category><![CDATA[Multifactor Authentication]]></category>
		<category><![CDATA[OCC]]></category>
		<category><![CDATA[Risk Management]]></category>
		<category><![CDATA[Salvatore Scanio]]></category>
		<category><![CDATA[Social Engineering]]></category>
		<category><![CDATA[UCC Article 4A]]></category>

		<guid isPermaLink="false">http://www.ludwigrobinson.com/blog/?p=180</guid>
		<description><![CDATA[On January 16, 2020, the FDIC and OCC issued a joint statement (FDIC FIL-3-2020 , OCC Bulletin 2020-5) to remind banks of sound cybersecurity risk management principles.  The statement observes, “Cyber actors often use malware to exploit weaknesses in a [bank’s] &#8230; <a href="https://www.ludwigrobinson.com/blog/?p=180">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<p>On January 16, 2020, the FDIC and OCC issued a joint statement (<a href="https://www.fdic.gov/news/news/financial/2020/fil20003.pdf" target="_blank">FDIC FIL-3-2020</a> , <a href="https://www.occ.gov/news-issuances/bulletins/2020/bulletin-2020-5a.pdf" target="_blank">OCC Bulletin 2020-5</a>) to remind banks of sound cybersecurity risk management principles.  The statement observes, “Cyber actors often use malware to exploit weaknesses in a [bank’s] computers or networks. They often obtain access to financial institution systems and networks by compromising user credentials and introducing malware through social engineering [bank] employees and contractors with phishing or spear phishing attacks.”</p>
<p>The Joint Statement focuses on six key aspects of cybersecurity risk management, which we summarize as follows:</p>
<p><b><i>Response, Resilience, and Recovery Capabilities.  </i></b>Maintain comprehensive, documented, and current incident and business resilience plans that include responding to and recovering from a destructive cyber attack.  One consideration is the use of cyber insurance as part of a broader risk management strategy.</p>
<p><b><i>Identity and Access Management.  </i></b>Use and validate the effectiveness of authentication controls, such as multifactor authentication, to segment and safeguard access to critical systems and data on the network.</p>
<p><b><i>Network Configuration and System Hardening.  </i></b>Review the appropriateness of default system settings, change default user profiles, configure security settings, implement security monitoring tools, and apply security updates and system patches.</p>
<p><b><i></i></b><b><i>Employee Training.  </i></b>Ongoing employee training on recognizing cyber threats, phishing, and suspicious links.</p>
<p><b><i></i></b><b><i>Security Tools and Monitoring.  </i></b>Use qualified cybersecurity staff or provider to actively monitor systems for network threat and vulnerability information available from industry sources.</p>
<p><b><i></i></b><b><i>Data Protection.  </i></b>Maintain a data classification program to identify sensitive and critical data.  Encrypt or tokenize sensitive and critical data in transit and at rest.</p>
<p>The Joint Statement is the latest in a growing line of cybersecurity regulations applicable to banks.  For a discussion of relevant guidelines, see L&amp;R’s latest article, Robert W. Ludwig, Salvatore Scanio, and Joseph Szary, <i>Technology and Salvage: Using Social Media in Recovery and Allocating Cybercrime Funds Transfers to Third Parties</i>, Am. Bar Ass’n, Tort Trial &amp; Insurance Practice Section, Fidelity and Surety Law 2020 Midwinter Conference, Jan. 31, 2020, at 25-30.</p>
<p>Like other banking agency guidelines, the Joint Statement also expands the guideposts for evaluating whether bank security procedures are commercially reasonable under UCC Article 4A. <i>See, e.g.,</i> <i>Patco Constr. Co., Inc. v. People’s United Bank,</i> 684 F.3d 197, 201-04 (1<sup>st</sup> Cir. 2012).</p>
<p>For further information, contact Salvatore Scanio at sscanio@ludwigrobinson.com or 202-289-7605.</p>
]]></content:encoded>
			<wfw:commentRss>https://www.ludwigrobinson.com/blog/?feed=rss2&#038;p=180</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
