When DefiniSec (or the managing Service Provider) releases an update for the :Foundation Client, you receive notification immediately after SSProtect Login*. This offers an option to apply the Update or defer the procedure to a later time. Non-Privileged Users can do this once, to avoid the hassle of updating before attending to immediate needs. Administrators and Delegates can defer an Update continuously.
Updates are not immediately available to Organization Users, and only become visible once an Administrator or Delegate releases it for Non-Privileged User visibility. Procedural aspects of the Update are described in the article, Updating the :Foundation Client.
*NOTE: Update prompts are not presented when SSProtect Login results from a request to access protected content or perform other actions that require authentication and authorization. In certain cases, the Update prompt is deferred to a subsequent Login operation.
Operating System Update Dependencies
SSProtect does not rely on Windows Updates to retain protective integrity. While most Windows security applications utilize secure key storage (for example) and a mix of other host-local, managed services for sensitive data protection, SSProtect only utilizes related OS primitives as a secondary enhancement to our core protective technologies. This provides a defense-in-depth solution that avoids limitations in the underlying platform while minimizing technical dependencies. This reduces the need to apply critical Windows Updates in order to maintain effective protection (though of course other systems will be more directly affected).
When you have questions or concerns related to the software and Windows Update, contact our Support staff and we will work with you to enumerate dependencies and help you build a remediation plan if and when necessary.
Filesystem Drivers and :Shell In-Place Encryption
There are two different packages available - one that includes a filesystem driver, and one that does not. The filesystem driver is required for :Shell In-Place Encryption, which provides application-independent protection even when accessing and modifying content in a data file's native application container. Without the filesystem driver, you have to manually Release Protections (decrypt w/ proper Access Control) before accessing plaintext, which provides a window of opportunity for attackers.
The package without the filesystem driver is suitable for :Email-only use, so long as email content does not make extensive use of protected data files used by other applications. For those primarily interested in protecting email message content, host installation and update is simplified.
Manually Acquiring Install/ Update Packages
Updates are automatically delivered in response to end-user Update acknowledgment during SSProtect Login. If you need to manually acquire an update package, utilize the naming scheme described below. This allows you to form a URL for download since older packages are not indexed for public browsing.
Note that the Standard Update (as opposed to FAST UPDATE) package is the same as the installation package, resulting from the use of the Advanced Installer framework that manages Windows Installer requirements.
As expected. refer to the Download page for the latest available packages.
Install/ Update Package Naming
The package with the filesystem driver - the Full-Featured package - and the Limited-Feature Package (without the filesystem driver) use similar names:
Full-Featured Package Name: SSProtect Setup-va.b.c-x64.exe
Limited-Feature Package Name: SSProtect-nf Setup-va.b.c-x64.exe
...where a.b.c is the version of the package.
The Limited Feature Package includes, "-nf" in the name, which stands for, "no filter". You can always tell the type of :Foundation Client by the original package name. This is included in the caption of all UI displays for convenience.
Older Update Packages
You can acquire older versions of the software directly from the Content Delivery Network using the following URLs:*
...where a.b.c is the version of the package.
Enter the proper URL in your browser to download any version of the :Foundation Client.
*NOTE: Packages are only available to users in the United States, and links will not resolve for other users.
SSProtect provides a facility to manually execute a software update, allowing you to choose the version you wish to target. This allows you to work through issues with automatic update notification. To manually update your :Foundation Client, proceed as follows:
- Login to SSProtect and navigate to the notification icon's context menu
- Click the notification icon and choose the License and Components item
- Choose Update Client then navigate to the package you wish to use
- Choose Open to start the process
SSProtect will execute the Update using the same logic that's invoked when you respond to a dynamic Update prompt. When the update is complete, you may be prompted to manually restart the software using the Desktop Shortcut that's created during installation.
Note that this procedure differs from removing an existing Client and re-installing from scratch, though this is always an option. However, when using the Full-Featured package, you may need to reboot if you choose to approach. This is useful when troubleshooting compatibility and installation dependency issues (which is rare).
Installation frameworks help application developers manage software install, update, maintenance, and uninstall procedures. On Windows, these frameworks wrap a more fundamental Windows Installer framework, simplifying software packaging and installation. This results in an installation process that keeps a detailed audit record of system changes which is required for proper application setup, configuration, licensing, troubleshooting, and most importantly proper and complete uninstallation.
In reality, there are cases when changes are simple, straightforward, and do not require the extensive capabilities of such a framework. When this is the case, SSProtect avoids the overhead associated with loading such resources and makes direct changes to materials that must be modified. SSProtect reporting will show the update through :Assess, a much more secure option than host-based records that can be modified by attackers. This approach greatly improves the speed at which an update can be executed - reducing the time required from upwards of a couple minutes down to several seconds - without any compromise.
FAST UPDATEs and Uninstall
SSProtect uninstall utilizes an Installer framework which, among other things, removes files that it initially installs. If however a target file's hash does not match the hash recorded with the source material, it doesn't get removed. Because FAST UPDATE modifies target files, the uninstaller framework detects the change and, as a result, does not remove the file.
For this reason. FAST UPDATE keep copies of target files for convenience. The original content is copied to a local instance with, ".old" appended to the filename. This only happens once, and on uninstall the software restores this version before running the uninstaller framework software. This allows it to proceed without deviation.
Reverting FAST UPDATEs
FAST UPDATE also keeps a local backup of the most recent target file, also stored in the same folder with, ".prev" appended to the filename. This is overwritten each time FAST UPDATE executes (while, ".old" always holds the original file's content). This allows you to "back out" of any FAST UPDATE that results in unexpected issues. Revert by stopping SSProtect, removing the target file, and renaming the, ".prev" file by removing the suffix. Restart SSProtect and you will have reverted back to the version that existed prior to FAST UPDATE.
Auditing Reverted Versions
Audit logs and reports won't show revert actions directly, however SSProtect records the client version at Login. This version comes directly from the resources bound to the executable. Thus, if you execute a FAST UPDATE then revert back to the previous state, :Assess event reports will show the successive Logins with different version data. This shows changes to the client file, though it will not show the person who made the changes.