Frequently asked questions
Detailed information is available in the Certificates, licenses and attestations section and on the Certificates and licenses page.
Additional documents are provided after signing a non-disclosure agreement (NDA).
Yes, it does. Detailed information is available in the Certificates, licenses and attestations section and on the Certificates and licenses page.
Yes, there is. For more details, see the Platform security section.
VK Cloud may engage subcontractors to provide services. Clients who may be affected are informed about this.
VK Cloud ensures that contracts with subcontractors include the necessary information security measures that comply with VK Cloud's information security obligations to its clients.
VK Cloud is responsible for the security of the cloud infrastructure, while the client is responsible for the security of their systems and data deployed inside the cloud.
When using the special service Cloud 152-FZ, responsibility for personal data storage is also divided.
For more details, see the Cloud security page.
This is the client's own responsibility.
For more details on the division of responsibility, see the question above.
Yes, it is possible.
Yes, the client chooses the possible methods for labeling their information themselves.
Accounts can be created:
- by the user themselves after registration;
- via export from LDAP systems.
After registration, the client manages access rights themselves, including inviting users, configuring the access level, two-factor authentication, etc.
Authentication is performed using a login and password, which are not transmitted in plain text. Additionally, you can enable two-factor authentication (2FA) using TOTP.
Use long and complex passwords consisting of multiple character categories, and also enable two-factor authentication (2FA) for the account.
Yes, it is supported. The client's SSO system can be connected for logging in to the VK Cloud management console using SAML or ADFS protocols.
Yes, it can. To do this, you need to connect the client's LDAP server to the platform using SAML or ADFS protocols and control the password policy on that server.
Yes, it is. For more details, see the Role-based access control model section.
Yes, it can be implemented on the client side using SAML.
Immediately try to change the password. If that fails, contact technical support and select the service type in your ticket: VK Cloud → Report a problem → Management console and account → Account has been hacked.
Detailed information is available in the Security groups section.
You can connect these services by submitting a request in the management console in the Special services section or on the website. For more details about these special services, see the WAF and AntiDDoS section.
- When using the AntiDDoS special service, the client can choose between the StormWall, ServicePipe and Variti solutions.
- When using the WAF special service, the client can choose between the Positive Technologies Cloud WAF, SolidWAF and WebMonitorex solutions.
Isolation between clients is provided at the following levels:
- network,
- hypervisor,
- application.
The VK Cloud client's projects are isolated from other clients. Information flows are managed at the level of client VMs. VK Cloud infrastructure resources run on dedicated physical servers that are not used for operating in a virtualization environment. Access from client networks to service networks is impossible. When creating a VM, the user configures firewall rules themselves or selects a suggested security group.
No. VK client projects are created for each client and isolated from other clients. Reuse of one client's projects by other clients is not allowed.
Information security events of VK and VK Cloud infrastructures are monitored by the VK SOC duty shift on a 24/7 basis. SIEM is used to collect and store information security events. Access to information security event logs is restricted by SIEM tools.
VK Cloud users have access to the following event monitoring services:
Using NTP servers of the VK infrastructure, which, in turn, are synchronized with the NTP Pool.
Yes, it is. For more details, see the API reference.
Approximately one year. It is recommended to configure the delivery of information from the log to the client's SIEM systems.
Records are protected through access restriction and control over this information.
Report suspected information security incidents via technical support. After the request is received, the area of responsibility is determined:
- If the information security incident falls within the client's area of responsibility, the client resolves the incident themselves.
- If the information security incident falls within the VK Cloud area of responsibility, VK Cloud handles the incident.
VK Cloud informs clients about outages and incidents that may affect them in the Service status section and in the Telegram channel.
Yes, it is possible upon agreement.
Yes, for more details see the Cloud Backup section.
Responsibility for organizing backup and recovery processes lies with the users themselves.
Yes, it is. A geographically distributed S3 storage is used for storing backups (SLA of 99.9999% for data preservation).
Yes, it is.
VK Cloud is monitored by the Security Operations Center (SOC) and SIEM systems (Security Information and Event Management).
Administrators perform mandatory authentication and use specially configured intermediate hosts (jump hosts).
For more details, see the Platform security section.
Secure TLS and HTTPS protocols are used. If necessary, clients can configure additional data encryption.
When using VK Cloud, it is prohibited to use service programs (utilities) capable of bypassing normal operating procedures or security procedures without agreement with VK Cloud. By using VK Cloud services, you accept the terms of the agreements that govern the rules for working with the platform.
In turn, VK Cloud guarantees that the use of such programs by VK Cloud personnel is strictly limited and controlled.
VK Cloud timely informs users about the status of services, outages and changes that may affect them in the Service status section and in the Telegram channel.
Temporary files and documents are deleted within 1 month.
- Table of Contents