Telegram RegisterThe public register of Telegram

Channel

Безопасно говоря

@yndxcloudsecurity

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Polls · Citations · Cite this entry

666subscribers

+0 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002730160450
TypeChannel
Username@yndxcloudsecurity
DescriptionСледим за рисками, отражаем атаки, делимся решениями. Всё о безопасности облачной инфраструктуры — практика, кейсы и инсайты от команды Yandex Cloud, которая защищает её каждый день.
CreatedBetween 1 June 2025 and 30 September 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live6 August 2026
Measurements held2
On Telegramt.me/yndxcloudsecurity

Growth

6666 Aug 2026, 01:35 — 666 subscribers6 Aug 2026, 16:40 — 666 subscribers6 Aug 2026, 01:356 Aug 2026, 16:40
2 measurements taken within a single day. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 665–667 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
6 Aug 2026, 16:40666no change
6 Aug 2026, 01:35666first reading

Engagement

15 posts held, back to 17 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

ERR · 30 days
632.2%
avg views ÷ 666 subscribers
Avg views / post
4,210
15 posts measured
Reaction rate
0.22%
reactions ÷ views · ER floor
Posts in window
15
of 15 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate. It is computed over the 9 of 15 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 6 August 2026
Posts held15 (17 July 20266 August 2026)
Views total63,159
Reactions total133
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 16:40 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

What this channel posts

Photos
212
Videos
13
Links
123

Lifetime counters from Telegram’s own channel header, read 6 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

133 reactions across 9 posts, in 7 distinct kinds. The most used accounts for 34.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4634.6%
3828.6%
👍3828.6%
🤝53.76%
👏32.26%
👀21.50%
😍10.752%

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 9 of the 15 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 133reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 15 most recent posts we hold, published 17 July 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

6 Aug 2026, 15:57 UTC71 views8 reactionsread 6 August 2026
Photo

Всё самое главное о продуктах и инструментах ИБ Yandex Cloud за июль ▪️ Хотите — смотрите карточки⬆️⬆️⬆️ А если удобнее читать — выбирайте подходящий пост из списка ⬇️⬇️⬇️ ✔️ Закрыли свежую уязвимость CVE-2026-53359 — Januscape. ✔️ Показали обзор Yandex SIEM от AM Live. ✔️ Получили ещё два ГОСТа — ГОСТ 57580.3-2022 и ГОСТ 57580.4-2022. Они особенно актуальны для организаций финансового сектора. ✔️ Выпустили мод

👏32👀2🤝1

5 Aug 2026, 11:50 UTC192 views10 reactionsread 6 August 2026
Photo

Программа ☁️☁️☁️☁️☁️☁️☁️ готова! ⚡️ Составляйте свой трек из докладов и воркшопов — в этом году мы добавили новые форматы и возможности для тех, кто будет на Yandex Scale в онлайне. Теперь онлайн-участники могут работать на некоторых воркшопах. И только в онлайне будет транслироваться особенный трек — DeepTech. 🔥 На DeepTech расскажем о технологиях, исследованиях и разработках, которые лежат в основе сервисов Янде

4👍3🔥3

4 Aug 2026, 12:15 UTC258 views15 reactionsread 6 August 2026
Photo

Киберстраховка для бизнеса «СОГАЗ» и «Ингосстрах» вместе с Yandex Cloud (входит в Yandex B2B Tech) запустили программы киберстрахования для бизнеса: ⭐️ Страховые компании предлагают бизнесу страховую защиту от киберугроз. ⭐️ Yandex Cloud оценивает безопасность облачной инфраструктуры клиента для получения более выгодных условий страхового полиса. Киберриски компаний, желающих застраховаться, оценивают с помощью с

🔥8👍61

31 Jul 2026, 11:19 UTC≈57,700 views19 reactionsread 6 August 2026
Video

⚡️ Запускаем новый сезон подкаста «Безопасно говоря»! «Безопасно говоря» — подкаст для ИБ-практиков, где обсуждаем реальные кейсы, самые эффективные решения и внутреннюю кухню ИБ-продуктов. Все выпуски на YouTube ⏩ 🖇 В первом выпуске седьмого сезона говорим о том, как меняется SIEM в эпоху AI, и почему это — не «волшебная коробка». ✨ Гости выпуска: Ринат Сагиров, директор Центра мониторинга и реагирования Инфосис

🔥105👍4

28 Jul 2026, 07:44 UTC465 views22 reactionsread 6 August 2026
Video

Как бороться с шифровальщиками (ransomware) с помощью автоматических настроек Yandex Security Deck — продолжаем рассказывать о сервисе и его сценариях ✔️ 🖇 Предыдущие выпуски: Как начать работу в Security Deck Как работает модуль управления уязвимостями в Security Deck Контроль блокирующих политик в Security Deck Шифровальщики — один из наиболее распространённых и разрушительных видов кибератак, когда злоумышле

🔥97👍6

24 Jul 2026, 12:33 UTC412 viewsread 6 August 2026
Poll

Какой пример лучше всего описывает корреляцию событий?

  1. Сохранение логов за год0%
  2. Архивирование журналов0%
  3. Удаление устаревших записей0%

Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTC374 viewsread 6 August 2026
Poll

Что из перечисленного НЕ входит в основные этапы работы SIEM?

  1. Сбор логов4%
  2. Нормализация данных4%
  3. Корреляция событий6%
  4. Шифрование пользовательского трафика87%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTC387 viewsread 6 August 2026
Poll

Что означает низкое значение MTTD?

  1. Логи занимают меньше места8%
  2. Система быстрее обновляется1%
  3. Инциденты обнаруживаются быстрее58%
  4. Снижается количество ложных срабатываний32%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTC430 viewsread 6 August 2026
Poll

Что обычно делает EDR, в отличие от SIEM?

  1. Хранит логи дольше0%
  2. Формирует отчёты для регуляторов5%
  3. Выявляет и помогает остановить угрозы на конечных устройствах95%
  4. Собирает события только из файрволов0%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTC467 viewsread 6 August 2026
Poll

Какая система отвечает за автоматизацию реагирования?

  1. SIEM14%
  2. XDR8%
  3. SOAR70%
  4. IDS8%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTC498 viewsread 6 August 2026
Poll

Какая связка считается оптимальной?

  1. VPN + Firewall + Proxy4%
  2. DLP + CASB + WAF1%
  3. SIEM + XDR + SOAR88%
  4. SIEM + VPN + IDS7%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTC353 views9 reactionsread 6 August 2026
Photo

Проверьте, знаете ли вы базу SIEM — ответьте на 6 вопросов под этим постом⬇️⬇️⬇️ А чтобы освежить знания, пригодятся эти статьи в нашем блоге: ⏩ SIEM-система: что это такое и как выбрать решение для бизнеса ⏩ Как расследовать облачные инциденты в Yandex SIEM

3🔥3👍2😍1

Showing the 12 most recent of 15 posts we hold for @yndxcloudsecurity. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Polls

The 6 polls we hold for this entry, as Telegram rendered them when we read the post. A poll’s figures keep moving after that, so each one is dated.

24 Jul 2026, 12:33 UTCAnonymous Quiz83 voters

Что из перечисленного НЕ входит в основные этапы работы SIEM?

  1. Сбор логов4%
  2. Нормализация данных4%
  3. Корреляция событий6%
  4. Шифрование пользовательского трафика87%

Shares as published, totalling 101%. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTCAnonymous Quiz74 voters

Что означает низкое значение MTTD?

  1. Логи занимают меньше места8%
  2. Система быстрее обновляется1%
  3. Инциденты обнаруживаются быстрее58%
  4. Снижается количество ложных срабатываний32%

Shares as published, totalling 99%. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTCAnonymous Quiz73 voters

Какой пример лучше всего описывает корреляцию событий?

  1. Сохранение логов за год0%
  2. Архивирование журналов0%
  3. Удаление устаревших записей0%

Shares as published, totalling 0%. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTCAnonymous Quiz73 voters

Что обычно делает EDR, в отличие от SIEM?

  1. Хранит логи дольше0%
  2. Формирует отчёты для регуляторов5%
  3. Выявляет и помогает остановить угрозы на конечных устройствах95%
  4. Собирает события только из файрволов0%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTCAnonymous Quiz77 voters

Какая система отвечает за автоматизацию реагирования?

  1. SIEM14%
  2. XDR8%
  3. SOAR70%
  4. IDS8%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

24 Jul 2026, 12:33 UTCAnonymous Quiz75 voters

Какая связка считается оптимальной?

  1. VPN + Firewall + Proxy4%
  2. DLP + CASB + WAF1%
  3. SIEM + XDR + SOAR88%
  4. SIEM + VPN + IDS7%

Shares as published. No per-option vote count is published by Telegram, so none is shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none.The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100.Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 15 most recent posts we hold, published 17 July 2026 to 6 August 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

Citation-graph rank

Citation-graph rank — 24,818 of 1,160,990entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 4 registered channels — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 6 August 2026 — this entry's latest reading, not the date you are reading this.

“Безопасно говоря” (@yndxcloudsecurity), 666 subscribers as measured 6 August 2026. Telegram Register, tgregister.com/channel/yndxcloudsecurity.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.