Plug-ins and add-ons to tools provide great value, but can also create security exposure. This video lists some of the mitigating strategies that can mitigate risk from third-party extensions and tools.
- [Tutor] A fairly common thing these days … is third-party developers creating add-ons … or plugins for popular business tools. … These extend the capabilities of the tools … or it integrates them with other business systems. … Google calls them Extensions, … in SharePoint, they're apps, … Box has over a thousand different integration partners, … and so on and so on. … The good news is, … that all of these add-ons can provide some incredible value … in augmenting or expanding workflows. … For instance, … if you can move customer contracts … between a customer relationship tool, like Salesforce, … and your document management system, … it will save a lot of time and trouble. … Although some of the extensions need to be enabled … at a system level, … in many cases, … it's very simple for users to install them … onto their computers. … And a lot of them are even free. … However, because of the way these tools integrate … there may be additional security exposure involved. … Without some investigation, …
- Identify the group of people to be notified when making a document policy or procedure change.
- Recognize which types of documentation requires higher levels of security.
- Name the two rights available at folder level during collaboration.
- Recall the purpose of version control.
- Determine which application allows multiple libraries with custom permissions.
- Identify the term used for add-ins within the SharePoint application.
- Explain the most common cause of data breaches.