We’re wrapping up at re:Invent 2018 and I wanted to highlight our integration efforts with AWS Security Hub, announced in Andy Jassey’s keynote on Wednesday. AWS Security Hub is designed to provide users with a comprehensive view of their high-priority security alerts and compliance status by aggregating, organizing and prioritizing alerts, or findings, from multiple AWS services such as Amazon GuardDuty™, Amazon Inspector, and Amazon Macie™ as well as from other APN security offerings. The findings are then visually summarized on integrated dashboards with actionable graphs and tables.
The integration efforts we announced are twofold, allowing joint customers to use these collaborative efforts to protect their applications and data on AWS.
- RedLock integration: RedLock by Palo Alto Networks further protects AWS deployments with cloud security analytics, advanced threat detection and compliance monitoring. RedLock continuously collects and correlates log data and configuration information from AWS Config, AWS CloudTrail®, Amazon Virtual Private Cloud (Amazon VPC®) flow logs, AWS Inspector and Amazon GuardDuty to uncover and send security and compliance alerts to the AWS Security Hub console. The RedLock integration with AWS Security Hub provides additional context and centralized visibility into cloud security risks, allowing customers to gain actionable insights, identify cloud threats, reduce risk and remediate incidents, all without impeding DevOps. View a brief demo.
- VM-Series integration: The VM-Series next-generation firewall complements AWS security groups by first reducing the attack surface through application control policies, and then preventing threats and data exfiltration within allowed traffic. The VM-Series integration with AWS Security Hub uses a Python script or an AWS Lambda function to collect threat intelligence and send it to the firewall as an automatic security policy update that blocks malicious (IP address) activity. As AWS Security Hub updates the IP address information, the security policy is updated without administrative intervention, allowing security to operate at the speed of the cloud. View a brief demo.
With more businesses moving to the cloud, it’s critical that the alert data they receive provides them with actionable insights to successfully combat cyberattacks. These product integrations will help customers verify that their users, applications, and data are secure through a single pane of glass.
AWS Transit Gateway Support
For deployments with many VPCs, customers are commonly using a Transit VPC architecture as a means of reducing operational complexity by centralizing common services like VM-Series firewalls, logging, perhaps DNS into a “hub” VPC. Spoke VPCs will connect to and transit the hub to gain access to other resources and locations via IPsec VPN and in some cases VPC peering. As the number of VPCs grows, so too does the connectivity complexity. That’s where the new AWS Transit Gateway will help. With the Transit Gateway you simply connect each Amazon VPC or VPN to the AWS Transit Gateway and it will route traffic to and from each VPC or VPN. With the VM-Series firewall deployed within a spoke connecting to the Transit Gateway, traffic can be protected from threats and data theft. We’re in the final stages of testing but currently, but we know we can secure traffic flowing Inbound, East/West and Outbound with VPC insertion and VPN insertion. Be sure to watch for updates to the Transit VPC with the VM-Series automation templates found here.