- About Kaspersky Security for Virtualization 6.1 Light Agent
- What’s new
- Solution architecture
- Preparing to install the solution
- Files required for installing the solution
- Downloading SVM images using the wizard
- Configuring the ports to use
- Accounts for installing and using the solution
- Configuring the use of secure cryptographic algorithms, ciphers, and protocols
- Configuring rules for moving virtual machines to administration groups
- Installing the Kaspersky Security solution
- Installing the Integration Server and Integration Server Console
- Deploying SVMs using the Integration Server Console
- Selecting an action
- Selecting infrastructure for SVM deployment
- Selecting the SVM image
- Selecting the number of SVMs for deployment (infrastructures based on OpenStack)
- Specifying SVM settings
- Specifying SVM settings (infrastructures based on OpenStack)
- Configuring SVM network settings (infrastructures based on OpenStack)
- Configuring IP address settings for SVM
- Specifying Kaspersky Security Center connection settings
- Creating the configuration password and the root account password
- Starting SVM deployment
- Starting SVM deployment (infrastructures based on OpenStack)
- SVM deployment
- Finishing SVM deployment
- Installing Kaspersky Security web plug-ins
- Installing Kaspersky Security MMC plug-ins
- Automatically creating tasks and a default policy for the Protection Server
- Preparing the Protection Server for operation
- About installing Kaspersky Security Center Network Agent on virtual machines
- About installing Light Agent for Linux
- About installing Light Agent on a virtual machine template
- Preparing Light Agents for operation
- Displaying virtual machines and SVMs in Kaspersky Security Center
- Viewing the list of SVMs connected to the Integration Server
- Updating Kaspersky Security from the previous version
- Removing the Kaspersky Security solution
- Application management framework
- About managing the solution using Kaspersky Security Center
- About Kaspersky Security management plug-ins
- Starting and closing Kaspersky Security Center Web Console
- Managing the solution using Kaspersky Security Center policies
- Managing the solution using tasks
- About access rights to the settings of policies and tasks in Kaspersky Security Center
- About Integration Server Console
- Connecting to the Integration Server via Integration Server Console
- Viewing Integration Server settings in the Integration Server Console
- Licensing Kaspersky Security for Virtualization 6.1 Light Agent
- About the End User License Agreement
- About data provision
- About the license
- About the License Certificate
- About license key
- About the activation code
- About the key file
- About subscription
- License-specific solution functionality
- About activating Kaspersky Security for Virtualization 6.1 Light Agent
- Procedure for activating the solution
- Renewing a license
- Renewing subscription
- Viewing information about the license keys used in Kaspersky Security Center
- Starting and stopping Kaspersky Security
- Virtual machine protection status
- Connecting SVMs and Light Agents to the Integration Server
- Connecting Light Agents to SVMs
- Protecting large infrastructures
- Updating Kaspersky Security databases and application modules
- Using Kaspersky Security Network
- Additional Protection Server settings
- Reports and notifications
- SVM reconfiguration using the Integration Server Console
- Selecting an action
- Selecting SVM for reconfiguration
- Entering the configuration password
- Editing SVM network settings
- Editing SVM network settings (infrastructures based on OpenStack)
- Changing SVM IP settings
- Changing Kaspersky Security Center connection settings
- Changing the configuration password and root account settings
- Starting SVM reconfiguration
- Starting SVM reconfiguration (infrastructures based on OpenStack)
- SVM reconfiguration
- Finishing SVM reconfiguration
- Configuring Integration Server settings
- Replacing the Integration Server and SVM certificates
- SNMP monitoring of SVM status
- Checking the integrity of solution components
- Using Kaspersky Security for Virtualization 6.1 Light Agent in multitenancy mode
- Deploying a tenant protection infrastructure
- Configuring the Integration Server connection settings to the Kaspersky Security Center Administration Server
- Creating a tenant and virtual Administration Server
- Configuring SVM location and Protection Server settings
- Configuring settings for SVM discovery by Light Agents and general tenant protection settings
- Installing a Light Agent on tenant virtual machines
- Registering tenant virtual machines
- Activating a tenant
- Registering existing tenants and their virtual machines
- Enabling and disabling tenant protection
- Getting information about tenants
- Getting tenant protection reports
- Removing virtual machines from the protected infrastructure
- Removing tenants
- Using Integration Server REST API in multi-tenancy scenarios
- Deploying a tenant protection infrastructure
- Contacting Technical Support
- How to get technical support
- Technical Support via Kaspersky CompanyAccount
- Getting information for Technical Support
- Protection Server and Light Agent dump files
- Trace files of the Kaspersky Security Components Installation Wizard
- Trace files of the Integration Server and Integration Server Console
- Trace files of the tool for managing Integration Server and SVM certificates
- Trace files of SVMs, Light Agent, and Kaspersky Security management plug-ins
- The SVM Management Wizard log
- Using the utilities and scripts from the Kaspersky Security distribution kit
- About remotely diagnosing a device using Kaspersky Security Center
- Appendices
- Using the klconfig script API to define SVM configuration settings
- Executing configuration commands
- Using the SVM first startup script
- Configuring SVM configuration settings
- Description of commands
- accept_eula_and_privacypolicy
- apiversion
- checkconfig
- connectorlang
- dhcp
- dhcprenew
- dns
- dnslookup
- dnssearch
- dnsshow
- getdnshostname
- gethypervisordetails
- hostname
- listpatches
- manageservices
- nagent
- network
- ntp
- passwd
- permitrootlogin
- productinstall
- reboot
- resetnetwork
- rollbackpatch
- setsshkey
- settracelevel
- test
- timezone
- version
- Settings in the ScanServer.conf file
- Object ID values for SNMP
- How to remove duplicate virtual machines from the list of managed devices in Kaspersky Security Center
- How to restore the Integration Server database and settings from a backup copy
- Using the klconfig script API to define SVM configuration settings
- Sources of information about the solution
- Glossary
- Activation code
- Active key
- Administration Server
- Application activation
- Backup
- Backup copy of a file
- Compound file
- Database of malicious web addresses
- Database of phishing web addresses
- Desktop key
- End User License Agreement
- Heuristic Analysis
- Integration Server
- Kaspersky CompanyAccount
- Kaspersky Security databases
- Kaspersky Security Network (KSN)
- Key file
- Key with a limitation on the number of processor cores
- Key with a limitation on the number of processors
- Keylogger
- License
- License certificate
- License key (key)
- Light Agent
- OLE object
- OpenStack domain
- OpenStack project
- Phishing
- Protected virtual machine
- Reserve key
- Server key
- Signature Analysis
- Startup objects
- SVM
- SVM Management Wizard
- Update source
- Information about third-party code
- Trademark notices
Settings in the ScanServer.conf file
The ScanServer.conf file contains the SVM operation settings. The file is located on the SVM in the /etc/opt/kaspersky/la/ directory.
Root account permissions are required to view and modify the file.
This section describes the settings in the ScanServer.conf file that allow you to configure logging of the SVM traces and dumps, usage of the SVM system log, and agree to the terms of the End User License Agreement. Information about other settings, if necessary, can be obtained from the Technical Support.
Unassisted modification of the Kaspersky Security operation settings in the ways not described in the Kaspersky Security help or in the recommendations from the Technical Support specialists can lead to slowdowns and malfunctions of the operating system, decrease of the virtual machine protection level, as well as to a violation of the availability and integrity of the processed information.
General settings trace_level = 0 Determines the trace level for all SVM trace files except the SnmpTool.log file. Possible values: After changing the trace level, restart the scanserver service by running the following command: trace_protected_data Writing potentially personal data (for example, passwords) to trace files. Possible values: trace_file = /var/log/kaspersky/la/ScanServer.log The name of the Protection Server trace file. The date is appended to the file name, for example, ScanServer.2020-11-19T130126.log. The rotation settings are controlled by the scanserver service. The trace file is used if system log usage is disabled (see section [syslog]). trace_format = %Y-%m-%dT%X %I %p: The format for logging the lines in the Protection Server trace file (ScanServer.log). Qualifiers: %Y = year, %m = month, %d = day, %H = hour, %M = minute, %S = second, %i = millisecond, %p = trace level, %N = device name, %P = process identifier (PID), %I = thread ID, %C = component ID, %D = component instance ID, %X = time. The trace file is used if system log usage is disabled (see section [syslog]). accept_eula_and_privacypolicy = yes|no Accept or decline the terms of Kaspersky Security End User License Agreement between you and Kaspersky and the Privacy Policy that describes processing and transmission of data. Possible values: yes – accept the terms of the End User License Agreement and the Privacy Policy, no – do not accept the terms of the End User License Agreement and the Privacy Policy. You must accept the terms of the End-User License Agreement and the Privacy Policy for the proper SVM operation. By setting this parameter to 'yes', you confirm the following: The text of the End User License Agreement and Privacy Policy is included in the Kaspersky Security distribution kit.systemctl reload la-scanserver
[rotation_settings] section This section contains processing and rotation settings for the Protection Server trace file (ScanServer.log). period = 3 File rotation frequency. Possible values: 1 – monthly, 2 – weekly, 3 – daily, 4 – hourly. max_file_size = 1073741824 The maximum trace file size in bytes. When reached, rotation is performed. Possible values: 0 – unlimited, 1073741824 – 1 GB. max_file_count = 15 The maximum number of the trace files. When the limit is reached, old files are deleted. Possible values: number or 0 – unlimited. new_file_on_start = 1 Logging to a new file or to the last available trace file when Protection Server starts. Possible values: 1 – write to a new file, 0 – write to the last created file.
[extra_tracing] section enabled = 1 Logging general information to trace files every time the trace level is changed (information about the license, KSN usage, and the anti-virus databases used). Possible values: 0 – disabled, 1 – enabled.
[syslog] section This section contains the system log usage settings. enabled = 0 System log usage. Possible values: 1 – enable, 0 – disable. If the system log usage is disabled, data is logged to the Protection Server trace file. The file name is specified by the trace_file setting (see the General settings section). program_name = ScanServer System log name. facility = 176 System log category (LOG_LOCAL6 = 176). format = %I %p: Syslog entry format: %Y = year, %m = month, %d = day, %H = hour, %M = minute, %S = second, %i = millisecond, %p = trace level, %N = device name, %P = process identifier (PID), %I = thread ID, %C = component ID, %D = component instance ID, %X = time.
[dumps] section This section contains the settings of the Protection Server dump files. dir = /var/opt/kaspersky/la/dumps Directory for logging dumps. schema = ScanServer_%d_%p_%n.dmp Name configuration: max = 10 The maximum number of dumps in the repository. freeMiB = 1024 The minimum amount of free disk space required to write the dump (in MB).