Versions Compared

Key

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

Description:

...

  1. Firewall rule needs to be for a valid University business purpose.

  2. Firewall rule needs to be reviewed and approved by the Information Security Officer.

  3. Firewall rule needs to be assigned an a “Requestor” and will be audited annually.

...

  1. A Tracker ticket is submitted by a firewall rule Requestor. A "RrequestorRequestor" maybe any member of the campus community that meets the above requirements and is an employee or affiliate (e.g. FSA).

  2. The Tracker ticket is automatically assigned to the ISO and Network Design and Development Manager for review. Reviews may expand to include the Fredonia Security Operations team or ITS leadership should additional consultation becomes necessary.

  3. Upon review, a Nessus Vulnerability Management scan (Non-credentialled) will be completed by the ISO of the source and or destination hosts. NOTE: All new virtual and physical hosts are required to complete the ITS Service Production Certification Checklist.

  4. Upon approval from the ISO, the Firewall Audit Register will be completed internally and the following information will be collected  to conduct annual audits moving forward:

    1. Request Date

    2. Requestor

    3. Ticket#Reason

    4. Source

    5. Destination ports

    6. Firewall affected

    7. ISO approval

    8. approval Approval date

    9. ruled Rule created by

    10. created Created date

5.  The firewall rule is completed by the Network Design and Development Manager (Requestor - "First Name Last Name" will be annotated in the Comments section of the rule.)

...