<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: TreasuryDirect enhances security features</title>
	<link>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/</link>
	<description></description>
	<pubDate>Mon, 13 Oct 2008 14:47:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>by: Tom Adams</title>
		<link>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-770</link>
		<pubDate>Mon, 21 Aug 2006 17:32:11 +0000</pubDate>
		<guid>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-770</guid>
					<description>The problem with email notifications mentioned in this article has been fixed. I tested it this morning and received notifications at both the old and new address. For more information, see &lt;a href="http://www.savings-bond-advisor.com/treasurydirect-email-notifications-fixed/" rel="nofollow"&gt;TreasuryDirect email notifications fixed&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>The problem with email notifications mentioned in this article has been fixed. I tested it this morning and received notifications at both the old and new address. For more information, see <a href="http://www.savings-bond-advisor.com/treasurydirect-email-notifications-fixed/" rel="nofollow">TreasuryDirect email notifications fixed</a>.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Charles</title>
		<link>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-763</link>
		<pubDate>Fri, 18 Aug 2006 19:21:17 +0000</pubDate>
		<guid>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-763</guid>
					<description>The fact that the new TD is paperless does add somewhat to the security. In a way, your account # is as good as your password since no statements are sent. When you get your 1099's at the end of the year or a statement, any crook with access to your mail can get your SS#, account# and everything else that is printed and they are good to go.

My local back sent out last years 1099 with my SS# showing under my name thru the plastic window of the envelope :'(</description>
		<content:encoded><![CDATA[<p>The fact that the new TD is paperless does add somewhat to the security. In a way, your account # is as good as your password since no statements are sent. When you get your 1099's at the end of the year or a statement, any crook with access to your mail can get your SS#, account# and everything else that is printed and they are good to go.</p>
<p>My local back sent out last years 1099 with my SS# showing under my name thru the plastic window of the envelope :'(
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: billy</title>
		<link>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-759</link>
		<pubDate>Thu, 17 Aug 2006 22:40:38 +0000</pubDate>
		<guid>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-759</guid>
					<description>A prenote is a zero dollar ACH to give the bank the opportunity to verify the account.  TD does send your account info with it, but it's up to the bank to make sure the account is yours.  They DONT normally do that since ACH rules only require them to check that the account exists, hence, the risk  of fraud.

If the bank is liable....well...good luck in trying to collect.

The big risk is what could happen if a crook gets your password.</description>
		<content:encoded><![CDATA[<p>A prenote is a zero dollar ACH to give the bank the opportunity to verify the account.  TD does send your account info with it, but it's up to the bank to make sure the account is yours.  They DONT normally do that since ACH rules only require them to check that the account exists, hence, the risk  of fraud.</p>
<p>If the bank is liable&#8230;.well&#8230;good luck in trying to collect.</p>
<p>The big risk is what could happen if a crook gets your password.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: jon</title>
		<link>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-758</link>
		<pubDate>Thu, 17 Aug 2006 22:11:26 +0000</pubDate>
		<guid>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-758</guid>
					<description>I believe Reg E applies to any electronic transaction like ACH.  If I'm a victim of fraud in a bank to bank ACH transfer, I'm covered (by the bank).  TD uses ACH (no protection).

Investment accounts have SIPC (an FDIC equivalent).</description>
		<content:encoded><![CDATA[<p>I believe Reg E applies to any electronic transaction like ACH.  If I'm a victim of fraud in a bank to bank ACH transfer, I'm covered (by the bank).  TD uses ACH (no protection).</p>
<p>Investment accounts have SIPC (an FDIC equivalent).
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mario</title>
		<link>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-750</link>
		<pubDate>Thu, 17 Aug 2006 02:36:16 +0000</pubDate>
		<guid>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-750</guid>
					<description>I'm actually more worried about elaborate schemes, such as when someone gains access to your TD account, changes the registration such that they are co-owner, gives themselves transact rights, then transfers the security to their account and deposits in their bank account.

Therefore I think registration changes are probably the weakest link, and should require something like TD sending you an email that prompts you to verify by logging back into your account before the change becomes effective. And email changes should require the same such that the thief can't change the email to theirs.

Tom, please forward ideas to your TD contacts ... ;)</description>
		<content:encoded><![CDATA[<p>I'm actually more worried about elaborate schemes, such as when someone gains access to your TD account, changes the registration such that they are co-owner, gives themselves transact rights, then transfers the security to their account and deposits in their bank account.</p>
<p>Therefore I think registration changes are probably the weakest link, and should require something like TD sending you an email that prompts you to verify by logging back into your account before the change becomes effective. And email changes should require the same such that the thief can't change the email to theirs.</p>
<p>Tom, please forward ideas to your TD contacts &#8230; <img src='http://www.savings-bond-advisor.com/wp/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Mario</title>
		<link>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-749</link>
		<pubDate>Thu, 17 Aug 2006 02:27:44 +0000</pubDate>
		<guid>http://www.savings-bond-advisor.com/treasurydirect-enhances-security-features/#comment-749</guid>
					<description>Billy, thanks for providing all the information. In the PIA you linked, it does say "financial institutions provide the initial defense against fraudulent or unauthorized transactions" which implies to me that the Treasury pushes the responsibility to the banks - which makes logistic sense, because anyone who knows your account number could otherwise attempt an ACH; generally speaking for an ACH debit, do we know if the liability lies with the bank that requests the ACH or the bank thar receives the request?

They also say in that document that the names you provided on the account are transmitted to the bank. I would assume the Treasury would at least flag the transaction if you don't provide your own name; and the bank would hopefully flag if the name doesn't match the name on file for the account. I think ideally they should also transmit SSN because two people could have the same name.

I don't see that as being very different from a prenotification, where it is also the bank which verifies account ownership.</description>
		<content:encoded><![CDATA[<p>Billy, thanks for providing all the information. In the PIA you linked, it does say "financial institutions provide the initial defense against fraudulent or unauthorized transactions" which implies to me that the Treasury pushes the responsibility to the banks - which makes logistic sense, because anyone who knows your account number could otherwise attempt an ACH; generally speaking for an ACH debit, do we know if the liability lies with the bank that requests the ACH or the bank thar receives the request?</p>
<p>They also say in that document that the names you provided on the account are transmitted to the bank. I would assume the Treasury would at least flag the transaction if you don't provide your own name; and the bank would hopefully flag if the name doesn't match the name on file for the account. I think ideally they should also transmit SSN because two people could have the same name.</p>
<p>I don't see that as being very different from a prenotification, where it is also the bank which verifies account ownership.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
