TomasP

We apologize for the inconvenience, the issue should be fixed as of now.

That is indeed true, we are always 1 hour ahead of the UK. But that's not what the "+1" refers to 🙂 In winter, UK is on GMT and we are on GMT+1. In summer, UK is on GMT+1 and we are on GMT+2. The difference is always one, but the time zone name refers to GMT, rather than UK time.

Thank you for the report, @Damjan, the data is now fixed. @cyberhash The "+1" offset is not compared to the UK, though, but to UTC/GMT time, which does not shift for daylight saving (time in the UK is the same as UTC/GMT only during the "winter" half of the year). So the green zone from your map is UTC/GMT+2 during daylight saving time (CET becomes CEST), while the blue zone (UK including) is officially UTC/GMT+1 (British Summer Time).

Just to add to Aryeh's well-put answer, I would like to react to A country's international position very much depends on the current government. Up until the recent elections in late 2023, Slovakia's government was very pro-Ukraine since day one of the invasion. Anyway, since its inception, ESET has seen several governments in Slovakia, leaning to either side of the political spectrum - and regardless of the government at any given time, ESET has always maintained its core values and principles, which are also reflected in the links provided by Aryeh. We will now lock this topic, as politics have no place in this forum and tend to create heated discussions, but we wanted to provide you with accurate information to address your concern.

Hello, as mentioned earlier, the specifics of pricing can vary from market to market, that's why you need to contact your local ESET distributor for the details. Marcos provided you with as much as can be said from a general, non-country-specific point of view. Thank you for your understanding.

Welcome to ESET API & Integrations forum! ESET Connect is an API gateway positioned between a client and a suite of ESET Cloud Enterprise Products. ESET Connect functions as a reverse proxy, accepting all application programming interface (API) calls for our cloud products. It aggregates the necessary services to process these calls and returns the corresponding results. Fundamentally, ESET Connect serves as a central hub for addressing both internal and external integration use cases. It primarily manages common tasks prevalent across an API service system, such as user authentication, rate limiting and statistics. ESET APIs, along with 3rd party integrations (both inbound and outbound), provide opportunities to automate monitoring, security, and administrative tasks in our Endpoint Protection Platform and our EDR solution, ESET Inspect. Leveraging these, users can achieve not only automation and efficiency but also access new data sources and insights to enhance their security posture. Should you encounter any technical challenges, please open a Support Ticket. Ensure you choose "ESET Connect" as the component. Describe your API-related issue in detail. If feasible, include the full API requests and responses, as well as pertinent details like the product version and operating system. Please refrain from including your API credentials or any personal information.

I was informed that the issue lies within a third party text editor that is used on the forum. The forum development team reported the issue to the editor developers, but don't have the info on when it should be fixed.

I am checking with the forum developers whether there is any progress on this.

Dear ESET Forum Users, we'd love to hear your success stories! Can you share a positive quote about your experience with Intel Threat Detection Technology (TDT) in combination with ESET Endpoint solutions? How do you feel about this cooperation helping you thwart ransomware attacks? Responses may be published in joint ESET and Intel marketing materials.

Dear ESET Forum Users, we'd love to hear your success stories! Can you share a positive quote about your experience with Intel Threat Detection Technology (TDT) in combination with ESET Endpoint solutions? How do you feel about this cooperation helping you thwart ransomware attacks? Responses may be published in joint ESET and Intel marketing materials.

Dear ESET Forum Users, we'd love to hear your success stories! Can you share a positive quote about your experience with Intel Threat Detection Technology (TDT) in combination with ESET Endpoint solutions? How do you feel about this cooperation helping you thwart ransomware attacks? Responses may be published in joint ESET and Intel marketing materials.

Hello, it was most likely related to this: https://status.eset.com/incidents/q864fw1rjxf2 Please try to access your EPC instance again now. We apologize for the inconvenience.

Dear valued customer, We would like to invite you to participate in the Mail Security survey about the server e-mail setup you are using and your product preferences. We are looking for direct feedback from customers to influence the future development of all future server e-mail-related products. If you are an IT administrator, a security administrator, or someone responsible for setting up e-mail accounts, your opinion is very precious to us. You can participate in the survey by visiting our Research Landing Page, where you can regularly find surveys running at ESET. The survey should take no longer than 5 minutes to finish. Thank you for your time and for sharing your workflow and preferences with us. posted on behalf of ESET Product Management

Dear valued customer, We would like to invite you to participate in the Mail Security survey about the server e-mail setup you are using and your product preferences. We are looking for direct feedback from customers to influence the future development of all future server e-mail-related products. If you are an IT administrator, a security administrator, or someone responsible for setting up e-mail accounts, your opinion is very precious to us. You can participate in the survey by visiting our Research Landing Page, where you can regularly find surveys running at ESET. The survey should take no longer than 5 minutes to finish. Thank you for your time and for sharing your workflow and preferences with us. posted on behalf of ESET Product Management

Hello, that is not something related to your account, but to this thread.

The current version's announcement was posted here when it was released: https://forum.eset.com/topic/31738-eset-endpoint-antivirus-for-linux-version-9050-has-been-released/

Just an update, it was recognized and confirmed as a bug in the forum's software.

Hi, I was able to reproduce this, thanks for reporting. I will raise this issue with the forum developers.

Hello, the "until version 9 + 3 years" applies to version 8 as a whole (8.0, 8.1, etc...), meaning the latest build of version 8 will be supported for that long. Given there was no version 8.1 at that time, the timeframe was listed with the latest available version (8.0). When 8.1 was released, it "inherited" the "until version 9 + 3 years" support window. Technically, it should have said just 8, apologies for that, I can see how that could have been confusing. It needs to be pointed out, though, that according to https://support-eol.eset.com/en/policy_business/versioning_rules.html, differences between versions 8.0 and 8.1 only consist of bug fixes and minor changes, so a customer may freely and safely upgrade to the latest build within the major version 8 (for which the "until version 9 + 3 years" policy applies) without any significant functionality changes. With all this being said, we do understand this may not be absolutely clear and easy to understand and, as Marcos already said, a new EOL policy is being prepared, under which every build will have a clearly defined support timeframe already at the time of release.

Hello, the changelog is now available at https://www.eset.com/int/business/download/file-security-windows/

Hello You2022, this is not a ticket request. On the ESET Security Forum, users help each other and ESET representatives may step in when necessary or when a question can't reasonably be answered by someone else. However, in case of an unprotected server, I recommend to contact your local support team, who can assign an adequate priority to your case and help you out. Regards, Tomas

Hello forum users, We are happy to announce that as of today, you can you can share your requests or ideas for new ESET documentation content (KB articles, videos, help pages...) right from the ESET Security Forum. There is a new "Request ESET Documentation Content" button in the right column, which opens the full pop-up widget where you can describe what you would like to see at support.eset.com, help.eset.com or on our YouTube channel. Feel free to use this feature, we are always looking to hear from our customers and meet their expectations! On behalf of the teams involved, Tomas

Our position is clearly laid out on the linked page, so with that being said, we'll close this topic before it gets nasty and political.

Not to worry, @URBAN0, it was clearly not posted with bad intentions.

Hello everyone, The recently discovered Log4j remote code execution vulnerability has affected organizations, ESET customers and their IT teams around the globe and as cybersecurity professionals we need to ensure their safety. Our Research & Threat Analysis team has responded rapidly and done a great job of creating a package of 4 rules for detection of Log4j exploitation and more general Java runtime exploitation. We advise to import these rules (the import procedure is very simply done from the Admin -> Detection Rules -> Import section of EEI as described here). These rules will also be included in the upcoming hotfix for EEI 1.6, but we are making them available to you: Possible Log4Shell (CVE-2021-44228) exploitation [D0532a] Possible Log4Shell (CVE-2021-44228) exploitation [D0532b] Potential Java Runtime exploitation [E0461] Java Runtime executing suspicious script/command interpreter [E0462] The first two rules are designed to detect the exploit itself so the false positives count should be absolutely minimal. However, these rules are using an experimental feature of EEI which is not currently fully supported, so the detection may not work in 100% of cases. E.g. when there is a detection already reported on the network layer, rule in EEI will not be triggered (but in this case you should have detection from at least one source and protection is in place). Because of the way how the feature is implemented it is more reliable when executed as re-run task for a retrospective threat hunt. The last two rules are focused on more general types of cases, general exploitation of Java Runtime i.e. not only by CVE-2021-44228. That means that those rules may generate occasional false positives for the cases when some legitimate Java application is executing system components which may indicate an attacker's activity. We have tested these rules to not have an excess number of false positives, but in case you will observe unusual amount of FPs in your environments - please report them back to us. The rule pack itself can be found here. Thank you.