Each ethernet device is assigned a unique hardware address by the manufacturer. Manufacturers are each assigned a range of addresses that they may use in their manufacturing, so that it is not possible for two vendors to assign the same address. These hardware addresses are called MAC Addresses.
You can search by MAC number to find out what vendor's hardware you are looking for. An interactive database is available from the IEEE for this purpose. You can also check Cavebear's list of Vendor Codes
- Plan A: "Managed Allocation": Departments that routinely host short-term events such as continuing education classes, conferences, or sports camps. These events typically draw numbers of visitors to campus who request or require Internet access and can make use of Wifi capability.
- Plan B: "Ad-hoc Service": Departments that only occasionally host a visiting faculty, or vendor. These guests need Internet access temporarily and can utilize Wifi with their laptop in order make a presentation, contact company resources, or check their email.
Request Access and Provisioning
- Plan A: Guest Wifi Allocation account will be established which allows designated departmental staff to assign Wifi access for their visitors, through the use of an authenticated Web site at https://commservices.comm.uab.edu/guestwifi/login.aspx without ongoing requests to UABIT. The Allocation account will be provisioned with a maximum number of slots which can be in use at any given time.
- Plan B: Departmental finance officers and/or their designees can request Wifi access for a visitor on an as-needed basis, by submitting a service order to UABIT via an authenticated Web site at https://commservices.comm.uab.edu/guestwifi/login.aspx
- Plan A: Five business days to establish a new Allocation account, immediate guest access activation.
- Plan B: Immediate guest access activation
- Plan A: Setup fee of $20 per allocation account, and then $8.50 per month per available access slot
- Plan B: $1.50 per day per guest
- Error messages
- Computer make and model
- Internet connection type
- PGP installer version
- Estimated time of occurrence (if possible)
Common Solutions to Installation Issues
- Verify that you are an administrator of the system on which you are attempting to install PGP.
- Open your web browser and ensure that you have Internet connectivity by opening a website.
- Be sure that you have a current installation package for PGP Desktop. Visit www.uab.edu/it/software for the latest installation files.
- Ensure that you are using your BlazerID and strong password for the PGP Enrollment credentials.
Common Solutions to Password Related Issues
- Verify that Caps Lock is not on while authenticating.
- If you recently changed your account password, you may have to provide the old password until you log in to the system with your new password.
- If the previously mentioned steps do not resolve your issue, you should call the AskIT Help Desk to request a PGP recovery token for the system or portable device. A recovery token is a one-time password that will allow you to bypass PGP, but it will not bypass the operating system password; you are still required to log in.
Common Solutions to Boot/Startup Related Issues
- Ensure that a keyboard is connected to the system. Systems such as tablets without physical keyboards will not be able to authenticate on the PGP boot screen.
- Remove any CDs, DVDs or USB drives from the system. Many of these devices have features that allow them to start before the system hard drive.
- Does the system have multiple operating systems or Dell Media Direct? If so, then you will need to contact your support personnel to assist you with the recovery of your hard drive. Please note that PGP should never be installed on systems with multiple operating systems, as it will render the system inoperable.
- See the PGP Recovery documentation for further support.
UAB has contracted with DriveSavers to provide data recovery services for the UAB
community. DriveSavers is the only data recovery company in the industry that undergoes
annual SAS 70 Type II Audit Reports and is HIPAA compliant, offering the highest level of data
security available. DriveSavers is also compliant with FAR 52.224-2 (Privacy Act), ISO 17799,
Sarbanes-Oxley Act of 2002 (SOX), the US government Data-At-Rest (DAR) mandate, the
Gramm-Leach-Bliley Act (GLBA) and the new regulation by National Institute of Standards and
Technology, NIST SP 800.34 (Rev. 1).
To view DriveSavers certifications, and learn more about Data Recovery Industry standards,
Data Custodians must:
- Designate appropriate individuals with system administration responsibilities, ensuring that their role in securing the system is defined in their job description, and that they are trained in administration and security of the system.
- Ensure adherence to UAB guidelines and procedures for protecting data as found in IT Security Practices.
- Ensure compliance with all stipulations of this and other UAB policies and other legal and regulatory requirements including those related to dissemination of data (UAB's Information Disclosure and Confidentiality Policy) and disposal of computer equipment and systems (UAB's Equipment Accounting standards, and "Guidelines for secure disposal of media containing sensitive information").
- Ensure that risk assessments are performed (including disaster recovery plans, backup and contingency plans) as required by HIPAA for all PHI. Risk assessment is recommended for all other sensitive or mission critical data.
- Ensure that documentation of data resources created, used, or stored within their area of control is maintained.
- Ensure that systems containing sensitive information are physically secured from unauthorized access.
- Ensure that the department/unit follows procedures to mitigate all identified compromises or identified data security threats.
- Ensure that actual or suspected data security breaches, especially when involving sensitive data, are reported to the Data Security Office immediately and that any recommended corrective action is implemented.
- Ensure that non-UAB entities or contracted third party vendors handle data in accordance with UAB policies and procedures.