<?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>Steal This Data &#187; shared passwords</title>
	<atom:link href="http://steal-this-data.com/tag/shared-passwords/feed/" rel="self" type="application/rss+xml" />
	<link>http://steal-this-data.com</link>
	<description>A Information Security Guide for Small and Medium Sized Businesses</description>
	<lastBuildDate>Mon, 01 Dec 2008 01:19:31 +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>The Problem with Shared Usernames and Passwords</title>
		<link>http://steal-this-data.com/2008/11/the-problem-with-shared-usernames-and-passwords/</link>
		<comments>http://steal-this-data.com/2008/11/the-problem-with-shared-usernames-and-passwords/#comments</comments>
		<pubDate>Mon, 17 Nov 2008 14:06:57 +0000</pubDate>
		<dc:creator>earlylit</dc:creator>
				<category><![CDATA[Password Management]]></category>
		<category><![CDATA[access control]]></category>
		<category><![CDATA[authentication]]></category>
		<category><![CDATA[shared passwords]]></category>
		<category><![CDATA[shared usernames]]></category>

		<guid isPermaLink="false">http://steal-this-data.com/?p=99</guid>
		<description><![CDATA[&#160;A lot of small to medium sized companies use shared passwords to access information in their internal IT&#160;systems or managed using remote managed services. They do this to subvert internal IT&#160;groups that may be too slow to enable information access or to reduce licensing costs with external providers who price their services using a per [...]


No related posts.]]></description>
			<content:encoded><![CDATA[<p>&nbsp;A lot of small to medium sized companies use shared passwords to access information in their internal IT&nbsp;systems or managed using remote managed services. They do this to subvert internal IT&nbsp;groups that may be too slow to enable information access or to reduce licensing costs with external providers who price their services using a per user cost.</p>
<p>From an information security standpoint, using shared passwords is a bad idea for several reasons:</p>
<ul>
<li>It will cause you to fail a security audit. Almost all state regulations on personally identifiable information and industry regulatory standards such as PCI DSS, HIPAA, Sarbanes Oxley, or Gramm-Leach-Bliley prohibit the use of shared user names and passwords.</li>
<li>It causes more work for your IT&nbsp;group, particularly when an employee resigns or is terminated, because the shared password must be changed and everyone using it must be informed.</li>
<li>If any information is inappropriately changed or stolen, you have no way of determining which individual is responsible.</li>
<li>The use of shared passwords will likely increase your liability if you are sued for an information security breach.</li>
</ul>
<p>Here&#8217;s what you have to do to:</p>
<ol>
<li>Identify every internal or outsourced service that your company uses to manage information. This can be an eye opener: you may use a lot more systems for this purpose than your realize.&nbsp;</li>
<li>Identify each individual who must have access to information in each internal or remote system. Your IT&nbsp;group should keep this information up to date in a matrix so that it can be easily referenced in the event of an <a href="http://steal-this-data.com/2008/11/defining-an-employee-termination-policy/">employee termination</a>, transfer or during an security incident investigation.&nbsp;</li>
<li>When an new employee is hired, determine which information systems they need access to. Incorporate this into your new employee IT&nbsp;provisioning process. In addition, channel all new requests for information access through your IT group so that they can keep their records up to date.</li>
<li>Create an information systems acceptable use policy, distribute it to all of your employees, and have them sign it. Include provisions in this agreement that prohibit the sharing of user names and passwords between employees or 3rd parties.</li>
<li>Systematically create new user names and passwords for individuals who have been sharing them and distribute them.</li>
</ol>
<p>&nbsp;</p>
<a class="a2a_dd addtoany_share_save" href="http://www.addtoany.com/share_save?linkurl=http%3A%2F%2Fsteal-this-data.com%2F2008%2F11%2Fthe-problem-with-shared-usernames-and-passwords%2F&amp;linkname=The%20Problem%20with%20Shared%20Usernames%20and%20Passwords"><img src="http://steal-this-data.com/wp-content/plugins/add-to-any/share_save_171_16.png" width="171" height="16" alt="Share/Bookmark"/></a>

<p>No related posts.</p>]]></content:encoded>
			<wfw:commentRss>http://steal-this-data.com/2008/11/the-problem-with-shared-usernames-and-passwords/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
