Please note that on June 1, 2018, SpringCM will disable the TLS 1.1 encryption protocol. After we disable TLS 1.1, any inbound or outbound connection with SpringCM will need to use the TLS 1.2 encryption protocol.
Alert: TLS Encryption Protocol Standards Changing - June 2018
POSTED: May 3, 2018 2:57:16 PM
Security,
TLS,
Encryption,
Browser
4/20/2018 9:35 pm CDT: The SpringCM Technology team has resolved both the performance degradation issue as well as the issue with legacy workflow reports, which are now available for all customers on NA11 Production. Please check the status of trust.springcm.com frequently for updates regarding the root cause of this issue.
4/20/2018 9:15 am CDT : The SpringCM Technology team has resolved the performance degradation issue on our workflow engine and all customers on NA11 (Production) should no longer be experiencing timeout issue when accessing the workflow page.
SpringCM UAT and Production Release Schedule (2018)
POSTED: Mar 26, 2018 2:26:17 PM
UAT,
Production,
New Release,
Deployment
SpringCM has confirmed the deployment dates for all remaining 2018 product releases. During each window, the specified SpringCM environment will be unavailable:
Thursday, April 19th
8PM - 11PM U.S. Central Time
UAT Environment
Friday, May 4th
9PM - Midnight U.S. Central Time
Production Environments (NA11, NA21, EU11, EU21)
[ANNOUNCEMENT] | NA11| UAT Maintenance Scheduled for Wednesday, March 14, 2018 from 8PM-12AM CDT
POSTED: Mar 12, 2018 1:40:03 PM
Maintenance,
Alert,
UAT
SpringCM has scheduled the following upcoming routine maintenance event(s) for the UAT environment. During the maintenance window, SpringCM's UAT environment will be unavailable.
The maintenance event(s) will occur on:
Wednesday, March 14, from 8PM to 12AM, U.S. Central Time
Should you have any questions, please contact support@springcm.com. Thank you for your attention.
Maintenance Alert: SpringCM March Release Production Deployment (March 9)
POSTED: Feb 23, 2018 9:59:11 AM
Maintenance,
Alert,
Production,
New Release
SpringCM's March 2018 Release, featuring a simplified and more intuitive navigation design, is coming your way on March 9th. The new release will be deployed to the Production Environment on Friday, March 9th from 9PM to midnight US Central Standard Time.
February 2, 2018 08:00AM CT - The workflow queues returned normal to normal at approximately 5:30pm CT on Thursday, February 1, 2018.
We have detected an abnormal increase in workflow volume that is resulting in intermittent workflow delays starting between approximately 9am and 10am CT. At present time the engineers have addressed the degradation in workflow execution and we anticipate the workflow queues to return back to normal shortly.
Our engineering team is currently investigating the root cause of the issue and will provide another update.
[ANNOUNCEMENT] | NA11, NA21 | File It 4.90 Package Released
POSTED: Jan 29, 2018 7:13:59 PM
File It,
Salesforce
File It 4.90 RELEASED:
This update delivers enhanced security and support for SpringCM’s European data centers (EU11 and EU21). Accounts that do not upgrade are unaffected by this update.
The following steps must be completed for both Salesforce Classic and Salesforce Lightning versions if you install or upgrade to the File It 4.90 package. You need to access your Salesforce organization as a Sys Admin for the SpringCM_FileIt Connected App when configuring this update. Steps continued.
Wildcard Certificate Update
POSTED: Jan 24, 2018 10:38:15 AM
Security
On January 31st at 5:30pm CDT SpringCM will upgrade the SSL certificate used for the platform by customers who bypass the Akamai network. This change only affects customers who use a specific URL to bypass the default SpringCM login page and the Akamai caching network.
The new SSL certificate uses a SHA256 root, instead of the SHA1 root of the current certificate. All recent computer operating systems and browsers support this new certificate. Legacy operating systems including OSX Leopard and Windows XP may experience browser connection warnings.
Customers can test their computers ahead of this change by loading this SpringCM test website: https://sha256test.springcm.com
Continue reading...
The new SSL certificate uses a SHA256 root, instead of the SHA1 root of the current certificate. All recent computer operating systems and browsers support this new certificate. Legacy operating systems including OSX Leopard and Windows XP may experience browser connection warnings.
Customers can test their computers ahead of this change by loading this SpringCM test website: https://sha256test.springcm.com
Planned SSO Certificate Upgrade
POSTED: Jan 22, 2018 4:14:29 PM
SAML
On Wednesday, January 31, 2018 at 5:30PM CST, SpringCM will be upgrading the certificate used to sign outgoing SAML requests. If you are using SSO with SpringCM and your Identity Provider is set to validate the signature on incoming SAML requests, but is not setup to monitor and auto update the certificate via SpringCM's service provider metadata, you may need to upgrade the certificate manually.
New certificates will be available in Account Preferences under SAML SSO at the time of upgrade and have been made available now via public download below.
Please contact SpringCM Support with any questions.
SpringCM addresses ‘Spectre’ and ‘Meltdown’ vulnerabilities
POSTED: Jan 19, 2018 11:53:22 AM
CVE-2017-5715,
CVE-2017-5753,
CVE-2017-5754
On January 3, 2018, the National Cybersecurity and Communications Integration Center (NCCIC) became aware of a set of security vulnerabilities—known as Meltdown (https://meltdownattack.com/) and Spectre (https://spectreattack.com/)— that affect modern computer processors. Exploitation of these vulnerabilities could allow an attacker to obtain access to sensitive information.
After the January 3 announcement, the SpringCM Security team immediately evaluated the systems affected by these vulnerabilities and completed an assessment on the likelihood and impact. At this point no systems appear to be compromised and an ongoing monitoring system is in place to alert on suspicious events. As vendors continue to release updates to the most stable releases of their software, SpringCM will continue to remediate these vulnerabilities.
Re: CVE-2017-5715, CVE-2017-5753, CVE-2017-5754
