ESET Agent additional usage examples
The examples below provide additional usage of the scanner agent's available commands.
Using SSL Between Agent and Balancer
This command demonstrates how to run the scanner agent with Secure Sockets Layer (SSL) encryption enabled for communication between the agent and the load balancer.
Command:
scanner_agent -t 172.17.0.4:50052 -s -c cert.pem -j 1 test.txt |
Explanation of the command parameters:
•-t 172.17.0.4:50052; Specifies the target endpoint (scanner) for scanning, using IP address and port.
•-s; Enables SSL/TLS communication, encrypting all traffic between the agent and balancer.
•-c cert.pem; Declares the SSL certificate (or certificate bundle) to be used for verifying the balancer's identity.
•-j 1; Sets the number of parallel files to be scanned; here, only one at a time.
•test.txt; The file to be scanned.
Using SSL and Authorization Between Agent and Balancer
This command extends the previous example by adding user authorization via an authentication server, in addition to SSL encryption.
Command:
scanner_agent -t 172.17.0.4:50052 -s -c cert.pem -u user -p password -a https://172.17.0.2:50055/token -k |
Explanation of the command parameters:
•-u user -p password; Specifies credentials to authenticate the agent with the authorization (token) server.
•-a https://172.17.0.2:50055/token; Sets the URL of the authorization server (token endpoint) used for authenticating and obtaining a token.
•-k cert.pem; Provides a certificate or certificate bundle to verify the authorization server's identity over SSL.
AWS example with OAuth2 Authentication
In this example, the scanner agent connects securely to a remote ESET PRIVATE Static Scanning Engine endpoint (commonly used with AWS-hosted workloads), authenticating with OAuth2 credentials for enhanced, identity-based security.
Command:
scanner_agent -t e2kr9b8x.threat.scanners.eset.systems:50052 -j 1 -c cert.pem -u 'OAuth2 client_id' -p 'OAuth2 client_secret' |
Explanation of the command parameters:
•-u 'OAuth2 client_id' -p 'OAuth2 client_secret'; Supplies the OAuth2 client credentials, in place of static user/password, for secure, managed authentication.
•-a https://.../openid-connect/token; Targets the OpenID Connect (OIDC) token endpoint for OAuth2-based authentication, essential for integration with modern identity providers.
•--skip_cloud_reputation; Disables cloud reputation and dynamic scan, instructing the scanner to perform a static scan only.
•All SSL/identity parameters apply as above.
•/bin/bash: Indicates the path to the file to be scanned.
|
The target endpoint (scanner) addresses shown in the examples are for illustration purposes only. Be sure to replace these, along with placeholders such as 'OAuth2 client_id', 'OAuth2 client_secret', and ‘cert.pem’, with the actual endpoint URLs, credentials, and certificate file paths corresponding to your environment. |
