Getting Started with a Free Codefortify Account

This guide will help you get started with our platform, manage your projects, integrate GitHub repositories, and configure security scanners like Gitleaks.

Free Account Features

When you sign up for our free account, you'll have access to:

• 5 user seats

• 1 scanner: Gitleaks (example)

Setting Up Your First Project

1. Create a Project Begin by creating a project in Codefortify.

   
2. Add a Repository Add a repository to your project using our GitHub SSO integration. Turn on the scanners you want installed in your repository.

   
3. Automatic Scanner Setup Codefortify automatically configures scanners for your GitHub repository by setting up the correct scanner and GitHub Action.

Managing Your Scanners

There are two ways to manage your scanners:

1. Using the Integrations Page

   • Navigate to the Integrations link in the left-hand menu.

   • From here, you can turn on or off the scanners available to you, depending on your subscription level.

1. Via the Repository Settings

   • Go to Projects > Repo and select your repository.

   • Click the "Edit GitHub Repo" button.

   • Toggle your available scanners on or off.

Using the Gitleaks Secrets Scanner with Codefortify

License Key for Organization Repositories

Gitleaks scanning requires an additional step if you're scanning repositories belonging to an organization account. You'll need a free Gitleaks license key.

For personal account repositories, no license key is required.

How to Get a Free Gitleaks License Key

1. Visit Gitleaks.io.
2. Click Sign Up to complete a Google form with your name, email, and company details.

3. After submitting the form, you will receive an email with your free license key.

Adding Your License Key

Once you have your Gitleaks license key, it must be added as an encrypted secret in one of the following locations:

• The repository

• The organization

---

Using Secrets in GitHub Actions

Secrets in GitHub Actions allow you to store sensitive information in your repository, organization, or specific repository environments. Ensure you follow best practices when handling and storing sensitive data, such as your Gitleaks license key.

For more information on how to use and configure secrets in GitHub Actions, visit the GitHub documentation on secrets.