Paranoid Broken in IS 2016
Windows 7 Home SP1 x64 - BDIS 2016 188.8.131.527
As with with reports in the 2017 forum, I have found that Paranoid mode in IS 2016 is also broken.
In researching the optional .NET reliability update in Windows Updter, I ran the little known dotNETInspector by Firedancer Software for the first time in almost two years. Long before I started using IS 2016 in December, 2015.
Upon opening dotnetinspector.exe it connects to hosting24 dot com to check for updates. Knowing this I found it strange I had not been presented with an alert.
An allow rule had been built silently.
When first testing Paranoid mode I fully remember running the mostly unknown Off By One browser, ob1.exe, and acted upon the alert.
Today I deleted the rule for ob1.exe and it too was allowed and a rule built without an alert.
I also recall that until IS learned by rule most of my network programs (Internet and LAN) the alerts were diligent, which is what I wanted.
In looking through the rules I have noticed several other programs that have allow rules which were built silently, some of them I would have blocked. Like a productupdater.exe for a recently installed program which otherwise has no need for the Internet.
Many other recent silent allows built for stuff in C:\windows. Folders system32, servicing, syswow64 and so on.
Early on I remember noticing that the alert was active for MS stuff, like mscorsvw.exe.
In that BD didn't deem it necessary to time stamp the rules I can't even speculate when Paranoid broke.
If I had to best guess, maybe with the 184.108.40.2068 update in May. Which would be disturbing to say the least.
All Time Leaders
- 1.9K All Categories
- 921 Windows
- 102 Mac
- 350 Mobile Security
- 266 VPN
- 299 Central & Subscriptions
- 340 Other Products & Services
- 75 Security Research Team
- 133 Product features and Ideation
- 128 Enterprise Security
- 606 General Topics
- 158 News & Blogs
- 4.8K Home & home office protection
- 24.2K Old forum topics