Kaspersky Scan Engine
- About Kaspersky Scan Engine
- Getting started with Kaspersky Scan Engine
- Installing Kaspersky Scan Engine
- Using Kaspersky Scan Engine in HTTP mode
- Kaspersky Scan Engine and HTTP mode
- Configuring Kaspersky Scan Engine in HTTP mode
- HTTP mode configuration file
- Configuring Format Recognizer
- Recognizable file formats
- Setting up the connection queue in HTTP mode
- Setting the session timeout
- Changing variables in the HTTP mode init script (Linux)
- Changing variables in the HTTP mode unit file (Linux)
- Configuring updating in HTTP mode
- Running Kaspersky Scan Engine in HTTP mode
- Running Kaspersky Scan Engine in HTTP mode manually
- Running Kaspersky Scan Engine in HTTP mode with init script (Linux)
- Running Kaspersky Scan Engine in HTTP mode with systemd unit file (Linux)
- Running Kaspersky Scan Engine in HTTP mode as service (Windows)
- Running Kaspersky Scan Engine in HTTP mode with a BAT script (Windows)
- Monitoring Kaspersky Scan Engine in HTTP mode
- Making requests in HTTP mode
- About KAV protocol
- Making requests in HTTP mode via KAV protocol version 3
- Supported API methods in KAV protocol version 3
- Format of a scan POST request
- Format of a response to a scan POST request
- Increasing the detection rate
- Example of an HTTP request to scan a local file
- Example of an HTTP request to scan a block of memory
- Example of an HTTP request to check a URL
- Example of an HTTP request to get the release date of the anti-virus database
- Example of an HTTP request to get the current KAV SDK version
- Example of an HTTP request to get licensing information
- Example of an HTTP request to get accumulated statistics
- Example of an HTTP request to clear accumulated statistics
- Example of an HTTP request to update the anti-virus database
- Example of an HTTP request to get the database update status
- Making requests in HTTP mode via KAV protocol versions 1 and 2
- Supported API methods in KAV protocol versions 1 and 2
- Request headers
- Example of an HTTP request to scan a local file
- Example of an HTTP request to scan a block of memory
- Example of a multipart HTTP request to scan a block of memory
- Example of an HTTP request to check a URL
- Example of an HTTP request to get the release date of the anti-virus database
- Example of an HTTP request to get the current KAV SDK version
- Example of an HTTP request to get licensing information
- Example of an HTTP request to get accumulated statistics
- Example of an HTTP request to clear accumulated statistics
- Using the sample HTTP client
- Using a proxy server
- Updating the anti-virus database in HTTP mode
- Logging in HTTP mode
- Building executable files for the HTTP service and the HTTP client
- Using Kaspersky Scan Engine in ICAP mode
- Kaspersky Scan Engine and ICAP mode
- Configuring Kaspersky Scan Engine in ICAP mode
- Running Kaspersky Scan Engine in ICAP mode
- Updating the anti-virus database in ICAP mode
- Getting accumulated statistics in ICAP mode
- Using Kaspersky Scan Engine in ICAP mode with Squid
- Logging in ICAP mode
- Building executable files for Kaspersky Scan Engine used in ICAP mode
- Using Kaspersky Scan Engine GUI
- Manually editing Kaspersky Scan Engine configuration file
- Verifying virus detection capabilities
- Logging
- Boosting performance of Kaspersky Scan Engine
- Uninstalling Kaspersky Scan Engine
- Using the password utility
- Using the encrypting utility
- Licensing
- Kaspersky Scan Engine GUI and SSL certificates
- Troubleshooting
- Data transferred to Kaspersky Lab
- Contacting Technical Support
- Information about third-party code
- Trademark notices
- Copyright
Data transferred to Kaspersky Lab > Data transferred to Kaspersky Lab during File and URL Reputation Checking
Data transferred to Kaspersky Lab during File and URL Reputation Checking
Data transferred to Kaspersky Lab during File and URL Reputation Checking
When you use the File and URL Reputation Checking feature, Kaspersky Scan Engine transfers to Kaspersky Lab information about the installed copy of Kaspersky Scan Engine and detected objects.
The following information is transferred:
- Identifier of Kaspersky Scan Engine
- Full version of Kaspersky Scan Engine: major, minor, build, revision, and hotfix
- Identifier of the license owner
- Checksums of processed files (MD5, SHA256)
- Version of KSN
- Checksums of the detected object name (MD5, SHA256)
- Normalized URL
For details about the data provisioning process, see section "About data provisioning".
Article ID: 180813, Last review: Aug 28, 2024