Please be advised that we have been notified of an upcoming and planned Microsoft system patch. This patch is set to occur automatically by Microsoft on or around March 10, 2020.

 

We believe that this patch could have an impact on the operation of eSign Plus for certain clients. We are reaching out to those clients that we believe could be impacted.

 

However, being cautious, we are posting this update/alert just as a form of secondary notification to our valued IMMeSign Plus clients.

 

In order to navigate this very complex situation resulting from the Microsoft patch, we have detailed the potential impact of the planned patch and how you can navigate it. Please click below to review this important information.

Learn More ➜

Microsoft has sunset Windows 7 client and Windows Server 2008 software systems. IMM eReceipts 6.3.3 (formerly known as TotaleReceipts) only operates on these retired MS software systems. Therefore, IMM will be formally sunsetting support for eReceipts version 6.3.3 and older versions effective May 31, 2020.

 

All customers must begin migration planning as soon as possible in order to upgrade their eReceipt system to a supported version before May 31, 2020. Please review our Support Guidelines at our website: immonline.com in the Support Section for more information.

 

As a part of our commitment to customer success, we will assist you as you migrate to a current version of eReceipts. Please make sure that you schedule your upgrade as soon as possible to avoid complications, risks and additional costs of running an unsupported version. You may contact us to initiate the upgrade process by using the methods below.

 

• Telephone: 800-836-4750 Option 3
• Email:projects@immonline.com

 

For any questions, please contact our Support center or your IMM Client Success Manager.

Adobe will be sun-setting all “SOAP” API’s and utilizing solely “REST” API’s effective June 30, 2020. This will have an impact for IMM eSign clients with the below two scenarios – as the Adobe API’s are the method used for IMM eSign to communicate remote signature transactions to the Adobe Cloud:

 

1. Your IMM eSign version is version 5.3, 6.8, 6.9, 2015.1, 2015.2 or 2016.1. All IMM eSign clients running these versions will need to upgrade to a current version of our software which does not utilize the API’s being sunset by Adobe.
2. If your financial institution utilizes the native Adobe Sign portal to perform “Ad-Hoc” transactions (send documents directly from Adobe for eSignature and bring these documents back via our Ad-Hoc downloader) – then you will need to upgrade to a current version of our software which does not utilize the API’s being sunset by Adobe.

ACTION REQUIRED: If you fall into either #1 or #2 as described above. Please check your production version(s) of IMM eSign and the Ad-Hoc downloader and report back to IMM Support using the link below.

 

Please click here to Report Back to IMM Support >>

 

If it is determined that your organization does require an upgrade, we will place you in our deployment queue and an IMM project manager will contact you to schedule a patch to avoid issues.

 

If you are affected by this product alert, the resulting upgrade to IMM’s current software version must be completed and in production by June 30, 2020 in order to avoid potential service disruption.

 

If you have any questions regarding the above, please contact IMM Support at 800.836.4750 Option 3 or support@immonline.com.

IMM has recently tested the most currently available versions of Adobe Reader for compatibility and is pleased to make our new compatibility matrix available to our clients.

 

View Compatibility Matrix ➜

 

We hope you will find this information to be helpful. If you have questions about Adobe Reader version compatibility, please contact our customer support center.

To maintain the quality of our customer support and overall customer satisfaction, we are announcing the formal support sunset date of June 30, 2019, for IMM eSign Plus 5.3x (fka: TotaleAtlas Workflow).

 

All customers affected by this announcement are strongly encouraged to begin migration planning as soon as possible to move their implementation to a supported product version before June 30, 2019. After this date, IMM will no longer provide any form of technical or product support for versions 5.3x and below.

 

Please be aware that all labor for product support or services by IMM on an unsupported product version is not included in your annual maintenance, and is, therefore, a billable service as documented in our support guidelines. This also includes any support related to product upgrades. Additionally, if a support request requires a software modification, changes can only be applied to a currently supported version. Therefore, it is highly suggested that you upgrade to a supported version as soon as possible to avoid further complications.

 

As a part of IMM’s commitment to customer success, IMM will assist customers with a smooth migration to the newer product versions. Please ensure you schedule your upgrade early to ensure you avoid the complications, risk, and cost of running an unsupported product.

 

You can initiate your upgrade migration by:

1. Contacting IMM’s Client Support Center; or

2. Emailing your upgrade request to projects@immonline.com.

 

For any questions or clarifications on this announcement, please contact our Client Support Center or your Regional Client Success Manager.

Overview

It has been recently reported that Ghostscript contains multiple -dSAFER sandbox bypass vulnerabilities, which may allow a remote, unauthenticated attacker to execute arbitrary commands on a vulnerable system.

 

Description

Ghostscript contains an optional -dSAFER option, which is supposed to prevent unsafe PostScript operations. Multiple PostScript operations bypass the protections provided by -dSAFER, which can allow an attacker to execute arbitrary commands with arbitrary arguments. This vulnerability can also be exploited in applications that leverage Ghostscript.

 

IMM Position

IMM products are not affected by this vulnerability. Our products do not utilize the specific parameters needed in order for this vulnerability to be exploited within an IMM implementation.

The CR25 and CR55 scanners ended manufacturing in June of 2011. Support is scheduled to end in June of 2018. With this development, IMM will be severely limited in our ability to provide support for these devices.

 

The CR50 and CR80 ended production in April of 2017, and are currently projected to end support in April of 2022. (This is not an immediate or urgent item that you need to address today).

 

The current models available from Canon are the CR120 and CR150 units. If you are still using CR25 and/or CR55 devices, you should upgrade to the current units as soon as possible to avoid any interruption of service or support with your IMM eTeller Check21 solution.

 

If you should have any questions about this informational communication, please contact our support center or your IMM Client Success Manager.

Overview
In July of 2016, IMM provided notification to all eSign and eSign remote clients recommending the updating of TLS to version 1.2 in order to reduce identified security vulnerabilities in TLS 1.0 and 1.1.

 

Due to the importance Adobe places on security practices and policies, as of January 16, 2018 – Adobe will only accept transactions submitted using TLS 1.2 protocol. Any transactions submitted via 1.0 and 1.1 will be rejected and will not be processed. This mandate applies to both remote eSign transactions submitted by IMM eSign (TotaleAtlas) as well as transactions performed directly via the Adobe Sign portal – what we refer to as “ad-hoc” transactions.

 

In addition, RC4 cipher will need to be disabled.

 

Description
Due to an identified security vulnerability with TLS 1.0 and 1.1, IMM advised clients in July 2016 to determine if either TLS 1.0 and/or 1.1 protocol was running on your IMM eSign (TotaleAtlas) Server. If in fact, it was in use, IMM’s recommended action at that time to resolve the vulnerability was to implement TLS 1.2.

 

Now Adobe is mandating that any IMM eSign Remote transactions (formerly known as Document Exchange) will require TLS 1.2. RC4 cipher will also need to be disabled.

 

If you have not updated your TLS protocols to 1.2 or have disabled RC4 cipher, please be advised that your IMM eSign remote transaction submissions; ad-hoc submissions, or; the IMM eSign download service will be at risk for operational disruption.

 

Action Required
In 2015 Microsoft released an update to support TLS 1.2. If these updates are applied to the IMM eSign (TotaleAtlas), and SQL servers in use by IMM eSign, the application will continue to function properly. Disabling TLS 1.0 & TLS 1.1 and not implementing the TLS 1.2 update will cause both servers to not run properly and in turn will not allow IMM eSign to operate normally. We have included the links below that pertain to the various updates that you may need to be able to download Microsoft’s patch for TLS 1.2.

 

1. TLS 1.2 needs to be enabled on the following:
   • eSign server
   • Standalone SQL server (Please refer to this page to determine which potential update you might require)
   • Workstations that process ad hoc remote sessions, widgets and have access to the Adobe portal.
   • Any server that runs the ad hoc downloader separately from the eSign server
2. RC4 cipher needs to be disabled on the following (Please refer to this page for further details on RC4 disablement)
   • eSign server
   • Workstations that process ad hoc remote sessions and widgets.
   • Any server that runs the ad hoc downloader separately from the eSign server

 

We hope you will find this information to be of value. If you have further questions about TLS version updates, older version vulnerabilities, and the associated Adobe TLS 1.2 requirements, please contact our customer support center.

In order to enhance and streamline installed product upgrades, IMM is announcing a change in our upgrade support policy effective immediately. If you should have any questions regarding the updated policy, please contact our technical support center.

 

The below-changed policy language has also been updated in our published Support Policies Document.

 

NOTE: At this time, our new upgrade installation policy is not applicable to our workflow-based solutions.

 

Upgrades
Product upgrades are provided via our “Express” model as part of your annual maintenance. Non- standard Custom installations are billable and not included in AM.

 

Express Installation
Express installs are delivered via a virtual server download in an OVA file, to be imported by you into your VMware or Microsoft virtual server platform (other virtual server platforms are not supported for installation).

 

Once you import the server into your environment, IMM installer(s) will make product configurations (settings) to enable the product to work for you. All Express installation work is performed during IMM business hours.

 

Custom Installation
If you choose to not use the standard Express model for installation of your IMM product, you fall under the Custom Installation model and installation time is billable. Examples of non-Express installs are (but are not limited to) Physical server installation, Manual installation in the FI environment, Changes to (other than settings) the software installation like moving the database to another server or requiring different versions of infrastructure components to be installed.

 

To understand why this change in our policy was made, and how it benefits our valued clients, you can learn more here.

Canon has announced changes to their check scanner product lines and have discontinued several units previously used by IMM clients. We have been advised of the following sunset dates for the products listed below. Please incorporate this information into your product replacement and future budgeting plans.

IMM considers the protection and security of our systems along with the information processed by our technology a very serious matter. In light of recent security incidents that have been reported in the media, we’d like to take a moment to share information that may be of interest to our clients.

 

IMM’s internal systems have not been impacted by the recent “WannaCry” malware/ransomware scenario. The most proactive protection that can be taken for this and other malicious software is to maintain current release levels and patches of all internal software including but not limited to desktop operating systems, network operating systems, database systems, virus protection and intrusion detection programs.

 

IMM has internal policies combined with security protocol in place that keeps our systems up to date with the most current security patches and release levels to protect our systems. We highly recommend that our clients check to make sure that their software is up-to-date, and that appropriate security, virus and malware detection programs are maintained to protect systems and the data that resides within them.

 

If you have any questions regarding information security policies, please feel free to contact our client support center.

Due to enhanced features and functionality that we are adding to the IMM eSign platform going forward, you may find that older models of Topaz Signature Pads may not fully support the new functionality. Specifically, models T-LBK766, and T-LBK57GC series LCD display pads will need to be evaluated. In some cases, Topaz can provide firmware updates that will allow these older devices to operate with the new releases of IMM eSign.

 

If you have these devices, please contact the Topaz Technical Support team by calling 805-520-8286 and see if your device will support a firmware update.

 

As always, if you should have any questions about this technical update, please contact our customer support center.

To maintain the quality of our customer support and overall customer satisfaction, we are announcing the formal support sunset date of September 30, 2017 for the IMM products and versions listed below:

 

1. TotaleAtlas 5.3x (all variants of 5.3) and below
– Note: Does not apply to TotaleAtlas Workflow clients

2. Teller Item Capture Server 4.2 and below
– Client 3.0.9 and below

3. TotaleReceipts Server 6.3.2 and below
– Client 6.3.1 and below

 

All customers affected by this announcement are strongly encouraged to begin migration planning as soon as possible to move their implementation to a supported product version before September 30, 2017. After this date, IMM will no longer provide any form of technical or product support for the product versions listed above.

 

Please be aware that all labor for product support or services by IMM on an unsupported product version is not included in your annual maintenance, and is, therefore, a billable service as documented in our support guidelines. This also includes any support related to product upgrades. Additionally, if a support request requires a software modification, changes can only be applied to a currently supported version. Therefore, it is highly suggested that you upgrade to a supported version as soon as possible to avoid further complications.

 

As a part of IMM’s commitment to customer success, IMM will assist customers with a smooth migration to the newer product versions. Please ensure you schedule your upgrade early to ensure you avoid the complications, risk, and cost of running an unsupported product.

 

You can initiate your upgrade migration by:

1. Contacting IMM’s Client Support Center; or

2. Completing the TotaleAtlas 2015 upgrade request form (only used for TotaleAtlas upgrades) on our website by using the button below; or

3. Emailing your upgrade request to: projects@immonline.com.

 

For any questions or clarifications on this announcement, please contact our Client Support Center or your Regional Client Success Manager.

As a part of our on-going efforts to enhance our messaging and description of our solutions to the market, IMM announced a product re-branding initiative in the fall of 2016. All IMM products are the process of undergoing a name change, first in the sales and marketing areas (website, product brochures, etc.) to be followed in the physical product itself. The new names listed below will be present in all new product releases going forward. The product brand name changes does not impact the feature or functionality included today or in the future of each product, but rather is only a name change.

 

Old Product Name-> New IMM Product Brand

TotaleAtlas -> IMM eSign

TotaleAtlas Workflow -> IMM eSign plus

Document Exchange -> IMM eSign (Remote eSignatures)

TotaleReceipts -> IMM eReceipts

Teller Item Capture -> IMM eTeller Check21

TotaleChecks -> IMM eChecks

 

If you should have any questions, please contact your IMM Client Success Manager, or our Client Support Center.

Adobe Sign is expanding their North American data center and will undergo a period of planned maintenance that will result in expected system downtimes during the expansion procedure. This action is being performed to enhance the data center and is expected to result in improvements to service reliability, durability, scalability and automation.

 

When is the Planned Maintenance Operations?
The expansion will occur in 2 separate project phases on the dates and times listed below. The Adobe Sign services are expected to be unavailable for usage during these maintenance periods.

 

#1: Sat. March 11 @ 8pm ET – Sunday, March 12 @ 5am ET
#2: Sat. April 8 @ 8pm ET to Sunday, April 9 @ 2am ET

 

What Action Should You take?
Simply be aware that consumers will not be able to sign documents or complete transactions during these periods. However, all transactions in flight prior to the outage will be preserved and available for completion upon service restoration.

 

New IP Address Ranges
As a part of the data center expansion, new IP address ranges are being made available for the service. Please check with your IT Department to see if your institution needs to add the new IP address ranges to your existing range settings. The new IP address ranges can be obtained by contacting our Technical Support Center.

 

For any questions or clarifications on this announcement and the upcoming maintenance periods, please contact our Client Support Center or your Regional Client Success Manager.

Overview

IMM is providing notification to our clients of a potential issue that could impact the security of your IMM TotaleAtlas solution due to identified TLS vulnerabilities. Please take a few moments to carefully review this information and determine if you need to take any corrective action to properly secure your operation. If you have any questions, please do not hesitate to contact our customer support center for assistance.

 

Description

Due to an identified security vulnerability with TLS 1.0 and 1.1, IMM is advising each customer to determine if either TLS 1.0 and/or 1.1 protocol is running on your IMM TotaleAtlas Server. If in fact, it is, IMM’s recommended action to resolve the vulnerability is to implement TLS 1.2.

 

Please take note that If you disable TLS 1.0 and 1.1, you must ensure that TLS 1.2 is installed both on the TotaleAtlas and the SQL Server. TotaleAtlas uses SQL Server internally (by default IMM uses SQL express unless you have a licensed SQL standard version).

 

Microsoft released an update to support TLS 1.2. If these updates are applied to the SQL server in use by TotaleAtlas, the application will function properly. Disabling TLS 1.0 & TLS 1.1 and not implementing the TLS 1.2 update will cause SQL service to not run and in turn, will not allow TotaleAtlas to operate normally. We have included the link to be able to download Microsoft’s patch for TLS 1.2 here

 

We hope you will find this information to be of value. If you have further questions about TLS version vulnerabilities and the associated security impact on TotaleAtlas, please contact our customer support center.

This is a reminder notice for all of our TotaleAtlas customers. In October of 2015, IMM formally distributed a sunset announcement for older versions of TotaleAtlas. We are re-distributing this to all clients today as a courtesy reminder of the official sunset of older TotaleAtlas versions prior to version 5.3. This sunset is effective April 1, 2016.

 

We’ve included the original email content below for your convenience. If you should have any questions or concerns, please contact our customer support center today and we will be happy to assist you.

 

In July of 2015, IMM announced the next-generation of TotaleAtlas, called TotaleAtlas 2015. This new release of TotaleAtlas provides many attractive product updates and new functionality – and is designed to align with current technology standards.

 

In order to maintain the quality of our customer support and overall customer satisfaction, IMM is announcing the formal sunset date for support of some of the older versions of TotaleAtlas. Please read the information below carefully in order that you may plan accordingly to avoid any disruption in the support of your TotaleAtlas implementation.

 

IMM is formally announcing the sunset of support for the following prior versions of TotaleAtlas, effective March 31, 2016.

 

Older Release Versions Scheduled for Support Sunset:
TotaleAtlas 4.x
TotaleAtlas 5.1
TotaleAtlas 5.2

 

Beginning April 1, 2016, all clients must have either TotaleAtlas 5.3 or TotaleAtlas 2015 installed and operational in order to maintain support of their TotaleAtlas implementation.

 

All TotaleAtlas clients affected by this announcement are strongly encouraged to begin migration planning as soon as possible to move their implementation to either TotaleAtlas 5.3 or TotaleAtlas 2015. After March 31, 2016, IMM will no longer provide any form of technical or product support for the prior versions of TotaleAtlas listed above. As a part of IMM’s commitment to customer success, IMM will assist customers with a smooth migration to the newer product versions.

 

Customers may contact IMM’s support center or the upgrade migration team by either completing the TotaleAtlas 2015 upgrade request form or by emailing their upgrade request to: projects@immonline.com.

 

For any questions or clarifications on this sunset announcement, please contact either our technical support center or your regional IMM Client Success Manager.

Overview
On December 1, 2015, Adobe will implement a modification to the Document Exchange service. This modification will not impact the consumer or the employee experience while using the service. However, it will result in a noted visual difference in the appearance of the signed documents processed by the service.

 

Current Product Behavior
Once a document has been signed and processed through the Document Exchange service, a visible blue border is placed around the document contents. The document integrity validation indicator (green check mark), along with the Adobe transaction ID are displayed within the bottom section of the blue border.

 

New Change in Product Behavior
On December 1, 2015, Adobe will discontinue the use of the blue border and it will no longer visually appear on the signed documents. This modification is being made in order to maintain the original quality and integrity of the document contents as it appeared before, during, and after the signing event.

 

Replacement for Blue Border
While the blue border will no longer visually appear on the document, the tamper evident validation and certification of document integrity is still being performed. An indication of document integrity status will now be visually portrayed with the following behavior as the document is viewed in Adobe Reader (or compatible PDF viewer):

 

a. Document Integrity Validated: A blue banner is displayed at the top of the document viewing window with the corresponding language that confirms the document has been certified by Adobe. This certification behavior has actually been in operation for a period of time now. (See example below)

 

b. Document Integrity Not Validated: A red banner is displayed at the top of the document viewing window with corresponding language indicating that the document has not passed certification. This will be an indicator that the document integrity is suspect and should require immediate research and attention.

 

Transaction ID/Audit Trail Access
With this new behavior, the transaction ID and the Audit Trail can be accessed simply by clicking on the signature area of the document while it is being viewed in Adobe Reader. This will take the user to the Adobe Document Cloud eSign Services portal where the transaction ID is verified and the audit trail can be accessed.

 

We hope that you will find this information helpful. Should you have questions or require further information regarding this change to the Document Exchange service, please contact IMM’s Support Center.

Recently we advised our clients that in the initial qualification of iOS 9.x, our testing revealed unexpected behavior. We asked that you not update any iSign iPads to the new release until notification from IMM that the unexpected behavior was resolved.

 

We are pleased to share that we have released IMM iSign v209 which fully supports iOS 9.x. iSign customers may now proceed to update iPads to Apple’s new iOS release knowing that it is compatible and supported with IMM’s iSign solution. Also be sure to download and install the new iSign app from the App Store.

 

If you should have any questions or would like further information, please do not hesitate to contact our customer support center.

In July of 2015, IMM announced the next-generation of TotaleAtlas, called TotaleAtlas 2015. This new release of TotaleAtlas provides many attractive product updates and new functionality – and is designed to align with current technology standards.

 

In order to maintain the quality of our customer support and overall customer satisfaction, IMM is announcing the formal sunset date for support of some of the older versions of TotaleAtlas. Please read the information below carefully in order that you may plan accordingly to avoid any disruption in the support of your TotaleAtlas implementation.

 

IMM is formally announcing the sunset of support for the following prior versions of TotaleAtlas, effective March 31, 2016.

 

Older Release Versions Scheduled for Support Sunset:
TotaleAtlas 4.x
TotaleAtlas 5.1
TotaleAtlas 5.2

 

Beginning April 1, 2016, all clients must have either TotaleAtlas 5.3 or TotaleAtlas 2015 installed and operational in order to maintain support of their TotaleAtlas implementation.

 

All TotaleAtlas clients affected by this announcement are strongly encouraged to begin migration planning as soon as possible to move their implementation to either TotaleAtlas 5.3 or TotaleAtlas 2015. After March 31, 2016, IMM will no longer provide any form of technical or product support for the prior versions of TotaleAtlas listed above. As a part of IMM’s commitment to customer success, IMM will assist customers with a smooth migration to the newer product versions.

 

Customers may contact IMM’s support center or the upgrade migration team by either completing the TotaleAtlas 2015 upgrade request form or by emailing their upgrade request to: projects@immonline.com.

 

For any questions or clarifications on this sunset announcement, please contact either our technical support center or your regional IMM sales manager.

Recently we advised our clients that in the initial qualification of iOS 9.x, our testing revealed unexpected behavior. We asked that you not update any iSign iPads to the new release until notification from IMM that the unexpected behavior was resolved.

 

We are pleased to share that we have released IMM iSign v209 which fully supports iOS 9.x. iSign customers may now proceed to update iPads to Apple’s new iOS release knowing that it is compatible and supported with IMM’s iSign solution. Also be sure to download and install the new iSign app from the App Store.

 

If you should have any questions or would like further information, please do not hesitate to contact our customer support center.

IMM has completed compatibility testing on Adobe PDF Reader versions that have been released by Adobe in recent weeks.

 

We have determined that Adobe Reader versions 11.0.12 and DC15 008.20082 (Adobe’s latest 11 and DC versions) are supported for use with TotaleAtlas versions 5.3 SP1 and TotaleAtlas 2015.

 

Our testing has also revealed that Adobe Reader versions 10.1.14, 10.1.15, 11.0.11 and DC 2015 (007.20033) are not supported with TotaleAtlas because of issues associated with expressions and calculated fields. Therefore do not attempt to utilize these versions with TotaleAtlas.

 

If you have any questions or require further clarifications, please contact our support center.

Adobe recently released three new versions of their PDF Reader, Adobe Reader 10.1.14, 11.0.11 and DC 2015 (007.20033). On our initial evaluation of these newly released versions there appears to be an issue with calculated fields on documents used withinTotaleAtlas XML Edition. Therefore, IMM asks that you DO NOT download and install these Adobe Reader versions until we have completed our quality assurance testing.

 

We anticipate completing our standard testing over the next few weeks and at that time we will advise all clients of our findings. Until then, please do not install Adobe Reader 10.1.14, 11.0.11 and DC 2015 (007.20033).

 

If you should have any questions in the meantime, please do not hesitate to contact our Support Center via telephone, email, or via our website.

As of today, February 23, 2015 – the new user signing experience has been rolled-out to all IMM Document Exchange customers. This new signing experience provides an enhanced consumer signing experience across all devices. If you should have any questions about this new experience, please contact IMM’s customer support center.

IMM would like to provide you with important security information about your IMM solution(s) as they relate to this most recent vulnerability alert. IMM is aware of an SSL v3.0 vulnerability known as POODLE (Padding Oracle On Downgraded Legacy Encryption). The POODLE vulnerability (CVE-2014-3566) impacts SSL (Secure Sockets Layer) version 3 which provides encryption of data transported via the Internet. Under the right conditions, POODLE could allow an attacker to gain access to sensitive data that’s encrypted by SSLv3 encryption. Your IMM solutions and the data being processed remain safe and unaffected by the potential vulnerabilities of the Poodle vulnerability as reported.

 

In regards to IMM’s Document Exchange remote eSignature service (Strategic partnership with Adobe EchoSign), Adobe has advised IMM that they have instituted all necessary procedures in order to maintain the ongoing security of their systems, servers and data. Currently, they advise that Poodle vulnerability can only be exposed when the signing user is operating a machine running Internet Explorer 6. Adobe has remediation plans in place to close this particular element by November 25.

As word of the BASH bug is beginning to spread across various media outlets, IMM would like to provide you with important security information about your IMM solution(s) as they relate to this report. The BASH vulnerability only affects computers/servers that are running the LINUX or Mac OS X operating systems. IMM’s software applications run on the Windows Server operating system and therefore are not affected by this media report and it’s associated vulnerabilities. Your IMM solutions and the data being processed remain safe and unaffected by the potential vulnerabilities of the BASH reports.

 

In regards to IMM’s Document Exchange remote eSignature service (Strategic partnership with Adobe EchoSign), Adobe has advised IMM that they have instituted all necessary procedures in order to maintain the ongoing security of their systems, servers and data.