Channel
@pdn1ru
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
215subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002674453948 |
|---|---|
| Type | Channel |
| Username | @pdn1ru |
| Description | Обучение от Ex.DPO/DSO OK.RU (VK) по защите ПДн (152-ФЗ) для DPO и ИТ-юристов. Все об аудитах ИСПДн, КИИ, ГИС, PCI DSS, GDPR, ISO 27001, AICPA SOC2, CCSS Контакты: @Alexander_Tsakharias, tsakharias@yandex.ru Чат: https://t.me/+TgX3-cE1Hp5lNGEy |
| Created | Between 1 March 2025 and 31 July 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/pdn1ru |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 10:47 | 215 | no change |
| 7 Aug 2026, 17:23 | 215 | first reading |
16 posts held, back to 13 December 2025 — 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 pageof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 2 August 2026 |
|---|---|
| Posts held | 16 (13 December 2025 – 2 August 2026) |
| Views total | 72 |
| Reactions total | 9 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 10:47 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.
Lifetime counters from Telegram’s own channel header, read 8 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.
52 reactions across 10 posts, in 3 distinct kinds. The most used accounts for 80.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 👍 | 42 | 80.8% | |
| 🔥 | 6 | 11.5% | |
| ❤ | 4 | 7.69% |
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 10 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 52reactions 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 13 December 2025 to 2 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.
Будущее ИБ в надежных руках 🛡💻 Вчера входил в жюри БАУМАНТЕХ и оценивал проекты второй смены по информационной безопасности для ребят из БАУМАНТЕХ.ДЕТИ. Удивительно, как за короткий интенсив подростки успевают примерить на себя роль настоящих специалистов по кибербезу. Буквально за одну неделю каждая команда разработала свой ИБ-продукт. Горжусь, что могу участвовать в таком проекте и видеть, как растет крутая сме…
🔥6👍3
🛠 Запускаю бесплатный практикум по аудиту ИСПДн Качество аудита ИСПДн решается не на этапе отчета, а на этапе сбора информации (обследования). Если обследование проведено бессистемно, это неизбежно проявится в отчете: неполное покрытие компонентов, слепые зоны в рисках и выводы, построенные на ощущениях, а не на фактах. Поэтому я сделал универсальный опросник для аудита ИС (goGRC), который использую в каждом своем п…
👍12❤3
продолжение... 2. С другой стороны, если что-то не проверишь, сразу как-будто бы попадаешь под нарушение. 1. Закон не требует «проверить все» - ни 152-ФЗ, ни ISO 27001. Меры защиты выбираются по рискам: если риск низкий и это задокументировано - отсутствие глубокой проверки не нарушение. 2. Регулятор смотрит на систему, а не на идеал. Достаточно базового набора мер и документированного процесса управления (реестры, …
Евгения, добрый день! 1. Поделитесь, пожалуйста, практикой разработки положения о внутреннем контроле и (или) аудите соответствия обработки персональных данных Федеральному закону № 152-ФЗ. Может, кто-то уже решил для себя, как будет корректней. Проанализировала имеющиеся в открытом доступе примеры положений о контроле, и в отдельных содержится примерный перечень вопросов, подлежащих контролю. Во-первых, положения (…
ПД№1: школа персональных данных № 1 pinned «‼️ Резервный (да кого я обманываю, скорее всего - основной) канал в MAX: https://max.ru/join/mV0Lat0-2dolbbgRO7PFROurmtHyrXzJOHkabB0hWfk Пока буду постить в оба канала, а там посмотрим.»
‼️ Резервный (да кого я обманываю, скорее всего - основной) канал в MAX: https://max.ru/join/mV0Lat0-2dolbbgRO7PFROurmtHyrXzJOHkabB0hWfk Пока буду постить в оба канала, а там посмотрим.
📝 Обзор изменений ПП № 171 (Разработка и производство СЗИ): Было vs Стало Для разработчиков средств защиты конфиденциальной информации (СЗИ) изменения вносятся в ПП № 171. Здесь регулятор сделал упор на количество программистов в штате и обязательные процессы безопасной разработки. 👥 1. Кадровый состав (Общий штат: руководитель + инженеры) Требования к штату теперь зависят от того, создаете ли вы «железо» или програ…
👍3
📝 Обзор изменений ПП № 79 (ТЗКИ): Было vs Стало Опубликован проект изменений в ПП № 79 о лицензировании технической защиты. Основной акцент — на радикальном увеличении штата. 👥 1. Кадровый состав (Общий штат: руководитель + инженеры) Главное изменение — отказ от единого требования в «3 человека» для всех. Теперь штат зависит от сложности работ: Проектирование, монтаж и ремонт (пп. а, б, д, е): Было: 3 человека (1 ру…
👍5❤1
Channel photo updated
Postmortem: Попадание секретного токена в централизованные логи 1. Краткое резюме В ходе проверки журналов событий (логов) было обнаружено, что секретный токен доступа к системе автоматизации (Jenkins) был передан небезопасным способом и, как следствие, оказался в централизованной системе логирования. Инцидент не привел к подтвержденному взлому, однако: ⇢ токен считается скомпрометированным; ⇢ был выявлен системный …
👍4
Channel photo updated
✅ УКФ.4 – Документирование информации (данных) об изменениях в конфигурации информационной системы и системы защиты персональных данных (Приказ ФСТЭК № 21) Требование обязывает фиксировать все изменения конфигурации ИС и СЗПДн, обеспечивая полноту и прослеживаемость действий, влияющих на безопасность персональных данных. 🗂 Примечания по применимости Требование распространяется на: ⇢ изменения конфигураций серверов, …
👍3
Showing the 12 most recent of 16 posts we hold for @pdn1ru. 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.
Citation-graph rank — 478,684 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
Named by 1 registered channel — 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.
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 8 August 2026 — this entry's latest reading, not the date you are reading this.
“ПД№1: школа персональных данных № 1” (@pdn1ru), 215 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/pdn1ru.
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.