Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Other security for Windows, Mac, Linux
FortiClient 6.0.0 (Windows)
Message
<blockquote data-quote="imuade" data-source="post: 761056" data-attributes="member: 73949"><p>Fortinet's documentation is pretty good, you can have a look at it:</p><p><a href="https://docs.fortinet.com/forticlient/admin-guides" target="_blank">https://docs.fortinet.com/forticlient/admin-guides</a></p><p><a href="https://docs.fortinet.com/d/forticlient-6.0.0-xml-reference" target="_blank">https://docs.fortinet.com/d/forticlient-6.0.0-xml-reference</a></p><p>A very useful under-the-hood setting is <popup_registry_alerts>0</popup_registry_alerts>. If you set it to 1, FortiClient displays alerts if a process tries to change registry start items.</p><p></p><p></p><p>Everyone here said FortiClient shouldn't be tested alone, but at least with SysHardened (if not with OSArmor). It would be nice if [USER=72251]@MoriartyOW[/USER] could make some tests with FC + SH (as [USER=51905]@Evjl's Rain[/USER] usually does with Avast).</p><p>I think SH would have picked the missed samples of this test <a href="https://malwaretips.com/threads/30-08-2018-21.86368/" target="_blank">https://malwaretips.com/threads/30-08-2018-21.86368/</a> and the setting I wrote above should have prevented the items set on startup (you can see them in Autoruns and Process Explorer)</p></blockquote><p></p>
[QUOTE="imuade, post: 761056, member: 73949"] Fortinet's documentation is pretty good, you can have a look at it: [URL]https://docs.fortinet.com/forticlient/admin-guides[/URL] [URL]https://docs.fortinet.com/d/forticlient-6.0.0-xml-reference[/URL] A very useful under-the-hood setting is <popup_registry_alerts>0</popup_registry_alerts>. If you set it to 1, FortiClient displays alerts if a process tries to change registry start items. Everyone here said FortiClient shouldn't be tested alone, but at least with SysHardened (if not with OSArmor). It would be nice if [USER=72251]@MoriartyOW[/USER] could make some tests with FC + SH (as [USER=51905]@Evjl's Rain[/USER] usually does with Avast). I think SH would have picked the missed samples of this test [URL]https://malwaretips.com/threads/30-08-2018-21.86368/[/URL] and the setting I wrote above should have prevented the items set on startup (you can see them in Autoruns and Process Explorer) [/QUOTE]
Insert quotes…
Verification
Post reply
Top