From 154e74f76f96d60112c53c264538d2f72beaed26 Mon Sep 17 00:00:00 2001 From: goddesswarship <103530016+goddesswarship@users.noreply.github.com> Date: Mon, 21 Oct 2024 15:55:10 -0700 Subject: [PATCH] Update to Introduction/security-overview.md Reduced information to a summary since this content was otherwise a duplicate of the Security Overview page --- docs/introduction/security-overview.md | 37 ++------------------------ 1 file changed, 2 insertions(+), 35 deletions(-) diff --git a/docs/introduction/security-overview.md b/docs/introduction/security-overview.md index 3a577d8..3fad735 100644 --- a/docs/introduction/security-overview.md +++ b/docs/introduction/security-overview.md @@ -1,38 +1,5 @@ # Security Overview -Wildbook provides broad flexibility in **securing data ownership** and **visibility**. For example, a Wildbook could be completely secured to only ever be accessible to a User who has logged in, blocking any public visibility of data. +Wildbook provides flexibility in **securing data ownership** and **visibility**. For example, a Wildbook could be completely secured to only ever be accessible to a user who has logged in, blocking any public visibility of data. In another configuration, Wildbook can be a very visible repository of global data (see [Sharkbook](https://www.sharkbook.ai/)) but only allow for data curation by pre-approved users. -In another configuration, Wildbook can be a very visible repository of global data (see the [sharkbook.ai formerly Wildbook for Whalesharks ](https://www.whaleshark.org/) for an example) but only allow for data curation by authenticated and pre-approved researchers and volunteers. And there are many possible configurations in between. - -Check with the Administrator of your Wildbook(s) for more information about the security model followed. - -## General Security Models - -Wildbooks generally follow **two security models**. - -### Silo Security - -**Silo Security** provides a secure sandbox for individual Users to enter and curate their data. Here is a quick summary: - -* Your User data is visible only to you. -* You can share data visibility and data curation with other, specific Users in Wildbook via pairwise Collaborations, which must be reciprocally approved at the "view-only" and "edit" levels, respectively. -* Other users can potentially match individual animals from your catalog but must have a Collaboration with you to set the match ID and affect your catalog. -* Other Users attempting to view your data will be blocked from reviewing your Encounters and Marked Individuals and be prompted to extend you an invitation for a Collaboration. Invitations and acceptances can sent inside Wildbook. - -[For more information about Silo Security, click here.](../security/silo-security/index.md) - -Examples of Silo Security-based Wildbooks include: - -* [Flukebook](https://www.flukebook.org) -* [African Carnivore Wildbook](https://africancarnivore.wildbook.org) - -### Location-based Role Security - -**Location-based Role Security** pairs User Roles in Wildbook with specific study sites around the globe, as reflected in the **Encounter.locationID** data field. For example, a User with the "Mozambique" role assigned to their User Account can edit data assigned to Encounters with the the **locationID** (a.k.a "study site") named "Mozambique". - -In this mode, all researchers within a catalog can view all data, but only Users with the correct location role can curate a particular Encounter. This model creates effective groups of collaborators in a geographic location while providing global visibility to the broader research community. - -Examples of Location-based Role Security Wildbooks include: - -* [sharkbook.ai formerly Wildbook for Whalesharks](https://www.whaleshark.org/) -* [MantaMatcher](https://www.mantamatcher.org) \ No newline at end of file +To learn more, see [Silo Security](../security/silo-security/index.md).