RedLock is proud to be a launch partner for Amazon GuardDuty and enable deeper visibility into AWS security and compliance risks
With RedLock, organizations can ensure compliance, govern security, and enable security operations across AWS environments.
Monitor, auto-remediate, and report on compliance using out-of-the-box policies for standards such as CIS, PCI, and HIPAA.
Enable DevSecOps by establishing policy guardrails to rapidly detect and remediate risks across resource configurations, network architecture, and user activities.
The security of public cloud infrastructure is a shared responsibility between AWS and the organization. AWS is responsible for protecting the physical infrastructure such as hubs, switches, and routers. Organizations are responsible for monitoring resource configurations, user activities, network traffic, and host vulnerabilities. However, the dynamic nature of the cloud makes this pretty challenging.
While the cloud enables agility by allowing users to create, modify, and destroy resources on-demand, this often occurs without any security oversight. RedLock provides hundreds of out-of-the-box policies for common security and compliance standards such as CIS, PCI, and HIPAA to monitor AWS environments. You can rest assured that any misconfigurations of AWS resources such as Amazon S3, EC2, security groups, and IAM roles will be immediately detected and remediated.
In cloud environments, multiple users have privileged access which enables productivity but creates greater risk of exposure. It is imperative to monitor users across your entire AWS environment for anomalous activities. Unfortunately, the distributed nature of the cloud consisting of multiple accounts and regions makes this difficult. RedLock consumes AWS CloudTrail data and Amazon GuardDuty findings from across your entire AWS environment, enabling you to detect account compromises and insider threats.
The absence of a physical network boundary to the internet increases the attack surface in the cloud by orders of magnitude. Monitoring network traffic is necessary for detecting suspicious activity. However, traditional tools create security blind spots since they cannot be deployed for monitoring traffic to API-driven services. RedLock ingests Amazon VPC flow logs and Amazon GuardDuty findings to surface, investigate, and respond to threats in your AWS environment.
As is the case in on-premise environments, unpatched hosts in cloud computing environments are also vulnerable to attack. Relying on standalone vulnerability management investments is ineffective. These tools perform periodic scans of an environment to identify hosts with missing patches based on IP address. However, cloud environments are constantly changing and IP addresses are elastic, which makes the results unreliable. RedLock integrates with external vulnerability services such as AWS Inspector to continuously scan your environment for unpatched hosts, especially those exposed to the internet.
AWS provides a number of native security tools to address each responsibility in the shared security model as an individual problem:
– Resource Configurations: AWS Config and AWS Trusted Advisor enable you to monitor resource configurations and ensure compliance
– User Activities: You can analyze AWS CloudTrail logs for suspicious user activities
– Network Traffic: Amazon Virtual Private Cloud (VPC) flow logs can be used to search for suspicious network activities
– Host Vulnerabilities/Activities: Amazon Inspector and Amazon GuardDuty enable detection of host vulnerabilities and compromises
While organizations can address each responsibility in the shared security model as an individual problem, comprehensive cloud context is necessary to be effective. For example, organizations that are simply monitoring their AWS environments for risky configurations will receive an alert if an open security group is created. Unfortunately, the severity of the threat is hard to determine based on this data point alone. Alerts without context make it hard to triage issues in a timely manner and ultimately lead to alert fatigue.
A more meaningful alert would be if the open security group is determined to be associated with an unpatched MongoDB resource that is receiving traffic from a suspicious IP address. Such an alert would require correlation of configuration, network traffic, host vulnerability, and threat intelligence data. In order to achieve this, organizations would have to build a solution that stitches together the data from each individual AWS security tool and applies AI to produce context. This exercise becomes more infinitely complex for organizations with multiple cloud accounts across multiple regions.
The RedLock Cloud 360 platform embraces and extends native AWS security capabilities by using AI to correlate disparate data sets from your environment. Specifically, it correlates resource configurations, user activities, network traffic, and host vulnerabilities/activities with third party threat intelligence sources to produce the necessary context. This provides you with actionable alerts and enables you to prioritize response based on the severity of issue.