Jump to content

Trooper

ESET Insiders
  • Posts

    184
  • Joined

  • Last visited

Posts posted by Trooper

  1. 5 hours ago, Marcos said:

    Sent files are logged in the Sent files log by default, you don't need to enable logging.

    image.png

    To find out if a particular file was actually sent out and analyzed (a verdict could be known without analyzing the file), please provide logs collected with ESET Log Collector as well the name of the file.

    That is what I thought.  When I checked this morning, nothing appeared in sent files.  I will run the Log Collector to see.

    EDIT:  Sent you a PM with the logs @Marcos

  2. This morning I received a popup saying that a file was being analyzed and was blocked until it was checked by LiveGuard.  A short while later I received another pop-up that the file was safe.

    My question is, how do I see what file was analyzed and was blocked?  If I go to "Sent Files" logs nothing appears.

    Time;Component;Event;User
    8/17/2022 8:59:27 AM;ESET Kernel;ESET LiveGuard is analyzing the file to ensure it's safe to use. We will notify you in a few minutes.Unblock the file (not recommended)Change setup;DESKTOP-CR8F50R\User
    8/17/2022 8:59:27 AM;ESET Kernel;ESET LiveGuard has analyzed a file. It is safe to use.;DESKTOP-CR8F50R\User

    I am running the latest ESSP and Windows 11 21H2 and is fully patched.

    Thanks.

  3. On 8/3/2022 at 2:47 AM, AAndrejko said:

    Hello all,

    This issue was caused by the ESET Package Installer, a new installer has since been pushed to the Protect repository so if you do have an installer producing this error code, please re-download the installer from your console. It should pick up the new version.

    This was the fix.  I re-downloaded a new installer from ESET Protect Cloud and all was ok after that.  Sorry for my late reply, been rather busy of late.

    Cheers.

  4. On 7/4/2022 at 2:40 AM, Peter Randziak said:

    Hello @Trooper

    ESET PROTECT Cloud hasn't used the affected Configuration module, so #1 from the list is not applicable 

    https://forum.eset.com/topic/32875-eset-endpoint-shutting-down-after-scheduled-scan-with-9120510/?do=findComment&comment=153054

    #2 and #3 from the list should be resolved automatically with the fixed Configuration module so based on my current knowledge of the issue, you do not need to take any action.

     

    Peter 

     

    Thanks Peter I appreciate it. 

  5. 8 hours ago, Peter Randziak said:

    Hello guys,

    Fixed configuration module 2011.5 is now available on pre-release update stream for EP/ESMC/ERA management agents and Endpoints

    Reverting update to Configuration module 1998.2 has been released for EP/ESMC/ERA servers (on release update stream, since ~ 11:25 CEST) in order to prevent further policies corruption.

     

    Peter

    I am on ESET PROTECT Cloud.  Do I need to take any action on this @Peter Randziak?

  6. Question.  Can you shed some light on this please from the changelog?

    NEW: Endpoint restart/reboot improvements for managed networks

    Also, will it still be the same thing as the last time where it will take up to 30 days for auto upgrades to take place?

    Just today, after a weekly scheduled can, ESET prompted me that it was going to shut down my computer.  This has never happened before.  Do I need to log a ticket for this?  I was able to cancel the shutdown thankfully.  I am the only one using at the moment thankfully so no harm done to my end users.

    Thanks in advance.

     

  7. 6 hours ago, itman said:

    Based on my testing of recent Follina malware samples, Eset has you covered in regards to this specific msdt.exe exploit. All samples were detected upon download; either by signature detection of payload or via Eset exploit protection by CVE.

    However, there's another exploit technique that has been discovered that I posted about over at wilderssecurity.com and described here: https://www.bleepingcomputer.com/news/security/new-dogwalk-windows-zero-day-bug-gets-free-unofficial-patches/ . This one appears to be a Microsoft Defender bypass since opening of the malware dropper, a .cab file, bypassed Mark-of-the-Web checking. Until shown otherwise, I would say Eset should cover this one also.

    -EDIT- Looks like Eset has issues with Qbot malware deployment of Follina exploit: https://forum.eset.com/topic/32642-eset-not-detecting-qbot-deploying-follina-exploit/

    Thank you for your reply.  Looks like ESET has now addressed the Qbot malware deployment as well.  Cheers.

×
×
  • Create New...