![]() When connecting through a proxy with FIPS mode enabled, Deep Security Agent sometimes had connectivity issues with IoT devices.Deep Security Agent now includes path and PID (process ID) for Anti-Malware events.Updated Deep Security Agent to improve MQTT connection quality and reduce the occurrence of connection timeouts.For more information on certificate upgrade, see Upgrade the Deep Security cryptographic algorithm. This prevents the agent from updating and becoming unresponsive, since Deep Security Agent 20.0.0-6313 and higher requires RSA-2048 and SHA-256. Deep Security Agent installer now prevents the agent from updating if it detects SHA-1 was used to sign the certificate on the agent installer.Updated Deep Security Agent to make the connection timeout for proxy probing configurable by adding a line to ds_agent.ini.(This requires Deep Security Manager 20.0.759+.) Enhancements (This requires Deep Security Manager 20.0.759+.)ĪlmaLinux 9 support: Deep Security Agent 20.0.0-6912+ now supports AlmaLinux 9, including Secure Boot support. Red Hat Enterprise Linux Workstation 7 support: Deep Security Agent 20.0.0-6912+ now supports Red Hat Enterprise Linux Workstation 7, including Secure Boot support. When Anti-Malware was enabled, Deep Security Agent caused high CPU usage on some systems.After replacing a connection, Deep Security Agent reported metrics as though it was still connected to the old connection for up to 4 minutes.Deep Security Agent only reported a single Anti-Malware event for an infected compressed file, even if it contained multiple infected files.Systems running Red Hat Enterprise Linux 7 (64-bit) with SELinux may require some manual configuration to avoid permission issues following this update. ![]() Agent self-protection now secures the Advanced TLS inspection process ( ds_nuagent), preventing local users with administrator privileges from stopping it.Deep Security Agent crashed some systems when they were out of memory.Updated Deep Security Agent to reduce the amount of redundant data sent when Activity Monitoring is enabled.MQTT connection credentials were entered in the Deep Security Agent log file ( ds_agent.log) in certain scenarios.Deep Security Agent - 20.0.0-7119 (20 LTS Update )
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |