Very good signatures and web filter. Also it's one of the lightest I have seen.
Sandbox feature is paid, I only use it with antivirus and web filter modules.
Version 6.0.x is.
Nagisa security config 2020
- Thread starter Nagisa
- Start date
Very good signatures and web filter. Also it's one of the lightest I have seen.
Sandbox feature is paid, I only use it with antivirus and web filter modules.
Version 6.0.x is.
- Jan 10, 2017
- 1,061
Can u pls share the link for the free version of forticlient?
- Dec 12, 2016
- 1,405
- Reinstalled Forticlient with only antivirus module
Web filter cause random connectivity issues. (one specific site refuses to load at all)
Web filter cause random connectivity issues. (one specific site refuses to load at all)
- Jul 29, 2018
- 566
Yes, I'm also experiencing some issues, FortiClient web filter is blocking absolutely safe websites such as bing.com. It looks like it's blocking random websites first, but it allows them later.
Not sure if it's due to some incompatibilities with Windows 10 version 2004
It’s happening both on my Win 10 and 7 pcs. So i don’t think anything relatable with the os itself.
- Dec 12, 2016
- 1,405
Another thing is that if a new version fixes it .
lastest version of Forticlient still isn't free.
Hi,
Just one suggestion. I would enable the Scanning Optimisation for Real-Time protection. Keeping it disabled will cause files to be rescanned again and again, which is pointless when you have other powerful layers found in Comodo. In a long run, not only it can decrease your performance, but also, the lifespan of your HDD/SDD.
Let @cruelsister have a look at other settings.
Last edited by a moderator:
I tested it myself and found 'on access' scanning to be much reliable and faster. Also as far as i can observe, on access scan uses transient cache as well. I don't see any disk usage from comodo when running a program second time.
Today my system just stuck at welcome screen on startup without an apparent reason. No matter how many times i restarted i couldn't get into desktop. I have had to boot into safe mod and run ciscleanup script and looks like that fixed the issue. Im suspecting that my configurations probably blocked a script or a file that's created by Windows itself because it hasn't got yet flagged safe by Comodo. Maybe it could have been solved by itself if i waited but anyway i decided no. I will either install again and add some exclusion rules for Windows system proccesses or install McAfee ENS or AVG.
That’s why I suggested you don’t overkill your system. It’s not necessary and it might break your system and patience
If you keep Comodo, make sure you find a balance of productivity and security, which will most likely be the default setup.
Yeah the default setup were actually goodThat’s why I suggested you don’t overkill your system. It’s not necessary and it might break your system and patience
If you keep Comodo, make sure you find a balance of productivity and security, which will most likely be the default setup.
Guess im going to choose CFW with tweaked Defender. By the way, Defender instantly blocked the sample you sent me with wacatac(I guess ml based) named detection.
Wacatac is the name of a trojan that can perform various actions. Normally all AVs have clear markings of what’s detected by machine learning. Indicators can vary, but mostly you’ll see a number, which represents the machine learning model. It might have ML or AI appendix and you might see percentage of confidence with some.Yeah default setup were actually good
Guess im going to choose CFW with tweaked Defender. By the way, Defender instantly blocked the sample you sent me. I guess wacatac is the nickname for ML based static detections.
- May 4, 2018
- 2,261
This is why you should a simple config of the following:
- AV or AV Suite
- Firewall (don't need if you have a Suite)
- Backup
Then build from there.
~LDogg
- AV or AV Suite
- Firewall (don't need if you have a Suite)
- Backup
Then build from there.
~LDogg
Changed containment policy rules.
It looks like the issue I had at thursday maybe wasn't from comodo after all. Though i still have no idea why it happened.
It looks like the issue I had at thursday maybe wasn't from comodo after all. Though i still have no idea why it happened.
Upgraded to 20H2 and changed security config a little bit.
Similar threads
