Telegram RegisterThe public register of Telegram

Channel

КИБЕРТЕСТ пароли

@e_cybersecurity

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

101subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001799652453
TypeChannel
Username@e_cybersecurity
DescriptionКомпании усиливаются: SIEM, PAM, AV... системы. А проблемы защиты доступов, паролей - в топе векторов кибер-атак. Здесь - новости компании КИБЕРТЕСТ, события сферы, инсайты, сравнения продуктов, советы. Узнал - защитился. Подписывайся! Добро пожаловать!
CreatedBetween 1 January 2022 and 31 December 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live9 August 2026
Measurements held2
On Telegramt.me/e_cybersecurity

Growth

1017 August 2026 — 101 subscribers9 August 2026 — 101 subscribers7 August 20269 August 2026
2 measurements spanning 2 days. 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 100–102 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
9 Aug 2026, 10:32101no change
7 Aug 2026, 20:58101first reading

Engagement

11 posts held, back to 10 December 2025the 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
32.7%
avg views ÷ 101 subscribers
Avg views / post
33.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 11 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 4 August 2026
Posts held11 (10 December 20254 August 2026)
Views total33
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken9 Aug 2026, 10:32 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
79
Videos
11
Links
94

Lifetime counters from Telegram’s own channel header, read 9 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.

Video runtime
14s
Average length
14s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

7 reactions across 3 posts, in 3 distinct kinds. The most used accounts for 42.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍342.9%
228.6%
😁228.6%

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 3 of the 11 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 7reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 11 most recent posts we hold, published 10 December 2025 to 4 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

4 Aug 2026, 12:59 UTC33 viewsread 9 August 2026

Отклик от одного из потенциальных заказчиков по итогу ознакомления с описанием Продукта: Ознакомились с кратким содержанием продукта. Мы в работе опираемся на то, что любой пароль может быть скомпрометирован (уже или через какое-то время) и выстраиваем процессы исходя из этого, с применением PAM, MFA, обучения, выявления аномалий, также проверяем базы утечек для УЗ в наших доменах/системах и т.д. и т.п. Ваше ре

Signed Dmitry.Ru ⌛️

7 May 2026, 06:12 UTC101 views2 reactionsread 9 August 2026
Photo

28 апреля прошел CISO-форум. Он собрал 1800 участников из 1000 компаний - топ-менеджеры банков, ритейл, промышленность, ИТ-корпорации, телеком. Форум - площадка для прямого диалога с CISO, CIO, архитекторами ИБ и бизнес-лидерами. Сбер, VK, Т-Банк, Wildberries, Мос. биржа, Ozon, Билайн, Яндекс и др. Особенно ценно живое профессиональное общение: участие КИБЕРТЕСТ в CISO FORUM 2026 стало временем диалога, обмена опыт

👍2

Signed Dmitry.Ru ⌛️

21 Apr 2026, 15:36 UTC102 viewsread 9 August 2026
Forwarded from @nikolay_khl

Vercel (очень популярная IT-инфраструктурная компания, оценка под 10 миллиардов долларов) подверглась кибер-атаке, вектор оказался неожиданным: AI-ассистент, которого сотрудник подключил через OAuth к своему рабочему Google Workspace. Ни хитрые уязвимости в ПО, ни вирусы, ни фишинг тут ни при чём. Хакеры на BreachForums уже выставили дамп исходников и переменных окружения на продажу за $2 миллиона. Механика такая: A

Signed Dmitry.Ru ⌛️

2 Mar 2026, 15:07 UTC118 views2 reactionsread 9 August 2026
Photo

Эстония, как обычно, немного запаздывает ))))

😁2

Signed Dmitry.Ru ⌛️

28 Feb 2026, 08:32 UTC117 viewsread 9 August 2026

Создали канал в МАКСе. Добро пожаловать!

Signed Dmitry.Ru ⌛️

26 Feb 2026, 14:00 UTC136 views3 reactionsread 9 August 2026

Сегодня добрался до сравнения нашего продукта с известным SpecOps. Это решение для управления идентификацией и доступом в AD, фокус на расширенных парольных политиках, самообслуживании пользователей (сброс/MFA) и защите Service Desk от соц. инженерии. SpecOps развивается в сторону усиления парольной политики и самостоятельного управления учетками - например, предупреждение о скорой просрочке пароля. Это, своего рода,

2👍1

Signed Dmitry.Ru ⌛️

26 Feb 2026, 13:01 UTCviews —

Channel name was changed to «КИБЕРТЕСТ инсайт - защити базовое»

25 Feb 2026, 20:25 UTC116 viewsread 9 August 2026
Forwarded from @portnyaginlivePhoto

Новости из мира ИИ за неделю Коротко по событиям, которые произошли за последнее время в мире искусственного интеллекта 1. ByteDance прикрутил фильтры к Seedance 2.0. После того как нейросеть научилась генерировать видео в стиле известных франшиз слишком хорошо, разработчикам прилетели письма с требованиями прекратить. Теперь защита стала жетсче 2. Meta запатентовала цифровое бессмертие. Технология позволяет ИИ об

Signed Dmitry.Ru ⌛️

19 Dec 2025, 19:55 UTC155 viewsread 9 August 2026

А что бы вы сказали, если бы был TG-бот, который защищал бы ваш аккаунт он несанкционированного доступа, даже если у вас выманили 6-значный код Telegram? Насколько для вас это актуально? Обычно те, кого уже взламывали, понимают, насколько это неудобно. А ещё именно так часто угоняют популярные tg-каналы.

Signed Dmitry.Ru ⌛️

10 Dec 2025, 04:22 UTC185 viewsread 9 August 2026
Forwarded from @F_S_C_P

🤯 Еще одна причина не доверять слепо ИИ. Data Poisoning меняет правила игры Старая пропаганда работала топорно — парадами и лозунгами. Мы привыкли, что пропаганда современное работает через «затопление» шумом (flooding) — ботофермы создают тысячи комментариев, чтобы заглушить правду шумом. Но иэта эпоха уходит. На смену приходит Data Poisoning (отравление данных). Злоумышленникам больше не нужно перекрикивать оппоне

Signed Dmitry.Ru ⌛️

Showing the 11 most recent of 11 posts we hold for @e_cybersecurity. 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.

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

Names

Channels on the register whose handles appear in this channel's posts.

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 9 August 2026 — this entry's latest reading, not the date you are reading this.

“КИБЕРТЕСТ пароли” (@e_cybersecurity), 101 subscribers as measured 9 August 2026. Telegram Register, tgregister.com/channel/e_cybersecurity.

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.