Securing your Email is IMPORTANT!!


Recommended Posts

When it comes to securing your online accounts with a strong password and two-factor authentication, one of the most IMPORTANT online accounts to secure is your email.

 

When a password is forgotten on a website, the password reset link is usually sent to your email (or a code is sent to your phone if you have two-factor authentication turned on). If someone got a hold of your email password, they could go to sites around the internet, resetting your website passwords (by having reset links sent to your email account which they now have access to) giving them complete access.

 

In the case of Gmail (which is a google account), it may be used to sync your chrome browser. If someone gets access to it, they also get access to any saved passwords saved inside chrome for other websites.

 

Your email is 1 password you DO NOT want to reuse! When creating a password, NEVER use a word found in the dictionary all by itself. Pad it with something, add some punctuation. For instance, take the word microscope. That word used by itself is a HORRIBLE password, but padding it with more characters makes it dramatically more secure. Let’s put a date and some punctuation on the end of it. Now we have microscope1954*!# This is a MUCH stronger password.

 

Strong, secure password are hard to remember, I get that. So don’t feel bad about writing your passwords down, in fact I highly encourage it! I’m much less concerned about someone breaking into your house steeling your book of passwords, than I am about someone hacking your email account because you reused / used a weak password.

 

Online services such as Gmail, Outlook and Yahoo typically won’t let you use a horrible password without adding a capital letter and some numbers (but they will obviously let you reuse one). 

 

Most email providers also support two-factor authentication. When enabled, you must provide a second factor of authentication when logging into your online account after providing the correct password.

 

The two types of Two-factor for your email are typically

 

SMS : A SMS message (Text message) is texted to your phone with a one time use code - This is the least secure two-factor method, but it is still more secure with it than without it.

 

Authenticator: Once enable you scan a provided QR code into an authenticator phone/tablet app of your choosing (Example, Google Authenticator or the Microsoft Authenticator) with your camera and the app will then generate a 1 time code every 30 seconds. 

 

If you use the Authenticator method I recommend saving the QR code that you initially scan into the authenticator, so you can scan that same QR again into the same phone (should you have to reset it) or in to a new phone (should something happen to your current one).

 

Two-factor codes are typically required when the email site detects a new login from a browser or computer it has not seen before.

 

So just remember, if your email password is not unique, change it! If your email password contains a just a single dictionary word, change it! If your email provider supports two-factor authentication but it's not enabled, turn it on! Your email is the single greatest point of failure of your online identity.

Link to comment
https://www.neowin.net/forum/topic/1385127-securing-your-email-is-important/
Share on other sites

12 hours ago, Steven P. said:

Or use two-factor authentication, then you can have a weak ass password all you like, but you aren't getting in without the second step auth.

That isn't true at all. 2FA isn't the end all and isn't a guarantee you are safe. 

2 hours ago, Steven P. said:

Thread cleaned, please stay on topic.

It's ok Steve, I don't mind if my threads go off topic, Off topic is still comments, comments still bump me to the front page, front page gives me views :)

Hello,

 

A properly-engineered, properly-implemented and properly-used multi-factor authentication system can greatly increase the security of account logins by providing resistance against brute-forcing, password-reset attacks and so forth.  Of course, if the second factor is vulnerable to phone (SIM or account) resets, token theft, biometric spoofing, and so forth, then a large amount of additional security layer is mitigated.

 

Regards,

 

Aryeh Goretsky

On 7/24/2019 at 1:53 AM, Circaflex said:

That isn't true at all. 2FA isn't the end all and isn't a guarantee you are safe. 

Many security experts are saying that if you use 2fa you never have to change your password again. 

 

Right now, there is no known way to bypass 2fa or get the code/onetime auth key without having your device.  It is better to use a token that is registered to your device via an authenticator app vs a password.  If you know of a way to bypass/circumvent 2fa, I am sure all of us would like to know.

2 hours ago, sc302 said:

Right now, there is no known way to bypass 2fa

Depends what the 2fa method is.

SMS can for sure be circumvented - there are many know hacks to this. Pretty sure nist has or is dropping it as valid/recommended method even.

This is why the 3 points of @goretsky "A properly-engineered, properly-implemented and properly-used" are so critical - and can tell you for pretty much fact the weakest link in that chain is going to properly used point "user"... 

 

And there are multiple ways to get around other 2fa.. mitm sort of attacks, mitendpoint, compromised software, etc. etc..

here

https://www.rsaconference.com/writable/presentations/file_upload/idy-f02-12-ways-to-hack-2fa.pdf

So saying there is no known way is just not true..

 

3 minutes ago, BudMan said:

Depends what the 2fa method is.

SMS can for sure be circumvented - there are many know hacks to this. Pretty sure nist has or is dropping it as valid/recommended method even.

This is why the 3 points of @goretsky "A properly-engineered, properly-implemented and properly-used" are so critical - and can tell you for pretty much fact the weakest link in that chain is going to properly used point "user"... 

 

You are right a PAYG phone and a weak password written on a post it note stuck on the computer screen just isn't enough!

Also, malware on the device that would forward the 2FA. This would be more of a whaling type scenario though. Also, if you have a device that was compromised or you wrote your secret that is used to generate the 2FA token and it was stolen, by passing 2FA would be fairly easy. 

 

Always have the application/software alert you of any new logins. This would help incase it was compromised. 

On 7/23/2019 at 10:55 PM, warwagon said:

When it comes to securing your online accounts with a strong password and two-factor authentication, one of the most IMPORTANT online accounts to secure is your email.

Very true! I secure my personal and professional email accounts with crazy long passwords generated by LastPass, and behind TOTP 2FA. And my LastPass password is even longer, again behind 2FA. Finally, I change these 3 passwords and a few other critical ones once a month. :)

2 hours ago, BudMan said:

Depends what the 2fa method is.

SMS can for sure be circumvented - there are many know hacks to this. Pretty sure nist has or is dropping it as valid/recommended method even.

This is why the 3 points of @goretsky "A properly-engineered, properly-implemented and properly-used" are so critical - and can tell you for pretty much fact the weakest link in that chain is going to properly used point "user"... 

 

And there are multiple ways to get around other 2fa.. mitm sort of attacks, mitendpoint, compromised software, etc. etc..

here

https://www.rsaconference.com/writable/presentations/file_upload/idy-f02-12-ways-to-hack-2fa.pdf

So saying there is no known way is just not true..

 

sorry, going back several years to when rsa key was the standard.  I should know to stay up on knowBe4

2 hours ago, The Dark Knight said:

Very true! I secure my personal and professional email accounts with crazy long passwords generated by LastPass, and behind TOTP 2FA. And my LastPass password is even longer, again behind 2FA. Finally, I change these 3 passwords and a few other critical ones once a month. :)

Ya, I don't change mine once a month. That just sounds like a pain, give I have 8 gmail address :D

Change my important passwords usually every 6 months, which is coming due again,  I used to do it around Windows new releases, but I got a little behind this year,  but will get it done in a day or two, and make accounts more secure again.    Then I should be set,   might setup Microsoft Authenicator as well,  I do have Google setup with clicking yes or no on login if it's me from my Galaxy S10e.

 

Too much trouble trying to change every account password, but I know I should again, just know it's gonna take a while

 

11 hours ago, bikeman25 said:

Change my important passwords usually every 6 months

You guys need to keep up, and I have always said this - changing passwords for the sake of changing passwords is BS.. And the guy  that wrote the standard has come out and said as much.

 

NIST now clearly states

"“SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically).”"

 

Unless something has happened, someone left the company.  There has been some breach or something... Changing your password because its been 90 days has always just been utter ######.. And you know what it does do - it forces people to write ###### down ;)

9 minutes ago, BudMan said:

You guys need to keep up, and I have always said this - changing passwords for the sake of changing passwords is BS.. And the guy  that wrote the standard has come out and said as much.

 

NIST now clearly states

"“SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically).”"

 

Unless something has happened, someone left the company.  There has been some breach or something... Changing your password because its been 90 days has always just been utter ######.. And you know what it does do - it forces people to write ###### down ;)

When I first started working, I needed to remember three fairly complex passwords all of which needed to be changed every 90 days. And like you said, in the end I wrote my passwords down. 

2 hours ago, BudMan said:

You guys need to keep up, and I have always said this - changing passwords for the sake of changing passwords is BS.. And the guy  that wrote the standard has come out and said as much.

 

NIST now clearly states

"“SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically).”"

 

Unless something has happened, someone left the company.  There has been some breach or something... Changing your password because its been 90 days has always just been utter ######.. And you know what it does do - it forces people to write ###### down ;)

Forcing users to change their password every 90 days also forces them to rotate ###### passwords

2 minutes ago, Steven P. said:

## # ### isn't a great password :s 

Why does the 4 letter swear word that starts with S ends with T show up as ###### <------6 characters long ... now they don't know what swear word I was going for, so then I have to edit it so it has the correct amount of ####

2 minutes ago, warwagon said:

Why does the 4 letter swear word that starts with S ends with T show up as ###### <------6 characters long ... now they don't know what swear word I was going for, so then I have to edit it so it has the correct amount of ####

Because at the time moderators didn't want swear words to have the same amount of characters so that people could instantly fill in the word by themselves, it was requested to use a generic term, which is what I did. (and another fine example of how I don't decide everything on my own).

2 hours ago, BudMan said:

You guys need to keep up, and I have always said this - changing passwords for the sake of changing passwords is BS.. And the guy  that wrote the standard has come out and said as much.

 

NIST now clearly states

"“SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically).”"

 

Unless something has happened, someone left the company.  There has been some breach or something... Changing your password because its been 90 days has always just been utter ######.. And you know what it does do - it forces people to write ###### down ;)

Ya, I always thought changing passwords just for the sake of it or due to number of days was dumb as dirt. Can't even begin to remember last time I changed my passwords! Don't know a single person that's changed their passwords. Don't know of a single person that's ever had their e-mail hacked or anything either.

Still required to change passwords every 90 days for various work related sites/government sites.  Some of them have to be around 15 characters ... can't use x number of characters previously used (so you can't just go up a digit or whatever) ... 

 

Though the work related sites are slowly but surely transitioning away from username/password to CAC card/pin number.  Praise baby Jesus.

3 hours ago, BudMan said:

You guys need to keep up, and I have always said this - changing passwords for the sake of changing passwords is BS.. And the guy  that wrote the standard has come out and said as much.

 

NIST now clearly states

"“SHOULD NOT require memorized secrets to be changed arbitrarily (e.g., periodically).”"

 

Unless something has happened, someone left the company.  There has been some breach or something... Changing your password because its been 90 days has always just been utter ######.. And you know what it does do - it forces people to write ###### down ;)

100% 

 

I used to change my entire list every 90 days. What a fool I was. I was using LastPass at the time and have since migrated to BitWarden and have always used strong, tool generated passwords, often at the length limit of the site. I was changing these for no reason.  Today I continue to use strong passwords (as should everyone) and 2FA when available with a preference to time based values over SMS codes. Changing a 23 character password that I never knew to start with every 90 days was foolish and a monumental waste of time.  

 

I just wish my employer would stop making us change them every 90 days AND allowed us to use a password manager.

  • 4 weeks later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • This whole dumb age verification thing needs to die and be replaced by giving parents tools to control devices. Why am I required to plaster my ID all over the internet to prove I'm old enough when parents should be the ones dictating what their kids are doing on their phones. Apple released great set of tools for iPhones coming to iOS 27 that do just that. Why are governments not mandating that kind of control to phone makers to built them into phones. This whole thing is so absolutely idiotic it's wild.
    • Remeber this decade, when the free internet died... tell your grand kids about this, record there reaction and post it on InstaTwitBook.com
    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code by Paul Hill Image via Pexels The UK government, just like many state governments in the US and national governments around the world, has begun going on a bit of a power trip when it comes to digital safety. The major step taken so far is the introduction of the Online Safety Act, which requires users to prove their age to access adult websites (it includes more than this, too). Now, UK PM Keir Starmer is calling on Apple and Google, and presumably other mobile OS makers, to scan phones for explicit images to protect children. This potentially mandatory on-device scanning by vendor-controlled software will create unacceptable harms to individual freedoms and transparency, and introduce massive surveillance risks. In a statement on June 8, the Prime Minister stated that big tech companies, such as Apple and Google, must add features to their platforms, such as iOS and Android, that will detect and block sexually explicit or nude images involving under-18s on phones or tablets. Adults who want to take or send nudes would be required to hand over some form of identification to stop their phone from blocking these pictures, creating unnecessary privacy risks. According to the government, it wants to see these measures implemented within three months; otherwise, the government will introduce legislation to force them to introduce such technology. The legislation will include fines for companies and maybe even criminal liability for tech bosses who do not comply with the measures. In its announcement, the government said that stopping users from taking, sending, or receiving nudes without verifying their age is technically feasible, and pointed to a British firm called SafeToNet, which has made proprietary, closed-source, uninstallable software called HarmBlock and is actively selling a device with it enabled and is working with other OEMs. The fact that this software is closed source is a huge problem because it’s a black box; you do not know what it is doing on your device. The fact that it is unremovable is also a problem because you lose control of a phone that you own. Laughably, the government, just before highlighting SafeToNet, says that companies must introduce such measures “without threatening privacy or collecting any data.” It then says over-18s will still be able to view adult content by providing proof of age… Which sounds to me like data collection. SafeToNet makes some debatable claims about HarmBlock The government’s example software, HarmBlock, is a hugely alarming choice to espouse the virtues of this type of software. SafeToNet claims that HarmBlock is “ethically developed,” but this is the opposite of the truth. This black box software puts digital handcuffs on you if it’s installed in your device, taking away your freedom to control what software runs on your device, as it cannot be removed. It is not even free software, so we cannot inspect the source code to see what it is doing. For all we know, it could be acting maliciously. While that’s unlikely, we can’t verify that it’s not doing that. When Google and Apple do inevitably integrate these features on devices in the UK, they are very likely to be closed-source binaries, which will also be non-auditable. They will also have identity services built into them, which will require at least temporary collection of sensitive identity documents to verify your age. One saving grace for Android users is that this nudity blocker will very likely be implemented within the Google Play infrastructure that’s deeply tied into commercial Android devices. However, anyone with enough determination to throw out Google apps from their phone by flashing a custom ROM could find they regain control over their phone again without these digital handcuffs. Obviously, this is only how I expect Google to implement the feature; if it bakes it into the open-source Android somehow, that would be bad news for anyone looking to escape it. Outside of stripping mobile phone users of their freedom and sovereignty over their devices, these proprietary on-device machine learning or hash-matching solutions cannot be independently audited. This means that hackers could potentially exploit them because security researchers can’t investigate the code, and they could overstep their intended use case and collect even more user data without anybody knowing. We also wouldn’t know if the code is prone to detecting false positives or biased classification, because we can’t see the code. In the government’s announcement, contributing comments from the Internet Watch Foundation keep talking about “on-device protections” as if to say that users don’t need to worry about server-side processing; however, this is misleading, as data could flow from devices for the purpose of updates, remote model changes, telemetry, or server-side matching. We’ve also seen with the Online Safety Act that the government is never content with the laws it introduces; it always wants to expand the controls. If this scanning functionality arrives on devices, it might only block nudes initially, but later governments could pressure vendors for expanded access or use mandated features for other surveillance aims. The introduction of on-device scanners opens the door to massive risks in the future. Once nude blocking becomes normalized, regulators like Ofcom or politicians themselves could push for more controls over people’s devices. Very possible candidates for blocking include hate speech, misinformation, or undesirable political content. Also, there is a chance that once Apple and Google have developed this software, they might attempt to reuse the infrastructure for commercial or foreign requests, putting customers in greater danger. Just the UK's demand for this sets a precedent. What if a dictatorship decides to spy on activists by demanding that Google or Apple implement similar controls? Another concern with this scanning is that it adds compliance costs for businesses looking to get into the mobile operating system space. While Google and Apple dominate the space right now, there are lots of smaller companies creating mobile operating systems too, including community projects with very shallow pockets. How are these smaller competitors supposed to implement sophisticated nudity detectors? Simply put, they can’t. Then the government goes after them, causes them to shut down, and Google and Apple have less competition. Image via Aurora Store For us users who value sovereignty over our technology, this development will force us to seek freedom-respecting alternatives. The simplest path forward will likely be to install a custom ROM on an Android device; however, kicking Google off the phone with its black box nudity blocker could also make it harder to access apps such as banking apps, which tend to need you to pass Google's integrity checks. Thankfully, Google Play Store apps can still be obtained by storefronts such as the Aurora Store, but it just adds to the friction. To be fair to those pushing this measure to protect children, I think it will be reasonably effective, but people will still try to find ways around it, just as they’ve done with age gates on adult websites introduced under the Online Safety Act. In the effort to find circumvention methods, it could lead users to join riskier platforms that introduce new dangers. This effort also diverts resources from proven interventions such as law enforcement cooperation, targeted investigations, education, and support services to broad technical controls that have uncertain effectiveness (due to their newness). If the government is set on introducing such tools, then there ought to be safeguards in place. Any mandated code should be released as free software so that it can be audited, and the binaries should be reproducible builds so that the public knows nothing has been tampered with in the code used to create the binaries shipped out. Ideally, these tools should also be voluntary, opt-in, and even community-run. This would also allow people to have full control over their hardware while allowing parents to flip a switch to turn on these protections for children, with the knowledge that the code being run is doing exactly what it says on the tin, and nothing nefarious, like a black box solution could be doing. The government should also have a narrow legal scope where this technology stays with blocking nudes and not spreading to blocking political opinions, hate speech, and so on. Ideally, any implementation should avoid identity-linked age verification to keep user data safe, and matching should be done locally with no server telemetry to ensure it is truly on-device. While I do understand that stakeholders such as parents want to keep children safe, the potential for abuse with this type of software is colossal. It would entrench black-box surveillance and take away our freedom to use our devices as we want. There is also the acute risk that the government will demand this surveillance be expanded to block other activities, which could be particularly dangerous. If you are in the UK and don’t wish to see these measures implemented, it is still possible to write to your MP, which could lead to some better safeguards being introduced before it’s too late. Once we get more technical information about how this will be implemented, then we will be able to see if de-Googling Android devices will bypass this measure. For anyone with an iPhone, there is zero chance that you’ll be able to take off these handcuffs because Apple doesn’t let you mess with your software.
    • I'm reading the reports as EU rejecting Apple's proposal because Trusted System Agent would be an intermediary offered to third party AI's (this article is also worded as such) but Siri AI itself would not pass this intermediary. This would cause a situation where Siri AI would have more direct system access and offer it an unfair advantage. (speaking from EU regulator perspective here) Apple is citing security issues with doing what EU asked for, and I think this also supports this theory, because truly direct system access like Siri AI would make it impossible to control third party AI's running on the devices and e.g. reign them in via adjustments to Trusted System Agent. So, I _think_ this is the sticking point right now: EU saying they need to be on equal footing as Siri AI, Apple saying they can't be because Apple only trusts their own AI. Apple could of course be leaning a bit extra hard towards this because they're biased in terms of excluding competitors. One method to find an agreement would be to have Siri AI also run through Trusted System Agent and treat it as untrusted. This kind of defensive architecture design (especially when involving an AI) would honestly not be a very bad idea from a sheer engineering standpoint. But then Apple would need to swallow their pride and adapt worldwide due to EU, and make perhaps major updates delaying Siri AI once more.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!