Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Security in Yandex Cloud
  • Key security principles
  • Division of responsibility for security
  • Compliance
  • Security measures on the Yandex Cloud side
  • Security tools available to cloud service users
    • All sections on one page
    • Introduction
    • Authentication and access management
    • Session and cookie security
    • Monitoring and audit
    • Data encryption and protection
    • Integrations and third-party solutions
  • User support policy during vulnerability scanning
  • Security bulletins
  • Public IP address ranges

In this article:

  • Data encryption and protection
  • Every domain user has a linked phone number (secure phone)
  • If there is an existing DLP system in place, configure it for Yandex 360 services
  1. Yandex 360 protection and safe use standard, version 1.0.0
  2. Data encryption and protection
Written by
Yandex Cloud
Updated at September 22, 2025
  • Data encryption and protection
    • Every domain user has a linked phone number (secure phone)
    • If there is an existing DLP system in place, configure it for Yandex 360 services

Data encryption and protectionData encryption and protection

Every domain user has a linked phone number (secure phone)Every domain user has a linked phone number (secure phone)

Y360-4

For added security, domain users must have a mobile phone number (secure phone) linked to each account. In addition to reliable authentication and account recovery, this will also enable two-factor authentication (2FA).

Checking from the Yandex 360 console
Checking via the API
  1. Go to the Phones page.

    The page will display several numbers if a phone number different from main one was specified in a different Yandex service.

To get the 2FA setup status for each domain user, use the UserService_Get2fa REST API method for the UserService resource. In the response, check that the hasSecurityPhone field is set to true.

Note

For users with a Yandex ID account, this verification mechanism will be implemented at a later stage.

How to implement:

It is the administrator's duty to have the users' phone numbers linked to their domain accounts. This is done to strengthen security and prevent unauthorized access.

If there is an existing DLP system in place, configure it for Yandex 360 servicesIf there is an existing DLP system in place, configure it for Yandex 360 services

Y360-14

To protect corporate information and minimize the risk of data leaks, we recommend setting up the DLP (Data Loss Prevention) system in Yandex 360 services. DLP automatically detects sensitive information, such as passwords, tokens, secret keys, personal data, etc., and prevents it getting in the hands of unauthorized recipients.

Checking via the API

To check if there is a rule for incoming and outgoing mail to be forwarded to a DLP address, use the RoutingService_GetRules REST API method for the RoutingService resource. Make sure that one of the rules (the first or required one) has the forward action to forward emails to a dedicated DLP address (dlp@domain.ru or similar).

Response example:

{
  "terminal": false,
  "condition": {},
  "actions": [
    {
      "data": {"email": "dlp@domain.ru"},
      "action": "forward"
    }
  ],
  "scope": {"direction": "outbound"}
}

Also check the incoming mail forwarding setting: we recommend forwarding all correspondence for extended control.

How to implement:

  1. Consider setting up forwarding of outgoing (and, optionally, incoming) mail to a dedicated DLP mailbox for automated analysis:
    • Check if there is a forwarding rule with the help of the GET https://api360.yandex.net/admin/v1/org/{ORGANIZATION}/mail/routing/rules API request.
    • Make sure that one of the rules has the forward action to forward emails to a dedicated DLP address, e.g., dlp@domain.ru.
  2. Make sure the DLP mailbox can be accessed externally:
    • Create a dedicated user for integration of the DLP platform with the mailbox.
    • Set up an app-specific password or OAuth access for this user.
  3. Check if email scans are on for:
    • Passwords and password reset requests.
    • Access tokens.
    • SSH, PKI, or VPN private keys.
    • Personal or confidential data (if this is part of the policy).

Was the article helpful?

Previous
Monitoring and audit
Next
Integrations and third-party solutions
© 2025 Direct Cursus Technology L.L.C.