🦅 Attack Surface Management in 2026: Why Point-in-Time Scans Can’t Keep Up With Cloud Sprawl 🦅 Cloud infrastructure now changes by the hour, yet many security teams still map their external attack surface once a quarter or once a year. That mismatch creates blind spots that can last for months. A developer spins up a test environment on a Tuesday, an engineer opens a storage bucket for a partner on Wednesday, …

Channel
🛡 Cybersecurity & Privacy 🛡 - News
@cibsecurity
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Telegram's recommendations · Cite this entry
28,261subscribers
+789 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
Register entry
| Telegram ID | -1001262650373 |
|---|---|
| Type | Channel |
| Username | @cibsecurity |
| Description | 🗞 The finest daily news on cybersecurity and privacy. 🔔 Daily releases. 💻 Is your online life secure? 📩 [email protected] |
| Created | 4 September 2018 — measured — cross-checked against a third-party dataset (TGDataset) |
| First recorded | 6 August 2026 |
| Last confirmed live | 25 September 2026 |
| Measurements held | 35 |
| Confirmed unchanged | 1 time, most recently 25 September 2026 |
| On Telegram | t.me/cibsecurity |
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 10 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 25 Sept 2026, 16:58 | 28,261 | +142 |
| 17 Sept 2026, 08:41 | 28,119 | +48 |
| 15 Sept 2026, 09:19 | 28,071 | +30 |
| 13 Sept 2026, 20:36 | 28,041 | +51 |
| 12 Sept 2026, 03:59 | 27,990 | +49 |
| 9 Sept 2026, 23:00 | 27,941 | +72 |
| 6 Sept 2026, 17:38 | 27,869 | +52 |
| 4 Sept 2026, 08:19 | 27,817 | +24 |
| 2 Sept 2026, 21:34 | 27,793 | +7 |
| 1 Sept 2026, 20:56 | 27,786 | +12 |
| 31 Aug 2026, 19:25 | 27,774 | +27 |
| 30 Aug 2026, 18:35 | 27,747 | +9 |
| 29 Aug 2026, 21:39 | 27,738 | +20 |
| 28 Aug 2026, 19:37 | 27,718 | +3 |
| 27 Aug 2026, 19:32 | 27,715 | +1 |
| 26 Aug 2026, 19:58 | 27,714 | +35 |
| 25 Aug 2026, 16:23 | 27,679 | +7 |
| 23 Aug 2026, 03:37 | 27,672 | +21 |
| 21 Aug 2026, 14:44 | 27,651 | +18 |
| 20 Aug 2026, 15:17 | 27,633 | first reading |
Engagement
429 posts held, back to 4 August 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 73 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 0.773%
- avg views ÷ 28,261 subscribers
- Avg views / post
- 219
- 148 posts measured
- Reaction rate
- 0.269%
- reactions ÷ views · ER floor
- Posts in window
- 148
- of 429 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 7 of 148 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 September 2026 |
|---|---|
| Posts held | 429 (4 August 2026 – 28 September 2026) |
| Views total | 32,352 |
| Reactions total | 7 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 29 Sept 2026, 23:43 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
- Links
- ≈90,900
Lifetime counters from Telegram’s own channel header, read 29 September 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
33 reactions across 26 posts, in 4 distinct kinds. The most used accounts for 69.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 23 | 69.7% | |
| 👍 | 6 | 18.2% | |
| 👏 | 2 | 6.06% | |
| 🔥 | 2 | 6.06% |
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 28 of the 429 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 33 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 429 most recent posts we hold, published 4 August 2026 to 28 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.
Recent posts
🌊 UnderDefense Launches MAXI Service Desk, Delivering Direct Native Support for Enterprise Security Teams 🌊 New capability embeds SOC analyst communication directly into the UnderDefense platform, replacing slow ticket queues with contextaware, auditready support Jacksonville, FL, September 18, 2026. UnderDefense, a cybersecurity company delivering Agentic AI SOC and Compliance AI to enterprise clients across the US…
❤1
📔 Citrix Patches Critical Zero Days Under Active Exploitation 📔 Citrix has confirmed exploitation of two critical zeroday RCE bugs. 📖 Read more. 🔗 Via "Infosecurity Magazine" ---------- 👁️ Seen on @cibsecurity
👍1
📔 MCP Is Creating Major Governance Gaps, Researchers Warn 📔 Ox Security found security shortcomings in analysis of over 15,000 MCP servers. 📖 Read more. 🔗 Via "Infosecurity Magazine" ---------- 👁️ Seen on @cibsecurity
📔 Deepfakes Are Becoming a Costly Reality for Businesses, Report Warns 📔 A quarter of victims of deepfake attacks have lost over 1m. CISOs worry that boardrooms dont understand the threat. 📖 Read more. 🔗 Via "Infosecurity Magazine" ---------- 👁️ Seen on @cibsecurity
📔 NVIDIA Launches Open Platform to Secure Autonomous AI Agents 📔 NVIDIA has launched a platform pairing runtime controls with hardware monitoring for AI agents. 📖 Read more. 🔗 Via "Infosecurity Magazine" ---------- 👁️ Seen on @cibsecurity
📔 Bitget Restarts Bitcoin Withdrawals Following $387.5m Wallet Breach 📔 Bitget has restarted Bitcoin withdrawals after a 387.5m breach of its hot and warm wallets. 📖 Read more. 🔗 Via "Infosecurity Magazine" ---------- 👁️ Seen on @cibsecurity
🚨 Exploitation of vulnerabilities affecting Citrix NetScaler ADC and Citrix NetScaler Gateway 🚨 The NCSC is urging UK organisations to promptly mitigate vulnerabilities affecting Citrix NetScaler ADC and Gateway, two of which are being actively exploited. 📖 Read more. 🔗 Via "UK NCSC" ---------- 👁️ Seen on @cibsecurity
🖋️ CISA Says Attackers Are Exploiting Two Critical Citrix NetScaler Flaws Globally 🖋️ The U.S. Cybersecurity and Infrastructure Security Agency CISA on Sunday added two critical Citrix NetScaler ADC and Gateway flaws to its Known Exploited Vulnerabilities KEV catalog, following reports of active exploitation. The vulnerabilities are listed below CVE202688771 CVSS score 9.5 An improper input validation vulnera…
🖋️ JADEPUFFER-Linked Attackers Used Compromised Service Principals to Delete Azure Resources 🖋️ The threat actor known as JADEPUFFER has been observed orchestrating destructive actions within a Microsoft Azure environment using compromised service principals. Microsoft, which is tracking the activity under the name Storm3168, has called it an evolution of the threat actor's tradecraft. The attack took place in earl…
🖋️ Carbonato Botnet Compromises Docker Hosts to Deploy Telegram-Controlled Hermes AI Agent 🖋️ Cybersecurity researchers have disclosed details of a new botnet malware called Carbonato that's targeting exposed Docker daemons to deploy an opensource artificial intelligence AI agent framework called Hermes Agent. "The implant installs the framework unchanged, then overwrites its SOUL.md persona file," ThreatDown said.…
🖋️ Webinar: How to Govern AI Agents, Reduce Excessive Access, and Control Shadow AI 🖋️ AI agents are moving into production faster than security teams can govern them. They are connecting to apps, handling data, calling APIs, and acting across business systemsoften without the same controls applied to human users. According to Oktas Global CISO Insights 2026 report, only 47 of CISOs are confident they can identify …
Showing the 12 most recent of 429 posts we hold for @cibsecurity. 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.
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 3 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.
Channels Telegram recommends alongside this one
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.
@ctinow · 38,690#1
@thehackernews · 164,155#2
@Cyber_Security_Channel · 56,644#3
@PentestingNews · 26,663#4
@thebugbountyhunter · 51,082#5
@IRCyberGuardians · 19,804#6
@vxunderground · 52,210#7
@information_security_channel · 11,521#8
@OffensiveTwitter · 21,041#9
@cloudandcybersecurity · 21,809#10
@Venari_By_BetterCyber · 5,131#11
@BlueTeamOps · 27,712#12
@secharvester · 9,988#13
@cybersecurity_outlook · 9,867#14
@VulnerabilityNews · 5,391#15
@SeguInfoChannel · 9,055#16
@cKure · 7,089#17
@cybdetective · 27,360#18
@DarkfeedNews · 9,369#19
@RedPacketSecurity · 3,053#20
@noobtooscp · 22,787#21
@CyberThreatHunting · 7,118#22
@officialpwnsystem · 6,210#23
@Cyber_Defend · 7,892#24
@CyberSIRT · 3,746#25
@dailybountywriteup · 10,111#26
@DFIRHunting · 6,634#27
@APT_Notes · 16,685#28
@BlueTeamKit · 5,554#29
@RNetsec · 7,903#30
@Hide01 · 35,428#31
@fuzzinglabs · 3,419#32
@CSecurity_Expert · 1,382#33
@bugbounty_tech · 7,151#34
@AllSecurityEngineeringCourses · 19,250#35
@IT_Audit · 7,131#36
@LibrarySecOfficial · 9,382#37
@OsintLosena · 8,012#38
@linuxgram · 72,668#39
@cve_mitre_org · 1,306#40
@udemyrip · 68,291#41
@Infoseclearning · 12,999#42
@HackTheBox_Training · 6,676#43
@OsintManuelBot59 · 1,366#44
@learningnets · 30,505#45
@blueteam_soc_hacks · 2,539#46
@avleonovnews · 1,430#47
@pleyades_it · 5,220#48
@RedBlueTM · 21,371#49
@reverseame · 3,566#50
@cybersecuritycare · 13,250#51
@informationsecuritylife · 8,092#52
@ransomwarelive · 2,150#53
@CCNCERT · 6,782#54
@cybersecuritypulse · 6,884#55
@CyberSecurityJobs · 18,806#56
@hypersec · 4,514#57
@itseccompliance · 8,223#58
Read from Telegram’s recommendation API, most recently 10 September 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.
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.
@cloudandcybersecurity · 21,809
Telegram ranks this channel #1 of 62 here — alongside 61 others — read 22 September 2026
@Cyber_Security_Channel · 56,644
Telegram ranks this channel #2 of 71 here — alongside 70 others — read 23 August 2026
@thehackernews · 164,155
Telegram ranks this channel #5 of 58 here — alongside 57 others — read 13 August 2026
@ctinow · 38,690
Telegram ranks this channel #6 of 42 here — alongside 41 others — read 31 August 2026
@cyberdosti4c · 21,531
Telegram ranks this channel #7 of 60 here — alongside 59 others — read 23 September 2026
@PentestingNews · 26,663
Telegram ranks this channel #9 of 46 here — alongside 45 others — read 12 September 2026
@elearninglinks · 34,287
Telegram ranks this channel #10 of 31 here — alongside 30 others — read 3 September 2026
@OffensiveTwitter · 21,041
Telegram ranks this channel #14 of 53 here — alongside 52 others — read 25 September 2026
@BlueTeamOps · 27,712
Telegram ranks this channel #17 of 53 here — alongside 52 others — read 11 September 2026
@cybdetective · 27,360
Telegram ranks this channel #20 of 49 here — alongside 48 others — read 11 September 2026
@codelivly · 35,373
Telegram ranks this channel #22 of 41 here — alongside 40 others — read 8 September 2026
@thebugbountyhunter · 51,082
Telegram ranks this channel #24 of 60 here — alongside 59 others — read 25 August 2026
@linuxgram · 72,668
Telegram ranks this channel #30 of 90 here — alongside 89 others — read 19 August 2026
@Prelims_Upsc · 200,768
Telegram ranks this channel #54 of 58 here — alongside 57 others — read 11 August 2026
@seguridadinformatic4 · 29,172
Telegram ranks this channel #56 of 76 here — alongside 75 others — read 8 September 2026
This channel appears in 15 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 25 September 2026 — this entry's latest reading, not the date you are reading this.
“🛡 Cybersecurity & Privacy 🛡 - News” (@cibsecurity), 28,261 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/cibsecurity.
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.