Eset nod 32 antivirus 4.0.424.0 serial key or number

Setting Up Autotask Endpoint Management
Refer to "Overview" on page 5. We introduce you to the two interface components of Autotask Endpoint Management. Refer to "AEM Web Portal and Agent" on page 6. Before you begin with the configuration of your Endpoint Management site, you should make sure that you are hosted on the right platform, whitelist a number of IP addresses and URLs, and learn about supported operating systems and requirements for the Agent browser. Refer to "Infrastructure and Requirements" on page 9. © 2015 Autotask Corporation l Page 4 of 197 Overview About Remote Monitoring and Management (RMM) Remote monitoring and management (RMM) software enables managed IT service providers (MSPs) to remotely and proactively monitor their customers' networks and computers. Data about the remote devices, also known as endpoints, is collected by a lightweight software program called Agent which then communicates this data to the Endpoint Management application. The service provider has access to this information via a Web Portal. With an RMM solution, you can collect information about the customers' network, hardware and software ("audit"), remotely support customers, proactively monitor every endpoint, deploy patches, create alerts and tickets when issues arise, schedule maintenance jobs, and more. You can stay ahead of issues and resolve them without going on-site, often before your customers are aware of a problem. Autotask Endpoint Management and Autotask PSA Autotask offers complete solutions for RMM (Autotask Endpoint Management) and IT Business Management (Autotask PSA). Our products can be used as an integrated solution, or as stand-alone products. We will continue to support partner solutions for both product lines. l l For an overview of the Autotask integration of PSA and AEM, refer to "Integrate with Autotask PSA" on page 95. For an overview of other RMM tools that integrated with Autotask PSA, refer to Partner Solutions. © 2015 Autotask Corporation l Page 5 of 197 AEM Web Portal and Agent The Autotask Endpoint Management (AEM) platform consists of two separate components: the Web Portal and the Agent. The Web Portal The Web Portal is a cloud-based browser application that lets you manage any number of devices ("endpoints") for multiple customers across multiple operating systems. On the Web Portal, you can: l Administer your site, including users, security levels, branding, profiles, groups and filters l Set up and manage the profiles and the devices that are associated with them l Configure the ready-made components (applications and utilities) you downloaded from the ComStore l Schedule jobs to be performed on selected devices, and much else... © 2015 Autotask Corporation l Page 6 of 197 The Agent The Agent is a lightweight software program that is installed on all managed devices that support agent installation. It also acts as a go-between for network devices that do not support Agent installation, but can be managed using SNMP. The Agent collects data on the devices, and communicates it to the Web Portal. It can also execute a variety of actions on the remote device, such as: l Audit the installed hardware and software l Proactively monitor the device l Deploy software, patches and updates l Enable the remote takeover of devices that have the Agent installed Most of these tasks are accomplished in the Agent browser, an application launched from the Agent icon in the system tray or from the Web Portal. It contains multiple tools to take control of a remote device. © 2015 Autotask Corporation l Page 7 of 197 In the Agent browser, you can: l Take a screen shot of the remote device or open a remote takeover tool like RDP, VNC or Splashtop l Open a Command Shell and add and edit registry items on the remote device l Control Windows Services on the remote device l Wake up, shut down or restart the remote device l Monitor resources such as CPU or memory in real time l Transfer files l View event logs It allows you to diagnose and fix many issues remotely, and often in the background, without the user being aware of it. © 2015 Autotask Corporation l Page 8 of 197 Infrastructure and Requirements If you are responsible for rolling out Autotask Endpoint Management (AEM) in your company, we recommend that you familiarize yourself with the following technical topics: l l l l The AEM cloud application is located on a number of platforms around the globe. Customers are assigned to the platform that provides the fastest connection, based on their location. Refer to "AEM Platforms" on page 10. To allow seamless connectivity to the AEM Web Portal (formerly CSM) and between AEM Agents (formerly CAGs), you must open TCP PORT 443 Outbound through your firewall. The IP addresses you must whitelist are specific to your platform. Refer to "Whitelisting Requirements for IP Addresses and URLs" on page 12. The AEM Agent can be installed on a wide range of operating systems. Refer to "Supported Operating Systems and Requirements for the Agent Browser" on page 21. For a detailed review of the AEM infrastructure and security, refer to "Infrastructure and Security" on page 23. © 2015 Autotask Corporation l Page 9 of 197 AEM Platforms The Autotask Endpoint Management cloud application (AEM) is located on a number of platforms around the globe. Each platform consists of a number of individual server instances that control different areas of the product (Agent connectivity, Web Portal etc.). To achieve the fastest connection, your account will reside on the platform that is geographically nearest to you, based on the location you specified when you signed up. If you have accidentally selected a wrong location, contact your Account Manager for assistance to have your account migrated to the correct platform. Unified Login Server (ULS) The AEM Unified Login Server (ULS) is a single sign-on server managing all AEM customers’ credentials, allowing them to log in at one location and be directed to their specific platform. The login page address of the AEM ULS is https://centrastage.net. Current regions and platforms When logging in through the single sign-on server, you will be directed to the platform where your account is hosted. The name of the platform will be displayed in the first part of the URL once you have logged in. For example, if your account is hosted on the Merlot (EMEA West 2) platform, the following URL will be displayed once you have logged in through the single sign-on server: https://merlot.centrastage.net/csm/. In addition to the ULS, all five platforms host their own login page. You can log in to your account using the correct direct login URL. Region Platform Name Direct Platform Address Direct Login Page Europe (Dublin) Pinotage (EMEA West 1) Merlot (EMEA West 2) https://pinotage.centrastage.net https://merlot.centrastage.net https://pinotage.centrastage.net/csm/login https://merlot.centrastage.net/csm/login US (Virginia, Oregon) Concord (US East) Zinfandel (US West) https://concord.centrastage.net https://zinfandel.centrastage.net https://concord.centrastage.net/csm/login https://zinfandel.centrastage.net/csm/login Asia-Pacific (Sydney) Syrah (APAC) https://syrah.centrastage.net https://syrah.centrastage.net/csm/login © 2015 Autotask Corporation l Page 10 of 197 To connect to your platform, you must open your firewall for platform-specific IP Addresses. Some firewalls, proxies or security appliances may require access to the URL of the service as well as the IP address. For further information, refer to "Whitelisting Requirements for IP Addresses and URLs" on page 12. © 2015 Autotask Corporation l Page 11 of 197 Whitelisting Requirements for IP Addresses and URLs Administrator To allow seamless connectivity to the Autotask Endpoint Management (AEM) Web Portal, the ComStore, and between Agents, you must open TCP PORT 443 Outbound through your firewall. If your company has a more aggressive security posture and port 443 is not open, you must whitelist a number if IP addresses to allow AEM to make the required connections. The IP addresses you must whitelist are specific to your platform, and you only need to whitelist the ones associated with your platform. For information about the platform your site is hosted on, refer to "AEM Platforms" on page 10. Connecting to the AEM Web Portal To ensure full connectivity to AEM, you will need to open TCP PORT 443 Outbound through your firewall to the IP addresses and URLs associated with your platform. IP addresses for each platform © 2015 Autotask Corporation l Page 12 of 197 EMEA West 1 (Pinotage) EMEA West 2 (Merlot) US East (Concord) US West (Zinfandel) APAC (Syrah) 54.77.247.84 54.194.25.164 52.5.251.79 54.201.211.18 54.79.25.73 54.77.108.71 54.194.54.213 52.6.151.191 54.213.57.149 54.79.44.13 54.77.69.163 54.194.245.26 52.7.200.96 54.201.174.248 54.206.73.160 54.154.123.55 54.194.70.100 52.4.97.130 54.201.158.254 54.206.60.138 54.154.110.191 54.194.17.228 54.88.94.23 54.201.148.211 54.79.20.109 54.154.110.190 54.194.42.15 54.172.198.183 54.200.154.205 54.252.198.125 54.154.16.237 54.194.217.74 54.88.212.141 54.213.162.73 54.206.10.157 54.154.76.59 54.194.87.166 54.164.96.143 54.201.132.105 54.206.12.124 54.171.166.217 54.194.59.222 54.165.85.82 54.201.16.209 54.206.20.221 54.77.122.85 54.194.73.199 54.165.240.214 54.191.61.99 54.206.24.91 54.194.81.165 54.173.70.131 54.191.117.5 54.79.4.211 54.194.153.16 54.186.19.220 54.194.242.0 54.186.13.123 54.194.218.239 54.194.100.128 54.194.50.12 URLs In addition to IP addresses, some firewalls, proxies or security appliances may require access to the URL of the service as well as the IP address. If you are using a proxy or security appliance, ensure that the relevant URLs to your platform are whitelisted. © 2015 Autotask Corporation l Page 13 of 197 TCP Port Platform URLs Direction EMEA West 1 (Pinotage) Web Service: https://01ws.centrastage.net Agent Updates: https://update.centrastage.net Web Portal: https://pinotage.centrastage.net Control Channel: 01cc.centrastage.net:443 Tunnel Server: ts.centrastage.net:443 Component Library: https://cpt.centrastage.net, https://cpt.centrastage.net.s3.amazonaws.com HTTPS / 443 Outbound EMEA West 2 (Merlot) Web Service: https://02ws.centrastage.net Agent Updates: https://update-merlot.centrastage.net Web Portal: https://merlot.centrastage.net Control Channel: 02cc.centrastage.net:443 Tunnel Server: ts.centrastage.net:443 Component Library: https://cpt-merlot.centrastage.net, https://cpt-merlot.centrastage.net.s3.amazonaws.com HTTPS / 443 Outbound US East (Concord) Web Service: https://01concordws.centrastage.net Agent Updates: https://update-concord.centrastage.net Web Portal: https://concord.centrastage.net Control Channel: concordcc.centrastage.net:443 Tunnel Server: ts.centrastage.net:443 Component Library: https://cpt-concord.centrastage.net, https://cpt-concord.centrastage.net.s3.amazonaws.com HTTPS / 443 Outbound US West (Zinfandel) Web Service: https://03ws.centrastage.net Agent Updates: https://update-zinfandel.centrastage.net Web Portal: https://zinfandel.centrastage.net Control Channel: 03cc.centrastage.net:443 Tunnel Server: ts.centrastage.net:443 Component Library: https://cpt-zinfandel.centrastage.net, https://cpt-zinfandel.centrastage.net.s3.amazonaws.com HTTPS / 443 Outbound APAC (Syrah) Web Service: https://syrahws.centrastage.net Agent Updates: https://update-syrah.centrastage.net Web Portal: https://syrah.centrastage.net Control Channel: syrahcc.centrastage.net:443 Tunnel Server: ts.centrastage.net:443 Component Library: https://cpt-syrah.centrastage.net, https://cpt-syrah.centrastage.net.s3.amazonaws.com HTTPS / 443 Outbound Connecting Agents through the Tunnel Server Grid Unless a peer-to-peer connection can be established between devices, Agent to Agent connectivity and remote takeover are managed by a tunnel server over an encrypted connection. Tunnel servers are connection relays located around the globe to provide maximum coverage and the best performance depending on your location. They are automatically available to all users. © 2015 Autotask Corporation l Page 14 of 197 l When a remote takeover session is initiated, the admin device queries DNS to find the nearest tunnel server. The tunnel server is picked based on the proximity to the admin device. l Then a connection is made to a load-balanced tunnel server cluster. l Finally, a connection is established to the remote device. To make the most of the tunnel server grid, please ensure that the IP addresses relevant to your geographic location are open on your own and your endpoint's firewalls. IP Addresses for the Tunnel Server Grid © 2015 Autotask Corporation l Page 15 of 197 EMEA APAC (Sidney) APAC (Singapore) 54.72.228.106 54.79.75.129 54.169.119.179 54.207.102.187 54.191.106.204 54.172.163.43 54.77.25.238 54.79.97.42 54.187.170.202 54.173.173.38 54.169.73.64 South America (Sao Paulo) 54.207.105.254 US WEST (Oregon) US EAST (Virginia) 54.76.210.230 54.77.1.79 54.77.29.239 54.93.70.139 NEW 54.93.63.109 NEW This list will be updated as we add more tunnel servers to the grid. Connecting to the Component Library (ComStore) The component library is hosted on Amazon servers. EC2 stands for Elastic Computing Cloud. The IP addresses are assigned when the Amazon EC2 instance is launched. To ensure a successful connection, you must whitelist all IP address ranges that host components for your region. Amazon AWS EC2 IP Address Ranges © 2015 Autotask Corporation l Page 16 of 197 EU (Ireland) US East (Virginia) Asia Pacific (Sydney) 79.125.0.0/17 (79.125.0.0 79.125.127.255) 72.44.32.0/19 (72.44.32.0 72.44.63.255) 54.252.0.0/16 (54.252.0.0 54.252.255.255) 46.51.128.0/18 (46.51.128.0 46.51.191.255) 67.202.0.0/18 (67.202.0.0 67.202.63.255) 54.253.0.0/16 (54.253.0.0 54.253.255.255) 46.51.192.0/20 (46.51.192.0 46.51.207.255) 75.101.128.0/17 (75.101.128.0 75.101.255.255) 54.206.0.0/16 (54.206.0.0 54.206.255.255) 46.137.0.0/17 (46.137.0.0 46.137.127.255) 174.129.0.0/16 (174.129.0.0 174.129.255.255) 54.79.0.0/16 (54.79.0.0 54.79.255.255) 46.137.128.0/18 (46.137.128.0 46.137.191.255) 204.236.192.0/18 (204.236.192.0 204.236.255.255) 54.66.0.0/16 (54.66.0.0 54.66.255.255) NEW 176.34.128.0/17 (176.34.128.0 176.34.255.255) 184.73.0.0/16 (184.73.0.0 184.73.255.255) 176.34.64.0/18 (176.34.64.0 176.34.127.255) 184.72.128.0/17 (184.72.128.0 184.72.255.255) 54.247.0.0/16 (54.247.0.0 54.247.255.255) 184.72.64.0/18 (184.72.64.0 184.72.127.255) 54.246.0.0/16 (54.246.0.0 54.246.255.255) 50.16.0.0/15 (50.16.0.0 50.17.255.255) 54.228.0.0/16 (54.228.0.0 54.228.255.255) 50.19.0.0/16 (50.19.0.0 50.19.255.255) 54.216.0.0/15 (54.216.0.0 54.217.255.255) 107.20.0.0/14 (107.20.0.0 107.23.255.255) 54.229.0.0/16 (54.229.0.0 54.229.255.255) 23.20.0.0/14 (23.20.0.0 23.23.255.255) 54.220.0.0/16 (54.220.0.0 54.220.255.255) 54.242.0.0/15 (54.242.0.0 54.243.255.255) 54.194.0.0/15 (54.194.0.0 54.195.255.255) 54.234.0.0/15 (54.234.0.0 54.235.255.255) 54.72.0.0/14 (54.72.0.0 54.75.255.255) 54.236.0.0/15 (54.236.0.0 54.237.255.255) 54.76.0.0/15 (54.76.0.0 54.77.255.255) 54.224.0.0/15 (54.224.0.0 54.225.255.255) © 2015 Autotask Corporation l Page 17 of 197 EU (Ireland) US East (Virginia) 54.78.0.0/16 (54.78.0.0 54.78.255.255) 54.226.0.0/15 (54.226.0.0 54.227.255.255) 54.74.0.0/15 (54.74.0.0 54.75.255.255) NEW 54.208.0.0/15 (54.208.0.0 54.209.255.255) 185.48.120.0/22 (185.48.120.0 185.48.123.255) NEW 54.210.0.0/15 (54.210.0.0 54.211.255.255) 54.170.0.0/15 (54.170.0.0 54.171.255.255) NEW 54.221.0.0/16 (54.221.0.0 54.221.255.255) 87.238.80.0/21 NEW 54.204.0.0/15 (54.204.0.0 54.205.255.255) Asia Pacific (Sydney) 79.125.0.0/17 NEW 79.125.0.0/17 NEW 54.78.0.0/16 NEW 54.78.0.0/16 NEW 54.76.0.0/15 NEW 54.76.0.0/15 NEW 54.74.0.0/15 NEW 54.74.0.0/15 NEW 54.72.0.0/15 NEW 54.72.0.0/15 NEW 54.247.0.0/16 NEW 54.196.0.0/15 (54.196.0.0 54.197.255.255) 54.198.0.0/16 (54.198.0.0 54.198.255.255) 54.80.0.0/13 (54.80.0.0 54.87.255.255) 54.88.0.0/14 (54.88.0.0 54.91.255.255) NEW 54.92.0.0/16 (54.92.0.0 54.92.255.255) NEW 54.92.128.0/17 (54.92.128.0 54.92.255.255) NEW 54.160.0.0/13 (54.160.0.0 54.167.255.255) NEW 54.247.0.0/16 NEW 54.246.0.0/16 NEW 54.172.0.0/15 (54.172.0.0 54.173.255.255) NEW 54.246.0.0/16 NEW 54.240.220.0/22 NEW 54.240.197.0/24 NEW 54.239.99.0/24 NEW 54.239.32.0/21 NEW © 2015 Autotask Corporation l Page 18 of 197 EU (Ireland) US East (Virginia) Asia Pacific (Sydney) 54.231.128.0/19 NEW 54.229.0.0/16 NEW 54.229.0.0/16 NEW 54.228.16.0/26 NEW 54.228.0.0/16 NEW 54.228.0.0/16 NEW 54.220.0.0/16 NEW 54.220.0.0/16 NEW 54.216.0.0/15 NEW 54.216.0.0/15 NEW 54.194.0.0/15 NEW 54.194.0.0/15 NEW 54.170.0.0/15 NEW 54.170.0.0/15 NEW 54.155.0.0/16 NEW 54.155.0.0/16 NEW 54.154.0.0/16 NEW 54.154.0.0/16 NEW 46.51.192.0/20 NEW 46.51.192.0/20 NEW 46.51.128.0/18 NEW 46.51.128.0/18 NEW 46.137.128.0/18 NEW 46.137.128.0/18 NEW 46.137.0.0/17 NEW 46.137.0.0/17 NEW © 2015 Autotask Corporation l Page 19 of 197 EU (Ireland) US East (Virginia) Asia Pacific (Sydney) 185.48.120.0/22 NEW 185.48.120.0/22 NEW 178.236.0.0/20 NEW 176.34.64.0/18 NEW 176.34.64.0/18 NEW 176.34.159.192/26 NEW 176.34.128.0/17 NEW 176.34.128.0/17 NEW 176.32.104.0/21 NEW © 2015 Autotask Corporation l Page 20 of 197 Supported Operating Systems and Requirements for the Agent Browser Operating Systems The Autotask Endpoint Management (AEM) Agent can be installed on a wide range of operating systems that are outlined below. Operating System / Device Version Windows • Windows XP SP2 (Home, Professional, Professional x64, Tablet PC, Media Center, Starter editions) • Windows Vista 32/64-bit (Starter, Home Basic & Premium, Business, Enterprise, Ultimate editions) • Windows Server 2003 & R2 32/64-bit (Web, Standard, Enterprise, Datacenter, Small Business, Home Server editions) • Windows 7 (32/64-bit) • Windows 8/8.1 (32/64-bit) • Windows 2008 & R2 32/64-bit (Standard, Enterprise, Datacenter, Web, Small Business) • Windows Server 2012 (64-bit) & Windows Server 2012 R2 Apple Macintosh • Intel based Mac OS X 10.6.x and later Linux* • Fedora 19, 20, 21 • Debian 7, 8 • CentOS 6, 7 • Ubuntu 12, 13, 14, 15 Smartphones and Tablets • iOS 7 and later • Android 2.3.3 and later *The Agent may work with any Debian-based distribution but support is only provided for the ones listed. Detailed Windows requirements AEM runs as a .Net service and needs Windows Installer 3.1 and .Net Framework 2.0 to install and run. Windows Installer 3.1 is part of the standard MS Windows Update and should be present on all devices. If it is not, it can be downloaded from Microsoft. If Microsoft .Net 2.0 is not installed on the device, the Agent installer will automatically download and install it. It can also be downloaded manually from Microsoft. For further information on .Net Framework versions, refer to .NET Framework Versions and Dependencies. © 2015 Autotask Corporation l Page 21 of 197 .NET Framework on Windows 8 or Windows Server 2012 In order to install AEM, you'll need to enable .NET Framework 3.5.1 (it includes .NET 2.0 and 3.0). You can enable it by following the paths below. l Windows 8 Go to Control Panel > Programs & Features > Turn Windows features on or off. This can also be enabled via the following command line: dism.exe /online /enable-feature /featurename:NetFX3 l Windows Server 2012 Go to Server Manager > Roles and Features > Add Roles > Features. This can also be enabled via the following command lines: dism.exe /online /enable-feature /featurename:NetFX3ServerFeatures dism.exe /online /enable-feature /featurename:NetFX3 © 2015 Autotask Corporation l Page 22 of 197 Infrastructure and Security Autotask Endpoint Management (AEM) enables IT support organizations to monitor and manage multiple remote computers over any network, bringing visibility and control to the service provider. The solution has been built for organizations supporting IT over public networks, so careful consideration has been given to the infrastructure and security of the product. Platform Infrastructure AEM operates on multiple resilient, high-availability, scaling platforms hosted within Amazon Web Services (AWS). These Platforms exist and span a number of different AWS Regions to provide increased performance for customers around the globe. At present the core platforms are hosted in the EU-WEST-1 (Ireland), US-WEST-2 (Oregon), US-EAST-1 (Virginia) and AP-SOUTHEAST-2 (Sydney) regions, with additional servers in AP-SOUTHEAST-1. All communication that needs to travel between AWS Regions is performed via secure SSH Tunnels or HTTPS connections. To help to achieve the required levels of resilience and scalability, AEM servers are separated into three customer facing services. The services are separated as follows: l l l AEM Server Manager (CSM) - The web management portal Control Channel (CC) – A permanent connection established with all connected devices to facilitate low latency event and command communication Web Service (WS) – A stateless Web Service for Agent to Platform communication Availability Zones Within each AWS Region there exist two or more Availability Zones. These zones are distinct locations within a region that are engineered to be isolated from failures in each other, while still providing high performance, low latency inter-AZ connectivity. By hosting across multiple Availability Zones, AEM is able to ensure that a failure in a single Data Center does not affect the availability of a platform. Load Balancing All of the core platform services (CSM, CC, WS) exist as multiple servers within AWS and are themselves only accessible through dedicated Load Balancers. For the CSM, this load balancing is provided via the use of the Amazon Elastic Load Balancer service, whilst the CC and WS servers use dedicated Load Balancing instances. By spreading these load balancers across multiple availability zones and using DNS Round-Robin, we are able to ensure high availability, scalability and performance of the platform. Servers can be commissioned and decommissioned as required with no impact to the service itself. © 2015 Autotask Corporation l Page 23 of 197 Server Instances AEM uses Ubuntu for the base operating system of the server instances, hosted within AWS Elastic Compute Cloud (EC2). The version used has been specifically prepared and hardened for use in AWS by Canonical Ltd, the provider of the Ubuntu platform. Server instances are launched from prebuilt and tested machine images to ensure 100% consistency. These machine images are backed up to the AWS Simple Storage Service (S3) which has 99.999999999% (11 9’s) durability. Servers are stateless in that they do not store any persistent data allowing them to be replaced on demand, negating the need for individual server backups, and ensuring that the failure of a server does not result in a loss of customer data. File Storage All components uploaded to the AEM platform are uploaded to buckets within S3. This ensures durability of data, and also provides a highly available mechanism to securely serve these files back to devices across the globe as required. By using S3 we ensure that components can be instantly provisioned to any number of devices over a high bandwidth connection, not tied to a static number of background instances. Firewalls AWS EC2 instances are, by default, closed for ingress via the use of configurable security groups. By default, AEM core servers are only accessible via dedicated Load Balancer or SSH Tunnel instances, which exist in separate security groups. This means that access to these instances is either via 443 for HTTPS or secure TCP traffic from Load Balancers, or via SSH Tunnel on port 22 through a dedicated SSH Instance. Any servers which do not require external connections are therefore locked down and accessible only on port 22 via first connecting to a controlled SSH Instance. This “Security Group” concept extends to Amazon's Relational Database Service (RDS), and means that the Databases that back the platforms are not externally accessible, and instead only open to connections from specific Security Groups. Auto Scaling In times of high load, AEM servers can auto scale, adding additional server resource automatically to areas of the system that are most heavily utilized. Additional servers can be automatically brought online and added to the load balancer as required. Conversely, auto scaling can remove excess processing in times of minimal load. Additional server instances are can be provisioned in under 60 seconds, and ensure a consistent level of service for users despite platform load. Database AEM is underpinned by a high availability, relational database service (RDS) for MySQL, which is distributed across two availability zones in a Master-Slave arrangement. In the unlikely event of a database failure, AEM will automatically fail over to the slaved database in the other availability zone within a matter of minutes. RDS automatically patches the database software and backs up the database, storing the backups for a userdefined retention period and enabling point-in-time recovery. © 2015 Autotask Corporation l Page 24 of 197 Data Protection We work hard to ensure the security and protection of any data stored on the AEM platform. For sensitive information, in addition to access controls and platform penetration testing, this also includes encryption using the AES/CBC/PKCS5Padding Cipher before it is transferred to the AEM Database. Customers should also be aware that data is never stored outside of the platform region that they select when signing up for the service. For customers on our EU platforms this means all data is stored in Ireland, for customers on US Platforms this currently means all data is stored in Virginia or Oregon, and for customers in APAC this means all data is stored in Sydney. Where new platforms are added in the future, the location of the corresponding data center will be announced to allow customers to make appropriate decisions when reviewing concerns such as the Data Protection Directive. Platform Monitoring AEM uses a number of services in order to provide effective monitoring of platform health and metrics. In addition to the instance monitoring services provided by AWS CloudWatch, core platform services are monitored for health and throughput via both custom metrics pushed to CloudWatch, the NewRelic Application and Server Monitoring Service, and Graphite in combination with custom metric gathering code deployed to each server. NewRelic and our own custom metrics provide us with near real time feedback on platform load, allowing the system to scale on demand when required and alerting us to potential problems or service outages. 24/7 response is ensured through the use of PagerDuty and a robust and well practiced escalation procedure within AEM. By monitoring the platforms in this fashion, and coupled with the log aggregation services currently being deployed across the estate, AEM is moving towards being able identify, pinpoint and resolve potential customer issues before they become apparent to the end user, with both predefined intelligence and exception based alerting. Platform Status Current platform status, health and issues are pro-actively reported to end users via a comprehensive Status Page at http://www.autotaskstatus.net/. Not only does this give users a way of being alerted to potential platform issues and notification of upcoming planned maintenance, but it also provides a complete history of issues that have affected the platform, giving new and existing customers insights into platform stability and response times. Platform Stability AEM performs regular stability testing on the platform, using automated tools to terminate core servers and ensure the platform is able to both continue functioning, and gracefully recover the affected services without the need for manual intervention. © 2015 Autotask Corporation l Page 25 of 197 Through this kind of testing we can ensure that not only has the platform itself been effectively engineered to ensure resilience and high availability, but that in the event of an unexpected issue, all the core staff within AEM are able to execute a well-practiced response. Global Relay Servers Despite platforms themselves being located in specific regions, all inter-Agent connectivity takes advantage of a network of Tunnel Servers, with the Agents intelligently selecting their closest and healthiest server through which to establish a connection. Customers who do not wish to utilize this network can select a specific server to use, with IP Addresses of those, and the other endpoints. For further information, refer to "Whitelisting Requirements for IP Addresses and URLs" on page 12. AEM AWS Architecture Figure - AEM Platform Infrastructure – This is a high level diagram and may not represent the full set of services and servers. Product Security © 2015 Autotask Corporation l Page 26 of 197 AEM Server Manager Security Encryption AES-256, 256 Bit keys. The connection supports TLS 1.0/1.1/1.2 Passwords Strong passwords required – Min 8 characters. Password Expiry Optional password expiration every 30/60/90 days. Authentication RADIUS server integration can be enabled together with single sign on and one time passwords, or SecurID tokens. Accounting Session activity logged to system level log files and audit trail database. Two-Factor Authentication When logging into the AEM Server Manager Website, customers can choose to enable a Two-Factor Authentication mechanism based around the use of Time-Based One-Time Passwords (TOTP - http://tools.ietf.org/html/rfc6238). This allows any user with a smartphone the ability to use that device as a second step in the authentication process, requiring them to provide a Username, Password, and token generated on their phone to log into the website. By enabling TOTP across all users in their account, customers can ensure that a compromised password doesn’t lead to a third party being able to access the CSM. AEM Agent Security Encryption (Agent to server) TLS 1.0 Encryption (Agent to Connection Broker) 3DES in CBC mode. Protocol HTTPS / TCP 443 Stateful Packet Inspection It is strongly recommended that any Stateful Packet Inspection be turned off for access to any centrastage.net address, and that all attempts possible are made to guarantee that TCP connections to the cc.centrastage.net addresses are not terminated in cases of inactivity (These connections may be inactive for up to 180 seconds at a time if no client activity is detected). Platform Infrastructure Security AEM runs on a hardened Ubuntu Linux platform, with all instances launched from a patched and maintained © 2015 Autotask Corporation l Page 27 of 197 Elastic Block Storage (EBS) image, based on an original provided by Canonical Ltd. All instances exist for a maximum of one release cycle before being terminated and replaced by a newly instantiated server. This ensures consistency across all servers in the AEM platform, and provides a base level of Security without the need to worry about missing critical patches or configuration for each server. AWS Console Access Each AEM Platform is hosted within a separate AWS Account, with no shared access. Administration of the services provided by AWS (EC2, RDS, S3, etc.) is performed through the use of both the AWS Console and the AWS API Services for programmatic access. Only essential staff within AEM has access to these services, with access configured on a per platform basis through the use of AWS Identity and Access Management. All logins to the console are required to have a secure password of at least 12 characters and high complexity in addition to the use of TOTPs. Programmatic access to the AWS API is controlled through Secure Keys and Secrets issued via the IAM interface. Each user, and by extension each Secure Access Key, has their rights and permissions tailored to their role or intended usage. This ensures that should a single access key be compromised, its access is restricted to specific areas of functionality, it cannot be used to “mint” more access keys, and it can be easily revoked and replaced. Instance Access There exists a single instance within the Pinotage platform which is externally accessible over a port other than 443. This instance is the SSH Instance, and can be accessed via a secure SSH connection on port 22, authenticated only through the use of one of a small number of Private Keys. This ensures that access to the platforms can be tightly controlled and logged. Access to further AWS Instances is then available through this dedicated SSH instance, via the use of additional Private Keys. Since the database is not externally accessible, it too must be accessed through this dedicated SSH instance, via the use of a secure SSH Tunnel. Penetration Testing The AEM platform undergoes periodic Penetration Testing via external approved companies. In addition to this, the platform is also regularly tested for vulnerabilities via the use of automated tools such as Tenable Nessus. Not only is the platform itself probed for vulnerabilities, but the Web Interface and Web Services are regularly tested. This testing focuses on ensuring that not only are accounts secure from unauthorized access, but that the Web Interface is hardened against XSS or CSRF attacks, username enumeration, file upload vulnerabilities, and more. © 2015 Autotask Corporation l Page 28 of 197 Instance Monitoring Where previously all instances were periodically logging to S3, with the SSH Instance logs regularly reviewed, AEM is now moving to a centralized log aggregation system called Loggly. This system ensures that all system and application logs can be monitored and reviewed in real time, providing instant alerting of issues or unauthorized access attempts to a system. This centralization not only provides increased security, but also visibility of potential application issues before they become a problem. ISO27001/ISO9001 As a result of the above processes, and a commitment to best practice moving forwards, AEM has been awarded ISO27001 accreditation for Information Security and ISO9001 accreditation for Quality Management. This provides an assurance that we follow a structured process of continuous, customer focused, improvement when addressing issues with and improving processes and systems. Hosting Security A brief outline of AWS Security and Compliance information is provided below but for a full overview please visit https://aws.amazon.com/security/. Physical Security AWS data centers are housed in nondescript facilities. Physical access is strictly controlled both at the perimeter and at building ingress points by professional security staff utilizing video surveillance, intrusion detection systems, and other electronic means. Authorized staff must pass two-factor authentication a minimum of two times to access data center floors. All visitors and contractors are required to present identification and are signed in and continually escorted by authorized staff. Our hosting center only provides data center access and information to employees and contractors who have a legitimate business need for such privileges. When an employee no longer has a business need for these privileges, his or her access is immediately revoked, even if they continue to be an employee of the hosting center. All physical access to data centers by employees is logged and audited routinely. Control Environment Our hosting center manages a comprehensive control environment that includes the necessary policies, processes and control activities for the delivery of each of the AEM service offerings. The collective control environment encompasses the people, processes, and technology necessary to maintain an environment that supports the effectiveness of specific controls and the control frameworks for which the hosting center is certified and/or compliant. Our hosting service is compliant with various certifications and third-party attestations. These include: © 2015 Autotask Corporation l Page 29 of 197 l l l l SAS70 Type II. This report includes detailed controls the hosting service operates along with an independent auditor opinion about the effective operation of those controls. PCI DSS Level 1. The hosting service has been independently validated to comply with the PCI Data Security Standard as a shared host service provider. ISO 27001. The hosting service has achieved ISO 27001 certification of the Information Security Management System (ISMS) covering infrastructure, data centers, and services. FISMA. The hosting service enables government agency customers to achieve and sustain compliance with the Federal Information Security Management Act (FISMA). The hosting service has been awarded an approval to operate at the FISMA-Low level. It has also completed the control implementation and successfully passed the independent security testing and evaluation required to operate at the FISMA-Moderate level. Environmental Safeguards The hosted data centers are state of the art, utilizing innovative architectural and engineering approaches. Fire Detection and Suppression Automatic fire detection and suppression equipment has been installed to reduce risk. The fire detection system utilizes smoke detection sensors in all data center environments, mechanical and electrical infrastructure spaces, chiller rooms and generator equipment rooms. These areas are protected by either wet-pipe, doubleinterlocked pre-action, or gaseous sprinkler systems. Power The data center electrical power systems are designed to be fully redundant and maintainable without impact to operations, 24 hours a day, and seven days a week. Uninterruptible Power Supply (UPS) units provide back-up power in the event of an electrical failure for critical and essential loads in the facility. Data centers use generators to provide back-up power for the entire facility. Climate and Temperature Climate control is required to maintain a constant operating temperature for servers and other hardware, which prevents overheating and reduces the possibility of service outages. Data centers are conditioned to maintain atmospheric conditions at optimal levels. Personnel and systems monitor and control temperature and humidity at appropriate levels. © 2015 Autotask Corporation l Page 30 of 197 Set Up Autotask Endpoint Management Administrator In this section, we document the steps that you should complete before you add any data (profiles and devices) to your AEM account. Step 1 - Review the AEM Infrastructure and Requirements Before you begin with the configuration of your Endpoint Management site, you should make sure that you are hosted on the right platform, whitelist a number of IP addresses and URLs, and learn about supported operating systems and requirements for the Agent browser. Refer to "Infrastructure and Requirements" on page 9. Step 2 - Your User Account Security is important, especially if you are the person who created your company's AEM account. We recommend that you review your own user account before you permit others to access AEM. Refer to "Your User Account" on page 33. Step 3 - Licensing and Billing Billing is based on the number of Agents you have licensed. The next step should be to review "Licensing and Billing" on page 36. Step 4 - Branding Optionally, you can add your own logo to your Web Portal, and change the default colors to your company colors. To learn more about this, refer to "Branding" on page 40. Step 5 - Roles By default, the Account Admin role is assigned to the user who registers the AEM account and it is the only role available to assign to new users until other roles are created. Most likely, not everybody in your company should have full access to everything in AEM. In this step, you will configure additional roles to assign to users. Refer to "Roles" on page 43. Step 6 - Users Now you are ready to create user accounts for other people in your organization. Refer to "Users" on page 48. Step 7 - Account Settings You have a lot of control about the global settings for your site. At a minimum, you need to review the Account > Settings page to see what is possible. Refer to "Account Settings" on page 67. © 2015 Autotask Corporation l Page 31 of 197 Step 8 - Configure Integrations If you are also a customer of Autotask PSA and would like to integrate it with AEM, you must configure the integration. Refer to this topic to learn the required steps in both PSA and AEM: "Integrate with Autotask PSA" on page 95. To learn about other integrations, refer to "Configuring Third Party Integrations" on page 91. © 2015 Autotask Corporation l Page 32 of 197 Your User Account All users with permission to navigate to Account > Details Account > Details Users with permission to access the Account > Details tab can view, or view and manage their own user account. These permissions are determined by roles. Refer to "Roles" on page 43. How to... Edit your user details If your role permissions include the ability to manage your user account, you can change the values in the following fields: Name Description Account/Company This is the name of your organization as set up when you registered. Note that anyone with permission to manage Account > Details will be able to edit this name. Username The string you use to log into AEM. Once created, it cannot be edited. First name, Last name Your first and last name. Emails Your email address. Billing Email The email address of the user to whom you want us to send your invoices. VAT Number Enter the VAT Number or Tax ID of your company here. Address Line 1 / Address Line 2 Enter your street address. City/Town Enter the name of the city or town. County/State Enter a county or state. Postal Code Enter your zip code or postal code. Country Enter the official name of your country. Telephone Enter your phone number, including your extension, if applicable. Time Zone Select the correct time zone for your location. Times and dates will be recorded and displayed using this time zone. The time zone selected will determine when scheduled jobs and patch management policies will run. © 2015 Autotask Corporation l Page 33 of 197 Enable or disable two-factor authentication Two-factor Authentication (2FA) can be required at the system level, or enabled by an individual user for themselves. If 2FA is required, all users will be forced to enable 2FA for their respective logins. The process is the same either way. Refer to "Two-Factor Authentication" on page 60. Change your password If you have Manage permissions, you can proactively change your password on the Account > Details tab. Refer to "Change your own password" on page 57. Change the language of the AEM interface You can change the display language of Autotask Endpoint Management to one of the following languages: l German l Spanish l Hungarian l French l Italian l Portuguese l Swedish When you select the desired language from the Language drop-down, the screen will be refreshed and displayed in the selected language. Change your default role AEM users can be associated with more than one role, but when you log in, your default role will be used. © 2015 Autotask Corporation l Page 34 of 197 To change your default role, click the Default role drop-down and select a different role. © 2015 Autotask Corporation l Page 35 of 197 Licensing and Billing Role that includes access to Account > Packages Account > Packages On the Account > Packages page, you can review the details of your Autotask Endpoint Management (AEM) account and access the Billing Portal to pay your invoices. You will see the following information: Field Description Package Details Account Name This is the name of the company Autotask is billing for Endpoint Management. Account UID The unique ID of your Endpoint Management site. Package Indicates whether you are billed annually or monthly. Managed Devices (Request Subscription Increase) The number of managed devices used of your device limit. For more information, see "Increase your device limit" on page 39. Click the Request Subscription Increase link to increase the number of devices. A member of our Sales team will contact you shortly. OnDemand Devices The number of OnDemand devices used. For more information, see "Increase your device limit" on page 39. Extensions Additional product features that are enabled for your account, such as Branding or Patch Policies. Billing Portal View and Pay Your Invoices Click this link to open the Autotask billing portal. Refer to "View and pay your invoices" on page 37. CentraStage Invoices (Deprecated) CentraStage Invoices Old invoices will still be available to view in the existing billing portal. New invoices and your account balance at the point of transition will be available in the Autotask Billing Portal and can be paid there. Terms and Conditions Clicking the link will open the Autotask Master Services Agreement. © 2015 Autotask Corporation l Page 36 of 197 You can find the VAT number for your account and the billing email on the Account > Details tab. How to... View and pay your invoices 1. Log into the Web Portal. 2. Navigate to Accounts > Packages. 3. In the Billing Portal section, click View and Pay Your Invoices. The Autotask Billing Portal will open. 4. Review your account information to make sure it is correct. You can update billing details on the Account > Details tab. Refer to "Edit your user details" on page 33. Changes may take up to 72 hours to apply. 5. If you have not yet configured a payment method, click Set Payment Method. The Payment Configuration window will open. © 2015 Autotask Corporation l Page 37 of 197 6. Enter the required information and click Save Settings. 7. Optionally, you can check Enroll in Autopay in the Autotask Billing Portal window. When Autopay is selected, your invoice will automatically be paid in full on the due date, using the credit card information you entered in the previous step. Invoices are listed below the account and payment information. The invoice status can be Awaiting (that is, unpaid) or Paid. 8. To view an invoice, click View PDF. 9. To pay your invoice, click Pay Now. © 2015 Autotask Corporation l Page 38 of 197 10. In the Confirmation window, click Submit Payment. The status of the invoice is updated to Paid. Invoices issued prior to June 29, 2015 can still be viewed but cannot be paid here. If you have additional questions about the invoicing process or an invoice, please contact the Autotask Accounts Receivable team. Increase your device limit All accounts in AEM have a device limit. This limit is generally the number you set up when you sign up for an account. You can check the number of used and available Managed and OnDemand licenses by logging into the Web Portal and navigating to Account > Packages. When your account reaches its device limit, the AEM Web Portal will alert you with a banner at the top of the Web Portal. AEM has a 10% buffer to ensure that you don't lose connectivity to your devices when your account has reached its limit, but any new devices added above that buffer will not connect to the AEM platform. To increase your device limit: 1. Click the Request Subscription Increase link. 2. A member of our Sales team will contact you shortly. © 2015 Autotask Corporation l Page 39 of 197 Branding Role that includes access to Account > Branding Account > Branding RebrandingBranding is an extension to the Autotask Endpoint Management application. Downloading the extension lets you apply your company brand to the Web Portal, the Agent browser and reports. Users with role permissions that include access to the Account > Branding tab can customize the color scheme of the Web Portal and a number of Agent settings. How to... Add custom branding to your account 1. Navigate to Account > Branding. 2. To edit the logos or color scheme of the Web Portal, click Edit on the CSM Branding header. 3. Modify the following settings: Setting Description Custom CSM Logo This is the logo that is displayed in the top left corner of the Web Portal. To keep the aspect ratio of your logo, you should not exceed a size of 260 pixels wide by 35 pixels high. © 2015 Autotask Corporation l Page 40 of 197 Setting Description Custom Report Logo This is the logo that is displayed at the top of Endpoint Management reports. To keep the aspect ratio of your logo, you should not exceed a size of 758 pixels wide by 130 pixels high. CSM Header colour Select the color of the page header in Hex value. CSM Menu colour 1 Select the color of the top navigation menu background in Hex value. CSM Menu colour 2 Select the color of the top navigation tabs in Hex value. 4. To keep your changes, click Update. To restore the factory defaults, click Restore Defaults. To cancel without saving any changes, click Cancel. 5. To edit the logos used for the Agent and some labels in the Agent browser, click Edit on the CAG Branding header. 6. Modify the following settings: Setting Description Company Name Appears under the About section in the Agent browser (either right-click on the Agent > About or open the Agent browser > Help > About.) Product Name This is the label for the Agent browser icon in the system tray. Primary Text Specify the text that will be displayed on the Managed Agent login screen. The current text is shown to the right. OnDemand Text Specify the text that will be displayed on the OnDemand Agent login screen. The current text is shown to the right. Company URL Specify the URL that will be used by the Agent. Company Support URL Specify the Company Support URL that will be used by the Agent. Primary Logo Select the primary logo for the Agent browser (176x176, PNG file). Icons Select the icons that will be used to represent the status of the device in the system tray. Icons must be 16 x 16 pixels in ICO format only. If you use the Mac Agent, ICO files with the dimensions of 48 x 48 are required. 7. To keep your changes, click Save. To restore the factory defaults, click Restore Defaults. © 2015 Autotask Corporation l Page 41 of 197 To cancel without saving any changes, click Cancel. 8. Once your changes have been saved, click on Push Changes so that they can be applied. Remove the RebrandingBranding extension To remove the rebranding extension, simply delete it from the Extensions category in your Component Library. © 2015 Autotask Corporation l Page 42 of 197 Roles Administrator Account > Roles Roles allow you to specify and limit the access users have when logged into the Autotask Endpoint Management (AEM) Agent Browser and Web Portal. Users can have more than one role, and change them as needed without having to log out. Roles can be added, edited or deleted only in the AEM Web Portal. Changing roles is possible both in the Agent Browser and the Web Portal. To be able to add, edit or delete a role in the Web Portal, you need to have Account Admin access. For further information, refer to "Users" on page 48. By default, the Account Admin role is assigned to the user who registers the AEM account and it is the only role available to assign to new users until other roles are created. The Account Admin role is a built-in role that cannot be modified or edited in any way. Users who have this role assigned have full and unlimited access to all AEM functionality, and can see and connect to all devices in the AEM account. How to... Add a role 1. In the Web Portal, click on the Account tab. 2. Click Roles. 3. Click Add Role. 4. If you would like to copy an already existing role to use it as a template, you can choose it from the Based On drop-down list on the next page. Otherwise, select New Role. © 2015 Autotask Corporation l Page 43 of 197 5. Give the role a name and a description. 6. Select the options applicable to the new role on the Role Details page. Expand each field. Field Definition Device visibility Controls which devices the role has access to. Turn on the options to include specific profiles or groups. Permissions Turn on permissions for each area of the Web Portal (such as system, profiles, components, etc.), then check Disabled, View or Manage for each separate view. Agent Browser Tools The Agent Browser Tools control the access to each of the functions available within the AEM Agent. Disabling any of the functions will result in the feature appearing as inactive to the user on the Agent Browser. Membership Defines which users belong to this role. 7. Click Apply and Save Changes to finish creating the role. This video tutorial demonstrates how to create a role for technical support engineers allowing them to use only the remote takeover functionality in the Agent Browser and access to the Web Portal. Edit a role 1. In the Web Portal, click on the Account tab. 2. Click Roles. 3. Click on the name of the role you wish to edit. 4. Edit the Role Details. 5. Click Apply and Save Changes. Delete a role 1. In the Web Portal, click on the Account tab. © 2015 Autotask Corporation l Page 44 of 197 2. Click Roles. 3. Hover over the name of the role you wish to delete. 4. Click Delete this role. 5. Confirm role deletion. If the role you are deleting is linked to any existing jobs or policy targets, it will need to be replaced with another of the available roles. While you can replace the role used in existing jobs or policy targets, be aware that it is possible to delete the only role associated with a user. 6. Click Delete. Change your role Users who have more than one role assigned can change their role on the fly in both the AEM Agent and the web browser. Agent © 2015 Autotask Corporation l Page 45 of 197 1. On the local device where AEM is installed, right-click on the AEM Agent icon in the system tray and click Open. 2. Log in with your username and password. 3. Click on the first menu option in the top left corner. 4. Hover over Roles and select the required role from the list. 5. You will be logged out of the Agent automatically. 6. Log back in to be able to use the selected role. Web Portal 1. In the top right corner, click on your current role to see a list of available roles. © 2015 Autotask Corporation l Page 46 of 197 2. Select the required role. 3. The page will automatically refresh and the selected role will be applied. © 2015 Autotask Corporation l Page 47 of 197 Users All users with permission to navigate to Account > Users Account > Users Users in Autotask Endpoint Management (AEM) are individuals set up with a user account. You add and manage users and review the user activity log on the Account > Users tab. On this tab, you can toggle between two views: l l The Users view displays a list of all users that have been set up in your AEM system. Here, you add and manage users. The Activity view is a log of all user activity performed in both the Web Portal and Agent Browser. You can view, filter, search and export the log or parts of it. Refer to User Activity. By default, the Users view is displayed. Manage Users When the Users view is displayed, you can Review your list of users The user list will show up to 100 records on a page. The following columns are displayed: Name Description Selection check box Click the check box in the header row to select all rows, or click one or more rows to perform an action. Username Clicking the Username hyperlink will open the User Details window in Edit mode. Refer to "Edit a user" on page 49. Name Fist and last name of the user. Roles Lists all roles that are associated with this user. © 2015 Autotask Corporation l Page 48 of 197 Name Description Security Level Determines which components can be accessed by users with this role. Select a number between 2 (Low) and 5 (Super). Refer to Components and ComStore. Account Admin A toggle that will instantly add or remove the Account Admin role for the user. Refer to "Roles" on page 43. Search for a specific user 1. In the Search field, enter part of a Username or Name. As you type, the search results are narrowed to match your search string. 2. To display the full list, delete the search criteria. Add a user 1. Click Add User. 2. Fill in all the fields. Field What to Enter Username Enter a unique username, such as [email protected]

Antivirus Systemthat provides well balanced, state-of-the-art protectionagainst threatsendangering your PC
NOD32 provides well balanced, state-of-the-art protection against threats endangering your PC and enterprise systemsrunning various platforms from Microsoft Windowsthrough a number of UNIX/Linux, Novell, MS DOS operating systemsto Microsoft Exchange Server, Lotus Domino and other mail servers.
Trojans, viruses, worms and other malware using NOD32 are kept out of striking distance of your valuable data. Advanced detection methods implemented in the software even provideprotection against the future threats from most of the new worms and viruses.

The fourth generation of the NOD32 Antivirus System features a fully integrated software suite characterized by an unprecedented detection track record, the fastest scanning rates and extremely low utilization of system resources.

NOD32's detection efficiency combined with 2-50 times faster hard disk scanning rate earned the product many international prestigious awards.

NOD32 is the world leader of the Virus Bulletin 100% Awards having won more awards (21) than any competing product. Since its first submission for testing in May 1998, NOD32 was the only tested product that has never missed a single In the Wild virus.

Here are some key features of "ESET NOD32 Antivirus":
· ThreatSense technology - a single optimized anti-threat engine for analyzing code to identify malicious behavior, such as viruses, spyware, adware, phishing and more
· Unprecedented heuristic analysis capable of discovering new malware threats as they emerge
· Powerful virtual PC emulation technology enables unpacking and decryption of all types of archives and run-time packing
· Able to clean active malware running in memory
· Protects at multiple infiltration points, including HTTP, POP3, SMTP and all local and removable media
· Removes infections from files that are locked for writing (e.g., loaded DLL file)
· Prevents infected files from being opened and executed, and warns on creation of infected files
· Automatic execution on system startup
· Supports multiple Terminal Server environments
· Supports scanning of mapped network disks

System Requirements
Processor Architecture: i386(Intel®80386) AMD®64 (x86-64)
Operating Systems: Microsoft®Windows® 7/ 2000/ XP/ Vista®
Memory: 44 MB
Disk-Space (Download): 28 MB
Disk-Space (Installation): 35 MB

What's new in ESET NOD32 Antivirus 4.0.474:
· Fix: Scheduler task not displaying scan targets
· Fix: Slow opening of Office documents from a Windows 2003 server share
· Fix: Intermittent error when saving files on Windows 7
· Other minor fixes and improvements

What's new in ESET NOD32 Antivirus 4.0.468:
· Fixed: External driver injection in ESET SysRescue on Microsoft Windows 7 RC fails when this option is selected in the advanced mode of ESET SysRescue wizard
· Fixed: Error sending a file via "Send to" in the right-click menu. The problem only occurs in combination of Microsoft Windows XP and Microsoft Outlook 2003 when the Microsoft Outlook process is not running.
· Fixed: Mozilla Thunderbird with IMAP account freezes when a virus-laden message is received
· Improved: Compatibility with server operating systems
· Improved: HTTP scanning compatibility
· Other minor fixes and improvements

ESET NOD32 Antivirus 4 (32-Bit)
Microsoft® Windows® 7/Vista/XP/2000
Version: 4.0.474, File size: 31.67 MB

ESET NOD32 Antivirus 4 (64-Bit)
Microsoft® Windows® 7/Vista/XP (64-bit)
Version: 4.0.474, File size: 34.55 MB

Installation:
1. Extract and Install x64 or x86 Eset Nod32AV.
2. Install NodEnabler Using ReadMe.txt
Enjoy !

Download Links :