The following was written by Equity Trust Company Chief Information Security Officer Jason Nester.
Since modifying our password policies to encourage the usage of “passphrases” and adding MultiFactor Authentication to our logon process, we have received a lot of great feedback and questions from our customers. Four specific questions have popped up more than others, and I wanted to take a moment to address them.
Why are your password policies different from everyone else?
This is the question we receive most often, and it is also the most important aspect of our new policies. Being different from other online services was exactly our goal.
Prior to our policy change, nearly every successful unauthorized logon to a myEQUITY.com account could be traced back to a compromise of a different website that the customer utilized. Due to customers reusing the same password across multiple websites, a single breach elsewhere allowed the attacker to access other website accounts, including myEQUITY.
We specifically designed our new policy to be unique from other websites to help prevent customers from reusing a common password, thereby providing better security for their myEQUITY accounts. So far, this policy change has proven to be very effective.
Video: myEQUITY Security Enhancements
Doesn’t MultiFactor Authentication remove the risk of unauthorized logons?
MultiFactor certainly helps reduce this risk, which is why we have deployed it. However, our records show that an overwhelming majority of our customers chose the least secure option of SMS/Voice when enrolling into our MultiFactor program rather than following our recommendation to use a MultiFactor application installed on their smartphone.
SMS is the weakest form of multifactor authentication and has several attack vectors. The most prevalent method of attacking SMS authentication is by tricking, or even bribing, employees at mobile phone stores to transfer control of a cellular number to a device under the control of the attacker. Your cellphone carrier likely employs tens of thousands of people who have the ability to transfer your phone number to another device. Each of these employees is a potential attack target for someone trying to gain access to your account.
Password reuse is also an issue here, as it is reasonable to expect customers who regularly reuse passwords do so on their cellular provider’s website as well. This provides an avenue for an attacker to make changes to a customer’s cell phone plan without their knowledge.
Recently, security reporter Brian Krebs wrote an excellent article detailing a far simpler and faster way for attackers to gain access to SMS text messages which I would encourage everyone to read.
In short, while we believe that adding MultiFactor Authentication to our logon process has greatly improved the security of our customers, we do not believe this to be a foolproof solution, and additional precautions must be taken to keep our customer’s accounts safe from attack.
How do you expect customers to remember unique passwords for every website?
We encourage customers to consider using a password manager application. This is an application you can install on your computer and/or smartphone that allows you to securely store your passphrases and passwords. The password manager is itself secured by a master password or by biometric controls such as fingerprint and face scanning. The result is that you only need to remember your master password, and that will give you access to all of your other passwords.
Furthermore, many of these applications are excellent at auto-populating the username and password fields of websites, meaning that the logon process becomes considerably faster and easier for the user. An up-to-date list of available password managers can be found on Wikipedia.
Additionally, we heavily encourage you to utilize a “passphrase” rather than a password. A passphrase is simply a sentence or collection of words. Passphrases are great because they are very easy to remember, but much more difficult to guess or crack.
What about account lockout policies?
This deals with the other common tactic for compromising accounts: Brute force logon attempts. During a brute force attack, an attacker tries to gain access to accounts by trying numerous common passwords.
A common misconception is that these attacks focus on a single username and attempt thousands of different passwords. If this were the case, account lockout policies after multiple incorrect attempts would indeed prevent the attacker from being successful. However, the way these attacks actually work is by trying the same common password across numerous usernames. This attack technique assumes that out of thousands of user accounts at least a few are likely to be using a simple, common password, and it is just a matter of time to find one. These attacks are often run slowly over many days, weeks, or even months in an attempt to stay under the radar.
At Equity Trust, we heavily monitor these brute force logon attempts and gather data about what the attackers are trying. Unsurprisingly, what we see is that over 75 percent of the passwords attempted in these attacks are below our minimum password policy requirements.
For the remaining 25 percent of logon attempts, the passwords are drawn almost entirely from publicly shared “password dumps” resulting from compromised websites, which we also prevent our customers from inadvertently using. These statistics show that our policies are effective in keeping our customers safe.
I hope these responses help explain the logic behind our passphrase and MultiFactor policies. These decisions were made specifically to help keep our customers’ assets safe from attackers, and we hope that our customers can appreciate our commitment to their account security. Attack techniques are ever-changing, and at Equity Trust we are constantly monitoring these changes to ensure that we have the appropriate defenses in place.
Join over 100,000 subscribers who receive investing and wealth-building news and education in their inbox.
You are leaving trustetc.com to enter the ETC Brokerage Services (Member FINRA/SIPC) website (etcbrokerage.com), the registered broker-dealer affiliate of Equity Trust Company. ETC Brokerage Services provides access to brokerage and investment products which ARE NOT FDIC insured. ETC Brokerage does not provide investment advice or recommendations as to any investment. All investments are selected and made solely by self-directed account owners.
We use cookies to improve your experience on our site. By using our site, you consent to cookies.
Cookie Preferences
When you visit our website, we and our vendors use cookies and other online tracking technologies ("Cookies") to enhance user experience, analyze website performance and traffic, and provide marketing and advertising.
We use certain Cookies to enable the website to function, including for website security and to remember your settings and privacy preferences. These Cookies are always active. You can set your browser to block or alert you about these Cookies, but if you block these Cookies, some parts of the website may not function properly.
A sale of personal information can refer to disclosures of personal information to third parties who may use the information for their own purposes, such as Cookie vendors. Similarly, sharing personal information refers to disclosing personal information to third parties for cross-context behavioral advertising. In this context we sell and share personal information through our website. If you would like to opt out of sales and sharing for cross-context behavioral, please opt out of the Targeting and Analytics sections below. If you choose to use the Global Privacy Control (GPC) browser signal, you will be opted out of sales and sharing for cross-context behavioral advertising associated with the browser for which you have enabled the signal. If you use multiple browsers or devices, you will need to activate the signal for each one that you use.
You can manage your Cookies at any time by clicking the "Do Not Sell or Share My Personal Information" link in the footer of the website.
Please see our Privacy Policy for more information about our privacy practices.
These Cookies are necessary for the website to function and are always active. These Cookies are used, for example, for the security of our website and to administer your privacy preferences. You may configure your browser to block or alert you about these Cookies, but some parts of the website may not function properly if you do so.
Name
Description
Duration
Geolocation Config
This cookie is used to store the consent settings based on the visitor's location.
365 days
Cookie Preferences
This cookie is used to store the user's cookie consent preferences.
365 days
CloudFlare provides web performance and security solutions, enhancing site speed and protecting against threats.
The _cfuvid cookie is only set when a site uses this option in a Rate Limiting Rule, and is only used to allow the Cloudflare WAF to distinguish individual users who share the same IP address.
session
cf_clearance
Whether a CAPTCHA or Javascript challenge has been solved.
session
__cfseq
Sequence rules uses cookies to track the order of requests a user has made and the time between requests and makes them available via Cloudflare Rules. This allows you to write rules that match valid or invalid sequences. The specific cookies used to validate sequences are called sequence cookies.
session
cf_ob_info
The cf_ob_info cookie provides information on: The HTTP Status Code returned by the origin web server. The Ray ID of the original failed request. The data center serving the traffic
session
cf_use_ob
The cf_use_ob cookie informs Cloudflare to fetch the requested resource from the Always Online cache on the designated port. Applicable values are: 0, 80, and 443. The cf_ob_info and cf_use_ob cookies are persistent cookies that expire after 30 seconds.
session
__cfwaitingroom
The __cfwaitingroom cookie is only used to track visitors that access a waiting room enabled host and path combination for a zone. Visitors using a browser that does not accept cookies cannot visit the host and path combination while the waiting room is active.
session
cf_chl_rc_i
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_ni
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
cf_chl_rc_m
These cookies are for internal use which allows Cloudflare to identify production issues on clients.
session
__cfruid
Used by the content network, Cloudflare, to identify trusted web traffic.
session
__cf_bm
Cloudflare's bot products identify and mitigate automated traffic to protect your site from bad bots. Cloudflare places the __cf_bm cookie on End User devices that access Customer sites that are protected by Bot Management or Bot Fight Mode. The __cf_bm cookie is necessary for the proper functioning of these bot solutions.
session
__cflb
When enabling session affinity with Cloudflare Load Balancer, Cloudflare sets a __cflb cookie with a unique value on the first response to the requesting client. Cloudflare routes future requests to the same origin, optimizing network resource usage. In the event of a failover, Cloudflare sets a new __cflb cookie to direct future requests to the failover pool.
session
Google Tag Manager loads the site's other analytics and advertising tags. It sets no cookies of its own; each tag it loads is listed under its own category and only runs with the consent that category requires.
Set on m.stripe.com to help Stripe detect fraudulent payments.
2 years
These Cookies help us understand how visitors interact with our website by collecting information about usage, traffic, and website performance. This information helps us improve the website and user experience.
Crazy Egg records how visitors scroll, click and move through pages (heatmaps and session recordings). Form fields are masked before any data leaves the browser.
Set by Cloudflare on Unbounce's content domain (js.ubembed.com) to distinguish people from automated traffic.
30 minutes
These Cookies are used by us and our advertising and marketing partners to deliver more relevant content and advertisements. They may collect information about your browser, device, and interactions across websites to help tailor advertising and measure campaign effectiveness.
Google Ads measures the results of advertising and builds audiences for showing relevant ads.
One cookie per offer (the name ends in the offer ID), recording that the visitor has already seen it.
30 days
_omappvs
Records the current visit, to decide which offers to show.
20 minutes
_omappvp
Records that the visitor has been to the site before, to decide which offers to show.
13 months
These Cookies enable enhanced features and personalisation, such as remembering your preferences and providing additional functionality. They may be set by us or our vendors. If disabled, certain website features may not operate as intended.
Calendly provides appointment scheduling for booking a consultation. The cookies below are set by Calendly's content delivery network.