BigFix Retrieved Properties
Description Below are the detailed properties that are reported from your computer to the UCSF BigFix console. Note: All of this information will be treated as confidential by those who have access to it.
Description Below are the detailed properties that are reported from your computer to the UCSF BigFix console. Note: All of this information will be treated as confidential by those who have access to it.
Installation Computers and laptops Download the appropriate installer for your computer (Windows, Mac OS X). Windows Mac OS X If your department, group, or lab, would like to request custom BigFix client installers please visit the IT Service Catalog.
Frequently asked questions General What is BigFix? What information is collected by BigFix?
OverviewThe UCSF secure email solution is designed to help faculty, students and staff comply with the federal HIPAA regulations that went into effect April 21, 2005.HIPAA regulations stipulate that electronic communications containing Protected Health Information (PHI) must be transmitted in a manner that protects the confidentiality of patient information. When you send, receive or store any electronic document containing UCSF confidential or patient information, you are responsible for ensuring that the information is processed securely.
DescriptionMailing lists can be sent using UCSF managed services or through a select number of popular third-party vendors.New listserv and Distribution List request: Go to help.ucsf.edu >> Accounts, Access & Email >> Electronic Mailing List Request.Do not use a mailing list when sending "protected data." including PHI, PII, FERPA. Use them when you need to:
Overview Box Drive allows you to navigate the contents of your Box folders from a desktop application. With Box Drive installed, you will have:
IntroductionYou just received a "secure" email message from someone at UCSF. It's your first one, and you aren't sure what to do. This page is here to explain next steps and help you:
What you need to know about each action Recipient Action Description Action required for routing to move forward?