Getting Started

Get Started in 5 Minutes

Want to jump right into using Fugue? Follow the steps below to have an environment up and running in 5 minutes.

Sign up for Fugue

Register for a free account here. You’ll start with a 30-day free trial, after which you can purchase a paid plan or be transitioned to the free-forever Developer plan.

Step 1: Environment Setup

Enter your environment’s name and select the provider (AWS, Azure, Google, Repository):

_images/step1_AWS_create.png

Step 2: Environment Settings

AWS and AWS GovCloud

Select the region(s) and resource types to scan, then create an IAM role and enter the role ARN:

_images/aws-setup-regions-resources.png _images/aws-setup-role-options.png

Azure and Azure Government

  1. Create an Azure Active Directory application and service principal.

  2. Assign the service principal a Reader RBAC role.

    1. If you want access to Active Directory resources then additionally assign the required AD role. We recommend only activating Active Directory support for the credentials associated with a single Fugue environment. Your Active Directory resources will show up in this environment and if you add Active Directory permissions in other environments, the resources will be duplicated.

  3. Generate a client secret.

  4. Enter tenant ID, subscription ID, application (client) ID, and client secret into the environment creation page.

_images/azure-setup-creds.png

5. Select resource groups to scan.

_images/azure-setup-rgs-1.png

Google

  1. Enable Google Service APIs.

  2. Create a Service Account and enter the returned email address back in the Fugue environment setup.

Repository

  1. Enter the Repository URL.

  2. Enter the Branch Name.

_images/step_2_repo.png

Step 3: Select Compliance Families

Select the compliance families you want Fugue to use to assess your infrastructure (AWS, Azure, or Google):

Note

Select Yes to use the list recommended compliance families, which includes Fugue out-of-the-box compliance families, as well as custom families.

_images/compliance-options-step3.png

Note

Repository environments currently utilize compliance settings that are configured locally with Regula. In a subsequent release, users will be able to manage compliance settings with the Fugue SaaS UI, API, and CLI.

Step 4: Review

AWS and AWS GovCloud

Review the following:

  • Environment name

  • Region(s)

  • AWS IAM role ARN

  • Compliance standards

  • Resource types to scan

_images/aws-setup-review-settings.png

Azure and Azure Government

Review the following:

  • Environment name

  • Credentials

    • Tenant ID

    • Subscription ID

    • Application (client) ID

    • Client secret

  • Compliance standards

  • Resource groups to scan

_images/azure-setup-review.png

Google

Review the following:

  • Environment name

  • Credentials

    • Service Account

  • Compliance standards

_images/review_google.png

Repository

Review the following:

  • Environment name

  • Provider

  • URL

  • Branch name

_images/step_3_repo.png
  • Kick off a scan to view resource details about your repository. See Setup- Repository.

Further Reading