Client Configuration Policy
  • 04 Jan 2021
  • 2 Minutes To Read
  • Print
  • Share
  • Dark
    Light

Client Configuration Policy

  • Print
  • Share
  • Dark
    Light

Client Configuration Policy sets various client settings.
Screen Shot 2020-12-28 at 2.03.18 PM.png

There is a default Client Configuration Policy called ‘Default policy’.

Create a new Client Configuration Policy

  1. Click on Client Configuration (under Policies) in the left-hand navigation menu bar
  2. Click Create Policy button
  3. Enter a Policy name
  4. Enter values for the various fields.
  5. Click Create
    The policy cannot be deleted if assigned to a Circle. Remove the Policy from all Circles first then Delete Policy.

Cache Settings (in seconds)

  • Online cache
  • Offline cache
  • Key cache

MagicFolder (multiple enveloping): defines the behavior for MagicFolders.

  • Allow enables protected files placed into a MagicFolder to be encrypted with the MagicFolder Circle information. If the file was protected in Circle1 and placed into a MagicFolder (for Circle2), the file is now protected by both Circle1 and Circle2. This requires users to have permissions to both Circles to access the data.
  • Strict denies the protected file from being protected multiple times. The file from Circle1 placed into the MagicFolder for Circle2 will only be associated with Circle1.

File Tagging

File Tagging is a file-level metadata feature which will populate the SecureCircle information into the file. This is useful for file-level scanning when scanners do not have access to SecureCircle protected data.

Protection Reporting

When enabled, clients will prioritize sending protection event logs to the server. Without enabling, the client will send the file protection logs when the file is accessed.

MagicDerivative

Enabling Derivative will enable automatically protected derivative works in the same Circle as the original content. This would include common tasks such as Save-As and Copy-N-Paste, but also include manually retyping content that is already protected.

Derivative Threshold

The (%) amount of data similarity required for data to be considered a derivative. The default threshold is 5%.

Derivative Extensions

The list of file types which derivatives will be calculated and compared. The default list of extensions is: mht, xps, doc, dot, wbk, docx, docm, dotx, dotm, docb, xls, xlt, xlm, prn, dif, slk, xlsx, xlsm, xltx, xltm, xlsb, xla, xlam, xll, xlw, ppt, pot, pps, pptx, pptm, potx, potm, ppam, ppsx, ppsm, sldx, sldm, odt, ott, odm, ods, ots, odg, otg, odp, otp, odf, odc, odb, csv, html, htm, xhtml, rtfd, pdf, rtf, xml, xslt, txt, pub, vsdx, ai, psd, jnt, pages, numbers

Regular Expressions (Regex)

A special function of Derivative detection is using regular expression patterns to trigger a derivative (automatic securing of data based on content).

The example expression below will detect 3 digits, a dash, 2 digits, a dash, and then 4 digits. This is standard format for a United States Social Security Number.

\d{3}-\d{2}-\d{4}

Regular Expression requires

  • Derivative enabled
  • Dertivative extension must be added to the extension list
  • File being reviewed must meet the Derivative file size requirements
If multiple expressions are entered in a single Client Configuration Policy

Expressions are logically OR so any of the expressions will trigger a regex match.

Addition resources for Regular Expression templates
https://regexr.com/
https://regexlib.com

Was This Article Helpful?