Data Security: Difference between revisions

From ZDN User Guide
(Created page with "None of the measures taken here will ensure bullet-proof security for your data.  A person who knows what they are doing can easily circumvent all of these measures.  The security steps here are merely to keep the average user safely out of the way and prevent amateur malfeasance. If your current system is a system of excel sheets and word documents, this will be much more secure.  If your current system is integrated into Tracks or ZIMS, this will be less secure.  A...")
 
mNo edit summary
 
(4 intermediate revisions by the same user not shown)
Line 1: Line 1:
None of the measures taken here will ensure bullet-proof security for your data.  A person who knows what they are doing can easily circumvent all of these measures.  The security steps here are merely to keep the average user safely out of the way and prevent amateur malfeasance. If your current system is a system of excel sheets and word documents, this will be much more secure.  If your current system is integrated into Tracks or ZIMS, this will be less secure.  And if you are using Zootrition, it’s exactly the same (that is a password-protected Access database too).
<languages/>
<translate>
<!--T:1-->
None of the measures taken here will ensure bullet-proof security for your data.  A person who knows what they are doing can easily circumvent all of these measures.  The security steps here are merely to keep the average user safely out of the way and prevent amateur malfeasance. If your current system is a system of excel sheets and word documents, this will be much more secure.  If your current system is Tracks or ZIMS, this will be less secure.   


== Protecting your data from casual disruption (someone who doesn't know what they are doing) ==
== Protecting your data from casual disruption (someone who doesn't know what they are doing) == <!--T:2-->


<!--T:3-->
* Before you distribute:
* Before you distribute:
** Move the ZDN Support Files folder to somewhere "off the beaten path" where users won't stumble on it accidentally
** Move the ZDN Support Files folder to somewhere "off the beaten path" where users won't stumble on it accidentally
** Hide the ZDN Support Files folder (right-click > Properties > Hidden)
** Hide the ZDN Support Files folder (right-click > Properties > Hidden)
* Distribution
* Distribution
** Use a [[Special:MyLanguage/Distribution|batch file]] to distribute to your users
** Use the available [[Special:MyLanguage/Backups and Emergencies|backup]] tools
** Coming soon: Keeper/Read-only versions of the database to distribute to users who should only be referencing, not changing, diet information.
** Coming soon: Keeper/Read-only versions of the database to distribute to users who should only be referencing, not changing, diet information.
** Use a [[Distribution|batch file]] to distribute to your users
< [[Software and Hardware]]


== Protecting your data from deliberate harm ==
> [[Backups and Emergencies]]
Likely you can't stop a talented and motivated person. But, you can automate backups so that you can recover quickly from any damage. See more details in the [[Distribution]] section.
</translate>

Latest revision as of 22:19, 16 February 2024

Other languages:

None of the measures taken here will ensure bullet-proof security for your data.  A person who knows what they are doing can easily circumvent all of these measures.  The security steps here are merely to keep the average user safely out of the way and prevent amateur malfeasance. If your current system is a system of excel sheets and word documents, this will be much more secure.  If your current system is Tracks or ZIMS, this will be less secure. 

Protecting your data from casual disruption (someone who doesn't know what they are doing)

  • Before you distribute:
    • Move the ZDN Support Files folder to somewhere "off the beaten path" where users won't stumble on it accidentally
    • Hide the ZDN Support Files folder (right-click > Properties > Hidden)
  • Distribution
    • Use a batch file to distribute to your users
    • Use the available backup tools
    • Coming soon: Keeper/Read-only versions of the database to distribute to users who should only be referencing, not changing, diet information.

< Software and Hardware

> Backups and Emergencies