Rule removal workflow

This topic describes the events that occur in each stage in a default rule removal change workflow.

Request

In the Request stage, a privileged user submits a request to remove or disable one or more device rules, initiating the FireFlow change request lifecycle.

This stage consists of the following steps:

1. The requesting privileged user selects a template on which to base their request.
2. If the template specifies a workflow, FireFlow assigns the request to that workflow.

3. The requesting privileged user submits the request to FireFlow.

   The request includes information about one or more device rules to remove or disable. For example, the requestor may submit the following request:

   

4. FireFlow receives the request information and creates a change request.
5. If a workflow has not yet been assigned, FireFlow assigns a workflow. For more details, see Request templates and workflows.
6. The default assignee of the role handling new change requests (by default, the Network Operations role) is assigned as the change request's owner.
7. FireFlow sends an email message informing the requesting privileged user that the change request was created, and specifying the change request ID in the format [FireFlow #<number>], for example [FireFlow #49].

Approve

In the Approve stage, the network operations user determines the network issues entailed in satisfying the request. This stage consists of the following steps:

1. The change request may change ownership in one of the following ways:

   • The change request owner assigns it to a user with the network operations role.
   • A network operations user chooses to take responsibility for the change request.

2. The network operations user initiates a search for change requests whose traffic intersects that of the selected device rule.

   FireFlow returns a list of related change requests:

   

3. The network operations user then specifies which of the related change requestors (and optionally other users) should receive a notification that the rule will be deleted.

   

4. FireFlow sends an email to the selected requestors.
5. The requestors respond via an email message or the web interface.

6. The network operations user does one of the following:

   • Approves the change request and sends it on to the next stage.
   • Rejects and closes the change request. In this case, an email message is sent to the requesting privileged user, indicating that the request is denied.
   • Contacts the requestor and asks for more information.
   • Extends the due date of the change request, giving users more time to respond.

Implement

In the Implement stage, the network operations user plans and executes request implementation.

This stage consists of the following steps:

1. FireFlow creates a work order and displays a list of recommendations for implementing the requested change.

   

2. The network operations user edits the work order, by adding notes to the work order.

3. The network operations user implements the requested changes on the security device according to the work order, by doing one of the following:

   • The user manually implements the changes or implements the changes using the relevant management system (for example, Check Point Dashboard or Juniper NSM).

   • The user implements the changes from FireFlow using ActiveChange.

     Note: In order to use ActiveChange, it must be licensed and enabled. For more details, see Implement changes with ActiveChange.

4. The network operation user sends the change request on to the next stage.

Validate

In the Validate stage, the network operation user validates the implemented rule removal/disablement against the change request. This stage consists of the following steps:

1. The network operations user validates the implemented rule removal/disablement against the change request.

   

2. If validation indicates that the specified rule was not removed/disabled, then the network operations user re-initiates the Implement stage.
3. Once the rule removal/disablement has been successfully validated, the network operations user resolves the change request.

At this point, the change request's lifecycle has effectively ended, and no further user action is required. However, the change request remains available in the system for auditing purposes, as described in the final stages.

Resolved

Once the change request has been validated, it enters the Resolved stage.

Audit

The Audit stage for rule removal request lifecycles is identical to the Audit stage for traffic change request lifecycles. See Audit.