Webroot SecureAnywhere Discussion & Update Thread

I can try to find out but they don't like giving out details.

Thanks,

Daniel

 

Since the Release of v9.0.10.17, for Beta Testers only expect a new Beta v9.0.10.19 as some have reported!

Daniel

 

Hi @Cache here is the extra info I received from Product Manager Brad West!

Thanks,

Daniel

 

Many thanks Daniel - that is much appreciated!

 

You're very Welcome! But remember what Brad said "Sure. This additional information is not particularly sensitive but it is “internal”." so as i said they really don't like giving details but for this is was Okay!

Thanks,

Daniel

 

Beta testers notice the Web Filter and Web Filter Driver is now at 1.2.0.51 this is a fix for the Driver failing at times!

For ones that what to turn on Verbose Logging for the Web Filter you can do these steps in the registry if your comfortable in doing so! Also note when the Web Filter changes the setting needs to be redone after each Web Filter update.

"Also Webroot is not in any way responsible or liable if anyone makes changes to the Registry."

 

current Security program giving grief again so, thinking of going back to WebrootAV.
Remain unsure (in my mind) what/how Webroot re W8.1/10 does for Outbound traffic.

I'm aware Webroot relies on WinFW for Inbound traffic (and Outbound).
I'm unsure as to whether Webroot re W8.1/10 > manages Outbound / hardens Outbound / protects Outbound / ?.

1) How would I describe to a novice what Webroot does for Outbound traffic with respect to WinFW default allow.
2) How would I describe to a geek what Webroot does for Outbound traffic with respect to WinFW default allow.

3) Does Webroot influence on WinFW Outbound traffic invoke either Webroot or WinFW Outbound traffic Alert/Dialog..?
Thanks

 

The granular firewall controls will be back for Windows 8, 8.1 and 10 users but there is no timetable and it does say in process https://community.webroot.com/t5/Id...tions-fw-control-in-Win-8-Win-8-1/idi-p/60003 ! Now WSA still has and outbound smart Firewall if any malware is trying to call out will be blocked with a pop-up the same with anything suspicious! And yes it must be used with Windows Firewall or another Firewall of your choice to have full inbound and outbound protection:

 

Okay, are pre-configured filters default/same for all....or, are filters configured related to my programs / my running processes.
And for example, will Webroot alert re Chrome Software Reporter Tool.
Current Security alerts for e.g., Chrome SRT, alerts for program license verify, alerts for new program install call home, alerts for that which I have not opted Always Allow. And I can allow/block/reset FW Program Controls.
I'll be disappointed sans granular firewall control, I'm used to....

 

It's a Cloud Based Smart Firewall and the granular firewall controls will be back! Chrome Software Reporter Tool is not Malicious so would not be blocked, but when the new firewall controls are back then you can block whatever you like so have patience! Also the Firewall Controls are still there in XP, Vista and Windows 7.

 

Okay, it's cloud based smart FW. So, generic traffic filters are cloud based, so heavy lifting in the cloud.
Hmm, so Outbound traffic deemed safe, no alert. Similar to downloads deemed safe, no alert.
I'm used to toaster for new events regardless. I B patient....Thanks!

 

Well I have been Beta testing Glasswire for that reason but when the Firewall controls come back in WSA it will be gone as it is only a outbound firewall as well.

 

Q: what's suggest re browser built-in phishing and malware protection with respect to Webroot Shields/Filtering Extension. Okay to leave On or suggest turn Off browser built-in phishing malware protection. Might browser built-in phishing malware protection bump Webroot Shields/Filtering Extension.

 

Statistically speaking 99% of users leave them on and 1% turn them off so you decide what's best for you. Also I use uBlock Origin Ad/Pop-up Blocker and sometimes it blocks some pages as well.

Thanks,

Daniel

 

Hmm, skewed towards On. Okay. Thanks.

 

Now personally I turn off the Browser Builtin feature as the Web Filter is far Superior and with uBlock Origin all is great for me!

 

Version 9.0.10.19 (Released July 5th, 2016)

Fixed

• Bug Fixes

https://www5.nohold.net/Webroot/ukp.aspx?pid=10&app=vw&vw=1&login=1&json=1&solutionid=1131&

Daniel

 

Edit: moved to Webroot Community

 

https://community.webroot.com/t5/An...-9-0-10-19-Released-July-5th/m-p/260021#M5919

 

Version 9.0.10.19 updated

 

Kwel!

 

FWIW ~ running 9.0.10.19 Application Protection for Firefox at Deny. I'm not feeling difference re Protect vs Deny. Based on my read Managing Protected Applications > Deny is tighter than default Protect.
Any Webrooters run browser at Deny.

 

Deny = Firefox will not be able to: Deny. “Denied applications” cannot view or capture protected data on the system, but can otherwise run normally.

Read here: http://www.webroot.com/En_US/Secure...6_IDProtection/CH6c_ManagingProtectedApps.htm

Under Protect is recommended why? Protect. “Protected applications” are secured against information-stealing malware, but also have full access to data on the system. You might want to add financial management software to the category. When you run a protected application, the Webroot icon in the system tray displays a padlock:

https://www.mrg-effitas.com/wp-cont...itas-Online-Banking-Certification-Q1-2016.pdf

Also you can Protect other Web Facing apps:

 

Hmm, "Deny = Firefox will not be able to: Deny". Then Deny is akin to Allow. Head scratch. Sorry, for my thickness. I kinda want Firefox to not facilitate aka Deny protected data leaving. "“Denied applications” cannot view or capture protected data on the system, but can otherwise run normally". Firefox at Deny > cannot view or capture protected data on the system / "Deny = Firefox will not be able to: Deny". Head scratch.....Sorry

Granted > Protect = Protected applications are secured against information-stealing malware, but also have full access to data on the system. And > Denied applications cannot view or capture protected data on the system, but can otherwise run normally.

Hmm, Protect is browser default. Ah, maybe web-facing default is Protect. And non web-facing = Allow or Deny. ?

 

Your getting there somewhat! Keep going!