||September 21st, 2021
The agent is now multi-region aware and can automatically detect to which region to connect to.
The agent now supports the Fail Closed capability. Refer to Fail Closed behaviour for more details.
The agent is now GA for Azure serverless function support
Updated anti-malware and malicious payload engines to resolve reported vulnerabilities with 3rd-party libraries: openssl, expat, and zlib.
Fixed an exception being raised when using the with statement with psycopg2.
||July 7th, 2021
Added the capability for the agent to protect Azure functions
Added support for the Advanced Threat Scan Engine (ATSE) aggressiveness level to be set from policy view.
Changed default ATSE aggressiveness level from High to Medium.
Upgraded advanced thread scan engine to version 12.500-1004
Wait until the engines rules blobs are written to cache before declaring the agent ready
Synchronize writing file to disk when updating the agent configuration cache
Re-initialise antivirus engine on first request when engine initialization failed
Fixed anti-malware engine returning error when scanning after malicious file upload policy rules were changed
Fixed vulnerable dependencies on pnet and crypto
||July 3rd, 2020
Include the server socket information when using Tornado framework.
Introduced the ability for the agent to manage atomic configuration updates from the backend.
Rulesets and patterns are not fetched or updated if Malicious Payload and Malicious File Upload are disabled.
Fixed the redirect override when using the Tornado framework.
Fixed the wsgi hooking when using the Pyramid framework.
Disabled providing the custom transaction ID via the header.
Fixed the poller hanging after re-authentication.
Fixed the agent continuously and quickly re-attempting to authenticate following repeated authentication failures.
Fixed agent cleanup and activation of anti-malware pattern files upon updates.
Fixed some agent errors not being reported to the backend properly, for remote diagnostics.
||April 30th, 2020
Tornado 5.1 with Python 3.7 and up
The Remote Command Execution algorithm was previously considering only the commands being run through a shell, all commands are now considered.
||January 24th, 2020
||First release of Trend Micro Cloud One Application Security python agent
Remote Command Execution
Illegal File Access
Malicious File Upload