Skip to content
English
  • There are no suggestions because the search field is empty.

How Do I Create Credentials in Edgescan?

Credentials are added into Edgescan and then associated with an asset. You can add network or application credentials. Edgescan also supports self-registration.

Version Number: v1.0.4

Published Date: 22 Apr 2026

____________________________________________________________________________

In order to facilitate testing by the Edgescan testing team, customers are required to provide current credentials for authenticated assets.

Credentials follow your organization's hierarchy and are only shared downward from parent to child, never upward or sideways.

What this means in practice:

  • Parent organization - Credentials added here are available to that organization and all organizations beneath it in the hierarchy.

  • Child organization -  Credentials added here are available to that organization and any of its child organizations, but are not visible to the parent or to sibling organizations at the same level.

  • Sibling organizations (same parent) - Credentials are never shared between organizations at the same level. Each sibling only has access to its own credentials and those inherited from above.

Regardless of inheritance, a user must still have the appropriate permissions to view or manage a credential. Inheritance makes a credential available within a scope; permissions determine who can act on it.

Creating Credentials

  1. Users with the authorization to modify credentials can easily do so by clicking on the Administration banner, and selecting Credentials. This will bring you to the credentials page.

  2. Click the add button to create a new credential.

  3. Enter a Name (required) and an optional Description

  4. Select the Organization the credential belongs to

  5. Select the Credential Type, further information about supported credentials are available in this article. 

  6. Fill in the username and password associated with the testing account and add the form field if you have any additional data that needs to be communicated during authentication. 

    Once restrict visibility is set to true for a field on a LoginForm credential it is no longer visible to any users in the UI or via the API and it cannot be reverted back to "No"

  7. Save