Security-as-a-Service for AWS compatibility and requirements



Security-as-a-Service for Amazon Web Services (AWS) is a malware protection service developed by Bitdefender for Amazon Elastic Cloud Compute (EC2) environments. Built on Security for Virtualized Environments (SVE) by Bitdefender, an innovative and comprehensive solution designed specifically for virtualized environments, Security-as-a-Service for AWS protects Amazon EC2 instances running Windows or Linux operating systems.

This article provides you with comprehensive information on the compatibility and requirements of Security-as-a-Service for AWS. It is useful to get familiar with the Security-as-a-Service for AWS components (described in this KB article).

Overview

Security-as-a-Service for AWS is exclusively compatible and integrates with the Amazon Elastic Compute Cloud (Amazon EC2) web service. To use Security-as-a-Service for AWS, you need an account on the Security-as-a-Service for AWS website (Security Console) and install the Silent Agent on each instance to be protected. You can obtain an account by registering here.

Security Console Requirements

Security Console can be accessed from the following web browsers:

  • Internet Explorer 8+
  • Mozilla Firefox 4+
  • Google Chrome
  • Safari
  • Opera

Internet connection is needed. Recommended screen resolution: 1024x768 or higher

Supported Guest Operating Systems

Security-as-a-Service for AWS protects instances running one of the following operating systems:

  • Windows Server 2012 / Windows Server 2012 R2 
  • Windows Server 2008 / Windows Server 2008 R2
  • Windows Server 2003 / Windows Server 2003 R2
  • Red Had Enterprise Linux / CentOS 5.6 or higher
  • Ubuntu 10.04 LTS or higher
  • SUSE Linux Enterprise Server 11 or higher
  • OpenSUSE 11 or higher
  • Fedora 15 or higher
  • Debian 5.0 or higher

Amazon Credentials

The following Amazon credentials are required in order to subscribe to and set up Security-as-a-Service for AWS:

  • Your Amazon sign in credentials (email address and password). When subscribing, you are required to sign in to Amazon Payments and authorize payments to Bitdefender for your Security-as-a-Service for AWS subscription.
  • Access key ID and secret access key of your Amazon account or of an AWS Identity and Access Management (IAM) user. The access key enables Security-as-a-Service for AWS to synchronize with your AWS account and provide real-time visibility into your Amazon EC2 infrastructure.

    Note: To learn how to create an AWS Identity and Access Management (IAM) user with the minimum required privileges for use with Security-as-a-Service for AWS, refer to this KB article.

  • The private keys of your Amazon EC2 key pairs. You need access to your instances to install Silent Agent.

Free Ports

The following ports are used with Security-as-a-Service for AWS:

Ports

Usage

SSH (22)

Port used to access instances running on Linux.

RDP (3389)

Port used to access instances running on Windows.

8082

Communication port between Silent Agent and Security Console.

7081

Communication port between Silent Agent and the scan daemon running on the Security Virtual Appliance.

7074

Communication port between Silent Agent and the Update Server hosted by Security Console.

Amazon EC2 security groups must allow inbound access to SSH and RDP during installation of Silent Agent on instances. If you run firewall software on your instances, make sure to configure it to allow access to all of the previously specified ports.


Note: Security-as-a-Service for AWS also supports by design Windows client operating systems (such as Windows XP or 7), which are currently not available on Amazon EC2.





Applies to: Security-as-a-Service for Amazon Web Services (AWS)

Operating Systems: Debian/Ubuntu, Fedora, FreeBSD, Mandrake, Red Hat, Slackware, SUSE, Windows 2003, Windows 2008, Windows 2008 R2

Related Articles: