...
As part of the process, the Firewall Policy Group requires that anyone who wants the firewall rules modified must provide the following details:
Request Detail | Detail Style | Example | ||
Date and time for change | Date in MM/DD/YYYY format | |||
Description of the port change | Descriptive blurb | Allow all workstations of the Application Development group access to the Oracle database port | ||
Ingress/egress characteristic | Descriptive blurb | Incoming on port 1521 | Destination/source specification | Source: |
Source Specification | Descriptive blurb | wk1.ucdavis.edu, wk2.ucdavis.edu, wk3.ucdavis.edu | ||
Destination : Specification | Descriptive blurb | dbhost.ucdavis.edu | ||
The term of the change (indefinite or otherwise) | One-liner | Indefinite | ||
Project(s) related to the requested rule(s) change | Descriptive blurb | Kuali Rice Implementation | ||
Urgent? | Pick either YES or NO | NO | ||
Modification in Effect? | Pick either YES or NO | NO | ||
Reason for Disapproval | Descriptive Explanation | This request did not reflect urgency becasue of Reason A, Reason B, and Reason C. Please resubmit request. | ||
Revert Firewall Modification | Checkbox | Autofilled by workflow if an URGENT request is disapproved. |
Create Users
Let's create an XML file that defines some users who will help us simulate the Request Firewall Change process. We have requester1 who will submit all requests and FPG1 & FPG2, who will be tasked with reviewing and approving (or disapproving) those requests.
...