Norton 360 suddenly identifying home WiFi as public, "suspicious network"

Archive
1

Hello. I'm posting to see if someone can tell me if something that recently began occurring is something to be worried over, or just unfounded paranoia on my end.

Product and OS details: Norton 360, Windows 10

Issue: Private, password-protected, frequently-used Wi-Fi recently reported as public, "suspicious" network when connecting; Norton pop-up message prompts VPN use.

Issue occurs: Whenever connecting to Wi-Fi networks.

Full description and explanation:

Over the past week, Norton has suddenly started flagging my home WiFi as a "suspicious" and public network. Additionally, every time it connects it prompts me to turn on VPN (whether at startup or disconnecting/reconnecting), which I've never used since I really don't have much use for that particular function.

On its own that wouldn't bother me, but the message (see attached image) seems grammatically incorrect ("has weak password" instead of "has a weak password") and the "suspicious network detected" history entry gives no details whatsoever beyond being high risk. Connecting to my Wi-Fi also creates a "connected to a public network entry" along with my MAC address (if memory serves). Both of these security history messages have shown up on separate, private, password-enabled Wi-Fi networks. I don't think I have ever connected the laptop in question to a truly public Wi-Fi network.

The only other thing I can remember was that on the same day it started, I had a window (non-browser) show up saying that there was some kind of connection issue with updating Norton. The message prompted me to restart my computer. I instead opened up Norton 360 proper and tried to update from there. It went through fine. After that, I think the restart-prompting window showed up one more time (I closed it) and then never again.

If this were a long-term thing I had only recently noticed, I wouldn't be concerned, but this only popped up a week ago. No entries of the same type appear in security history before March 7th of 2021. I've tried various scans, including Power Eraser, which haven't turned up any issues. But I'm paranoid enough that the security history messages and slightly weird Norton pop-up are keeping me from accessing anything potentially sensitive on this laptop.

Thanks in advance for any advice on this subject.

2

Alice. This guide will give you ideas about creating a strong password that won't be detected as simplistic. From the article:

According to the traditional advice—which is still good—a strong password:

  • Has 12 Characters, Minimum: You need to choose a password that’s long enough. There’s no minimum password length everyone agrees on, but you should generally go for passwords that are a minimum of 12 to 14 characters in length. A longer password would be even better.
  • Includes Numbers, Symbols, Capital Letters, and Lower-Case Letters: Use a mix of different types of characters to make the password harder to crack.
  • Isn’t a Dictionary Word or Combination of Dictionary Words: Stay away from obvious dictionary words and combinations of dictionary words. Any word on its own is bad. Any combination of a few words, especially if they’re obvious, is also bad. For example, “house” is a terrible password. “Red house” is also very bad.
  • Doesn’t Rely on Obvious Substitutions: Don’t use common substitutions, either — for example, “H0use” isn’t strong just because you’ve replaced an o with a 0. That’s just obvious.

SA

3

If "changing to a strong password will resolve the "suspicious network" warning" that is great, but WHAT does Norton define as a STRONG PASSWORD ? Changing the password is not a simple task when you you have multiple devices, so I want to know what syntax rules Norton uses so I only have to do it once. Thanks ...

 

 

4

I've changed the password which has stopped the "weak" pop-ups and "suspicious network" security history entries. Prior to the password change, performing a network reset, restarting, etc. yielded no change.

5

To peterweb and RK_L, yes changing the Wi-Fi network password removes the message. However, that doesn't resolve the question of why the network's existing password was suddenly being flagged as "weak". It had been unchanged for some months at least, but the network only began being flagged as suspicious on March 7th of this year

Maybe some update to Norton raised the bar a little on the requirements for what is considered a weak password.

 

6

Its been a couple of days since the last check in with you. In your Norton history, under Wifi Security are there any old and or new entries there? Have you gone as far as changing the wifi passcode to something a bit more difficult to decipher? In Windows settings as previously noted, did you perform a network reset and a reboot of the machine to allow Windows to reconnect and run its network checks? Just following up.

SA

7

Thanks for the additional response. Unfortunately, the settings in question were either already as displayed in your attached screenshots, or did not affect the messages.

To peterweb and RK_L, yes changing the Wi-Fi network password removes the message. However, that doesn't resolve the question of why the network's existing password was suddenly being flagged as "weak". It had been unchanged for some months at least, but the network only began being flagged as suspicious on March 7th of this year. Has Norton updated their definitions on what constitutes a weak/strong Wi-Fi password recently?

8

Yes, changing to a strong password will resolve the "suspicious network" warning.

9

cyberblade507

Your image also shows that the password is weak. Maybe that is one if the things that is being flagged. 

10

Thanks for the post back and screenshot. The screeshot doesn't say it has detected a "public" network. Have a look at the settings in the screenshots below. Check Network Trust first to see wha trust level is assigned to the current network you are using, make changes as necessary as it should be PRIVATE. 

network trust in settings.pngNext. I would also check the Public Network Exceptions in the Norton settings as well. 

 

public network exceptions norton 360 .pngSA

11

Windows 10 is 20H2, build 19042.867. Norton is version 22.21.1.151. I've attached the More Options window here. The SSID is the normal Wi-Fi network I connect to.

Unfortunately, the suggested actions in the Windows network settings don't seem to have resolved the issue, unless I've missed something or accidentally did something out of order.

More options.jpg

12

xjoex. Software won't change your network type from private to a public network on the active network being used, malware or a network prob for unpatched hardware and/or drivers is also a possible scenario. Viewing a screenshot of the detection from within the "more options" link in the lower right panel will give a greater detail of what is happening. 

SA

13

What is interesting to me is that it has flagged the network as suspicious and not suspicious activity on the network. Maybe you need to find out what exactly Norton means by suspicious network?

It also indicates high risk as you mentioned but no action required. Those two things seem to be incongruous. If the network is suspicious and high risk you would think it would block it or require some approval from you to proceed.

Also, you said you did a restart because of some pending program changes which as you suspect might be related since it showed up the same day. I think you are on the right track there and would continue to follow that up.

14

What is the Windows 10 version, aka 20H2 and build as an example? What is the Norton product version? The latest should be 22.21.1.151.

Click on "More Options" in that detection entry and please post what it is showing you there. Also have a look at the "available" wifi networks in your settings. I have more than once seen other networks listed on my laptop, AND, checked to auto connect. Unchecking those boxes and a restart cleared them on my system. At times Windows updates will cause weird settings to change this way, we all know all too well Microsoft doesn't QA their update releases in the manner they once did. You may also want to perform a network reset within Windows settings and then restart to see if this continues.

SA