<?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>Security Fight Club &#187; Internal Threats</title>
	<atom:link href="http://www.securityfightclub.com/category/security/internal-threats/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.securityfightclub.com</link>
	<description>Brought to you by Awareness Technologies</description>
	<lastBuildDate>Sat, 05 Jun 2010 04:08:44 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>T-Mobile UK Employees have been seeing your information</title>
		<link>http://www.securityfightclub.com/t-mobile-uk-employees-have-been-seeing-your-information/</link>
		<comments>http://www.securityfightclub.com/t-mobile-uk-employees-have-been-seeing-your-information/#comments</comments>
		<pubDate>Wed, 25 Nov 2009 19:00:05 +0000</pubDate>
		<dc:creator>mrdenny</dc:creator>
				<category><![CDATA[Data Loss]]></category>
		<category><![CDATA[Internal Threats]]></category>
		<category><![CDATA[T-Mobile]]></category>

		<guid isPermaLink="false">http://www.securityfightclub.com/?p=174</guid>
		<description><![CDATA[OK, so the title is a little more scary than needed, but it did the job, and got you to look at the article.
Customers at T-Mobile UK have been found to have been selling customer information to data brokers who work on behalf of other cellular phone companies in the UK.Obviously T-Mobile wasn&#8217;t aware that [...]]]></description>
			<content:encoded><![CDATA[<p>OK, so the title is a little more scary than needed, but it did the job, and got you to look at the article.</p>
<p>Customers at T-Mobile UK have been found to have been <a href="http://news.bbc.co.uk/2/hi/uk_news/8364421.stm" target="_blank">selling customer information</a> to data brokers who work on behalf of other cellular phone companies in the UK.<span id="more-174"></span>Obviously T-Mobile wasn&#8217;t aware that this was happening. However they needed to put more projections in place to ensure that this didn&#8217;t happen. Hopefully other companies will learn from this data breach and ensure that their employees aren&#8217;t selling off customer data.  I can&#8217;t stress enough that this wasn&#8217;t an external break-in.  This was employees selling customer data which they got from the customer management system.</p>
<p>I also hope that the prosecution of people responsible for this data theft and sale makes the next person think twice about doing this.  As the case moves forward I&#8217;ll be sure to post updates here.</p>
<p>Denny</p>
]]></content:encoded>
			<wfw:commentRss>http://www.securityfightclub.com/t-mobile-uk-employees-have-been-seeing-your-information/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>If the user doesn&#8217;t know the password a few times, lock&#8217;em out</title>
		<link>http://www.securityfightclub.com/if-the-user-doesnt-know-the-password-a-few-times-lockem-out/</link>
		<comments>http://www.securityfightclub.com/if-the-user-doesnt-know-the-password-a-few-times-lockem-out/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 18:43:39 +0000</pubDate>
		<dc:creator>mrdenny</dc:creator>
				<category><![CDATA[Brute Force Cracking]]></category>
		<category><![CDATA[External Threats]]></category>
		<category><![CDATA[Internal Threats]]></category>
		<category><![CDATA[Passwords]]></category>
		<category><![CDATA[SQL Server]]></category>

		<guid isPermaLink="false">http://www.securityfightclub.com/?p=121</guid>
		<description><![CDATA[One of the easiest things that you can do to keep people from guessing passwords is to slow them down.  Obviously I don&#8217;t mean do tell the person to try to log in less frequently, that just wouldn&#8217;t make any sense.  When someone is knocking on your computer&#8217;s door and trying a brute force password [...]]]></description>
			<content:encoded><![CDATA[<p>One of the easiest things that you can do to keep people from guessing passwords is to slow them down.  Obviously I don&#8217;t mean do tell the person to try to log in less frequently, that just wouldn&#8217;t make any sense.  When someone is knocking on your computer&#8217;s door and trying a brute force password attack, make them slow down.<span id="more-121"></span>Every system, either Internet facing or not (but especially Internet facing) should be configured so that if the wrong password is used to many times the account is automatically locked out for some period of time (more than a few minutes, less than a day) unless you have a secure way for users to verify who they are and reset there password.  If you have this sort of secure method to verify someone and reset there password, preferably in some sort of automated fashion you should do this and lock the account out until an administrator unlocks it (or customer service/help desk if this is your line of business app) or until the user resets the password.</p>
<p>In a perfect world this should be done at all layers of your application, both at the front end and at the back end.  At the front end, this is usually easy, as you control the application, and the code that goes into it.  Adding a module like this is pretty easy.  On the back end you&#8217;ve got less options available to you.  You are pretty much at the mercy of your database vendor on this one.</p>
<p>However the database vendors have heard our requests for more security in the platforms and they have begun to respond.  As an example <a href="http://www.microsoft.com/sql/" target="_blank">Microsoft SQL Server</a> has since the release of SQL Server 2005 included the ability to have the SQL Logons follow the same security requirements as Windows Logons on the Windows Active Directory domain.  (Other database vendors may offer similar features, but as I mostly use Microsoft SQL Server I&#8217;m not aware of them.  If you are please feel free to comment below.)</p>
<p>Now with this comes some risk.  Because if you were to enable these settings and someone did try to break into the database server using this account, the account would lock out.  This is both good and bad.  Its good because they aren&#8217;t able to continue the attack, however its also bad because your business application isn&#8217;t able to log into the database either.</p>
<p>Open source apps such as WordPress are starting to get these features added into them.  There&#8217;s a plugin for WordPress called &#8220;<a href="http://www.bad-neighborhood.com/" target="_blank">Login LockDown</a>&#8221; which allows the WordPress admin site to lock it self down if the same person gets the password wrong more than <em>n</em> number of times.  The options are totally configurable by the blog owner, so you can set your settings as high or as low as you want.</p>
<p>So, what&#8217;s the point of all this you ask?  It&#8217;s pretty simple, and it is easier when you look at the math.  Assume you wanted to attack a system which takes 1/10th of a second to check a password.  Using the characters on the standard keyboard (letters, numbers, symbols) you&#8217;ve got ~94 characters to work with.  Assuming an 4 character password of say &#8220;test&#8221; there are 78074896 character combination to try.  Assuming you try all the combination (just to make sure you get the correct password) it will take about 90 days to test all the options.  Now if every 5 failed attempts we lock the account for one hour that test times goes from 90 days to 3012 years (if I&#8217;m done my math correctly).</p>
<p>The next question then becomes, why would anyone take 90 days to break my password.  The answer is that they wouldn&#8217;t.  They would use more than one machine to reduce that 90 days down to a more manageable number.  If using 10 computers and you break with workload up evenly across the 10 computers that 90 days, is now 9 days.  20 computers will get it done in 4.5 days.  50 computers will get it done in 1.8 days.  All of a sudden by simply throwing a few computers at the problem the password gets broken very quickly.  Now longer passwords will make this take longer, but if you have a system which people really want to break into they could get access to one of the large <a href="http://en.wikipedia.org/wiki/Botnet" target="_blank">botnets</a> and have 100,000 computers work on breaking into your site.  Even with a very strong password, it wouldn&#8217;t take all that long to brute force your way into your passwords.</p>
<p>The only sure fire way to stop someone from brute forcing there way into your accounts is to lock those accounts after the password has been tried incorrectly several times.  Don&#8217;t make the limits to low that your customers can get into there own services, but don&#8217;t make them so loose that people can break into those services.</p>
<p>Denny</p>
]]></content:encoded>
			<wfw:commentRss>http://www.securityfightclub.com/if-the-user-doesnt-know-the-password-a-few-times-lockem-out/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Keep those workstations locked</title>
		<link>http://www.securityfightclub.com/keep-those-workstations-locked/</link>
		<comments>http://www.securityfightclub.com/keep-those-workstations-locked/#comments</comments>
		<pubDate>Tue, 13 Oct 2009 18:44:45 +0000</pubDate>
		<dc:creator>mrdenny</dc:creator>
				<category><![CDATA[Data Loss]]></category>
		<category><![CDATA[External Threats]]></category>
		<category><![CDATA[Internal Threats]]></category>
		<category><![CDATA[Networks]]></category>
		<category><![CDATA[Browser Security]]></category>
		<category><![CDATA[Domain Policies]]></category>
		<category><![CDATA[Passwords]]></category>
		<category><![CDATA[Security]]></category>

		<guid isPermaLink="false">http://www.securityfightclub.com/?p=113</guid>
		<description><![CDATA[Everyone in IT knows who you don&#8217;t leave your workstation unlocked when you leave your desk.  It&#8217;s because your co-workers will send fart jokes to the boss from your machine as punishment.  However there are actual security reasons for not leaving your machine unlocked.
When you leave your workstation unlocked you are giving anyone that walks [...]]]></description>
			<content:encoded><![CDATA[<p>Everyone in IT knows who you don&#8217;t leave your workstation unlocked when you leave your desk.  It&#8217;s because your co-workers will send fart jokes to the boss from your machine as punishment.  However there are actual security reasons for not leaving your machine unlocked.<span id="more-113"></span></p>
<p>When you leave your workstation unlocked you are giving anyone that walks by access to everything on your computer.  Your email, access to the company intranet, etc.  Anything that you have access to without entering a username and password (or that has a saved username and password) they have access to.</p>
<p>Have iTunes installed on your work computer with a credit card saved in it so you can grab the new song that just came out?  So do they.  They could download 10,000 songs on your account and you wouldn&#8217;t know it until the next time you opened iTunes or checked your credit card statement.  (I&#8217;m assuming that iTunes will save your credit card, I don&#8217;t actually use it but you get the idea.)</p>
<p>Have usernames and passwords saved in your browser so you can easily log into various websites like your bank, credit cards, forums, etc?  So does anyone who sits at your computer.</p>
<p>You are probably sitting there thinking to your self, if some strange person was sitting at my desk, someone would notice.  They might, but probably not.  Lots of times I&#8217;ve had strange people sitting in my chair waiting for me with no one around to question them.</p>
<p>If you have an office, you aren&#8217;t exempt.  Yes I know that you lock your office door at night.  Look around your office, do you have a trash can sitting in there somewhere?  Do you use it?  Is it empty in the morning?  The magic trash can fairy doesn&#8217;t clean out your trash.  Someone who makes way to little money to clean up after the slobs in the office (sorry I&#8217;m projecting a little here, or depending on your office maybe I&#8217;m not) comes in and cleans it out and dusts your desk off.  You know how they get in, either they have a key or the guards open the doors for them.</p>
<p>I know that one company I worked at everyone who had an office would be gone by 7pm.  At about 9pm the security guards would come around and unlock every single office from the lowest manager to the highest C level exec.  I know this because I worked swing there as a Database Engineer for several years (pretty much every department except for Marketing was staffed 24&#215;7 365 days a year).  After the guards would open the offices the cleaning crew would come through and clean all the offices, empty the trash, etc.  Some offices had a window to the inside of the building, some didn&#8217;t.  Most had blinds that could be closed for privacy.  Lost of people had only a laptop, many were left at the office on weeknights, and many people had a desktop.  I would say that 80% of offices had a computer in them at night.</p>
<p>How hard would it be for an outside person to pay someone from the cleaning crew $5000 to get them to copy some data to a USB drive, or infect the network with a virus?  That&#8217;s probably more than most people on the cleaning crew make in a month for just a few minutes of work.  To most people, especially in this economy this would probably be to much money to pass up.</p>
<p>If a competitor (or an employee for that matter) wanted access to data that was private, and we didn&#8217;t have a policy in place to automatically lock the computers, it would have been a piece of cake for someone to sit at a desk and download all sorts of confidential data from the persons computer.  All without anyone knowing about it.</p>
<p>Fortunately at this company we had a policy which required the computers to lock them selves, but many smaller companies don&#8217;t enable this feature for one reason or another.</p>
<p>If your computer isn&#8217;t locked when you get to work in the morning I urge you to talk to your IT staff and have them enable auto-locking on the company computers.  It&#8217;s a slight annoyance to have to unlock your computer in the morning, but it&#8217;s much better than having someone walk in and simply take all your personal and corporate data.</p>
<p>Denny</p>
]]></content:encoded>
			<wfw:commentRss>http://www.securityfightclub.com/keep-those-workstations-locked/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Mirroring isn’t a backup solution</title>
		<link>http://itknowledgeexchange.techtarget.com/sql-server/mirroring-isnt-a-backup-solution/</link>
		<comments>http://itknowledgeexchange.techtarget.com/sql-server/mirroring-isnt-a-backup-solution/#comments</comments>
		<pubDate>Tue, 21 Jul 2009 23:48:11 +0000</pubDate>
		<dc:creator>SQL Server with Mr. Denny &#62; Security » Security</dc:creator>
				<category><![CDATA[Data Loss]]></category>
		<category><![CDATA[Databases]]></category>
		<category><![CDATA[Internal Threats]]></category>
		<category><![CDATA[SQL Server]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[Syndicated]]></category>
		<category><![CDATA[Backup & recovery]]></category>
		<category><![CDATA[Database security]]></category>
		<category><![CDATA[JournalSpace.com]]></category>
		<category><![CDATA[SQL Injection]]></category>
		<category><![CDATA[SQL Server with mrDenny]]></category>

		<guid isPermaLink="false">tag:itknowledgeexchange.techtarget.com://8d6d0f149ad03e1b750353d5f507940d</guid>
		<description><![CDATA[In case you live under a rock and haven't heard about Journalspace.com's little mistake, they have gone out of business due to a database problem.  Here's a screenshot in case the site is down when you look at it.

In a nutshell it appears that they were relying on a RAID1 ...]]></description>
			<content:encoded><![CDATA[In case you live under a rock and haven't heard about Journalspace.com's little mistake, they have gone out of business due to a database problem.  Here's a screenshot in case the site is down when you look at it.

In a nutshell it appears that they were relying on a RAID1 ...]]></content:encoded>
			<wfw:commentRss>http://www.securityfightclub.com/mirroring-isn%e2%80%99t-a-backup-solution/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
