Telegram RegisterThe public register of Telegram

Channel

Избранное про ИБ

@sergeyborisov23

On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

1,094subscribers

+3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1001145054972
TypeChannel
Username@sergeyborisov23
CreatedBetween 1 May 2017 and 31 July 2020— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 August 2026
Measurements held3
Confirmed unchanged2 times, most recently 15 August 2026
On Telegramt.me/sergeyborisov23

Growth

1,0911,0941,092.56 August 2026 — 1,091 subscribers6 August 2026 — 1,092 subscribers12 August 2026 — 1,094 subscribers6 August 202612 August 2026
3 measurements spanning 6 days, net +3. 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 1,091–1,094 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 07:541,094+2
6 Aug 2026, 15:451,092+1
6 Aug 2026, 13:161,091first reading

Engagement

16 posts held, back to 19 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.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 16 posts for this entry, the most recent from 29 June 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

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

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
735.0%
👍735.0%
🔥630.0%

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

Measured over the 16 most recent posts we hold, published 19 December 2025 to 29 June 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.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 16 we hold a reading for · 6%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @sergeyborisov23. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 16 most recent posts we hold for this entry, published 19 December 2025 to 29 June 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

24 Jun 2026, 08:47 UTC393 viewsread 6 August 2026
Forwarded from @MetaSecurityInformationFile

Telegram | MAX | ВКонтакте

24 Jun 2026, 07:35 UTC335 viewsread 6 August 2026
Forwarded from @FrontSecOpsPhoto

Почему композиционный анализ (SCA) не гарантирует отсутствие вредоносного кода в frontend-приложении? В прошлый раз мы обсуждали, почему SAST не может обнаружить вредоносный код в frontend-приложениях. Сегодня рассмотрим SCA. 1️⃣ Современные js-фреймворки 📱 используют пакетный менеджер (npm). Все зависимости при билде упаковываются в файл-бандл (app.js, main.js и т.п.). Этот бандл подключается на веб-страницу в вид

30 Mar 2026, 05:32 UTC634 viewsread 6 August 2026
Forwarded from @devsecops_weeklyFile

Безопасное использование пакетных менеджеров Всем привет! В марте 2026 года ENISA выпустила руководство «Technical Advisory for Secure Use of Package Managers», (~ 28 страниц), которое можно найти в приложении. В нём приводятся практики, позволяющие повысить уровень информационной безопасности при работе с пакетными менеджерами. Материал структурирован по разделам: 🍭 Solution architecture and data flows. Общее оп

10 Feb 2026, 06:28 UTC705 viewsread 6 August 2026
Forwarded from @AISecHubPhoto

OWASP Vendor Evaluation Criteria for AI Red Teaming Providers & Tooling v1.0 https://genai.owasp.org/resource/owasp-vendor-evaluation-criteria-for-ai-red-teaming-providers-tooling-v1-0/

8 Feb 2026, 05:05 UTC642 viewsread 6 August 2026
Forwarded from @alexredsecPhoto

На портале Open Group можно найти набор стандартов "Security Roles and Glossary", призванный помочь построить зрелую системы кибербезопасности, основываясь на том, что кибербезопасность — это фундаментальный бизнес-риск, а каждый сотрудник, от топ-менеджера до рядового специалиста, должен понимать свою роль в защите компании. Набор состоит из четырех частей: 1️⃣В первом стандарте описана структура документов и приве

2 Feb 2026, 06:21 UTC585 views3 reactions1 Starread 6 August 2026
Forwarded from @k8securityPhoto

Wiz представила SITF (SDLC Infrastructure Threat Framework) — первую в мире открытую модель угроз, специально ориентированную на защиту инфраструктуры жизненного цикла разработки программного обеспечения. Эта инфраструктура (IDE, VCS, CI/CD, Registry) становится привлекательной целью для атак не только на код, но и на сами процессы сборки и доставки ПО. SITF предлагает визуализатор потоков атак, библиотеку из более

🔥2👍1

15 Jan 2026, 08:53 UTC673 views4 reactionsread 6 August 2026
Forwarded from @DevSecOps_Assessment_Framework

Предновогодний релиз DAF! С наступающим новым годом, друзья! Все подводят итоги года, а мы запрыгиваем в последний вагон трудовых будней 2025 года с очередным релизом DAF! Первая часть релиза (что добавилось и изменилось): 1. Актуализировали маппинг на ГОСТ 56939-2024 2. Добавили автомаппинг на BSIMM. Теперь проводя аудит по DAF можно сразу же получать результат относительно 5 фреймворков - ГОСТ 56939, DSOMM, SAMM,

🔥21👍1

15 Jan 2026, 08:52 UTC487 views2 reactionsread 6 August 2026
Forwarded from @devsecops_weeklyFile

Новая редакция Профиля Защиты от ЦБ РФ Всем привет! Банк России опубликовал новую редакцию Профиля защиты приложений для финансовых организаций (в приложении). В обновленном документе исправлено большинство недочетов прошлого издания. Основной лейтмотив обновления - синхронизация Профиля защиты с ГОСТ Р 56939-2024. Наш обзор изменений Профиля защиты можно почитать здесь И этот пост закрывает наш рабочий 2025 го

👍1🔥1

15 Jan 2026, 08:51 UTC483 viewsread 6 August 2026
Forwarded from @devsecops_weekly

USVL: визуализация атак и моделей угроз Всем привет! Universal Security Visualization Library (USVL) – open-source проект, который генерирует схемы на основании предоставленной конфигурации. Он может «отрисовать»: 🍭 Attack Trees. Иерархические диаграммы сценария атаки 🍭 Attack Graph. Визуализация атаки с точки зрения сети 🍭 Threat Modelling. Диаграммы потоков данных, учитывающие анализ, реализованный с использован

29 Dec 2025, 05:11 UTC614 views3 reactionsread 6 August 2026
Forwarded from @k8securityPhoto

Одним из самых частых вопросов на протяжении последних 3-х лет, который мне задавали на моем тренинге, да и вообще на конференциях, после докладов, в кулуарах - это: "А есть отечественные аналоги Talos?" Этот вопрос и сейчас активно спрашивают, НО теперь на него можно положительно ответить! Проект ALT Orchestra (исходники) от ребят из Базальта, на базе Talos и в реестре Российского ПО. О проделанной работе, вкладе

2🔥1

26 Dec 2025, 09:35 UTC497 views5 reactionsread 6 August 2026
Forwarded from @alukatskyPhoto

ФСТЭК 🗂 активизировалась в части подготовки методических документов по различным аспектам кибербезопасности. За последнее время регулятор выпустил следующие документы (в отдельном разделе на сайте): ➡️ Рекомендации по базовой настройке регистрации событий безопасности (для Windows и Linux) ➡️ Рекомендации по настройке механизмов безопасности почтового сервера Microsoft Exchange Server от атак, связанных с подменой от

👍32

Showing the 12 most recent of 16 posts we hold for @sergeyborisov23. 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.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

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

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

“Избранное про ИБ” (@sergeyborisov23), 1,094 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/sergeyborisov23.

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.