Technical requirements

  • A valid Archer user of the specified Instance

  • The user must have permission to view issues, create issues, and update issue status in a Risk Project.

Archer expires sessions per user if another session is active. Only one active Archer connection per user is supported. This includes the "Test Connection" button.

Default-assigned fields

The following fields are set by default:

  • Description

  • Overall Status (Default: Open)

  • Criticality

  • Finding Workflow Stage (Default: New)

  • Target (Risk Project)


The integration supports the following:

  • One-way status synchronization. The integration currently only supports synchronizing status from Archer tasks to SD Elements.

  • Advanced field support


The following configuration fields are available when creating a connection. Fields are available for both system and project connections unless otherwise specified. Fields will only be available for project connections if allowed by the system connection.

To ensure a successful integration, be sure to enter the correct values for the configuration fields instead of using the default values. Review the remaining fields as well, and change the default values as required.

Default Priority Mapping

SD Elements








Connection details

Enter the details SD Elements will use to connect to the Archer server.


Select the protocol for the connection (HTTPS or HTTP) (Default: HTTPS)


The domain name or IP address of the server (Example:

Context Root

Top-level location where Archer is installed on a server. The value for this may be dependent on the configuration of an internal corporate proxy, or where an administrator has installed Archer.

Archer Instance

Instance name for the Archer server.

Archer User Domain (Optional)

Domain name for User of the Archer Instance.


Enter the credentials needed to authenticate to the server.


Username authorized to connect with the server.


The password used to authenticate to the server.

Countermeasures to Synchronize

Select Countermeasures to synchronize.

Sync all Countermeasures

Synchronize all Countermeasures from SD Elements.

Sync Risk Policy Countermeasures

Synchronize only Countermeasures that fall under the risk policy.

Project details

Enter the project-level details.

Archer Risk Project Tracking ID

The Tracking ID of the Risk Project where findings should be created.

Advanced Archer configuration

States that map to DONE in SD Elements:

Comma-separated list of states in Archer that will be mapped to DONE in SD Elements. (Default: Closed)


Enter settings for synchronizing the SD Elements and Archer projects.

Authoritative Source

Select the tool that will be the authoritative system of record: Archer or SD Elements. This field is used in case of conflicting statuses between the Archer issue and the SD Elements Countermeasure. When you first synchronize a TODO Countermeasure in SD Elements with an issue in Archer, they will have the same status. If you then change the status in one tool, such as by closing the issue in Archer, they will have conflicting statuses. This conflict is resolved when the projects are synchronized.

  • ALM (default): The SD Elements Countermeasure will be updated to match the status in Archer. This is relevant to most workflows. Two-way status sync is not presently supported.

Include code sample How-To’s in Countermeasure descriptions

Whether or not to include detailed code samples and How-To’s in the Archer issue.

This ALM server is hosted within a private network and cannot be reached directly by SD Elements.

Select this option if SD Elements does not have direct network access to the Archer server.

For example, if you are using a hosted SD Elements instance but you want to integrate with an internal/protected Archer system, choose this option and run the Remote Integration Agent to perform integration.

Filter Countermeasures

Select SD Elements Countermeasures to synchronize to Archer.

Countermeasures having a minimum priority

Only synchronize Countermeasures with a minimum priority, such as 7 or above. This is useful if you want to limit the amount of work for users. (Default: 1)

Countermeasures with status meaning

Only synchronize Countermeasures with certain statuses, such as TODO or DONE. (Default: TODO)

Limit to Countermeasures having these phases

Only synchronize Countermeasures in certain phases, such as Requirements or Development. (Default: none selected, meaning Countermeasures from all phases will be synchronized)

Countermeasures having all of the following tags

Only synchronize Countermeasures containing certain SD Elements Countermeasure tags. (Optional)

Countermeasures with verification status

Only synchronize Countermeasures with a specific verification status, such as Pass or Fail. (Default: none selected, meaning Countermeasures with any verification status will be synchronized)

Advanced ALM options

Enter advanced configuration options for the connector.

ALM Title Format

Customize the issue titles created in the ALM by choosing one of the templates below. (Default: "T21: Countermeasure title")

Bypass server certificate validation for HTTPS (insecure, only for testing purposes)

ALM context

Provide a specific identifier to this project integration that can be used in an issue’s generated title format. This is applicable only when the ALM Title Format option contains 'Context'

Custom Priority Mapping

If the standard Archer priorities have been customized, you must map the customized priority names in Archer to their corresponding SD Elements numeric priorities.

By default, SD Elements maps priorities 7-10 to High, 4-6 to Medium, and 1-3 to Low.

Sync frequency

Select how frequently the SD Elements and Archer projects are synchronized. You can choose from the following options. The more frequently you run synchronization, the greater the performance impact on both the SD Elements and Archer servers. This is generally only a concern for large organizations running many synchronizations at once.

Hourly, Daily, Weekly, or Monthly

The projects will synchronize automatically every hour, day, week, or month. Daily synchronization is typically sufficient. However, you may want to select a more frequent interval if development moves quickly in your organization.


You must click the Sync button on the ALM Integrations page to synchronize the projects. This is the default value.

results matching ""

    No results matching ""