Погружение в мир корпоративной кибербезопасности и ИИ
🗓 Анонсы событий
🧠 Экспертные материалы
Обсудить 👉🏼 https://t.me/codeibcommunity
Купить рекламу: @Leonova_Anne
Узнать про программы в Код ИБ АКАДЕМИИ: https://codeib.academy
Created
10 July 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
Technology — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 12 September 2026 and assigned it the closest of 31 fixed categories, at 62% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.
Growth
26 measurements spanning 96 days, net +210. 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 6,733–7,046 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 26
Measured (UTC)
Subscribers
Change
10 Nov 2026, 14:20
7,007
-3
6 Nov 2026, 17:49
7,010
+11
3 Nov 2026, 19:39
6,999
-1
1 Nov 2026, 01:49
7,000
+1
29 Oct 2026, 07:16
6,999
+3
25 Oct 2026, 20:19
6,996
+19
23 Oct 2026, 01:50
6,977
+35
20 Oct 2026, 03:27
6,942
+18
16 Oct 2026, 18:18
6,924
+33
13 Oct 2026, 13:31
6,891
+8
7 Oct 2026, 19:15
6,883
-3
1 Oct 2026, 10:36
6,886
+34
16 Sept 2026, 13:00
6,852
-7
13 Sept 2026, 00:41
6,859
+3
9 Sept 2026, 01:16
6,856
+81
3 Sept 2026, 09:34
6,775
+6
31 Aug 2026, 12:26
6,769
-3
28 Aug 2026, 01:54
6,772
-3
25 Aug 2026, 03:54
6,775
-1
22 Aug 2026, 00:23
6,776
first reading
Engagement
72 posts held, back to 22 July 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 26 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
8.64%
avg views ÷ 7,007 subscribers
Avg views / post
606
26 posts measured
Reaction rate
0.336%
reactions ÷ views · ER floor
Posts in window
26
of 72 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 15 of 26 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 10 November 2026
Posts held
72 (22 July 2026 – 10 November 2026)
Views total
15,746
Reactions total
36
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
10 Nov 2026, 17:25 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
≈1,750
Videos
≈119
Links
≈2,470
Lifetime counters from Telegram’s own channel header, read 10 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
Reaction mix
298 reactions across 52 posts, in 21 distinct kinds. The most used accounts for 27.5% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
🔥
82
27.5%
❤
75
25.2%
👍
33
11.1%
👎
31
10.4%
❤🔥
11
3.69%
⚡
9
3.02%
😁
9
3.02%
👌
6
2.01%
✍
5
1.68%
🎉
5
1.68%
👏
5
1.68%
💯
5
1.68%
🙏
5
1.68%
🤣
3
1.01%
🥰
3
1.01%
🦄
3
1.01%
🤝
2
0.671%
🤩
2
0.671%
🤯
2
0.671%
😇
1
0.336%
1 further kind
1
0.336%
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 55 of the 72 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 303 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 72 most recent posts we hold, published 22 July 2026 to 10 November 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.
Advertising
Ad load
9.72%
7 of 72 posts carry an ad marker
Regulatory tokens
7
posts carrying an erid · 7 distinct tokens
Median views · ads
455
over 7 measured posts
Median views · rest
476
over 65 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. They are printed side by side with the count behind each rather than as a ratio: an ad and an ordinary post are not otherwise matched — for topic, for length, for hour of day — so the gap between them is a description of two groups and not the effect of one being an ad.
Advertising tokens recorded on this entry
erid
Posts
First seen
Last seen
2SDnjdYBzcU
1
3 November 2026
3 November 2026
2W5zFG6RrCr
1
5 November 2026
5 November 2026
2W5zFHHpCzu
1
29 July 2026
29 July 2026
2W5zFHrMEqX
1
8 August 2026
8 August 2026
2W5zFJJCEkA
1
6 November 2026
6 November 2026
2W5zFK776Mw
1
26 October 2026
26 October 2026
2W5zFKA5jtV
1
26 October 2026
26 October 2026
A token repeated across several posts is one advertising contract placed more than once, which is what the identifier is for. The strings are reproduced exactly as they appeared in the post or in its click-through URL and are not validated against any registry — we record the marker a channel published, and whether it resolves to a real contract is a question for the register that issued it.
Measured over the 72 most recent posts we hold, published 22 July 2026 to 10 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Telegram’s own ‘edited’ marker: 10 of 26 posts held from the last 30 days (38.5%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
КиберДень
Слепые зоны в ИБ: как выявлять подозрительную активность и предотвращать риски
🗓 11 ноября в 12:00 (МСК)
➡️ Регистрация
Привилегии выданы. Пользователи работают. А вы точно знаете, что происходит в этот момент?
Когда речь идёт о доступе к критичным системам, одного контроля прав недостаточно. Важно видеть и фиксировать все действия привилегированных пользователей, находить отклонения в их поведении и реа…
БОЛЬШАЯ РАСПРОДАЖА В КОД ИБ АКАДЕМИИ
Один день. 4 программы. 10 отдельных модулей. 2 практикума по КИИ. 2 Код ИБ ПРОФИ.
Скидка 11% на всё!
Год заканчивается, и это лучший момент вложиться в главное — в себя.
В декабре обычно считают расходы и откладывают развитие «на январь». Но именно в конце года вложения в обучение дают самую большую отдачу: вы входите в новый год с новыми знаниями и новыми аргументами в разгов…
✅ Обнаружить уязвимость — не значит устранить ✅
Сканер выявил критичные CVE, отчёт передан ИТ-команде. Но между обнаружением уязвимости и её устранением могут пройти недели. Как сократить этот разрыв и выстроить эффективный процесс управления уязвимостями?
💾18 ноября в 11:00 МСК Крайон совместно с Колибри-АРМ проведёт вебинар «Уязвимости под контролем: от обнаружения до устранения».
В программе:
🟢 Актуальные тенде…
Удобные ответы про XDR
12 ноября в 11:00 «Лаборатория Касперского» проведёт стрим «Удобные ответы про XDR» для тех, кто строит комплексную киберзащиту бизнеса. В прямом эфире команда продукта покажет новые возможности единой платформы безопасности в решении Kaspersky Symphony XDR и поделится планами по его развитию.
А чтобы лучше подготовиться к стриму – смотрите одноименный видеопроект, в котором специальная поясн…
Коллеги, привет! Я Владислав Прокопович.
16 лет в ИТ, из них 14 — во главе ИТ. Был ИТ-директором Hilton по России, Беларуси и Казахстану (17 отелей, шесть открывал с нуля) и директором департамента ИТ курорта «Мрия» в Сбере. Сейчас — директор по цифровой трансформации Арлифта, а с октября ещё и заместитель генерального директора по ИБ в TS Solution. Параллельно веду НейроШтат — автоматизацию продаж и учёта для компа…
Код ИБ ИТОГИ в Москве: ИИ, защита данных и новые задачи кибербезопасности
🗓 3 декабря, начало в 9:30
📍 Palmira Business Club, Новоданиловская набережная, 6, корп. 2
Искусственный интеллект меняет бизнес-процессы, подходы к работе с данными и требования к информационной безопасности. Компании внедряют новые технологии, пересматривают архитектуру защиты и сталкиваются с вопросами, на которые пока нет универсальных от…
КиберДень
Слепые зоны в ИБ: как выявлять подозрительную активность и предотвращать риски
🗓 11 ноября в 12:00 (МСК)
➡️ Регистрация
Привилегии выданы. Пользователи работают. А вы точно знаете, что происходит в этот момент?
Когда речь идёт о доступе к критичным системам, одного контроля прав недостаточно. Важно видеть и фиксировать все действия привилегированных пользователей, находить отклонения в их поведении и реа…
SOC Forum 2026: как ИИ меняет работу SOC и информационной безопасности
28 октября в Москве завершился SOC Forum 2026. Второй день форума посвятили практическому применению ИИ в кибербезопасности: эксперты обсуждали автономные атаки, безопасную разработку, управление ИИ-агентами и новую архитектуру SOC.
Собрали главные тезисы дискуссий.
Как изменится работа CISO?
На «Большой сессии CISO» представители «Почты Росси…
AI как конвейер: как собирать надежные сервисы и автоматизации без штата программистов
🗓 5 ноября в 12:00 (МСК)
➡️ Регистрация
Многие уже пробовали использовать нейросети для рабочих задач, но часто результат разочаровывает: модель галлюцинирует, теряет контекст и выдает не то. Причина проста: к AI пытаются обращаться как к «волшебной таблетке», а не как к инженерной системе.
Качественный результат с нейросетями —…
SOC Forum 2026: почему бизнесу пора перестать запрещать ИИ и научиться управлять рисками
ИИ уже стал частью бизнес-процессов. Запреты не решают проблему: сотрудники продолжают пользоваться нейросетями, а компании теряют возможности для развития. Участники пресс-конференции «AI First или AI Worst? Как перейти от хаоса инноваций к управлению рисками ИИ» на SOC Forum обсудили, как выстроить безопасную среду для работы …
КиберДень
Слепые зоны в ИБ: как выявлять подозрительную активность и предотвращать риски
🗓 11 ноября в 12:00 (МСК)
➡️ Регистрация
Привилегии выданы. Пользователи работают. А вы точно знаете, что происходит в этот момент?
Когда речь идёт о доступе к критичным системам, одного контроля прав недостаточно. Важно видеть и фиксировать все действия привилегированных пользователей, находить отклонения в их поведении и реа…
AI как конвейер: как собирать надежные сервисы и автоматизации без штата программистов
🗓 5 ноября в 12:00 (МСК)
➡️ Регистрация
Многие уже пробовали использовать нейросети для рабочих задач, но часто результат разочаровывает: модель галлюцинирует, теряет контекст и выдает не то. Причина проста: к AI пытаются обращаться как к «волшебной таблетке», а не как к инженерной системе.
Качественный результат с нейросетями —…
Showing the 12 most recent of 72 posts we hold for @codeibnews. 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.
Posts edited after publishing
@codeibnews edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
First edit seen
20 August 2026
Most recent edit
10 November 2026
Forward network
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
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 5 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
Appears in Telegram’s recommendations for other channels
The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.
Листок бюрократической защиты информации @bureaucraticsecurity · 19,134 Telegram ranks this channel #18 of 98 here — alongside 97 others — read 4 October 2026
Об ЭП и УЦ @ep_uc · 21,400 Telegram ranks this channel #33 of 97 here — alongside 96 others — read 24 September 2026
Борьба с киберпреступностью | F6 @f6_cybersecurity · 22,363 Telegram ranks this channel #47 of 85 here — alongside 84 others — read 21 September 2026
Privacy Advocates @prv_adv · 21,855 Telegram ranks this channel #57 of 98 here — alongside 97 others — read 22 September 2026
Пост Лукацкого @alukatsky · 38,431 Telegram ranks this channel #58 of 89 here — alongside 88 others — read 31 August 2026
Kaspersky @kasperskylab_ru · 28,873 Telegram ranks this channel #59 of 96 here — alongside 95 others — read 9 September 2026
IT и безопасность @tg_security · 26,812 Telegram ranks this channel #71 of 91 here — alongside 90 others — read 12 September 2026
Positive Hack Days Media @positivehackmedia · 30,043 Telegram ranks this channel #72 of 88 here — alongside 87 others — read 6 September 2026
This channel appears in 8 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 10 November 2026 — this
entry's latest reading, not the date you are reading this.
“Код ИБ: ИИ & КиберБезопасность” (@codeibnews), 7,007 subscribers as measured 10 November 2026. Telegram Register, tgregister.com/channel/codeibnews.
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.