Telegram RegisterThe public register of Telegram

Channel

Sophos Firewall

@Sophos_Firewall

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

1,841subscribers

+7 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-1001100358025
TypeChannel
Username@Sophos_Firewall
CreatedBetween 1 January 2017 and 31 January 2018— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live13 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 13 August 2026
On Telegramt.me/Sophos_Firewall

Growth

1,8341,8461,8406 August 2026 — 1,834 subscribers7 August 2026 — 1,834 subscribers10 August 2026 — 1,846 subscribers13 August 2026 — 1,841 subscribers1,8416 August 202613 August 2026
4 measurements spanning 6 days, net +7. 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,832–1,848 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Aug 2026, 08:061,841-5
10 Aug 2026, 00:031,846+12
7 Aug 2026, 09:061,834no change
6 Aug 2026, 21:151,834first reading

Engagement

20 posts held, back to 20 December 2024the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 2 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
64.6%
avg views ÷ 1,841 subscribers
Avg views / post
1,190
9 posts measured
Reaction rate
0.356%
reactions ÷ views · ER floor
Posts in window
10
of 20 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 8 of 9 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 August 2026
Posts held20 (20 December 20247 August 2026)
Views total10,711
Reactions total37
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken7 Aug 2026, 17:26 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.

Reaction mix

41 reactions across 11 posts, in 3 distinct kinds. The most used accounts for 53.7% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
2253.7%
👍1843.9%
🤔12.44%

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

Measured over the 20 most recent posts we hold, published 20 December 2024 to 7 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.

Recent posts

7 Aug 2026, 06:43 UTC224 views4 reactionsread 7 August 2026
Photo

4⃣ قسمت چهارم (پایانی) | چگونه بدون ارتقای سخت‌افزار، کارایی Sophos XGS را افزایش دهیم؟ ⭕آیا واقعاً لازم است از تمام ترافیک‌ها Log بگیریم؟ ⭕یکی از رایج‌ترین اشتباهات Adminهای و حتی شرکت‌های پشتیبانی کننده سوفوس در بسیاری از پیاده‌سازی‌های Sophos XGS، فعال بودن Logging برای تعداد زیادی از Firewall Ruleها است. ⭕ثبت لاگ برای عیب‌یابی و تحلیل رخدادهای امنیتی ضروری است، اما اگر برای تمام Ruleها و همه ترافیک‌ها فعال باشد،

👍31

Signed علی کیائی‌فر

6 Aug 2026, 07:47 UTC332 viewsread 7 August 2026

👥درخواست عضویت در گروه سوفوس 👥اگر از فایروال‌های سوفوس استفاده می‌کنید میتونید از طریق لینک زیر در گروه پرسش و پاسخ فایروالهای سوفوس عضو بشید: https://t.me/+Uxr1XK9fiiNiNjQ0 لینک به مدت ۳ روز فعال است.

Signed علی کیائی‌فر

6 Aug 2026, 06:50 UTC359 views10 reactionsread 7 August 2026
Photo

3⃣ قسمت سوم | چگونه بدون ارتقای سخت‌افزار، کارایی Sophos XGS را افزایش دهیم؟ ⭕آیا ترتیب Firewall Ruleها واقعاً روی عملکرد فایروال تأثیر دارد؟ پاسخ: قطعا بله! ⭕یکی از مواردی که معمولاً در شبکه‌های بزرگ نادیده گرفته می‌شود، چیدمان Firewall Ruleها است. فایروال Sophos قوانین را از بالا به پایین بررسی می‌کند و به محض اینکه یک Rule با ترافیک مطابقت داشته باشد، پردازش متوقف می‌شود. حالا تصور کنید: ⭕اگر پرترافیک‌ترین Rule ش

👍81🤔1

Signed علی کیائی‌فر

5 Aug 2026, 08:55 UTC418 views4 reactionsread 7 August 2026
Photo

2⃣ قسمت دوم | چگونه بدون ارتقای سخت‌افزار، کارایی Sophos XGS را افزایش دهیم؟ آیا واقعاً لازم است تمام ترافیک HTTPS را بازرسی کنیم؟ ⭕امروزه بیش از ۹۰٪ ترافیک اینترنت با TLS/SSL رمزگذاری شده است. به همین دلیل، قابلیت TLS Inspection یکی از مهم‌ترین ابزارهای Sophos XGS برای شناسایی تهدیدات پنهان در ترافیک رمزگذاری‌شده است. اما یک اشتباه رایج وجود دارد... ⭕بعضی مدیران شبکه، TLS Inspection را برای تمام کاربران، تمام وب‌سای

3👍1

Signed علی کیائی‌فر

4 Aug 2026, 07:23 UTC868 views6 reactionsread 7 August 2026
Photo

1⃣ قسمت اول | چگونه بدون ارتقای سخت‌افزار، کارایی Sophos XGS را افزایش دهیم؟ ⭕یکی از رایج‌ترین اشتباهات در پیاده‌سازی Sophos Firewall این است که برای همه ترافیک‌ها، یک IPS Policy یکسان در نظر گرفته می‌شود. در بسیاری از شبکه‌ها، مشاهده می‌شود که پروفایل‌هایی مانند Maximum Protection روی تمام Firewall Ruleها اعمال شده‌اند؛ در حالی که همه ترافیک‌ها به این سطح از بازرسی نیاز ندارند. نتیجه چیست؟ 🔴افزایش مصرف CPU 🔴کاهش Thr

3👍3

Signed علی کیائی‌فر

4 Aug 2026, 06:48 UTC≈3,240 views2 reactionsread 7 August 2026
Photo

🔜 چطور بدون ارتقای سخت‌افزار، کارایی Sophos XGS را به‌طور محسوسی افزایش دهیم؟ 🟥یکی از رایج‌ترین اتفاقاتی که در سازمان‌ها مشاهده می‌کنیم این است که با افزایش ترافیک یا فعال شدن قابلیت‌های امنیتی، مدیران شبکه تصور می‌کنند تنها راه‌حل حفظ Performance ، خرید یک فایروال قدرتمندتر است. 🟥اما در بسیاری از پروژه‌های واقعی، قبل از صرف هزینه برای ارتقای سخت‌افزار، تنها با بهینه‌سازی تنظیمات Sophos XGS توانسته‌ایم: ✅ مصرف CPU ر

2

Signed علی کیائی‌فر

3 Aug 2026, 13:04 UTC534 views3 reactionsread 7 August 2026
Photo

🔑 قابلیت DNS Protection در سوفوس؛ متوقف کردن حمله قبل از برقراری ارتباط! ◀️یکی از قابلیت‌های کمتر شناخته‌شده اما بسیار قدرتمند فایروالهای Sophos XGS، حفاظت هوشمند از DNS است. ◀️ تقریباً تمام بدافزارها، باج‌افزارها و تروجان‌ها قبل از هر اقدامی باید با یک دامنه اینترنتی ارتباط برقرار کنند. فایروال سوفوس درخواست‌های DNS برای برقراری ارتباط با دامنه های مخرب (Malicious Domains) را مسدود می‌کند. این کار منجر به مسدودسازی

2👍1

Signed علی کیائی‌فر

3 Aug 2026, 05:50 UTC606 views3 reactionsread 7 August 2026
Photo

🆕قابلیت جدید Sophos XGS؛ کنترل ارتباطات رمزنگاری‌شده Post-Quantum ⚫️سوفوس در نسخه SFOS 22.0 MR2 قابلیت جدیدی را به فایروال‌های Sophos XGS اضافه کرده است که می‌تواند استفاده از الگوریتم‌های رمزنگاری Post-Quantum Cryptography (PQC) را شناسایی و مدیریت کند که شامل موارد زیر میشود: ✅ شناسایی و مسدودسازی الگوریتم‌های ML-KEM و سایر مکانیزم‌های تبادل کلید Post-Quantum در لایه IPS ✅ جلوگیری از برقراری نشست‌های وب با الگوریتم

2👍1

Signed علی کیائی‌فر

3 Aug 2026, 00:06 UTC≈4,130 views5 reactionsread 7 August 2026
Photo

🔓 آیا SSL Inspection در Sophos XGS را فعال کرده‌اید؟ یا فقط تصور می‌کنید شبکه‌تان امن است؟ 😄امروزه بیش از ۹۵ درصد ترافیک اینترنت به‌صورت رمزنگاری‌شده (HTTPS/TLS) تبادل می‌شود. این یعنی اگر Firewall فقط هدرهای رمزنگاری نشده را پالایش کند، بخش بزرگی از محتوای واقعی ترافیک برای آن قابل بررسی نخواهد بود. در نتیجه: ☠️ فایل‌های آلوده از طریق HTTPS دانلود می‌شوند. ☠️ کاربران وارد وب‌سایت‌های فیشینگ می‌شوند. ☠️ بدافزارها با

4👍1

Signed علی کیائی‌فر

15 Jun 2026, 09:35 UTC≈1,140 views2 reactionsread 7 August 2026

نکته مهم درباره Third-Party Threat Feeds در Sophos Firewall: در هر Feed محدودیتی برای تعداد IOCها وجود ندارد. اما ظرفیت کلی ذخیره‌سازی Threat Feedها محدود است. این ظرفیت بین IP، Domain و URL مشترک است. یعنی اگر یک Feed بزرگ کل ظرفیت را مصرف کند، فضای دیگری برای IOCهای دیگر باقی نمی‌ماند. ظرفیت تقریبی: XGS 87/88/107/116 و همه Virtual/Cloud: IPv4: 180K | Domain: 98K | URL: 18K XGS 126/118: IPv4: 270K | Domain: 140

2

Signed Hesam

23 May 2026, 08:26 UTC≈1,400 views1 reactionsread 7 August 2026
Photo

در مورد قابلیت Third-Party Threat Feeds در Sophos Firewall چیزی شنیده‌اید؟ یکی از قابلیت های جالب در نسخه های جدید فایروال سوفوس، امکان استفاده Threat Feeds خارجی جهت اعمال خودکار پالیسی های امنیتی می باشد. فرض کنید یک مرکز Threat Intelligence لیستی از IP های مخرب، دامنه ها یا URL های آلوده منتشر می کند. راه معمول این است که این موارد به‌صورت دستی به فایروال اضافه شوند. اما اگر این لیست هر روز تغییر کند، شما هم باید

1

Signed Hesam

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

Citation-graph rank — 131,786 of 1,340,412entries 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.

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 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.

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

“Sophos Firewall” (@Sophos_Firewall), 1,841 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/Sophos_Firewall.

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.