We’re happy to inform you that SilentDefense version 3.13.3 has been released! This is a maintenance release to improve stability of our oldest supported SilentDefense version.
What is this?
This release provides fixes for several defects found in SilentDefense 3.13.2. It improves the overall stability of SilentDefense 3.13.3.
What does this mean for you?
SilentDefense customers that are still operating on version 3.13, may encounter the issues fixed in this release. You will be able to help them by providing this maintenance release to your customers.
What customers would care?
Only a few customers are working on SilentDefense 3.13. These typically are customers who value the stability of their operations to a high degree and who only use software that has been available for a longer time, for which issues have been found and fixed before they adopt that version. For customers with this profile, the stability of SilentDefense 3.13 is of the utmost importance.
What do I do about it?
When you service customers with an established 3.13 deployment – and for which an upgrade to SilentDefense 4.0.1 or SilentDefense 4.1.1 is not an option – please consider bringing this maintenance update to their attention.
What’s New
Download this update to resolve the following issues:
- Fixed an issue in the sensor returning an incorrect exit code, potentially causing the following effects on CC operations:
- Repeated false positive NTP health status warnings.
- Failure in the upload of zipped PCAPs.
- Failure in running NTP commands.
- Failure in dependency checks (e.g. sddump).
- Fixed an issue in handling underscores used in DNS A records. These are not allowed by protocol specification but are used in some implementations. These records are still logged as dns resolved events, but no longer used as a hostname.
- Resolved a parsing error that led to an exception to be wrongly raised when handling MMS/IEC61850 journaling feature data for Dranetz power quality analyzers.
- Fixed the number of times “Unexpected restart(s) of DNP3 field device” is triggered per hour.
- Corrected the L3 protocol displayed for “itl sec dos syn flood” alerts, from ARP to IP.
- Fixed an issue with hashing host and link data, that resulted in nids process termination due to slow packet processing; the enhancements lead to overall faster search and improved performance when processing host and link entries.
Supported Versions
This release is intended to update a SilentDefense 3.13.2 Monitoring Sensor to version 3.13.3.
Availability
Download the module and related documentation from https://portal.secmatters.com.
