What does Buzz do on its end to ensure that uploaded file types do not contain viruses or malware? I'm creating a list of file extensions, but want to know what else is done to protect our information on Buzz's server.
Thanks for your question. Buzz file storage and system security are managed through Amazon Web Services (AWS), which provides robust infrastructure protection. For more details on how data is secured across the platform, you can visit this Help Center article: Buzz's security model.
Let me know if you have any more questions about this!
Thank you for the info about AWS. So, is it necessary to include a list a list of prohibited file extensions on the domain settings page, if I'm going to specify what file types students can upload in an activity?
If you're specifying allowed file types directly within the activity, then students will only be able to upload files that match those specific extensions. In that case, it's not necessary to also include a list of prohibited file extensions in the domain settings. The activity-level file restrictions will control what students can submit for that activity.
If you want to enforce broader restrictions across all courses or activities, that is when the domain-level file restrictions can be useful.
I hope this helps. If you still have questions about this, I would be happy to answer them. Thanks!
Comments (4)
Hi Cheryl,
Thanks for your question. Buzz file storage and system security are managed through Amazon Web Services (AWS), which provides robust infrastructure protection. For more details on how data is secured across the platform, you can visit this Help Center article: Buzz's security model.
Let me know if you have any more questions about this!
Thank you for the info about AWS. So, is it necessary to include a list a list of prohibited file extensions on the domain settings page, if I'm going to specify what file types students can upload in an activity?
Hi Cheryl,
If you're specifying allowed file types directly within the activity, then students will only be able to upload files that match those specific extensions. In that case, it's not necessary to also include a list of prohibited file extensions in the domain settings. The activity-level file restrictions will control what students can submit for that activity.
If you want to enforce broader restrictions across all courses or activities, that is when the domain-level file restrictions can be useful.
I hope this helps. If you still have questions about this, I would be happy to answer them. Thanks!
Thank you - this is helpful!