Federal Information Security Management Act (FISMA) Data

Data Classification Level: Restricted

Key: Permission Levels

  • Permitted
  • Permitted with Information Assurance (IA) Consultation
  • Not Permitted

For IA consultation, please contact the ITS Service Center

Protecting sensitive data is a shared responsibility. You are responsible for ensuring that your use of permitted services complies with laws, regulations, and policies where applicable.

Permitted with IA Consultation

Not Permitted

Data Type Description 

The Federal Information Security Management Act (FISMA) requires federal agencies and those providing services on their behalf to develop, document, and implement security programs for information technology systems and store the data on U.S. soil. This means that, under some federal contracts or grants, information the university collects or information systems that the university uses to process or store research data need to comply with FISMA.

Whether data is regulated by FISMA is typically called out in a Request for Proposal (RFP) or in contract or grant language. It is important that researchers review grant and contract language closely to identify FISMA or other information security requirements.

Data Steward: U-M Office of Research (UMOR) Research Information Oversight Program: [email protected].

Examples 

Examples of research work that might be regulated by FISMA include research in which data is provided by federal organizations such as:

  • National Institutes of Health
  • NASA
  • Department of Veterans Affairs

Laws/Regulations/Policies 

Federal Information Security Modernization Act (Department of Homeland Security)
Andrew File System (AFS): 
Not Permitted
Canvas: 
Not Permitted
Cloud Storage Included with Software: 
Not Permitted
Data Warehouse: 
Not Permitted
Desktop Backup (Powered by Code42): 
Not Permitted
MiDesktop: 
Not Permitted
Digital Signage: 
Not Permitted
Echo360 - Lecture Capture and LectureTools: 
Not Permitted
eResearch: 
Not Permitted
Globus: 
Not Permitted
Amazon Web Services GovCloud at U-M: 
With Approval
Amazon Web Services (AWS) at U-M: 
Not Permitted
Google Non-Core Services: 
Not Permitted
Google Drive at U-M: 
Not Permitted
Google Mail and Calendar at U-M: 
Not Permitted
Google at U-M Core Services: 
Not Permitted
MiDatabase: 
Not Permitted
MiServer: 
Not Permitted
MiShare: 
Not Permitted
MiStorage CIFS with AWS S3 Cloud Storage Integration: 
Not Permitted
MiStorage (NFS): 
Not Permitted
MiVideo: 
Not Permitted
MiWorkspace: 
Not Permitted
Personal Accounts: 
Not Permitted
Personally Owned Devices (phone, tablet, laptop, etc.): 
Not Permitted
Qualtrics: 
Not Permitted
ServiceNow at Michigan Medicine: 
Not Permitted
MiBackup: 
Not Permitted
Turbo Research Storage: 
Not Permitted
Michigan Medicine Exchange/Outlook Email and Calendar: 
Not Permitted
Document Imaging System: 
Not Permitted
E-signature Service - SignNow: 
Not Permitted
Piazza Q&A: 
Not Permitted
Gradescope: 
Not Permitted
Electronic Research Notebook at U-M: 
Not Permitted
Microsoft Azure at U-M: 
With Approval
Google Cloud Platform (GCP) at U-M: 
With Approval
Perusall: 
Not Permitted
Secure Enclave Service (formerly Yottabyte Research Cloud): 
Not Permitted
Microsoft Office 365 at U-M: 
Not Permitted
Armis2: 
Not Permitted
Great Lakes Cluster: 
Not Permitted
Adobe Cloud Storage: 
Not Permitted
Zoom at U-M: 
Not Permitted
TeamDynamix at U-M: 
Not Permitted
Dropbox at U-M: 
Not Permitted
Virtru at U-M: 
Not Permitted
Microsoft Teams at U-M: 
Not Permitted
Denodo at U-M: 
Not Permitted
Slack at U-M: 
Not Permitted
Microsoft 365 at Michigan Medicine: 
Not Permitted
Lighthouse HPC Cluster: 
Not Permitted
MyDataHelps: 
Not Permitted
REDCap MICHR Academic License: 
Not Permitted
GitHub Enterprise SaaS: 
Not Permitted
Data Den Research Archive: 
Not Permitted
Locker Large-File Storage: 
Not Permitted
ITS AI Services: 
Not Permitted