|Software Component||System Monitor (SysMon)|
LogRhythm 7.10.0 GA
LogRhythm 7.9.0 GA
Microsoft .NET Framework 4.7.2
LogRhythm System Monitor Agents for Windows require the Microsoft .NET Framework 4.7.2.
- Before upgrading your System Monitor Agent, confirm that .NET Framework 4.7.2 is installed.
- For information on determining which .NET version is installed, see https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/how-to-determine-which-versions-are-installed.
- If necessary, install .NET Framework 4.7.2 and reboot your system. Because of the required reboot, we recommend that you perform this installation during off-peak hours.
- LogRhythm System Monitor is now completely supported in Windows 10 64-bit.
No new improvements in this release.
LogRhythm has deprecated Check Point collection via OPSEC LEA in favor of the newer Check Point Log Exporter. Support for OPSEC LEA was removed starting with LogRhythm System Monitor Collector version 188.8.131.5204 and results in an error in the scsm.log file if this collection method is used. Customers who need to use OPSEC LEA for collection should not upgrade agents past System Monitor 184.108.40.20602 release. For information on how to configure Check Point Log exporter, see Syslog - Check Point Log Exporter device configuration guide.
Salesforce Case ID
Found in Version
|DE16840||454960||7.9 (Linux)||Linux System Monitors no longer display a warning in the SIP setting.|
|452482||7.10.8001||Windows agents will no longer get out of sync and start collecting old MS Event logs in certain situations.|
Resolved Issues - Security
Resolved security-related defects can be viewed on the Community.
Found In Version
|DE14004||7.8.0||Mimecast||When enabling cleanup scripts for Mimecast collection, customers may receive tracking errors and collection may not be reliable.|
Expected Results: Collection should be reliable during cleanup.
Workaround: There is no workaround for this issue.