Jump to content

cutting_edgetech

ESET Insiders
  • Content Count

    276
  • Joined

  • Last visited

  • Days Won

    1

cutting_edgetech last won the day on February 18 2018

cutting_edgetech had the most liked content!

Profile Information

  • Gender
    Male
  • Location
    USA

Recent Profile Visitors

768 profile views
  1. All I want to do is make Eset Log inbound blocks for when there is no allow or deny rule. Eset blocks the connection attempt when there is no allow or deny rule and does not log it. I'm going to let Eset developers know about attacks they may not be aware of, and request a way to log them. If I create a rule to block all protocols then Eset will block all inbound access, and log all inbound connection attempts. My firewall log would be humongous and it would take an enormous amount of work to sort attacks from harmless connection attempts. I think it's best to sort this out with development if they are willing to add some additional capabilities.
  2. Sorry for the late reply. I was out of town for several days, and when I came back we had no internet which is typical of this area. My ISP is TDS, and they are incapable of fixing the internet outages here. I have no internet whenever it rains. Water is getting into the lines, and they have been unable to locate the problem after supposedly trying to for years. So, I have the TDS version of the router. I have always used the high setting for the "Security Firewall". The only visible thing that changes in the GUI is it unticks most of the default allowed inbound ports, but almost none of them are related to vulnerable Windows Services. It seems the High Setting is not much more secure than the Low. I have WAN Ping Block mode enabled, but I still get pinged to death if I use a VPN (which bypasses router's firewall). I have NAT enabled in the settings, but there is no mention of SPI anywhere in the GUI. I went through the router settings with a fine tooth comb when I got it, and I have everything configured with Security in mind. Disabling Remote Telenet Login, and changing the default password was the first thing I did when I got the router. I also changed the SSID to something false to cause hackers a little more work in order to know what kind of router I have. I have UPnP, and WPS disabled. I'm using WPA / WPA2 encryption. I also have almost all Windows Services disabled that uses an open port. I'm hoping Eset will want to make some changes to the positioning of the buttons used in the Network Wizard, UI changes to the Firewall, and provide better logging options. I tried using the diagnostic logging to see how much it logged, but you receive a nagging prompt reminding you to disable it about once a minute. Also, I think the IDS/IPS could be improved. I think it only detects a low percentage of the port scans that actually occur on my system. I will know more when I get a chance to test the firewall myself which I hope is very soon! Btw.. I have a degree in InfoSec, and Networking. I just graduated in May so I don't have much experience, but I do know quite a bit about Networking and Firewalls. I know I need more experience before I would be considered an expert. I think I may have just gotten a Networking Job at a Large Hospital though, i'm keeping my fingers crossed. Edited: 7/3/19 @ 5:35
  3. I'm beginning to wonder if my router even has SPI. I can't find anything that says it does. Also, Actiontec recently came out with a new DSL modem router combo that advertises that their latest product does have SPI, as if the prior didn't. This legacy product of theirs may not have SPI. If it does then I can't find any documentation stating that it does, and nothing in the user interface says it does. Also, the only logging feature I see in the UI says System Log with no options to change the logging level.
  4. Even when i'm not using a VPN, which is most of the time, my router does not log any blocked IP other than an IPV6 link-local address. It blocks that address over and over again. I'm using IPV4, and I have IPv6 disabled on my network adapter. I don't see any options to adjust the router's logging capability. I've ran plenty of port scans on my router, and never found any open ports. I have all unnecessary windows services disabled. I only have 5 services running that are listening, and their ports are filtered by Eset Firewall. There's not much to exploit on my machine by way of network attacks.
  5. The only thing my router ever logs as being blocked is some IPV6 address, and I have IPV6 disabled on my Network Adapter. I don't know how to log packets dropped from Eset's SPI filtering without turning on diagnostic logging. Eset does not recommend using diagnostic logging except for trouble shooting. The Nework Wizard does show packets dropped due to it's SPI filtering. I see them often. It says something like packet does not belong to any open connection. I would not have to use the Network Wizard if Eset had a better logging system. Also, Eset should not unblock blocked connections in the connection wizard when the user isn't even clicking on the unblock button. They should not have placed the drop down 1 hour selection directly over the unblock button, and also not ask the user for any confirmation before unblocking. Also the close details window button is over the unblock button. Maybe if they make a few UI changes, and ask the user to confirm before unblocking IPs then it would not be a problem at all.
  6. You don't have to set the Logging Level to warning in order for Eset to log blocked connections to the Log File. You can set it to Information Level, and it will Log the event as well. I have been using Information Level. I don't know what the difference is in Information Level, and Warning Level. They both produce an entry in the Log file when an IP has been blocked. I will try to find it in the manual after I have finished this post. The Network Wizard will show several different types of attacks that I have found no way to Log using Eset's Logging. I would not even know about them without the Network Wizard. That seems to be a flaw in Eset's design. Eset is seriously lacking on their logging capability, or i'm not finding the options if they do exist. I get a lot of attacks on port 500 on my VPN, but I can't block inbound connections to port 500 or my VPN will not work. The attacks show up in the Network Wizard as being blocked due to no allow or block rule being found. If Eset can not find an allow rule or block rule then it drops the packets. Also packets blocked by their SPI filtering shows up in the Network Wizard. I see them in the Network Wizard often. I do not remember the exact wording Eset uses, but it says something like blocked due to not belonging to any open connection. The only way I could log the blocked attacks I see in the Network Wizard is to turn on diagnostic logging which Eset does not recommend except for trouble shooting. It says it will fill your log file up quickly and i'm assuming it is a drain on resources.
  7. I have to use the Network Wizard to get the IP addresses for attackers that get blocked due to there not being an allowed rule or an explicit deny rule for. It's the only way I can get them, and I only have 1 hour to do it before they are lost. I totally agree with you on needing a new router. My router security sucks. We only get DSL here, and there are only 3 routers on the market that will work with my DSL. The other ones suck worse than the one I have. I have its settings configured for max security, but I can not block specific ports on my router unless it is one of the ports on the list of options for the router. Almost none of the vulnerable ports that belong to Windows services are on the list. I also can not block specific IP addresses on my router. My router does not state whether it uses SPI, which it would be a travesty if it does not!
  8. No, I don't have pre-release updates enabled. I try to stay away from updates that may not be stable. I doubt they will contain a fix for this since I don't think this has been reported. I'm going to send a bug report. The UI design is flawed anyway and should be changed.
  9. I use the Network Wizard many times a day, every day. After I made the above post yesterday I accessed the drop down menu to see the one hour window view, and there was a slight freeze before the Window changed to the 1 hour view. After that 3 attackers on my Network that showed blocked in the Network View Wizard changed to unblocked! I had to turn my router off, and reboot again. There is definitely an issue with the Network Wizard. Unfortunately since I use the wizard many times a day, every day, i'm being affected when most people will not. I'm going to have to send a bug report. I don't think posting in the forum is going to help. I'm sure they will want logs, and other info. I will obviously be forced to drop Eset if I can't find a fix for this. I could avoid using the Network Wizard if Eset would log all blocked connections. I maintain a really good blocklist that I use with Peerblock. I add all malicious network attacks to my blocklist which I have created from many different sources. Many of my Network attacks don't get logged since they get blocked when there is not an allow rule to allow their attempts to access my network. Is there a way to make Eset Log access attempts that get blocked for when there is no allow rule, and no specific block rule?
  10. I have encountered a serious problem with the Firewall Trouble Shooting Wizard Feature. It unblocks blocked connections on it's own (attackers in my case) when using the drop down menu to change the time frame from 15 minutes to 1 hour. The problem seems to be that if I click 1 hour then it unblocks the blocked IP address just under it since the 1 hour selection is exactly over the unblock button. I have had this happen at least 10+ times in the past 3 weeks. Once this occurs I don't see any obvious way to block the attacker's IP address again without creating a packet filter rule for that IP address. There is also a second way Eset is unblocking blocked IP addresses (malicious IP addresses in my case) on it's own from the Network Trouble Shooting Wizard. If I choose details to see why the IP address was blocked and use the Close Button to close the details window it will also sometimes unblock the IP address just under it. I assume this is also due to the close button being over the unblock button. Once Eset unblocks the attackers IP Address I have to turn off my router, and reboot my computer. I've been rebooting since I run in a virtual environment, and as mentioned above I see no obvious way to block the address again once Eset unblocks it without creating a packet filter rule for that one IP address. To be clear i'm not double clicking so this should not be occurring. That being said, the UI is not designed very well. The 1 hour selection from the drop down menu, and the close button from the details window should not be over the rather large unblock button. Also, I strongly believe the user should be prompted saying something like, "are you sure you want to unblock this IP Address". I have to assume there is a glitch in the UI since i'm 100% positive i'm not double clicking. I have turned on logging for most of my packet filter rules but all blocks do not get logged so that is my reason for using the Network Trouble Shooting Wizard so often. It's the easiest way to see attackers being blocked that are not written to the log file. Usually, the ones that don't get logged are those that get blocked due to there being no allow rule for. All most all of these have been verified attackers so far So I still need to use the Network Trouble Shooting Wizard so I can get those IPs to add to my blacklist (peerblock). I've already tried using another mouse and also reinstalling Eset, neither worked. I'm using Eset Internet Security 12.1.34.0 on Windows 10 X64 version 1709. I would strongly suggest making changes to the Firewall Trouble Shooting Wizard UI so that the 1 hour menu option, and the close button for the details window is not over the unblock buttons. What can we do to get this fixed? I've been using Eset since 2003, and I don't want to change to another product.
  11. I'm still waiting on a top notch behavior blocker, or a more usable HIPS like itman has also requested. I would like to see a behavior blocker that can be tuned to different levels of sensitivity. If Eset is worried about it causing false positives, especially in test like AV comparatives then just leave it disabled by default.
  12. hxxp://www.eset.com/int/about/technology/#advanced-memory-scanner "Advanced Memory Scanner complements Exploit Blocker, as it is also designed to strengthen protection against modern malware. In an effort to evade detection, malware writers extensively use file obfuscation and/or encryption. This causes problems with unpacking and can pose a challenge for common anti-malware techniques, such as emulation or heuristics. To tackle this problem, the Advanced Memory Scanner monitors the behavior of malicious processes and scans them once they decloaks in the memory. This allows for effective detection of even heavily obfuscated malware. Unlike Exploit Blocker, this is a post-execution method, which means that there is a risk that some malicious activity could have been performed already. However, it steps into the protection chain when everything else fails." I assume you had something like Emsisoft's Behavior Blocker in mind when you made this request. Just wanted to mention the purpose of AMS and what it does. hxxp://static3.esetstatic.com/fileadmin/Images/INT/Docs/Other/ESET-Technology-Overview.pdf Edit: This PDF literally explains the ins and outs of the software itself and what happens behind the scene on the back-end systems. Every customer/user that is interested in this kind of geek information (it is very informative) should take time and read through the whole PDF. Sorry for the late reply. I have not been on the forum in a while. I didn't think I was going to get a reply to my post. Thank you for the .pdf manual. I will have to look more at AMS, but I don't think it is the same as something like Emsisoft's BB. Marcos said AMS only triggers a memory scan here. https://forum.eset.com/topic/5283-behavior-blocker/So the question is if it only triggers a memory scan then is it only looking for already blacklisted executables.
  13. It would be nice to see Eset incorporate a Behavior Blocker into their products. If something slips through then the behavior blocker can help detect the malware when it executes. They could have the feature disabled by default if they are worried about it causing false positives when being tested by independent test organizations.
×
×
  • Create New...