AWS Onboarding

Simple Mode

1. In Simple Mode, Panoptica can only connect to a single AWS account, so Deploy single account is pre-selected
2. Type the Account Name as you you want it to appear in Panoptica's console.
3. Select your region from the drop-down box
4. Decide whether you want to enable automatic data scanning, to identify PII, PCI, PHI, or secret data in your environment. See Data Type Classification for details. (Data Scanning is in Preview mode, and may not be available in all tenants.)
5. Once all fields are complete, the blue Launch Stack button will light up. Click Launch Stack to open the CloudFormation template in your AWS environment.

🚧

Disable Popup Blocker

If you are running a Popup Blocker, please disable it before clicking Launch Stack

5. Leave the default settings in the CloudFormation − Create Stack screen, and check the box beside I acknowledge that AWS CloudFormation might create IAM resources.
6. Click Create set
7. Wait a few minutes for the Stack creation to complete, which will be indicated in the Panoptica platform as well as in AWS.

Once the Stack is deployed, Panoptica will start scanning your AWS resources.

Advanced Mode – Single account

1. In Advanced Mode, Panoptica can connect to a single AWS account, or an AWS organization.
   Let's start with selecting Deploy single account.

   
   

2. Type the Account Name as you you want it to appear in Panoptica's console.

3. Choose your region from the drop-down box

4. In Advanced Mode, you can configure how Panoptica executes workload scans. This is the step where you choose your scanning preferences.

   • Enabling Workload Scanning scans your AWS resources for CVEs and malware, as well as local user accounts in your VMs with weak passwords.
     In order to minimize impact to your environment, Panoptica takes a snapshot of the EBS volumes attached to the EC2 instances, then copies and converts those snapshots to new EBS volumes.
     You can choose where you want the snapshots scanned.
     • Selecting External scan scans the snapshots in an external Panoptica account. This calls for less internal resources, but requires more data mobility. The snapshots are shared with the external account, not copied.
     • Selecting Internal Scan scans the snapshots using a dedicated account in your environment. This improves performance and keeps your data local.
       If you select Internal Scan, you'll need to provide the Account ID of the account where the scanning will take place.
   • Enabling Serverless Scanning scans your Lambda functions, using a dedicated Panoptica Lambda
   • Enabling Data Scanning automatically identifies PII, PCI, PHI, or secret data in your environment. See Data Type Classification for details. (Data Scanning is in Preview mode, and may not be available in all tenants.)

🚧

Important

New AWS accounts have reduced concurrency and memory quotas for Lambda functions. AWS raises these quotas automatically based on your usage.
However, if you experience any performance issues, you may need to reserve or provision additional resources for Panoptica's Lambda function.

See the following AWS guides for additional information and assistance:

• Lambda function scaling
• Configuring reserved concurrency

5. Once all fields are complete, the blue Launch Stack button will light up. Click Launch Stack to open the CloudFormation template in your AWS environment in a new browser tab. It's best to make sure you're logged into your AWS account beforehand.

🚧

Disable Popup Blocker

If you are running a Popup Blocker, please disable it before clicking Launch Stack.

All of the relevant parameters will be pre-loaded in the AWS CloudFormation − Create Stack screen, according to the information you provided in Panoptica's onboarding procedure.

6. Leave the default settings, and check the box beside I acknowledge that AWS CloudFormation might create IAM resources.

7. Click Create set
8. Wait a few minutes for the Stack creation to complete, which will be indicated in the Panoptica platform as well as AWS.

Once the Stack is deployed, Panoptica will start scanning your AWS resources.

Advanced Mode – AWS Organization

📘

Prerequisites

• Enable StackSet trusted access with AWS Organizations. An AWS guide on how to do this can be found here. Note that this requires an Admin on the management account.
• If you have already onboarded individual accounts in this AWS organization to Panoptica, they must be deleted from Panoptica (via the Accounts table) before starting AWS organization deployment.

Organization Deployment - Create Stack

Before you start, log into your organization management (master) account in AWS, to make sure you have the proper credentials to deploy the stackset.

1. In Advanced Mode, Panoptica can connect to a single AWS account, or an AWS organization.
   Let's select Deploy AWS organization this time.

   
   

2. Type the Account Name as you you want it to appear in Panoptica's console.

3. Choose your region from the drop-down box

4. In Advanced Mode, you can configure how Panoptica executes workload scans. This is the step where you choose your scanning preferences.

   • Enabling Workload Scanning scans your AWS resources for CVEs and malware, as well as local user accounts in your VMs with weak passwords. In order to minimize impact to your environment, Panoptica takes a snapshot of the EBS volumes attached to the EC2 instances, then copies and converts those snapshots to new EBS volumes.
     • Snapshots from AWS Organizations are scanned "internally", using a dedicated account in your environment to perform the scans. Provide the Account ID of the account where the scanning will take place.
   • Enabling Serverless Scanning scans your Lambda functions, using a dedicated Panoptica Lambda
   • Enabling Data Scanning automatically identifies PII, PCI, PHI, or secret data in your environment. See Data Type Classification for details. (Data Scanning is in Preview mode, and may not be available in all tenants.)

🚧

Important

New AWS accounts have reduced concurrency and memory quotas for Lambda functions. AWS raises these quotas automatically based on your usage.
However, if you experience any performance issues, you may need to reserve or provision additional resources for Panoptica's Lambda function.

See the following AWS guides for additional information and assistance:

• Lambda function scaling
• Configuring reserved concurrency

5. Once all fields are complete, the blue Launch Stack button will light up. Click Launch Stack to open the CloudFormation template in your AWS environment in a new browser tab. It's best to make sure you're logged into your AWS account beforehand.

🚧

Disable Popup Blocker

If you are running a Popup Blocker, please disable it before clicking Launch Stack

All of the relevant parameters will be pre-loaded in the AWS CloudFormation − Create Stack screen, according to the information you provided in Panoptica's onboarding procedure.

6. Leave the default settings, and check the box beside I acknowledge that AWS CloudFormation might create IAM resources.

7. Click Create set
8. Wait a few minutes for the Stack creation to complete, which will be indicated in the Panoptica platform as well as AWS.

Once the Stack is created, you're ready to define and deploy the StackSets for your organization.

Organization Deployment - Define StackSets

1. Once all resources are created successfully, click StackSets from the menu to the left in your AWS management console.
   Select the PanopticaSecurityAudit StackSet that was created.

2. Click the Actions drop-down menu and select the Add stacks to StackSet option.

3. Set deployment targets:
   We recommend onboarding the entire Organization, but you can choose to onboard accounts from specific OUs (Organizational Units) if you prefer.

4. Specify regions:
   Select the US East (Ohio) region from the drop-down list. Once done, click Next.

5. Click Next again in the following screen.
6. After the final review click Submit to start the deployment.

Congratulations! You can now view the “Stack instances” tab to see the status of each account's deployment.

Each account that was successfully deployed should be onboarded and scanned by Panoptica in a matter of minutes. You can see the accounts and their statuses in Panoptica’s Accounts page.

📘

Note:

For larger Organizations, the initial scan of all accounts may take some time to complete.