New version Enhanced Notification Service for SCOM 1.1.0.8

New version released – Enhanced Notification Service for SCOM.

Supported Operations Manager versions: 2012, 2012 Sp1, SCOM 2012 R2, 2016, and SCOM 1801

You can access the upgrade through your account at http://www.lissproductions.com/my-account/

1.1.0.8 (Release) – 2018-07-16

– New version of SCOM supported 1801.
– Bug Fixed – Bug – Microsoft.Linux.Universal.* rules do not display alertprincipalname

– Bug Fixed – When receiving notifications from SCOM, check to see if file is zero bytes
– Bug Fixed – Not all overrides are showing for monitor/rule
– Improved – Deprecate TLS 1.0 and 1.1 to maintain the high security profile

Why Are We Deprecating TLS 1.0 and 1.1?
TLS 1.0 and 1.1 are both fairly dated versions of the TLS protocol. TLS 1.0 was published in 1999 as RFC 2246 while TLS 1.1 was published in 2006 as RFC 4346. Many improvements have been made since the release of these versions and upgrading to the current standard (TLS 1.2) is now considered the safest and most reliable method of delivering encrypted content over the Internet.

To give you an idea, here are couple major attacks which TLS 1.0 and 1.1 are vulnerable to:

POODLE – A man-in-the-middle attack that would downgrade the connection to a protocol that was vulnerable to the attack. Poodle primarily targeted SSL 3.0, however, TLS 1.0 and 1.1 were also vulnerable to POODLE as they accept incorrect padding structure after the decryption.
BEAST – Another man-in-the-middle attack that would take advantage of a vulnerability in the Cipher Block Chaining mode in TLS 1.0 and use it to decrypt data exchanged between two parties.
Furthermore, the PCI Data Security Standard (PCI DSS) requires that you disable the use of any SSL/TLS 1.0 implementations by June 30, 2018. TLS 1.1 will still be accepted by PCI although they strongly recommend using TLS 1.2. Given the vulnerabilities TLS 1.0 and 1.1 are susceptible to and the recommendations provided by PCI, we’ll be deprecating support of both of these versions and moving ahead with more recent versions of the TLS protocol.

Posted on July 16, 2018 in Releases

Share the Story

Back to Top