This whitepaper is for historical reference only. Some content might be outdated and some links might not be available.
Control Name Descriptions
This section provides detailed descriptions of the controls used in the intrusion method, in the order they are presented in the phases. Intrusion method implementations are likely to follow a category-based implementation.
For a list of these controls, ordered by category, and for recommendations on how to prioritize implementations, see the Prioritizing Control Implementations section.
Amazon GuardDuty
Amazon GuardDuty
Amazon GuardDuty detects reconnaissance activity, such as unusual API activity, intra-VPC port scanning, unusual patterns of failed login requests, or unblocked port probing from a known, bad IP address.
Amazon GuardDuty Partners
Amazon GuardDuty APN Partner
Amazon Detective
Amazon Detective
AWS security services like Amazon GuardDuty, Amazon Macie, and AWS Security Hub as well as partner security products can be used to identify potential security issues, or findings. These services are really helpful in alerting you when something is wrong and pointing out where to go to fix it. But sometimes there might be a security finding where you need to dig a lot deeper and analyze more information to isolate the root cause and take action. Determining the root cause of security findings can be a complex process that often involves collecting and combining logs from many separate data sources, using extract, transform, and load (ETL) tools or custom scripting to organize the data, and then security analysts having to analyze the data and conduct lengthy investigations.
Amazon Detective simplifies this process by enabling your security teams to easily investigate and quickly get to the root cause of a finding.
Bottlerocket
Bottlerocket
AWS WAF, WAF Managed Rules + Automation
AWS WAF
Scanners and Probes
Malicious sources scan and probe Internet-facing web applications for vulnerabilities. They send a series of requests that generate HTTP 4xx error codes, and you can use this history to help identify and block malicious source IP addresses. This solution creates an AWS Lambda function that automatically parses Amazon CloudFront or Application Load Balancer access logs, counts the number of bad requests from unique source IP addresses, and updates AWS WAF to block further scans from those addresses.
Known Attacker Origins (IP Reputation Lists)
A number of organizations maintain IP address reputation lists, which are lists of IP addresses operated by known attackers, such as spammers, malware distributors, and botnets. These services leverage the information in these reputation lists to help you block requests from malicious IP addresses.
Bots and Scrapers
Operators of publicly accessible web applications have to trust that the clients accessing their content identify themselves accurately, and that they will use services as intended. However, some automated clients, such as content scrapers or bad bots, misrepresent themselves to bypass restrictions. These services help you identify and block bad bots and scrapers.
AWS WAF Security Automations
Once deployed, AWS WAF protects your Amazon CloudFront distributions or Application Load Balancers by inspecting web requests. You can use AWS WAF to create custom, application-specific rules that block attack patterns to ensure application availability, secure resources, and prevent excessive resource consumption.
For more information, see AWS WAF Security
Automations
Amazon CloudWatch, CloudWatch Logs, CloudTrail + Insights, Reporting & Third Parties
In addition to Amazon CloudWatch, CloudWatch Logs, AWS CloudTrail, and reporting tools such as Amazon OpenSearch Service, and Amazon QuickSight, you can integrate with third-party tools such as Splunk, Trend Micro, and Alertlogic.
You can use Amazon CloudWatch Logs to monitor, store, and access your log files from Amazon Elastic Compute Cloud (Amazon EC2) instances, AWS CloudTrail, Amazon Route 53, and other sources. You can then retrieve the associated log data from CloudWatch Logs.
Amazon CloudWatch Logs Insights enable you to interactively search and analyze your log data in Amazon CloudWatch Logs. You can run queries to help you quickly and effectively respond to operational issues. If an issue occurs, you can use Amazon CloudWatch Logs Insights to identify potential causes and validate deployed fixes.
When you create your AWS account, AWS CloudTrail is automatically enabled. When activity occurs in your AWS account, that activity is recorded in a CloudTrail event. You can easily view events in the CloudTrail console in the event history. From the event history, you can view, search, and download the past 90 days of activity in your AWS account. You can also create a CloudTrail trail to archive, analyze, and respond to changes in your AWS resources.
Amazon CloudWatch Logs + Amazon Lookout for Metrics
Amazon Lookout for Metrics
You can use Amazon CloudWatch metrics as a data source for an Amazon Lookout for Metrics detector. For details, see the Amazon Lookout for Metrics Developer Guide.
Amazon CloudWatch Logs + Amazon Lookout for Metrics + Lambda
After Amazon Lookout for Metrics creates an anomaly detection model, or detector, you
can attach alerts to it using supported output connectors such as Amazon Simple Notification
Service (Amazon SNS), AWS Lambda functions, Datadog, PagerDuty, Webhooks, and Slack. You can
create custom alerts to notify you when Amazon Lookout for Metrics detects an anomaly of a
specified severity level. For more details, see Preview: Amazon Lookout for Metrics, an Anomaly Detection Service for Monitoring the
Health of Your Business
AWS Security Hub
AWS Security Hub
A Security Hub insight is a collection of related findings defined by an aggregation statement and optional filters. An insight identifies a security area that requires attention and intervention. Security Hub offers several managed (default) insights that you cannot modify or delete. You can also create custom insights to track security issues that are unique to your AWS environment and usage.
AWS Security Hub Automated Response and Remediation
The AWS Solutions Implementation AWS Security Hub Automated Response and Remediation
AWS Security Hub Automated Response and Remediation is an add-on solution that works with
AWS Security Hub
AWS Security Hub Partners
AWS Security Hub APN Partner
Amazon Virtual Private Cloud (Amazon VPC)
Amazon Virtual Private Cloud (Amazon VPC)
Amazon VPC provides advanced security features, such as security groups and network access control lists, to enable inbound and outbound filtering at the instance level and subnet level. In addition, you can store data in Amazon S3 and restrict access so that it’s only accessible from instances in your Amazon VPC. Optionally, you can choose to launch Dedicated Instances, which run on hardware dedicated to a single customer for additional isolation.
In this context, Amazon VPC can help prevent attackers from scanning network resources during reconnaissance.
NAT Gateways
You can use a network address translation (NAT) gateway to enable instances in a private subnet to connect to the internet or other AWS services, but prevent the internet from initiating a connection with those instances.
Amazon VPC Black Hole Routes
You can use Amazon VPC black hole routes as an allow list or deny list of network reachable assets before Security Groups or NACLs.
The state of a route appears in the route table (active | black hole). When the state is black hole, the route’s target isn’t available. For example, the specified gateway isn’t attached to the VPC, or the specified NAT instance has been terminated.
For more information, see describe-route-tables in the AWS CLI Command Reference.
VPC Endpoints
A VPC endpoint enables you to privately connect your VPC to supported AWS services and VPC endpoint services powered by PrivateLink, without requiring an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC do not require public IP addresses to communicate with resources in the service. Traffic between your VPC and other services does not leave the Amazon network.
AWS PrivateLink
AWS PrivateLink
Amazon EC2 Security Groups
A security group is a virtual firewall that controls inbound and outbound traffic to your network resources and Amazon EC2 instance.
Network Access Control Lists
Similar to a firewall, Network Access Control Lists (NACLs) control traffic in and out of one or more subnets. To add an additional layer of security to your Amazon VPC, you can set up NACLs with rules similar to your security groups.
AWS Identity and Access Management + AWS Organizations
AWS Identity and Access Management (IAM)
AWS Certificate Manager + Transport Layer Security
Protecting data in transit denies attackers the ability to capture data in transit during Reconnaissance, unless they are able to impersonate a legitimate endpoint.
AWS Certificate Manager
For more information, see:
Network Infrastructure Solutions in the AWS Marketplace
The infrastructure solutions in the AWS Marketplace can help deny attackers access to your data and infrastructure as they conduct reconnaissance.
For more information, see Network Infrastructure
Software on the AWS Marketplace
Amazon Virtual Private Cloud VPN Gateway + AWS Direct Connect
An Amazon Virtual Private Cloud (Amazon VPC) VPN gateway connection creates a link between your data center (or network) and your Amazon VPC . A customer gateway is the anchor on your side of that connection, and can be a physical or software appliance. The anchor on the AWS side of the VPN connection is known as a virtual private gateway.
For more information, see https://docs.aws.amazon.com/vpn/index.html.
You can use AWS Direct Connect
Amazon GuardDuty + AWS Lambda
Amazon GuardDuty
Amazon GuardDuty detects reconnaissance activity, such as unusual API activity, intra-VPC port scanning, unusual patterns of failed login requests, or unblocked port probing from a known bad IP address.
To learn more about the types of findings that Amazon GuardDuty can identify, see Finding types.
AWS Lambda
For example, the following blog post describes how to use AWS GuardDuty and AWS Web
Application Firewall to automatically block suspicious hosts by triggering AWS Lambda
responders: How to use Amazon GuardDuty and AWS Web Application Firewall to automatically block suspicious
hosts
When an attack is detected by Amazon GuardDuty, AWS Lambda responders can be used to modify security configurations to block traffic associated with an attack in progress as well as isolate the potentially compromised environment.
This same approach, AWS GuardDuty > Amazon CloudWatch Events > AWS Lambda responders, can be used to disrupt other flows.
Honeypot and Honeynet Environments
Deception technology products present themselves as part of a legitimate infrastructure. When an attacker attempts to compromise the infrastructure, the deception technology helps to degrade, detect, and contain the attack, so your system recovers from attacks faster.
Deception technology products for honeypot or honeynet environments include third-party deception technology solutions, both commercial and open-source. Solutions include Guardicore, Attivo, Illusive, TopSpin, or TrapX. There are also numerous open-source solution honeypot and honeynet projects on GitHub and elsewhere.
Honeywords and Honeykeys
Planting false credentials makes attackers think they have something of value when they do not. When an attacker attempts to use stolen, false credentials, it helps your system to detect and contain the attacker, so your system recovers faster. The detected use of honeykeys and honeywords is always a true positive for intrusion attempts.
AWS WAF + AWS Lambda
AWS WAF
Honeypot (A) for Bad Bots and Scrapers
This component automatically sets up a honeypot, which is a security mechanism intended to lure and deflect an attempted attack. The honeypot is a trap endpoint that you can insert in your website to detect inbound requests from content scrapers and bad bots. If a source gets access to the honeypot, the Access Handler AWS Lambda function intercepts and inspects the request to extract its IP address, and then add it to an AWS WAF block list.
Amazon CloudWatch Events & Alarms + Amazon SNS + SIEM Solutions
You can combine Amazon CloudWatch Events & Alarms with Amazon Simple Notification Service (SNS) and integrate them with security information and event management (SIEM) solutions like Splunk or AlertLogic.
Amazon CloudWatch Events delivers a near real-time stream of system events that describe changes in Amazon Web Services (AWS) resources. Using simple rules that you can quickly set up, you can match events and route them to one or more target functions or streams.
You can create a CloudWatch alarm that watches a single CloudWatch metric or the result of a math expression based on CloudWatch metrics. The alarm performs one or more actions based on the value of the metric or expression relative to a threshold over a number of time periods. The action can be a notification sent to an Amazon SNS topic.
You can also add alarms to CloudWatch dashboards and monitor them visually or integrate with other SIEM solutions.
For more information, see:
Network Infrastructure Solutions in AWS Marketplace
The network infrastructure solutions that are available in the AWS Marketplace can help you deny access to the attackers attempting get your data and infiltrate your infrastructure as they conduct reconnaissance.
For more information, see Network Infrastructure
Software on the AWS Marketplace
Amazon Cognito
Amazon Cognito provides solutions to control access to backend resources from your application. You can define roles and assign users to different roles so your application can access only the resources that are authorized for each user.
Amazon Cognito Identity Pools (Federated Identities)
Amazon Cognito identity pools (federated identities) enable you to create unique identities for your users and federate them with identity providers. With an identity pool, you can obtain temporary, limited-privilege AWS credentials to access other AWS services.
Reverse Proxy Architecture
Reverse proxies are a powerful software architecture primitive for fetching resources from a server on behalf of a client. They serve a number of purposes, from protecting servers from unwanted traffic to offloading some of the heavy lifting of HTTP traffic processing.
For more information, see NGINX reverse proxy sidecar for a web container hosted with Amazon ECS and
AWS Fargate
Amazon Virtual Private Cloud + Automation
With Amazon Virtual Private Cloud (Amazon VPC) Subnet Isolation, you can contain compromised systems by using AWS Command Line Interface (AWS CLI), or software development kits using predefined, restrictive security groups. You can save the current security group of the host or instance, and then isolate the host using restrictive ingress and egress security group rules.
For more information, see AWS Security Incident Response Guide.
AWS Shield
AWS Shield
All AWS customers benefit from the automatic protections of AWS Shield Standard, at no additional charge. AWS Shield Standard defends against most common, frequently occurring network and transport layer DDoS attacks that target your website or applications. When you use AWS Shield Standard with Amazon CloudFront and Amazon Route 53, you receive comprehensive availability protection against all known infrastructure (Layer 3 and 4) attacks.
Amazon VPC Flow Logs + Amazon CloudWatch Alarms
Amazon VPC Flow Logs enables you to capture information about the IP traffic going to and from network interfaces in your Amazon VPC. Flow log data is stored using Amazon CloudWatch Logs. After you’ve created a flow log, you can view and retrieve its data in Amazon CloudWatch Logs and Amazon S3, or another analytics tool. You can also use flow logs as a security tool to monitor the traffic that is reaching your instance.
For more information, see Publishing flow logs to CloudWatch Logs.
AWS Identity and Access Management (IAM) + IAM Policies and Policies Boundaries
AWS Identity and Access Management (IAM)
You manage access in AWS by creating policies and attaching them to IAM identities (users, groups of users, or roles) or AWS resources. A policy is an object in AWS that, when associated with an identity or resource, defines their permissions.
A permissions boundary is a managed policy in which you set the maximum permissions that an identity-based policy can grant to an IAM entity. When you set a permissions boundary for an entity, the entity can perform only the actions that are allowed by both its identity-based policies and its permissions boundaries.
AWS Identity and Access Management (IAM) Roles
AWS Identity and Access Management (IAM) Roles help deny or contain the blast radius of attacks. For example, you can use an IAM role to grant permissions to applications running on Amazon EC2 instances.
For more information, see Using an IAM role to grant permissions to applications running on Amazon EC2 instances.
Role-based access control (RBAC) and attribute-based access control (ABAC) are authorization strategies that provide flexibility in granting permissions to resources.
AWS Organizations + Service Control Policies (SCPs) + AWS Accounts
With AWS Organizations
Service control policies (SCPs) are one type of policy that you can use to manage your organization. SCPs enable you to restrict, at the account level of granularity, what services and actions are available to the users, groups, and roles in those accounts.
Amazon Simple Storage Service (Amazon S3) Bucket Policies, Object Policies
A bucket policy is a resource-based AWS Identity and Access Management (IAM) policy. You add a bucket policy to a bucket to grant other AWS accounts or IAM users access permissions for the bucket and the objects in it.
With an Amazon S3 bucket policy, malicious objects that contain attacker payload can be prevented from directly being uploaded into the bucket. All objects must be uploaded through the application and subject to malware checks before they can be stored in an Amazon S3 bucket.
For more information, see Managing access to resources.
Amazon EC2 – Linux, SELinux – Mandatory Access Control
Mandatory Access Control can be configured as a system policy that cannot be overridden, which mediates access to files, devices, sockets, other processes, and API calls for users (including root) and processes.
Amazon EC2 – FreeBSD, Trusted BSD – Mandatory Access Control
Mandatory Access Control for FreeBSD and Trusted BSD can be configured as a system policy that cannot be overridden, which mediates access to files, devices, sockets, other processes, and API calls for users (including root) and processes.
Amazon EC2 – Linux, FreeBSD – Hardening and Minimization
Hardening and minimization make it difficult to exploit a vulnerability in a service by reducing the services that are running and removing or uninstalling unnecessary services.
For example, applying carefully considered sets of recommendations from CIS Amazon
Linux 2 Benchmark - Level 2
Amazon EC2 – Linux – Role-Based Access Control (RBAC) and Discretionary Access Control (DAC)
RBAC and DAC provide least-privilege account profiles mediated by root that control which users can get access to your resources.
Amazon EC2 – Windows – Device Guard
With Windows Device Guard for your Amazon EC2 instance, you can specify which binaries are authorized to run on your server, including user mode and kernel mode binaries, which enhances AppLocker functionality.
Microsoft Windows Security Baselines
A security baseline is a group of Microsoft-recommended configuration settings. You can use security baselines to:
-
Set configuration settings. For example, you can use Group Policy to configure a device with the setting values specified in the baseline.
-
Make sure that user and device configuration settings are compliant with the baseline.
For more information, see Windows security baselines on the Microsoft Documentation site.
AWS Physical & Operational Security Policies & Processes
Amazon Web Services is responsible for protecting the global infrastructure that runs all of the services offered in the AWS Cloud. This infrastructure comprises the hardware, software, networking, and facilities that run AWS services. Protecting this infrastructure is AWS’s number one priority, and while you can’t visit our data centers or offices to see this protection firsthand, we provide several reports from third-party auditors who have verified our compliance with a variety of computer security standards and regulations.
For more information, see AWS
Compliance
Immutable Infrastructure – Short-Lived Environments
In the case of Amazon EC2, Containers, and especially AWS Lambda, short environment lifetimes (when compared to traditional datacenters) mean that an environment being targeted at time t=”now” may not be the same as an environment being targeted in time t=”now+5 minutes”. When environments are being rebuilt or refreshed every few minutes, it is a much more difficult task to make an attack payload persist.
When your production environment does not have privileges configured, including for the network infrastructure, there is nothing for attackers to modify and your environment is more resilient to attacks.
Load Balancing
With load balancing, before an attacker can consistently get access to your resources, all the instances included in the load-balanced service need to be compromised by the attack. If one or more instances has not been compromised, the load balancer switches to an unaffected instance, which degrades the attack.
For more information, see Elastic Load Balancing
AWS Lambda, Amazon Simple Queue Service (Amazon SQS), AWS Step Functions
These services are orchestration mechanisms for containment.
AWS Lambda
Amazon Simple Queue Service (Amazon SQS)
AWS Step Functions
AWS WAF
AWS WAF
AWS container and abstract services
AWS container and
abstract services
Linux cgroups, namespaces, SELinux
SELinux and the technologies that support it (including cgroups and namespaces) can enforce capability profiles that prevent running processes from accessing files, network sockets, and other processes, using Mandatory Access Control. This means that, even if a running process is compromised, it can be prevented from accessing other resources on the OS instance, or even doing things expected of regular Unix processes (such as forking copies of itself or reading world-read files).
Hypervisor-Level Guest-to-Guest and Guest-to-Host Separation
The hypervisor for Amazon EC2 instances and other services is in-scope for PCI-DSS certification for separating different operating system instances from each other, and guest operating systems from itself. Hypervisor separation, and the additional technologies incorporated as modules into it (such as Security Groups), provide mechanisms to mitigate some risks of one compromised Amazon EC2 instance being used as a platform to compromise other instances.
AWS Systems Manager State Manager
AWS Systems Manager State Manager helps you define and maintain consistent OS configurations such as firewall settings and anti-malware definitions to comply with your policies. You can monitor the configuration of a large set of instances, specify a configuration policy for the instances, and automatically apply updates or configuration changes.
AWS Partner Network (APN) Offerings – File Integrity Monitoring
File integrity monitoring (FIM) and enforcement are controls that help maintain the
integrity of operating system files and application files by verifying the current file
state and a known good baseline of these files. Check features of products carefully for
enforcement or reversion capabilities. For information about AWS Marketplace solutions, see File Integrity Monitoring on the AWS Marketplace
Third-Party WAF Integrations
Some examples of third-party tools that integrate with AWS WAF include Trend Micro, Imperva, and Alert Logic.
For more information about third-party integrations with AWS WAF, see AWS WAF Partners
AWS Config
AWS Config
AWS Config rules
AWS Config rules are a configurable and extensible set of Lambda functions (for which source code is available) that trigger when an environment configuration change is registered by the AWS Config service. If AWS Config rules deem a configuration change to be undesirable, they can act to remediate it. In common with all other Lambda functions, AWS Config rules can be assigned IAM Roles with permissions that enable them to make appropriate remedial API calls.
Amazon CloudWatch Events + Lambda
Amazon CloudWatch Events occur when various states are detected (such as GuardDuty findings), and can be used to trigger Lambda functions in the same manner as AWS Config rules. If the Lambda functions deem an event to be undesirable, they can act to remediate it, using IAM Roles with the correct permissions to allow them to make appropriate remedial API calls.
AWS Managed Services
AWS Managed Services
CloudFormation + Service Catalog
AWS CloudFormation
Service Catalog
AWS Systems Manager State Manager, or Third-Party or OSS File Integrity Monitoring Solutions on Amazon EC2
AWS Systems Manager State Manager is a secure and scalable configuration management service that automates the process of keeping your Amazon EC2 and hybrid infrastructure in a state that you define.
File integrity monitoring (FIM) and enforcement are controls that help maintain the
integrity of operating system files and application files by verifying the current file
state and a known good baseline of these files. Check features of products carefully for
enforcement or reversion capabilities. For information about AWS Marketplace solutions, see File Integrity Monitoring on the AWS Marketplace
Third-Party Security Tools for Containers
There are several third-party security tools available for containers offered by AWS
Partners on the AWS Marketplace
Third-Party Security Tools for AWS Lambda Functions
Two of the third-party security tools available for Lambda functions are offered by Check Point Software Technologies Ltd. and Palo Alto Networks.
Please check the AWS Marketplace
AWS Partner Offerings – Behavioral Monitoring, Response Tools and Services
AWS Partner offerings, such as Alert
Logic
AWS Partner Offerings – Anti-Malware Protection
AWS Technology Partner
AWS Lambda Partners
AWS Lambda Partners
AWS Container Partners – Security
AWS Container Competency
Partners
AWS IoT Device Defender + AWS IoT SiteWise
AWS IoT Device Defender
AWS IoT SiteWise
For more information, see Configuration and vulnerability analysis in AWS IoT SiteWise.
AWS Secrets Manager
AWS Secrets Manager
Amazon EC2 – Linux, Windows, FreeBSD – Address Space Layout Randomization (ASLR)
Address space layout randomization (ASLR) is a technology that prevents shellcode from being successful. It does this by randomly offsetting the location of modules and certain in-memory structures. Although this can help prevent the exploitation of vulnerabilities, there are limits to how effective it is. Processors, and operating systems need to provide ASLR support, and on some operating systems, applications must opt in.
Amazon EC2 – Linux, Windows, FreeBSD – Data Execution Prevention (DEP)
Data execution prevention (DEP) is a memory safety feature that makes it more difficult for malware to run. It prevents certain memory blocks, such as the stack, from being executed.
For more information about DEP, see Data Execution Prevention on Microsoft's Documentation site
Amazon EC2 – Windows – User Account Control (UAC)
UACs, also known as least-privilege user account, make it more difficult for malware to install and run.
For more information about UACs, see How User Account Control works
Amazon Simple Email Service Spam and Virus Protection
Amazon Simple Email Service (Amazon SES) uses a number of spam and virus protection measures. It uses block lists to prevent mail from known spammers from entering the system. It also performs virus scans on every incoming email message that contains an attachment. Amazon SES makes its spam detection verdicts available to you, so you can decide if you trust each message. In addition to the spam and virus verdicts, Amazon SES provides the DKIM and SPF check results.
Amazon SES uses in-house content filtering technologies to scan email content for spam and malware. In exceptional cases, accounts identified as sending spam or other low-quality email might be suspended, or Amazon SES may take such other action as it deems appropriate. When malware is detected, Amazon SES prevents these emails from being sent.
For more information, see Amazon SES FAQs
AWS Auto Scaling
AWS Auto Scaling
If a Respond control automatically kills an instance of an operating environment (such as an Amazon EC2 instance, container, or Lambda function), AWS Auto Scaling creates new instances from reference images to replace it in line with load requirements.
AWS Systems Manager State Manager, AWS Systems Manager Inventory, AWS Config
AWS Config
When attackers create new AWS assets, or if malware is installed with a regular package, the AWS Systems Manager Inventory identifies it and sends it to AWS Config for evaluation.
Amazon EC2 Forward Proxy Servers
A forward proxy server is an intermediary for requests from internal users and servers, often caching content to speed up subsequent requests. Companies usually implement proxy solutions to provide URL and web content filtering, IDS/IPS, data loss prevention, monitoring, and advanced threat protection.
Outbound Proxy Partners
Outbound proxy
partner products
Amazon GuardDuty + AWS Lambda + AWS WAF, Security Groups, NACLs
Amazon GuardDuty
When an attack is detected by Amazon GuardDuty, AWS Lambda responders can be used to modify security configurations to block traffic associated with an attack in progress as well as isolate the potentially-compromised environment.
For more information, see How to use Amazon GuardDuty and AWS Web Application Firewall to automatically block suspicious
hosts
AWS DR Options
The AWS Cloud supports many popular disaster recovery (DR) architectures, from pilot light environments that might be suitable for small customer workload data center failures, to hot standby environments that enable rapid failover at scale. With data centers in regions all around the world, AWS provides a set of cloud-based disaster recovery services designed to provide rapid recovery of your IT infrastructure and data.
For more information about available disaster recover technology, see CloudEndure Disaster Recovery
AWS Partners Offerings – SQL Behavioral Analytics Proxies
Third-party behavioral analytics proxies for SQL, such as SecuPi
AWS Nitro Enclaves
AWS Nitro Enclaves
AWS Key Management Service (AWS KMS) + AWS CloudHSM
AWS Key Management Service (AWS KMS)and AWS CloudHSM can prevent attackers from exfiltrating clear text data that has been encrypted, as well as crypto key material used to encrypt data.
AWS Key Management Service
AWS CloudHSM
For more information, see AWS CloudHSM
AWS KMS Key Policies
The primary method to manage access to your AWS KMS keys (formerly CMKs) is with policies. Policies are documents that describe who has access to what. Policies attached to an IAM identity are identity-based policies (or IAM polices), and policies attached to other kinds of resources are resource-based policies. In AWS KMS, you must attach resource-based policies to your AWS KMS keys. These are key policies. All KMS CMKs have a key policy.
AWS Network Firewall
AWS Network Firewall is a stateful, managed, network firewall and intrusion detection and prevention service for your virtual private cloud (VPC). Its flexible rules engine lets you define firewall rules that give you fine-grained control over network traffic, such as blocking outbound Server Message Block (SMB) requests to prevent the spread of malicious activity.
AWS Network Firewall includes features that provide protections from common network threats. Its intrusion prevention system (IPS) provides active traffic flow inspection so you can identify and block vulnerability exploits using signature-based detection. AWS Network Firewall also offers web filtering that can stop traffic to known bad URLs and monitor fully qualified domain names.