Cloud Security Scanning
Panther Cloud Security Scanning uses policies to detect misconfigurations in AWS accounts
Panther's Cloud Security Scanning works by scanning AWS accounts, modeling the Resources within them, and using Policies to detect misconfigurations. Cloud Security Scanning is automatically enabled when you onboard a Cloud Account to your Panther Console.
This feature can be used to power your compliance and improve your cloud security posture. Common security misconfigurations detectable by Panther include:
- S3 Buckets without encryption
- Security Groups allowing inbound SSH traffic from
- Access Keys being older than 90 days
- IAM policies that are too permissive
When adding a new AWS account, Panther runs a baseline scan and models all of the resources in your account. Account scans are performed daily to ensure the most consistent state possible. This works by using an assumable IAM Role with ReadOnly permissions.
Cloud Security Scanning is not available during Panther's free 30-day trial. Request access to the feature via an assisted trial by using the Intercom Messenger in the bottom-right corner of the Panther Console.
Onboarding a cloud account in Panther will automatically enable Cloud Security Scanning. Panther will scan the resources daily for potential vulnerabilities. You can onboard a cloud account in the Panther Console, or using the Panther API.
Additionally, we recommend onboarding your CloudTrail or CloudWatch logs as a log source integration so you can configure detections and receive alerts for active incidents and breaches.
Panther's Cloud Security Scanning performs scans daily.
- 1.Log in to your Panther Console.
- 2.In the left sidebar, click Configure > Cloud Accounts then click Connect an account.
- 3.Enter your account Name and AWS Account ID.
- You may also expand the Advanced Options to indicate which AWS Regions, Resource Types, and Resources by Region you would like to exclude from cloud scanning. This can help prevent too many alerts from being generated by regions and resources known to be misconfigured.
- 4.Click Continue Setup.
Panther needs an IAM role to have the ability to scan resources from your AWS account. You can choose from the following options to set this up:
- CloudFormation or Terraform Template File: Use Panther's provided CloudFormation template or Terraform template to create an IAM role by downloading the template and deploying on your own.
- 1.On the "Setup an IAM Role" page, click Select next to Using the AWS Console UI.
- 2.Click Launch Console UI.
- You will be redirected to the AWS console in a new browser tab, with the template URL pre-filled.
- Check the acknowledgements in the "Capabilities" box, and click Create Stack.
- 3.Navigate back to your Panther Console.
- 4.Click Continue Setup to complete the Cloud Account setup process.
- 1.On the "Setup an IAM Role page", click Select next to CloudFormation or Terraform Template File.
- 2.Click the template option you want to use, which downloads the template to apply it through your own pipeline.
- 3.Upload the template file in AWS.
- 4.Once deployed, navigate back to the Panther Console, and click Continue Setup.
If you wish to create an IAM role via some other mechanism, ensure it has the naming standard and permissions documented in Panther’s provided templates.
- 1.On the "Set Up an IAM role" page, click the link that says I want to set everything up on my own.
- 2.Create the required IAM role. You may create the required IAM role manually or through your own automation.
The Setup Verification page verifies whether the IAM role has been successfully created.
- 1.Optionally, you can click Setup CloudTrail to enable Real Time Scanning.
- If you have already configured a Log Source containing CloudTrail Logs or if you would like to configure this later, you may skip this step.
- 2.Click Finish Setup.
To onboard a cloud account with the Panther API, use the
CreateCloudAccountoperation. Note that after using this operation, you will still need to set up an IAM role in your AWS account—follow the Creating an IAM role manually or with other automation instructions above.
To set up real-time monitoring via CloudTrail logs, follow the instructions to onboard CloudTrail logs.
To leverage CloudWatch events for resource scanning and monitoring, you must configure a template in AWS and then onboard your Cloud Account.
Before getting started, review the
panther-cloudwatch-events.ymlfile within panther-auxiliary. This YAML file contains the CloudFormation stack information necessary to configure Panther's real-time CloudWatch Event collection.
It works by creating CloudWatch Event rules which feed to Panther's SQS Queue proxied by a local SNS topic in each region. Latency between an event occurring in AWS and the event being detected by CloudWatch Event rules is typically 1 minute or less.
- 2.Launch your AWS console and navigate to the CloudFormation project.
- 3.Click Create stack and choose the option "With new resources."
- 4.In the Template section, choose the option Upload a template file. Select your
- 5.Click Next.
- 6.In the Specify Details section, fill in the necessary fields, including the following:
- Stack name:
- 7.Click Next.
- 8.On the Configure stack options page, click Next.
- 9.On the Review page, make sure you have configured your settings correctly. Click Next.
To learn more about the attributes that can be referenced in Cloud Security policies, see Cloud Resource Attributes.
Visit the Panther Knowledge Base to view articles about Cloud Security Scanning policies and articles about Cloud Accounts that answer frequently asked questions and help you resolve common errors and issues.
Last modified 24d ago