Getting Started

How to get started with Cobalt software.

Use this document to visualize your journey through Cobalt to secure your systems.

You want to enhance the security of your software. You’re ready to set up penetration tests (pentests) to elevate your security posture. With pentest-driven solutions, you can comply with regulations and enhance the confidence of your customers. You want results as soon as possible.

You’ve come to the right place.

Learn more.


Our journey takes you through the steps required to create a pentest:

  1. Define Your Assets. Our pentesters analyze all kinds of assets, from web apps to internal networks.
  2. Create objectives for your pentest.
  3. Define details of your environment. Is your asset in production or in development? Is part of your system on a Cloud platform?
  4. Start planning the test. Define your desired pentest start date. We need time to find the best available pentesters for your assets.
  5. Review your pentest request. Use our Pentest Checklist to make sure you’ve included all information that our pentesters need.

Once you’ve set up a pentest, we start analyzing your asset. When possible, we share results even before we create your report. Here’s what you can expect.

Assuming you’ve received an email invitation, take the next step. Sign in to Cobalt.

Sign In to Cobalt

Start the pentest process. Sign in to the Cobalt app.

Define Your Assets

Security professionals perform pentests on your assets. Collect the info they need.

Create Pentest Objectives

Now that you’ve defined an asset, it’s time to define objectives for the pentest.

Specify Pentest Details

Describe key details of your Pentest.

Plan the Pentest

Set up a schedule. Confirm the scope.

Your Pentest Checklist

Review your pentest request.

Pentest Expectations

What happens after you’ve set up your pentest.

Customize Your Pentest Report

You may be able to customize your pentest report.


Learn more about the language of software security.

Was this page helpful?

Yes No Create an Issue

Last modified March.03.2022