<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Protecting Your Financial Data: Mint’s Approach to Security</title>
	<atom:link href="http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/</link>
	<description>The blog of the free, simple personal finance solution. Track all your spending automatically, find the best deals, save more money. And save the world.</description>
	<lastBuildDate>Fri, 20 Nov 2009 20:48:42 -0800</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Lestat</title>
		<link>http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/comment-page-1/#comment-32808</link>
		<dc:creator>Lestat</dc:creator>
		<pubDate>Sat, 11 Jul 2009 10:30:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/#comment-32808</guid>
		<description>I guess it is a great thing that something can now secure our financial information. It somehow lessened our worries of having our accounts or even identity hacked by some skilled hacker.</description>
		<content:encoded><![CDATA[<p>I guess it is a great thing that something can now secure our financial information. It somehow lessened our worries of having our accounts or even identity hacked by some skilled hacker.
<div class="like" id="rateboxComment_32808" style="height: 18px;"><a style="cursor: pointer;" onclick="loadContentC(this, 'like', '32808');"> like</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Darren</title>
		<link>http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/comment-page-1/#comment-13850</link>
		<dc:creator>Darren</dc:creator>
		<pubDate>Thu, 03 Jan 2008 00:16:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/#comment-13850</guid>
		<description>Hi Aaron,
Have you seen this?
http://www.davidairey.co.uk/google-gmail-security-hijack/
That&#039;s an interesting hack: basically any website that you might be logged into that anyone else can sign up for as well, could possibly become a target. A user just has to mimic a form post.  Your site&#039;s security seems to handle this by nature: there would be no account number, password etc that a person could steal. But I thought it would be worth mentioning, since the solution seems simple enough: submit and validate the current session ID for every request. A hacker couldn&#039;t duplicate that without cross-site scripting or something.

Looks like a great product, I&#039;m seriously thinking about it!
Cheers!
~Darren</description>
		<content:encoded><![CDATA[<p>Hi Aaron,<br />
Have you seen this?<br />
<a href="http://www.davidairey.co.uk/google-gmail-security-hijack/" rel="nofollow">http://www.davidairey.co.uk/google-gmail-security-hijack/</a><br />
That&#8217;s an interesting hack: basically any website that you might be logged into that anyone else can sign up for as well, could possibly become a target. A user just has to mimic a form post.  Your site&#8217;s security seems to handle this by nature: there would be no account number, password etc that a person could steal. But I thought it would be worth mentioning, since the solution seems simple enough: submit and validate the current session ID for every request. A hacker couldn&#8217;t duplicate that without cross-site scripting or something.</p>
<p>Looks like a great product, I&#8217;m seriously thinking about it!<br />
Cheers!<br />
~Darren
<div class="like" id="rateboxComment_13850" style="height: 18px;"><a style="cursor: pointer;" onclick="loadContentC(this, 'like', '13850');"> like</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Patzer</title>
		<link>http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/comment-page-1/#comment-13835</link>
		<dc:creator>Aaron Patzer</dc:creator>
		<pubDate>Wed, 02 Jan 2008 19:20:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/#comment-13835</guid>
		<description>John,

Specifically what I mean is that no data vulnerabilities have been found in our end production code shipped to users.

A long while ago (early 2007, before launch), we had a PHP error in one dynamic banner ad page that could have allowed cross-site scripting.  However, this was not on the product domain (https://wwws.mint.com), nor could any data have been exposed even if the product had been launched.</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>Specifically what I mean is that no data vulnerabilities have been found in our end production code shipped to users.</p>
<p>A long while ago (early 2007, before launch), we had a PHP error in one dynamic banner ad page that could have allowed cross-site scripting.  However, this was not on the product domain (<a href="https://wwws.mint.com)" rel="nofollow">https://wwws.mint.com)</a>, nor could any data have been exposed even if the product had been launched.
<div class="like" id="rateboxComment_13835" style="height: 18px;"><a style="cursor: pointer;" onclick="loadContentC(this, 'like', '13835');"> like</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wendy Leece</title>
		<link>http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/comment-page-1/#comment-13771</link>
		<dc:creator>Wendy Leece</dc:creator>
		<pubDate>Wed, 02 Jan 2008 06:10:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/#comment-13771</guid>
		<description>I signed on today. But now that I am signed on, I am a  little dubious that all that personal info is in someone else&#039;s hands and they have access to it. How do I know I am protected?</description>
		<content:encoded><![CDATA[<p>I signed on today. But now that I am signed on, I am a  little dubious that all that personal info is in someone else&#8217;s hands and they have access to it. How do I know I am protected?
<div class="like" id="rateboxComment_13771" style="height: 18px;"><a style="cursor: pointer;" onclick="loadContentC(this, 'like', '13771');"> like</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: john andrews</title>
		<link>http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/comment-page-1/#comment-13418</link>
		<dc:creator>john andrews</dc:creator>
		<pubDate>Sat, 29 Dec 2007 00:13:06 +0000</pubDate>
		<guid isPermaLink="false">http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/#comment-13418</guid>
		<description>Wow. I applaud your transparency (the comment here, for example). But I am put off by &quot;to date, no one has found any data vulnerabilities&quot;. That seems so unnatural, it suggests trouble. Either your employees are inhuman, or your audits are limited, or reporting is not comprehensive, or something. There are always msitakes, and the more you catch the safer you are, right? But you&#039;re not catching any (?)

I appreciate the secure colo bit, but again... I&#039;ve been in datacenters with &quot;biometric security&quot; that was turned off pending a visit from the repairman, &quot;locked&quot; cages where the key was kept in the lock for convenience, etc. Rather than describe how &quot;pick proof&quot; your locks are, what&#039;s happens when someone notices scratches on the lock? Or won&#039;t they notice?

I want to trust you guys... I really do ;-)</description>
		<content:encoded><![CDATA[<p>Wow. I applaud your transparency (the comment here, for example). But I am put off by &#8220;to date, no one has found any data vulnerabilities&#8221;. That seems so unnatural, it suggests trouble. Either your employees are inhuman, or your audits are limited, or reporting is not comprehensive, or something. There are always msitakes, and the more you catch the safer you are, right? But you&#8217;re not catching any (?)</p>
<p>I appreciate the secure colo bit, but again&#8230; I&#8217;ve been in datacenters with &#8220;biometric security&#8221; that was turned off pending a visit from the repairman, &#8220;locked&#8221; cages where the key was kept in the lock for convenience, etc. Rather than describe how &#8220;pick proof&#8221; your locks are, what&#8217;s happens when someone notices scratches on the lock? Or won&#8217;t they notice?</p>
<p>I want to trust you guys&#8230; I really do <img src='http://www.mint.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />
<div class="like" id="rateboxComment_13418" style="height: 18px;"><a style="cursor: pointer;" onclick="loadContentC(this, 'like', '13418');"> like</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Patzer</title>
		<link>http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/comment-page-1/#comment-12921</link>
		<dc:creator>Aaron Patzer</dc:creator>
		<pubDate>Sat, 22 Dec 2007 05:35:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/#comment-12921</guid>
		<description>David,

Yes, we do have internal security audits, network architecture audits, and physical infrastructure audits as well.  We work with two outside agencies for security consulting and penetration testing...to date, no one has found any data vulnerabilities.

I didn&#039;t mention in the main post, but we also have serious physical security.  Our servers are in an unmarked colocation facility which requires a biometric scanner to unlock.  After guards, the &quot;man-trap&quot; hallway, several more biometric scanners, and cameras monitoring both the servers and power supplies 24/7, we have our own locked cage (not shared with any other companies), locked server racks, and encrypted hard-drives beyond that.  In total, there are 7-layers of physical security...we take this stuff seriously.

Aaron</description>
		<content:encoded><![CDATA[<p>David,</p>
<p>Yes, we do have internal security audits, network architecture audits, and physical infrastructure audits as well.  We work with two outside agencies for security consulting and penetration testing&#8230;to date, no one has found any data vulnerabilities.</p>
<p>I didn&#8217;t mention in the main post, but we also have serious physical security.  Our servers are in an unmarked colocation facility which requires a biometric scanner to unlock.  After guards, the &#8220;man-trap&#8221; hallway, several more biometric scanners, and cameras monitoring both the servers and power supplies 24/7, we have our own locked cage (not shared with any other companies), locked server racks, and encrypted hard-drives beyond that.  In total, there are 7-layers of physical security&#8230;we take this stuff seriously.</p>
<p>Aaron
<div class="like" id="rateboxComment_12921" style="height: 18px;"><a style="cursor: pointer;" onclick="loadContentC(this, 'like', '12921');"> like</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Mackey</title>
		<link>http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/comment-page-1/#comment-12911</link>
		<dc:creator>David Mackey</dc:creator>
		<pubDate>Sat, 22 Dec 2007 02:39:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/#comment-12911</guid>
		<description>I like a lot of what you guys have to say about security. Do you have internal security audits besides HackerSafe? HackerSafe, in its default scans, does not scan any pages that are behind an authentication page. Thus while the outside pages might be secure, this doesn&#039;t say anything about vulnerabilities once a user has logged in.</description>
		<content:encoded><![CDATA[<p>I like a lot of what you guys have to say about security. Do you have internal security audits besides HackerSafe? HackerSafe, in its default scans, does not scan any pages that are behind an authentication page. Thus while the outside pages might be secure, this doesn&#8217;t say anything about vulnerabilities once a user has logged in.
<div class="like" id="rateboxComment_12911" style="height: 18px;"><a style="cursor: pointer;" onclick="loadContentC(this, 'like', '12911');"> like</a></div>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Patzer</title>
		<link>http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/comment-page-1/#comment-12875</link>
		<dc:creator>Aaron Patzer</dc:creator>
		<pubDate>Fri, 21 Dec 2007 16:06:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.mint.com/blog/updates/protecting-your-financial-data-mint%e2%80%99s-approach-to-security/#comment-12875</guid>
		<description>If you have any questions on Mint.com security, I&#039;m happy to answer them.

Aaron Patzer
Founder &amp; CEO, Mint.com</description>
		<content:encoded><![CDATA[<p>If you have any questions on Mint.com security, I&#8217;m happy to answer them.</p>
<p>Aaron Patzer<br />
Founder &amp; CEO, Mint.com
<div class="like" id="rateboxComment_12875" style="height: 18px;"><a style="cursor: pointer;" onclick="loadContentC(this, 'like', '12875');"> like</a></div>
]]></content:encoded>
	</item>
</channel>
</rss>
