Rackspace PDR on AWS

  • Last updated on: 2018-12-06
  • Authored by: Nick Shobe

Rackspace Proactive Detection & Response (PDR) on Amazon Web Services® (AWS) has two main components that need to be implemented in your AWS environment: the Network-based Intrusion Detection (NIDS) appliance infrastructure must be set up, and select vendor agents must be deployed.

Deployment of an NIDS appliance infrastructure

To enable visibility of your AWS network, we deploy NIDS appliances to each Amazon Virtual Private Cloud® (VPC) where you have Amazon Elasic Compute Cloud® (EC2) instances being monitored by our Rackspace PDR teams.

NIDS appliance platform requirements

Rackspace PDR uses either Amazon CloudFormation® or HashiCorp® Terraform® to deploy NIDS appliances in AWS. Our current NIDS appliances are provided by the Alert Logic® Threat Manager™ offering.

Our PDR teams deploy, manage, and monitor your NIDS Threat Manager appliances. Rackspace PDR has the following platform requirements:

  • Be a Rackspace AWS customer
  • Have a minimum of two (for H/A) threat manager appliances per VPC containing monitored instances
  • Have at least one NIDS per AZ containing monitored instances
  • Configure PDR-covered VPCs with a private subnet and NAT gateway routing to 0.0.0.0/0, even for subnets configured with public IP assignment. NIDS appliances are never assigned public IPs and should be able to reach instances on their private addresses.
  • Set up egress and ingress firewall rules as defined in Rackspace PDR Threat Manager network requirements
For Rackspace-manged AWS accounts

Work with your AWS support team to implement the standards in the following outline. Ensure that ingress and egress requirements pass through any security WAFs or AWS gateway devices that sit in front of 0.0.0.0/0.

For self-managed AWS accounts

The CloudFormation or Terraform templates that you are provided create and manage IAM roles, Security Groups, and so on that aid you in the set up and configuration of the following network configuration outline. You might need to implement some additional network rules where it makes sense for your environment.

NIDS appliance network configuration

In a default environment, our AWS team uses our deployment tools to create and manage the security groups needed to deploy your platform. Customers implementing custom routing or application firewalls should see Rackspace PDR Threat Manager Network Requirements to ensure that your AWS platform conforms to our specifications.

NIDS appliance end-to-end decryption

Many appliactions terminate Secure Socket Layer (SSL) and Transport Layer Security (TLS) at the network edge with a load-balancer or web application firewall. If your application uses end-to-end encryption, see the Rackspace PDR SSL Decryption Guide.

Deployment of vendor agents

Individual PDR agents are deployed and maintained by the Rackspace PDR team. However, we do have base requirements that must be met to ensure that our automated deployment system and PDR support team can access your instances to deploy or troublshoot agents and systems.

Following these steps helps to ensure successful agent deployments:

  • Deploy using operating systems and kernals compatible with Rackspace PDR.
  • Install the Amazon Systems Manager Agent® (SSM Agent).
  • Ensure that you’ve implemented the appropriate network access control lists (ACLs) and firewall configurations.

Building compatable instances

Due to the various vendors that we have selected to provide the nessessary telemetry to our systems, it is important that you select operating systems and kernel versions that are compatable with the vendor agents. For more information, see the Rackspace PDR System Requirements.

Golden or Base images

It is important that images taken from hosts that have Rackspace PDR agents deployed be prepared for deployment before using them as base images. Follow the Rackspace PDR Imaging Hosts guide to ensure Golden images are properly prepared.

Amazon System Manager Agent

The current requirement for all AWS environments is to have the SSM agent installed and configured on all Rackspace PDR monitored instances. This enables our select vendor agent deployment platform as well as our security operations team to perform nessessary actions against your infrastructure. For more information, see Install AWS Systems Manager Agent (SSM Agent).

Instance network requirements

The agents used to provide telementry to our Security Operations Center (SOC) do have specific networking requirements that must be implemented. Use the Rackspace PDR Agent Network Requirements guide to correctly implement network ACLs and firewall rules for your platform.

Additional information

For more information on the Threat Manager offering, see the Alert Logic upstream vendor documentation.

Share this information: