Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Requester

  1. Submits the request just as in the previous tutorial.
  2. Is now allowed to specify if the request is urgent.

Desktop Services

  1. Field all submitted requests.
  2. Check if the requested firewall configuration is already in effect.
  3. If so, cancel or deny the request. Otherwise,
    • forward urgent requests to the Firewall Gatekeeper.
    • forward non-urgent requests to the Firewall Policy Group.

Firewall Policy Group

Firewall Gatekeeper

...

  1. Review requests and decide if they meet policy.
  2. Forward approved non-urgent requests to the Firewall Gatekeeper.
  3. Forward disapproved urgent requests to the Firewall Gatekeeper.

Firewall Gatekeeper

  1. Implement urgent requested firewall configurations immediately.
  2. If disapproved by the Firewall Policy Group afterward, reverse firewall configuration.
  3. Implement non-urgent requests upon approval of the Firewall Policy Group.

Image Added

Info

We documented the Review Non-Urgent Request and Review Urgent Request as subprocesses because there is

...

potential for the members of the Firewall Policy Group to have continuous correspondence with each other and with the Requester.

...

At this point, it is not clear how we will address these subprocesses, as there is no routing going on during the rounds of correspondence.

In using eDocLite to facilitate this process, we'll need a few things:

...