Firewall Change Request


Firewall rules and changes are approved by the University Technology Services (UTS) Security Advisory Group (SAG) and implemented by the UTS Security Team.

This wiki covers key aspects of firewall requests and provides information to assist in composing a firewall request.

About Firewalls

Firewalls are systems that monitor and control network traffic based on predetermined rules in order to establish security barriers. A common characteristic of firewalls are to only allow approved, legitimate traffic on the network.

By default, University firewalls are configured to block all traffic, therefore firewall requests typically involve identifying what connectivity should be permitted to a server / application.

Firewall rules demo

More information about firewalls.

Requesting a Change

Firewall changes can be initaited by completing and submitting the appropriate electronic form located on the forms page. On the page scroll down to section "F" and select the "Firewall Change Request Form".

If you need assistance, or have questions you may create a firewall consultation ticket by sending an email to .

Filling out the Firewall Change Request Form

There are different fields to fill out to complete the form. In order to submit a request all boxes in red must be filled out.

Type of Request

The type of request helps categorizes the request and aids in the process all together. The type also defines the path to completion as only certain 'New' and 'Modify' requests have to be approved by the Security Advisory Group (SAG).

New Request

This request has never been made before

Modify Existing Request

The rule currently exists but needs modification

Replace Existing Request

The rule currently exists but needs to be replace with a new rule

Remove Existing Request

The rule currently exists and needs to be removed

  • To be eligible for firewall changes the software or service must have completed the university's purchasing process.

  • Multiple changes can be made in one request but must correlate to the project at hand. For example, two ports needing to be opened for one service.

Applicant Information

  • Email - Provide an email, that we can contact you at, this is a mandatory field to be fill out. * If your email is in the system, it will auto populate fields. Then you can fill out the rest of the form.

    • We might have follow up questions or need to clarify information with you.

  • Name - Enter your first and last name.

  • Phone number - Enter a phone number that we can contact you about the firewall request from. We might have follow up questions or need to clarify information with you.

  • Department - Enter your department that you are with.

  • OU Employee - Select this bullet if you’re an employee of Oakland University.

  • Student Employee - Select this bullet if you’re a student employee of Oakland University.

  • This Request will affect the following * Include what application(s) or service(s) that will be affect by this change. This is a mandatory field to be fill out.

Proposed Firewall Changes

Fill out what firewall rules you want to be implemented. To add a firewall rule, select the plus that is in the red circle in the image below. The trash can icon is how you remove a rule from your list.

Shows where to input firewall rules .

  • Source FQDN /IP - Input the source IP address. Identify by Fully Qualified Domain Name (FQDN), or IP address which servers/services will be impacted by requested change.

  • Destination FQDN/IP - Input the Destination address. Identify by Fully Qualified Domain Name (FQDN), or IP address which servers/services will be impacted by requested change.

  • Application - What type of protocol will be used. * Examples are : HTTP,HTTPS, URL, SSH, FTP, DNS.

  • Protocol - Select the type of Protocol. Is required and the options are: * TCP

    • UDP

    • ICMP

    • IP

    • TCP/UDP

  • Action - What do you want this rule to do. Your options are: * Permit - Allow the communication between the SourceFQDN /IP, Destination FQDN/IP and Port.

    • Block - Disallow the communication between the Source FQDN /IP, Destination FQDN/IP and Port.

Commonly Used Ports and Protocols

  • URL: TCP and UDP port numbers

  • HTTP protocol on port 80 (TCP/UDP)

  • HTTPs protocol on port 443 (TCP/UDP)

  • SSH protocol on port 22 (TCP/UDP)

  • FTP protocol on port 20-21 (TCP/UDP)

  • DNS protocol on port 53 (TCP/UDP)

Additional Information

  • Desired Start Date - Pick a date on which you would want the firewall change to be made by. * Note: Please allow a minimum of two weeks for requests to be reviewed and three weeks for implementation.

  • End Date - A date that the firewall rule(s) will no longer be implemented. To specify an end date uncheck the "Indefinite End Date" checkbox, then enter in date. * Starting/Stopping dates of the change if only needed for duration of time or only to take effect after a certain date.

  • Indefinite End Date - If you want to keep these rules in place, indefinitely, then select this checkbox.

  • Reason for Request - Please prove why these firewall rules are being implemented. This is a mandatory field to be fill out. * Provide a brief description / business case of why the request is being made.

    • If this is a new software/server/service please provide the previous ticket number submitted for Software reviewed to UTS.

    • List the application required (preferred but not required).

    • Vendor documentation or references that help support the requested change.

    • The physical location of a device or of the firewall.

    • Let it be known if VPN access will be required. * If so, then a VPN access form may be required.

  • Note: The more information you can provide, the better UTS can implement the firewall rule changes in a timely changes.

Other Actions:

  • Submit - This will submit the form to UTS .Upon submitting you will receive an email confirmation that your form has been sent to UTS.

  • FAQ - Will direct you to the Electronic Forms FAQ page.

  • Attach - Please attach all necessary vendor documentation and documentation related to this request.

    • Below are some examples of documentation, such as diagrams and tables, that your vendor may provide that are helpful to attach to a Firewall Request Form.

How a firewall works firewall information