Resources

Fairleigh Dickinson University regularly hosts on-campus visitors requiring access to our wireless network. As a security measure, in order to provide access to our Network, an FDU faculty member, staff member, or student must sponsor the guest(s) that they are providing access to. The sponsor takes responsibility for the Internet usage of their guests and ensures that they adhere to FDU’s Acceptable Use Policy for Computer Usage.

Choosing the Correct Account Type

• Accounts can be created for up to 8 days
• The sponsor can manage accounts (extend time, delete, suspend or reset password)
• Account creation requires a valid FDU NetID to create
• A single Guest Account (Known Guest) can be created or generic accounts (5 devices per account with the ability to create 10 generic accounts at once) can be created through this function

For events that will have a large audience, a Group Account may be needed. If you are a faculty or staff member and you require this account type, please create a sponsored guest account and then create a UTAC ticket. This can be accomplished by contacting the Fairleigh Dickinson University Technical Assistance Center (UTAC). 

Please provide UTAC with the following information:

• Guest account name
• The name that you would like to use for your Group account
• Faculty/staff sponsor name, contact number and e-mail address
• Location for the event (Building, Room, Classroom, etc.)
• Time and date of the event

Once the ticket is created, OIRT (Office of Information Resource Technology) will contact you within 3 business days to complete the Group account activation.

EduRoam

Fairleigh Dickinson is a member of Eduroam (education roaming) which provides secure, world-wide roaming access service for the international research and education community. If your guest is coming from another Higher Education institution that is also a member of Eduroam, they will not require an FDU guest account. Instead, they can gain access to our Network simply by logging into the eduroam network with their regular credentials.

(Available on Metro and Florham Campus Only)

Creating and Managing an FDU Wireless Guest Account

1. Log into access.net.fdu.edu using your NetID and password

2. Click the “Generic” or “Known Guest” button

• Generic – This option allows you to create up to 10 accounts concurrently without entering your guest’s information

• Known Guest – This option allows you to create an account with guest information. You need to input the guest’s “First name”, “Last name”, “Email address”, and “Phone number”. You also need to enter your own FDU email address

3. If you have selected “Generic”, enter the number of accounts that you would like to create (maximum of 10)

4. The remaining instructions are for both known guests and generic accounts. Choose how long you want the guest account to be active

• First Option – Click the box next to “End of business day” if your guest only requires access through the end of the day

• Second Option – Type the number of days required in the “Duration” box (maximum of 8). The “From Date” and “To Date” will automatically change based on the requested duration

• Optional – If needed, you can select an exact date and time for the guest account access to begin and end (24:00 format)

5. Click the “Create” button

1. Log into access.net.fdu.edu using your NetID and password

2. Click the “Manage Accounts” tab

3. Check the box next the account that you would like to update. You can now use the following administrative functions

• Edit: Modify any information entered during account creation
  
• Resend: Print or email the account username and password
  
• Extend: Add additional time to the account. The maximum total duration of 8 days will still apply
  
• Delete: Immediately delete the account
  
• Reset Password: This will reset the password and either print or email the new password

Support

For additional support, please contact the University Technical Assistance Center (UTAC)

All employees of Fairleigh Dickinson University are responsible for conducting business in a safe and secure way. Select employees may be required to view Personal Information (PI) and Personal Health Information (PHI) as part of their daily responsibilities, while others may handle sensitive information of another nature. All employees receive correspondence from outside the University. Ensuring that our community remains safe and diligent in the face of today’s cyber landscape is vital. The policy below will provide a baseline understanding of the data security protocols in place and the expectations on FDU employees to uphold them.

Effective Date: 12/01/2022
Last Revision: 03/15/2021
Last Review: 11/28/2022

I. OBJECTIVE

The objective of Fairleigh Dickinson University (“University”) in the development and implementation of this comprehensive Written Information Security Program (“WISP”) is to create effective administrative, technical and physical safeguards for the protection of Personal Information (“PI”) and Protected Health Information (“PHI”). The WISP sets forth the University’s procedure for evaluating its electronic and physical methods of accessing, collecting, storing, using, transmitting, and protecting PI and PHI.

For purposes of this WISP, PI means:

1. User name, email address, or any other account holder identifying information, in combination with any password or security question and answer that would permit access to an online account.

2. Someone’s name and any one of the following data elements:
   
   • Social Security number, Social Insurance number, National Insurance number, or equivalent;
     
   • Date of birth (MM/DD/YYYY),
     
   • Driver’s license number, state-issued identification card number, or provincially-issued identification card number;
     
   • Financial account number, or credit or debit card number, with or without any required security code, access code, personal identification number or password, that would permit access to an individual’s financial account;
     
   • Passport number;
     
   • Medical history, mental or physical condition, or medical treatment or diagnosis by a health care professional or health insurance information; or
     
   • Student/Employee (i.e., Datatel) ID number coupled with a password or security question and answer or any portion of any item in the list above that would permit access to an online account.

For purposes of this WISP, PHI includes information that is created, received, and/or maintained by the University that is related to an individual’s health care (or payment related to health care) that directly or indirectly identifies the individual.

PI or PHI shall not include information that is lawfully obtained from publicly available information, or from federal, state, provincial or local government records lawfully made available to the general public.

Notwithstanding the above and irrespective of whether or not it’s considered PII or PHI, one should always take care and caution to use the minimum data elements necessary to perform the business function at hand.

II. PURPOSE

The purpose of the WISP is to better:

1. Ensure the security and confidentiality of PI and PHI;
   
2. Protect against any anticipated threats or hazards to the security or integrity of such information; and
   
3. Protect against unauthorized access to or use of such information in a manner that creates a substantial risk of identity theft or fraud.

III. SCOPE

In formulating and implementing this WISP, the University has addressed and incorporated the following protocols:

1. identified reasonably foreseeable internal and external risks to the security, confidentiality, and/or integrity of any electronic, paper or other records containing PI and PHI;

2. assessed the likelihood and potential damage of these threats, taking into consideration the sensitivity of the PI and PHI;

3. evaluated the sufficiency of existing policies, procedures, information systems, and other safeguards in place to control risks;

4. designed and implemented a WISP that puts safeguards in place to minimize those risks, consistent with the requirements of the regulations in this document; and

5. implemented regular monitoring of the effectiveness of those safeguards.

IV. DATA SECURITY COORDINATOR

The University has designated the Chief Information Security Officer (CISO), working together with the Data Security Information Response Team (DSIRT), to implement, supervise and maintain the WISP. See Appendix II for contact information for the CISO and DSIRT. Together, they will be responsible for:

1. Initial implementation of the WISP;
   
2. Regular testing of the WISP’s safeguards;
   
3. Evaluating the ability of each of the University’s third party service providers to implement and maintain appropriate security measures for the PI and PHI to which the University has permitted them access, consistent with the regulations outlined in this document; and requiring such third party service providers by contract to implement and maintain appropriate security measures;
   
4. Reviewing the scope of the security measures in the WISP at appropriate intervals, including the review of any material change in the University’s business practices that may implicate the security or integrity of records containing PI and PHI; and
   
5. Conducting training sessions for all University employees, and independent contractors, including temporary and contract employees, who have access to PI and PHI on the elements of the WISP. All attendees at such training sessions are required to certify their attendance at the training, and their familiarity with University requirements for ensuring the protection of PI and PHI.

V. INTERNAL RISKS

To combat internal risks to the security, confidentiality, and/or integrity of any electronic, paper or other records containing PI and PHI, and evaluating and improving, where necessary, the effectiveness of the current safeguards for limiting such risks, the following measures are mandatory and effective immediately:

Internal Threats

1. The University shall only collect PI and PHI of students, their parents, alumni, donors, suppliers, vendors, independent contractors or employees that is necessary to accomplish the University’s legitimate need to access said records, and for a legitimate job-related purpose, or necessary for University to comply with state, provincial, or federal regulations.
   
2. Access to records containing PI and PHI shall be limited to those persons who are reasonably required to know such information in order to accomplish a University legitimate business purpose or to enable the University to comply with state, provincial or federal regulations.
   
3. All persons who fail to comply with this WISP shall be subject to disciplinary measures, up to and including termination, irrespective of whether PI and PHI was actually accessed or used without authorization. Any such discipline shall be in accordance with processes and procedures of Human Resources and subject to any protections afforded under the University’s agreement with “Office & Professional Employees International Union”, the “Faculty Handbook”, and similar documents.
   
4. Access to PI and PHI shall be restricted to authorized University personnel only.
   
5. Any PI and PHI stored shall be disposed of when no longer needed for business purposes or required by law for storage. Paper or electronic records (including records stored on hard drives or other electronic media) containing PI and PHI shall be disposed of only in a manner that complies with the regulations outlined in this document and as follows:
   
   • Paper documents containing PI and PHI shall be shredded upon disposal so that PI and PHI cannot be practicably read or reconstructed; and
     
   • Electronic media and other non-paper media containing PI and PHI shall be destroyed or erased upon disposal so that PI and PHI cannot be practicably read or reconstructed.

6. A copy of this WISP must be distributed to each current University employee and to each new University employee at the commencement of their employment.

7. Procedures for Terminated Employees (whether voluntary or involuntary)
   
   • Terminated employees must return all records containing PI and PHI, in any form that may at the time of such termination be in the former employee’s possession (including all such information stored on laptops or other portable devices or media, and in files, records, work papers, etc.)
     
   • A terminated employee’s physical and electronic access to PI and PHI must be immediately blocked. Such terminated employee shall be required to surrender all keys, IDs or access codes or badges, business cards, and the like, that permit access to the firm’s premises or information. Moreover, such terminated employee’s remote electronic access to personal information must be disabled.

8. Physical Assets Protocol
   
   • All assets must be secured from theft by locking up and maintaining a secure workplace, whether that work takes place in University stores, offices, at a client site, in a car, hotel or in a home.
     
     • All University laptops shall be deployed with encryption capabilities enabled. End users may not disable such encryption. Exceptions to this policy are as follows:
       
       • With the explicit written authorization of the CISO;
         
       • May be disabled by OIRT personnel for temporary maintenance purposes only;
         
       • Loaner laptops temporarily assigned with the understanding they will not be used to store or access any information that is considered to be protected under this policy.
         
     • All laptops should be placed in the trunk of vehicle when and wherever they are parked. If no secure trunk or other storage is available, employees should, whenever possible, keep their laptops in their possession or find a way to secure and conceal it.
       
     • Laptops, PDAs, phones and other portable devices that may contain or have access to PI and/or PHI left in the office or at home over night should be kept in a locked and secure location.
       
     • Employees must have assets secured or within their physical possession while on public or private transportation, including air travel.
       
   • Files containing PI and/or PHI are not to be stored on local computer hard drives, shared drives or other external media (which include externally hosted services such as, but not limited to OneDrive, Google, and Drop Box) without prior written authorization from the CISO. If approved, the method of storage and access to the data will be determined by the CISO during the discussion and placed in writing. (See Appendix I for more detail).

9. Access Control Protocol
   
   • Access to electronically stored PI and PHI shall be electronically limited to those University employees having a unique log-in ID.
     
   • Employees must ensure that all computer systems under their control are locked when leaving their respective workspaces. Employees must not disable any logon access.
     
   • Employees must log off of the VPN or Virtual Desktop (VDI) when they are not directly using those resources.
     
   • All Ellucian (Datatel) sessions that have been inactive for 60 or more minutes shall require re-log-in.
     
   • After 5 unsuccessful log-in attempts by any Ellucian (Datatel) or MS Active Directory NetID, that user ID will be blocked from accessing those systems until access privileges are re-established by University Systems and Networking.
     
   • Employees must maintain the confidentiality of passwords and access controls:
     
     • All Ellucian (Datatel) or MS Active Directory NetID passwords are required to adhere to strong password rules.
       
     • All Ellucian (Datatel) or MS Active Directory NetID passwords are required to be changed every 3 months.
       
     • Employees must not share accounts or passwords with anyone.
       
     • Employees should not record passwords on paper or in a document or in a place where someone other than the employee might have access to it. Tip: The University has identified a password vault application (Keepass); those interested should open a ticket with the Fairleigh Dickinson University Technical Assistance Center (UTAC) requesting assistance on setting it up.
       
   • Where practical, all external or internal visitors to a department are restricted from areas where files containing PI and PHI are stored. Alternatively, visitors must be escorted or accompanied by an approved employee in any area where files containing PI and PHI are stored.

VI. EXTERNAL RISKS

To combat external risks to the security, confidentiality, and/or integrity of any electronic, paper or other records containing PI and PHI, and evaluating and improving, where necessary, the effectiveness of the current safeguards for limiting such risks, the following measures are mandatory and effective immediately:

External Threats

1. Firewall protection, operating system security patches, and all software products shall be reasonably up-to-date and installed on any computer that stores or processes PI and PHI.
   
2. All system security software including, anti-virus, anti-malware, and internet security shall be reasonably up-to-date and installed on any computer that stores or processes PI and PHI.
   
3. To protect against external threats, all PI and PHI shall be handled in accordance with the protocols set forth above under “Internal Threats”.
   
4. In the event an individual inadvertently discovers he/she received PI or PHI from an external party, such PI or PHI shall be handled in accordance with the protocols set forth under “Internal Threats”.
   
5. There shall be secure user authentication protocols in place that:
   
   • Control user ID and other identifiers;
     
   • Assigns passwords in a manner that conforms to accepted security standards, or applies the use of unique identifier technologies;
     
   • Control passwords to ensure that password information is secure.
     
6. PI and PHI shall not be removed from the business premises in electronic or written form absent a legitimate business need and use of reasonable security measures, as described in this WISP.
   
   • PI and/or PHI that MUST be transmitted in electronic form shall not be sent without encryption.
     
   • PI and/or PHI in paper form must be secured.
     
7. All computer systems shall be monitored for unauthorized use or access to PI and PHI.

VII. IN CASE OF LOSS/THEFT OR SUSPECTED LOSS/THEFT

If you have reason to believe that any PI or PHI has been lost or stolen or may have been compromised or there is the potential for identity theft, regardless of the media or method, you must report the incident immediately by contacting the Fairleigh Dickinson University Technical Assistance Center (UTAC). The UTAC is available 24 x 7.

VIII. OTHER APPLICABLE POLICIES

Data Security Information Response Plan (September 15, 2019, not published on Web)

IX. EXCEPTIONS

Requests for exceptions to this policy should be directed in writing to the Chief Information Security Officer. Only the Chief Information Security Officer in consultation with the DSIRT may grant such exceptions and will do so only after careful review and in writing.

X. REVIEW

This policy shall be reviewed annually by the Data Security Incident Response Team (DSIRT) at the first meeting in April.

Appendix I

Technical requirements for the storage of files containing PI or PHI regardless of where the storage occurs will include but not be limited to the following:

1. All file(s) should be secured with AES 256bit encryption unless actively open for review or modification.
   
2. It is the responsibility of the person handling the PI or PHI file to securely delete any files created as a product of the manipulation of those files. As an example, temporary files created by Microsoft Office programs or any other programs would need to be securely deleted as well as the clear text versions of the original file after the encrypted version is properly created and verified.
   
3. Programs used for Encryption/Decryption and secure file deletion must be approved by the CISO including the methods in which they are to be used.
   
4. If the complete or partial PI or PHI containing file(s) are inadvertently written to a local hard drive, it is the user’s responsibility to diligently make sure the contents are securely deleted.

Appendix II

DATA SECURITY INCIDENT RESPONSE TEAM (ROLES AND RESPONSIBILITIES)

The Data Security Incident Response Team membership includes the Chief Operating Officer, the Chief Information Officer, the Chief Information Security Officer, the Chief Academic Officer, the University General Counsel and the University Risk Manager. Each member of the Data Security Incident Response Team (DSIRT) has responsibilities related to the security of all the organization’s sensitive information. The DSIRT members listed below have specific responsibilities with regard to the reporting and handling of data security incidents. Note that one person may serve in multiple roles.

Senior Vice President for Finance & Administration: Hania Ferrara
Daytime telephones: office: 201-692-2381; Email: ferrara@fdu.edu

Chief Information Officer (CIO): Neal Sturm
Daytime telephones: office: 201-692-8689; Email: sturm@fdu.edu

Chief Information Security Officer (CISO): Kimberley Dawn Dunkerley
Daytime telephones: office: 201-692-7672; Email: ddunkerley@fdu.edu

Privacy Officer: Kimberley Dawn Dunkerley
Daytime telephones: office: 201-692-7672; Email: ddunkerley@fdu.edu

Chief Academic Officer (CAO): Michael Avaltroni
Daytime telephones: Office: 201-692-7093; Email: mavaltroni@fdu.edu

University General Counsel: Edward Silver
Daytime telephones: office: 201-692-7071; Email: esilver@fdu.edu

University Risk Manager: Gail Lemaire
Daytime telephones: office: 201-692-7083; Email: lemaire@fdu.edu

Vancouver Campus Executive: Wilfred Zebre
Daytime telephone: office: 604-648-4462; Email: wilfred_zerbe@fdu.edu

---

Zoom experts host free and interactive live training webinars daily. Get up to speed in less than an hour. Please select the time zone that fits best for you when registering for one of our live training webinars.

Fairleigh Dickinson University has rooms dedicated as Zoom Rooms where you could have hybrid in person and remote learning.

On this page, you will find a link for the location of the Zoom Rooms on both New Jersey campuses, links for instructions on how to use the Zoom Rooms and the equipment for installed rooms, cart rooms and connecting with ITV rooms.

Zoom is a web-based video conferencing tool that allows users to meet online, with or without video. Zoom users can choose to record sessions, collaborate on projects, and share or annotate on one another’s screens, all with one easy-to-use platform. It offers quality video, audio, and a wireless screen-sharing performance across Windows, macOS, Linux, iOS, and Android. Zoom has a feature-rich, mobile app for both iOS and Android, allowing you to virtually connect from anywhere with an Internet connection.

Installing the Zoom Browser Client

1. The web browser client will download automatically when you start or join your first Zoom meeting, and is also available for manual download.

2. Once downloaded, you can go to the Zoom folder in your “START” menu and click “Start Zoom” on a PC or click on the “Zoom.us” app located in the applications folder on a Mac. Alternatively, you can open the application by searching for Zoom in your computers search bar.

To start, visit https://fdu.zoom.us

3. Click on “Sign In” at the top-right corner of the page and type your FDU NetID credentials

4. After logging in, you will see your profile information.
   • Joining a meeting – Click on the link and enter the meeting ID number provided by the host.
   • Hosting a meeting – You can host a meeting with or without video. Click on the option that you need and the meeting should start automatically.
   • Scheduling a meeting – Click on Meetings on the left navigation area and then click on Schedule a New Meeting.

Installing the Zoom Native Client

The following steps are for users who have already downloaded the Zoom desktop client or are planning to use the client. These instructions are NOT for users who will be using the web browser to participate in a Zoom meeting.

1. Launch the Zoom Desktop client
2. Click on “Sign In“

3. Click “Sign In with the SSO“

4. Type “FDU” in the company domain field and click “Continue“

5. You will be redirected to a page where you will be asked to login using your FDU NetID credentials

6. After signing in click “Open Zoom Meetings“

Zoom Mobile Apps and Plugins Install Links

Outlook Plugin

Mobile Apps

Resources for Troubleshooting Issues with Zoom

The following troubleshooting guide gives support for all devices that Zoom supports.