Telegram RegisterThe public register of Telegram
Telegram profile photo for CNsec

Channel

CNsec

@cnsec

On this record: Topic · Growth · Engagement · Posts · Cite this entry

145subscribers

-5 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001055424297
TypeChannel
Username@cnsec
CreatedBetween 1 May 2016 and 28 February 2017 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live7 November 2026
Measurements held9
Confirmed unchanged1 time, most recently 7 November 2026
On Telegramt.me/cnsec

Topic

Hacking & security — 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 25 September 2026 and assigned it the closest of 31 fixed categories, at 77% 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

145150147.55 August 2026 — 150 subscribers8 August 2026 — 150 subscribers14 August 2026 — 149 subscribers28 August 2026 — 150 subscribers3 September 2026 — 148 subscribers9 October 2026 — 146 subscribers15 October 2026 — 145 subscribers23 October 2026 — 146 subscribers7 November 2026 — 145 subscribers5 August 20267 November 2026
9 measurements spanning 93 days, net -5. 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 144–151 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
7 Nov 2026, 01:16145-1
23 Oct 2026, 03:40146+1
15 Oct 2026, 20:09145-1
9 Oct 2026, 16:37146-2
3 Sept 2026, 21:35148-2
28 Aug 2026, 03:26150+1
14 Aug 2026, 10:35149-1
8 Aug 2026, 19:47150no change
5 Aug 2026, 23:39150first reading

Engagement

20 posts held, back to 4 March 2020 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 20 posts for this entry, the most recent from 2 March 2022. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Mar 2022, 10:59 UTC593 viewsread 8 August 2026

Трифонов: Мы предлагаем бесплатно для пострадавших компаний свои средства защиты АСУ ТП на достаточно большой срок бесплатно и с бесплатной консультацией. #ИБКВО From @CnSec

Signed IFTTT

2 Mar 2022, 08:59 UTC586 viewsread 8 August 2026

Кубарев: По документам назначено два администратора одного средства антивирусной защиты и каждый считает себя единственным. Такого быть не должно. #ИБКВО #ФСТЭК From @CnSec

Signed IFTTT

2 Mar 2022, 08:59 UTC585 viewsread 8 August 2026

Кубарев: Бывает так: значимый объект упакован по полной - есть все СОВы и NGFW, но пользоваться ими ни кто не умеет. #ИБКВО From @CnSec

Signed IFTTT

2 Mar 2022, 08:59 UTC577 viewsread 8 August 2026

Кубарев: В текущей обстановке актуальные сведения по объектам КИИ в реестре очень важны и для нас, и для коллег из НКЦКИ. #ИБКВО #ФСТЭК From @CnSec

Signed IFTTT

2 Mar 2022, 08:59 UTC545 viewsread 8 August 2026

Кубарев: Спешу предупредить: подготовка и сбор штрафов в компетенцию ФСТЭК не входит. Наша задача - разработка рекомендаций по организации защиты. #ИБКВО #ФСТЭК From @CnSec

Signed IFTTT

2 Mar 2022, 08:59 UTC627 viewsread 8 August 2026

Кубарев: Рекомендации ФСТЭК в текущей ситуации: исключить автоматическое обновление, выявить точки возможного проникновения (ТВП), ограничить доступ к ИИ через ТВП, анализ уязвимостей ТВП, устранение критических уязвимостей ТВП. #ИБКВО From @CnSec

Signed IFTTT

2 Mar 2022, 07:59 UTC403 viewsread 8 August 2026

Кубарев: Как обстановка? А, не переживайте можете не отвечать - я и так знаю. #ИБКВО From @CnSec

Signed IFTTT

2 Mar 2022, 07:59 UTC390 viewsread 8 August 2026

Новиков: Многие руководители считают, что выбор объектов КИИ отдан на откуп им, но это не значит, что можно взять и ручкой вычеркнуть объект из перечня. #ИБКВО From @CnSec

Signed IFTTT

2 Mar 2022, 07:59 UTC345 viewsread 8 August 2026

Гаврилов: В 25 году новые технологии могут сокрушить оборону всех объектов и спровоцировать глобальную киберпандемию, считают эксперты Всемирного экономического форума. #ИБКВО From @CnSec

Signed IFTTT

3 Feb 2022, 14:59 UTC397 viewsread 8 August 2026

Торбенко: Госконтроль вас не задушит. Обещаю! #infoforum From @CnSec

Signed IFTTT

3 Feb 2022, 13:59 UTC773 viewsread 8 August 2026

Раевский: Цели атак злоумышленников: первое - госорганы, второе - промышленные предприятия, третье - хищение информации. Активность по всем 13 отраслям примерно одинакова. #infoforum From @CnSec

Signed IFTTT

3 Feb 2022, 07:59 UTC354 viewsread 8 August 2026

Хинштейн: Не всегда иностранный бизнес понимает доброе слово, поэтому были придуманы законы о цифровом суверенитете. #Infoforum From @CnSec

Signed IFTTT

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

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

“CNsec” (@cnsec), 145 subscribers as measured 7 November 2026. Telegram Register, tgregister.com/channel/cnsec.

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.