Channel
@bureaucraticsecurity
On this record: Topic · Growth · Engagement · Reactions · Posts · Posts edited after publishing · Citations · Telegram's recommendations · Cite this entry
19,137subscribers
+224 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1001171743239 |
|---|---|
| Type | Channel |
| Username | @bureaucraticsecurity |
| Created | 2 July 2018 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 6 August 2026 |
| Last confirmed live | 31 October 2026 |
| Measurements held | 50 |
| Confirmed unchanged | 1 time, most recently 31 October 2026 |
| On Telegram | t.me/bureaucraticsecurity |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 61% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 31 Oct 2026, 19:39 | 19,137 | -1 |
| 29 Oct 2026, 21:49 | 19,138 | +3 |
| 28 Oct 2026, 23:59 | 19,135 | +10 |
| 26 Oct 2026, 22:29 | 19,125 | -2 |
| 25 Oct 2026, 23:11 | 19,127 | -8 |
| 25 Oct 2026, 01:00 | 19,135 | +1 |
| 23 Oct 2026, 22:45 | 19,134 | +6 |
| 22 Oct 2026, 21:28 | 19,128 | +5 |
| 21 Oct 2026, 15:36 | 19,123 | +4 |
| 20 Oct 2026, 14:19 | 19,119 | +5 |
| 18 Oct 2026, 12:31 | 19,114 | +1 |
| 17 Oct 2026, 13:36 | 19,113 | +12 |
| 16 Oct 2026, 11:06 | 19,101 | +3 |
| 15 Oct 2026, 13:40 | 19,098 | +6 |
| 14 Oct 2026, 13:40 | 19,092 | -3 |
| 13 Oct 2026, 01:00 | 19,095 | -5 |
| 8 Oct 2026, 17:38 | 19,100 | +7 |
| 4 Oct 2026, 04:59 | 19,093 | +3 |
| 25 Sept 2026, 12:57 | 19,090 | +15 |
| 19 Sept 2026, 00:41 | 19,075 | first reading |
35 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 55 pages 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 35 posts for this entry, the most recent from 2 September 2026. An engagement rate over an empty window would be a number about nothing.
723 reactions across 35 posts, in 33 distinct kinds. The most used accounts for 15.1% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🤡 | 109 | 15.1% | |
| 👍 | 98 | 13.6% | |
| ❤ | 77 | 10.7% | |
| 🔥 | 60 | 8.30% | |
| 🥴 | 57 | 7.88% | |
| 🤣 | 39 | 5.39% | |
| 🗿 | 33 | 4.56% | |
| 👎 | 31 | 4.29% | |
| 🤮 | 31 | 4.29% | |
| 🤔 | 30 | 4.15% | |
| 😱 | 29 | 4.01% | |
| ✍ | 25 | 3.46% | |
| 🤯 | 15 | 2.07% | |
| 😁 | 14 | 1.94% | |
| 😭 | 12 | 1.66% | |
| 🤨 | 11 | 1.52% | |
| 💩 | 9 | 1.24% | |
| 👏 | 6 | 0.83% | |
| 🥱 | 5 | 0.692% | |
| 🆒 | 4 | 0.553% | |
| 13 further kinds | 28 | 3.87% |
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 35 of the 35 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 723 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 35 most recent posts we hold, published 22 July 2026 to 2 September 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.
🔎 Отраслевой мониторинг за субъектами КИИ по линии Росатома ➤ Официально опубликован приказ Госкорпорации «Росатом» от 30.07.2026 № 1/21-НПА «Об определении организации, привлекаемой Государственной корпорацией по атомной энергии «Росатом» к оценке актуальности и достоверности сведений, указанных в пункте 17 Правил категорирования объектов критической информационной инфраструктуры Российской Федерации, утвержден…
❤1
📝 Справка-доклад о ходе работ по плану ТК 362 (по состоянию на 28.08.2026).
👍1
🛡 Требования о защите ГИС с использованием СКЗИ ➤ Официально опубликован приказ ФСБ России от 22.08.2026 № 321 «Об утверждении Требований о защите информации, содержащейся в государственных информационных системах, иных информационных системах государственных органов, государственных унитарных предприятий, государственных учреждений, а также при использовании технических средств и программ для электронных вычислит…
🤔11🤡7🤯4👍2😁2💩1
🏳️ О безопасности конфискации ОКИ ➤ Официально опубликован Указ Президента Российской Федерации от 24.08.2026 № 604 «О мерах по обеспечению безопасности объектов критической инфраструктуры Российской Федерации», который не про безопасность КИИ, но про безопасность ОКИ, которые частично представлены в схожих с КИИ областях. Указом предусматривается возможность передачи под внешнее государственное управление ОКИ, вл…
🤣28🗿20🤡9🔥7❤5🤨4🤬3👍1
Вращаем глобус. Куда отправляются в путешествие инфобезопасники В новом выпуске рубрики «Лайфстайл» ИБ-спецы рассказали о самых запоминающихся путешествиях и тревел-мечтах. В списке предпочтений: ▪️плавание на катере из Москвы в Санкт-Петербург ▪️джип-сафари в Абу-Даби ▪️мотопробег по США ▪️новостройки и лотосы Северной Кореи ▪️горный Алтай, Байкал, Япония, Антарктида и многое другое… Своими воспоминаниями и планам…
❤4👎2
📧 Изменения в 117-й приказ ФСТЭК ➤ Для общественного обсуждения представлен проект приказа ФСТЭК России «О внесении изменений в Требования о защите информации, содержащейся в государственных информационных системах, иных информационных системах государственных органов, государственных унитарных предприятий, государственных учреждений, утвержденные приказом Федеральной службы по техническому и экспортному контролю…
🤡28💩7🤮3👍2💔1🙏1
📣 Порядок взаимодействия гос операторов с ГосСОПКА ➤ Официально опубликован приказ ФСБ России от 06.08.2026 № 297 «Об утверждении Порядка взаимодействия операторов государственных информационных систем, иных информационных систем государственных органов, государственных унитарных предприятий, государственных учреждений с государственной системой обнаружения, предупреждения и ликвидации последствий компьютерных ата…
🔥4❤1
🛡 Требования о защите информации для провайдеров хостинга для ГИС и иных гос. ИС ➤ Официально опубликован приказ Минцифры от 31.07.2026 № 702 «Об утверждении требований о защите информации при предоставлении вычислительной мощности для размещения информации в информационной системе, постоянно подключенной к информационно-телекоммуникационной сети «Интернет», операторам государственных информационных систем, иных и…
😱7🤡3❤2
🔒 Панельная дискуссия «Новые правила игры. Что изменится для субъектов КИИ уже завтра» ➤ Требования к безопасности критической информационной инфраструктуры продолжают меняться. Для организаций это означает новые задачи, связанные с сертификацией, внедрением средств защиты и подготовкой к актуальным киберугрозам. На «ИнфоБЕРЕГ 2026» пройдет панельная дискуссия, в ходе которой участники разберут, что именно меняется…
👍5💯2🆒2⚡1❤1👌1
🎙 Вебинар «Оценка зрелости ИБ: неужели обязательно для всех?» ➤ ФСТЭК России подготовлена методика по оценке зрелости защиты информации. В ходе вебинара будут разбираться следующие темы: • Кому нужно проводить оценку зрелости. • Какими документами подтверждать зрелость по каждому направлению. • Как считается УЗИ и профиль зрелости. • И главное — почему красивый регламент - не значит высокую зрелость. Спикер: Анаст…
❤10👍5🤡4🔥3🆒2
📣 Требования к созданию гос ИС, но не ГИС ➤ Официально опубликовано постановление Правительства Российской Федерации от 13.08.2026 № 1007 «Об утверждении требований к порядку создания и эксплуатации государственными органами информационных систем, не являющихся государственными информационными системами».
🥴39😁6❤1
▶️ День открытых дверей «Итоги и практика в сфере персональных данных» ➤ Уважаемые читатели канала, напоминаю, что в 13.00 начнется трансляция дня открытых дверей Роскомнадзора «Итоги и практика в сфере персональных данных». Присоединиться к трансляции можно здесь.
👍6
Showing the 12 most recent of 35 posts we hold for @bureaucraticsecurity. 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.
@bureaucraticsecurity edited 2 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.
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
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.
Named by 2 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.
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.
Telegram’s own answer, not this register’s. When this register asks Telegram’s API what is similar to this channel, this is the list it returns, in the exact order Telegram returns it — never re-sorted by subscribers or by anything else this register measures. The relationship, and the order, are Telegram’s; we record them and date them, and make no claim of our own about which of these channels actually resemble this one.
Read from Telegram’s recommendation API, most recently 4 October 2026. Telegram holds a list like this for a small and growing share of the register — how this is measured, and why most channel pages show nothing here.
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.
This channel appears in 7 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 31 October 2026 — this entry's latest reading, not the date you are reading this.
“Листок бюрократической защиты информации” (@bureaucraticsecurity), 19,137 subscribers as measured 31 October 2026. Telegram Register, tgregister.com/channel/bureaucraticsecurity.
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.