<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" 
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:admin="http://webns.net/mvcb/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd">
	<channel>
<title>News</title><link>http://www.coreim.com/index.html</link><description>Hot News&#x21;</description><dc:language>en</dc:language><dc:creator>joe@coreim.com</dc:creator><dc:rights>Copyright 2008 Joseph Compton</dc:rights><dc:date>2008-05-21T15:51:41-04:00</dc:date><admin:generatorAgent rdf:resource="http://www.realmacsoftware.com/" />
<admin:errorReportsTo rdf:resource="mailto:joe@coreim.com" /><sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>
<lastBuildDate>Wed, 21 May 2008 15:52:13 -0400</lastBuildDate><item><title>GLBA Security Program</title><dc:creator>joe@coreim.com</dc:creator><dc:subject>News</dc:subject><dc:date>2008-05-21T15:51:41-04:00</dc:date><link>http://www.coreim.com/News/files/b8dd4e4c99784bc15cba2aefcf672c6b-1.html#unique-entry-id-1</link><guid isPermaLink="true">http://www.coreim.com/News/files/b8dd4e4c99784bc15cba2aefcf672c6b-1.html#unique-entry-id-1</guid><content:encoded><![CDATA[Tackling the information security mandates of the Gramm &ndash; Leach &ndash; Bliley Act (GLBA) can be a challenge for any sized community bank. The core issue for compliance is building a GLBA Security Program.<br /><br />The heart of this program is a series of short policies that outline and define risk areas that each bank&rsquo;s management and board of directors must develop, implement, and monitor. In our view, to be compliant with GLBA, a bank must develop a GLBA Security Program that touches on nine different areas. Bank management needs to create:<br /><br />	1.	A departmental risk assessment policy<br />	2.	A bank-wide vendor management policy<br />	3.	An I.T. security policy<br />	4.	An acceptable use / confidentiality policy (signed by users)<br />	5.	A document and media retention policy<br />	6.	A business continuity and disaster recovery plan supported by business impact analysis worksheets<br />	7.	An employee security training policy<br />	8.	An internal and external I.T. audit policy (which should include the I.T. penetration test that most people associate with 		GLBA).<br />	9.	An incident response program<br /><br />These elements will allow more efficient technology and security compliance management. For more details, call today!]]></content:encoded></item><item><title>Site Update</title><dc:creator>joe@coreim.com</dc:creator><dc:subject>News</dc:subject><dc:date>2008-05-21T15:50:48-04:00</dc:date><link>http://www.coreim.com/News/files/d888d4dec3604adfbc7c24d31fc02345-0.html#unique-entry-id-0</link><guid isPermaLink="true">http://www.coreim.com/News/files/d888d4dec3604adfbc7c24d31fc02345-0.html#unique-entry-id-0</guid><content:encoded><![CDATA[We have updated the format of our site to be mobile phone friendly.  Stay tuned for more activity.]]></content:encoded></item></channel>
</rss>