Secure Derivative
  • 26 Mar 2021
  • 1 Minute to read
  • Dark
  • PDF

Secure Derivative

  • Dark
  • PDF

Secure Derivative (formerly known as Magyc or Magic Derivative)

SecureCircle’s Data Access Security Broker (DASB) protects more than just the file. DASB protects the content of the file, truly the data. Our patented similarity detection engine understands the data DNA of the protected file. When the data DNA is found in another file, that file is automatically protected. Security follows the content even with SaveAs, Copy/paste, or manual reconstruction of the data across any file type. The sensitivity of the Secure Derivative feature can be adjusted at any time to determine your threshold for automatic protection.

Client Configuration Policy

  1. To configure the Secure Derivative extensions and threshold, navigate to and expand Policies from the menu bar to the left.
  2. Under the expanded menu item, navigate to Client Configuration.
  3. Either choose to Create Policy to start with something new, or select an existing policy and use the Action drop down menu to select Modify Policies.


There are 3 options for you here related to Secure Derivative.

  1. Next to Secure Derivative there is a check box that is used to Enable or Disable the option.
  2. The Derivative Threshold Percentage option is used to define how much of a document needs to match before the resulting match is automatically protected. The default threshold is 5%, which means the unique data in a document must match 5% of another single protected document’s DNA.
  • The DNA of a document is calculated by (need input).
  • The % of data that is specified will only count unique data in a document. So using copy/paste to duplicate data multiple times to generate pages will not result in this data being unique and considered for protection.
  1. The last option is the Derivative Extensions. This category is used to list out the extensions you want SecureDerivative to protect. Using the extension names without periods, you can add multiples by separating them with a comma as shown above.

Caution is advised when using extensions commonly used by temporary files, system files, and configuration files as these files becoming protected could result in loss of function or other unexpected results in the related applications.

Was this article helpful?

What's Next