Hello,

We created the Python script but with some adjustments.

The path, login, and password are passed as parameters rather than hardcoded into the script.
Sensitive data is encrypted using a certificate.
The account used for the script is dedicated to this task.
A PowerShell script...

Thank you for your feedback.

Isn't it more secure to use encryption functions like the example below:

https://www.wapt.fr/en/doc-1.8/wapt-cre ... aquet.html

So the agent needs to be installed on the machine running the script?

In all cases, is the password hardcoded into a file?

Can we run it directly on our WAPT server, which is running Red Hat?

Is your code meant to be placed in an audit function of a scheduled package (audit_schedule)?

In your code, there's `password=password`; is it possible to avoid putting the password in plain text?

Hello,

The data is being retrieved correctly:

{
"id": 4042,
"host": "XXX",
"value_id": 3802606994107531265,
"value_date": "2026-02-10T12:34:28.809306+00:00",
"value_section": "test-encryption",
"value_key": "test-encryption",
"value": "-----BEGIN WAPT ENCRYPTION ...

The register hasn't changed anything and the problem is present for all machines that report this audit.

Hello,

No errors in the package audit.


Status; Audit Status; Package Name; Version; Installation Date; Audited on; Next audit
OK; OK; tcfpkg-rustdesk-config; 29; 09/02/2026 13:23:43; 09/02/2026 16:51:55; 11/03/2026 16:51:55.


No changes on the audit side.


id; Date; Section; Key; Value; Date of...

Hello,

I confirm that the certificate is the same.

Indeed, the audit remains unchanged.

Can this script run on a Linux machine?

We were thinking of running it on the WAPT server, at least for the Defender package, as it receives updates very regularly.

Hello,

Yes, the audit of the rustdesk-config package has started, the status is OK, and the date is correctly updated.

However, in the audit data, the value remains at 07/02.