Connecting to SecureTrack and SecureChange

The Rule Lifecycle Management App (RLM) retrieves expired, or soon-to-be expired, rules from SecureTrack and opens tickets in SecureChange to certify or decertify the rules, according to the decision of the rules' Rule Owners. In the Settings () tab, the App Administrator configures RLM to connect with SecureTrack and SecureChange.

Prerequisites

Create workflows in SecureChange:

• Rule Recertification (mandatory)
• Rule Decommission (optional)
• Rule Modification (optional)

It is strongly recommended that these workflows be unique for the app, as unique workflows may be needed for compliance/audit requirements and can be used in future reporting. For more information, see TOS Admin: Creating Users and Workflows.

Connect to SecureChange

In the SecureChange section:

1. Enter the SecureChange credentials:

   • Host: The IP address of the SecureChange server.

   • Login username

   • Login password

   RLM uses this user, with the permission Create and handle tickets on behalf of another user (via API only), to submit API requests to SecureChange. If this is a new user, log in to SecureChange with that user to validate it. This user performs all API requests, including opening tickets with the username defined in the requester field.

2. Enter the workflow information:

   • Rule Recertification Workflow: Select the name of the SecureChange workflow that RLM will use to open rule recertification tickets. Enable the toggle to update the rule metadata (implement the certification decision) automatically.

   • Rule Decommission Workflow: Select the name of the SecureChange workflow that RLM will use to open rule decommission tickets. The workflow must verify that the rule has changed before the ticket is closed. Enable the toggle if you want RLM to automatically open this workflow and disable rules after they have been decertified.

   • Rule Modification Workflow: Select the name of the SecureChange workflow that RLM will use to open rule modification tickets.

   For more details about these workflows, see Creating Workflows for the App.

3. Enter the Ticket Requester and Default Owner Group:

   • Ticket Requester: Enter the name of the user who will open SecureChange tickets. This is the user who will appear as the ticket requester, but does not require other RLM operations. This user does not need the on-behalf option (in SecureChange user permissions) to open tickets.

   • Default Owner Group: The group, which must have at least one member, will be added to the rules in RLM that are not fully covered by the owners. This group is responsible for mediating tickets for which owners disagree about the certification decision.

Connect to SecureTrack

In the SecureTrack section, enter the following information:

• Login username
• Login password

The username and password need to be for a SecureTrack user with Super Administrator permissions. If this is a new user, log in to SecureTrack with that user to validate it.