Zedmos
Demo ve fiyatlandırma:info@zedmos.comDemo talep edin

OPNsense Eklentisi

OPNsense® için Zedmos yazılımı

Bir paket deposundan kurulur ve Servisler altında görünür. Ekibinizin zaten kullandığı arayüzün içinde dokuz sayfa — pano, cihazlar, canlı oturumlar, raporlar, politikalar, ayarlar, bildirimler, güncelleme ve destek.

OPNsense içindeki Zedmos panosu: motor ve aracı durumu, en çok görülen uygulamalar, cihazlar ve uzak sunucular.
OPNsense içinde Zedmos: panoOPNsense · os-zedmos

Zedmos makes OPNsense a next-generation firewall

The firewall you run today decides by address and port. Zedmos installs into it and decides by what the traffic actually is, who it belongs to, and what it is carrying — without replacing anything that already works.

Konsolda tek bir güvenlik duvarının canlı oturumlar görünümü: cihaz, protokol ve adres sütunlarıyla bir akış tablosu ve tehditler, engellemeler, TLS oturumları ve yapay zekâ etkinliği sekmeleri.
  1. Bu ne?

    Her akış, porta göre değil uygulamaya göre sınıflandırılmış — bağlantılar sekmesi, diğer her şeyin ham maddesidir.

  2. Kimin?

    Cihaz, kategorisi ve donanım adresi akışla aynı satırda; böylece bir politika bir adres yerine bir kişiyi ya da grubu adlandırabilir.

  3. Tehlikeli mi?

    Aynı güvenlik duvarı için tehditler, engellemeler ve virüs bulguları bir sekme uzakta — imzalar ve istihbarat, oturum iletilmeden önce uygulandı.

  4. Ne taşıyor?

    TLS oturumları ve yapay zekâ etkinliği: hangi hizmetlerin, kimler tarafından kullanıldığı ve içerik incelemesinin gönderilende ne bulduğu.

  5. Barındırdığınız konsolun içinde

    Müşteri, şube ve güvenlik duvarı en üstten seçilir. Aynı görünüm, hangi platformu çalıştırırsa çalıştırsın filodaki her güvenlik duvarı için vardır.

Buradaki her sütuna cihazda karar verildi. Karara varmak için hiçbir şey cihazdan çıkmadı.console.zedmos.com · Live Sessions

The capabilities it adds

Grouped by the question each one answers. The same set on OPNsense, on pfSense and on Zedmos NGFW — one engine, one policy model, three ways to run it. Each has a fuller technical write-up under Resources.

What is this traffic, really?

Recognises applications, not ports200+

Almost everything is HTTPS on 443, so a port-based rule can only permit or deny all of it.

TLS inspection, applied selectively

Bump what you choose to; leave banking and health traffic alone by rule.

Client fingerprinting

JA3, JA4 and ALPN identify the software behind a session even when it is not decrypted.

QUIC and HTTP/3

The protocol most of the web moved to, seen and controlled rather than left as a gap.

DNS over TLS and over HTTPS

Encrypted resolution routes around a classic firewall's name-based rules. Not around this one.

Live sessions, with the reason

Every flow on screen as it happens, carrying the decision and what drove it.

The application-control tab: a searchable catalogue of applications and categories, each with the action the policy takes on it.
Applications and categories are chosen from the classifier's own catalogue, not typed as ports.Zedmos · Policies · App Controls

Should it be allowed through?

Intrusion detection and prevention

Signatures evaluated inline on the same appliance — a match is a block, not a morning alert.

Threat intelligence, shipped daily26

Indicators gathered and cross-checked, then pushed to every firewall you manage.

Files scanned in flight

Attachments and downloads examined before they land, not after.

Sixteen things a rule can do16

Allow, log, rate-limit, quarantine, reset, drop — and the rest, on both platforms.

The intrusion detection and prevention tab: rule sources, the action taken on a match, and the severity threshold that governs it.
Detection and prevention are one setting per policy group, not a separate product bolted alongside.Zedmos · Policies · IDS/IPS

What are people typing into AI?

The shadow-AI inventory

Which assistants are in use and by whom — answered without reading a single prompt.

Prompts checked before they leave

Source code, credentials and regulated data caught on the way out, not in a breach report.

The verdict is reached on your premises

Deterministic matchers plus a local model. Sending content away to ask whether it may be sent is a contradiction.

Three postures, one engine

Watch and record; strip the sensitive part and redirect; or block outright. The rule's action verb is the only change.

Every assistant, including yours

ChatGPT, Claude, Gemini, Copilot, Perplexity, Mistral — and an in-house endpoint you declare yourself.

The DLP and AI gateway tab: the action taken on a match, the detection mode that routes the scoped applications to the gateway, and the gateway's connection settings with a local provider and endpoint.
Only the applications you scope reach the gateway, and the model that returns the verdict answers at an address on your own network.Zedmos · Policies · AI Gateway

Is an agent acting on its own?

Who is really at the keyboard

Browser, SDK or script, autonomous agent, MCP client, or none of these — every request is placed in a class before an action is chosen.

Classified from what it sends

The user agent, the shape of the request envelope and the address it is posted to — a raw API endpoint and a chat surface are told apart.

Tool calls are their own decision

A request carrying tool definitions, calls or results is what turns an assistant into something that acts. It can be allowed, recorded or refused on that ground alone.

Unsanctioned providers, reached by script

Programmatic access to a provider nobody approved is its own case, separate from someone opening the same site in a browser.

Marked, not silently dropped

Marking forwards the request and records it with a reason and a sensitivity class on the AI activity page — so a class can be watched for a week before anyone decides to block it.

The AI agents tab: an action for each client class — browser, SDK or script, autonomous agent, MCP client and unknown — with separate dispositions for requests carrying tool calls and for programmatic access to an unsanctioned provider.
A person typing into a chat window and a script driving the same provider are not the same event, and they no longer get the same answer.Zedmos · Policies · AI Agents

Is confidential data leaving?

Detectors you switch on deliberately61

Card numbers, secrets, health and financial data, and national identity formats for twenty-two countries.

Uploads and messages both

A file attached to a web form and a paragraph pasted into a chat are the same risk.

A block you can defend

The record names the rule, what was detected and where — without keeping the content itself.

Fail closed where it matters

A control that lets traffic past when it cannot evaluate it is not a control on the path that matters.

The data-loss tab: the detector library grouped by family, with a checksum marker on the ones that validate what they match.
Sixty-one detectors, switched on deliberately rather than all at once; a checksum keeps the false positives down.Zedmos · Policies · DLP

Who and what is on the network?

Devices are recognised — and assessed

A managed laptop and a personal phone share a subnet and look identical to an address rule. For an enrolled remote device, your own Intune or CrowdStrike says whether it is healthy.

Users and groups from your directory

Active Directory, Entra ID or SCIM — and, for a remote person, your own OpenID Connect provider at enrolment. An entitlement follows the person, not their DHCP lease.

Quarantine without cutting off

A device restricted to what it needs to be fixed is a device you can still fix.

Policy by zone and schedule

Different rules for a guest network, a server segment, and outside business hours.

The device inventory: what each device is, the category it was placed in, and the identity attached to it.
A policy can name a person or a device class here, and keep meaning the same thing after the address changes.Zedmos · Devices

Where should it go, and what happened?

Each flow out the right link

Scored on loss, latency and jitter — a link that is up and losing packets is not a healthy link.

Encrypted overlay between sites

WireGuard, OpenVPN or GRE in four shapes — one hub, a hub pair, direct tunnels between spokes, full mesh — provisioned from one topology view rather than hand-built per firewall.

Rules change without a restart

A policy edit takes effect without dropping a packet or interrupting a session.

A feed your SOC already reads

Reports and live sessions on screen, and CEF, LEEF or syslog over TLS to whatever you run.

The application-routing tab: which application or category leaves by which egress, with the fallback when that egress is down.
Egress is chosen per policy — a second WAN, a tunnel or a plain interface — and falls back on its own.Zedmos · Policies · Application Routing

Şu anda ne yayımlanıyor

Bu sayfaya elle yazılmak yerine paket depolarından alınır; böylece elle yazılmış bir sürüm dizesi gibi kaymaz.

Zedmos for OPNsenseEklenti, paket deposundan
26.10.1_101
Zedmos for pfSenseEklenti, paket deposundan
26.10.1_101
Zero Trust ConsoleKendi barındırdığınız, sizin kurduğunuz
1.3.0

Konsol ve güvenlik duvarı kendi takvimlerinde yayımlanır, bu yüzden numaraları birbirini izlemez. Güvenlik duvarlarınızın her birinin hangi sürümü çalıştırdığı konsolunuzdadır.

Inside OPNsense

Pano · 1 / 6

Inside OPNsense — Engine and service health, top threats, applications and devices — rendered inside the OPNsense interface your team already knows.

Engine and service health, top threats, applications and devices — rendered inside the OPNsense interface your team already knows.

Rafta hâlihazırda duran bir şeyi değiştirmek

Mevcut her üretici için bir sayfa; o üreticinin kendi belgelerinden ve kamuya açık kayıtlarından kurulmuş — lisanslama, yaşam döngüsü, yönetim, yargı yetkisi ve istismar geçmişi; her satır kaynağıyla.

Sorular ve yanıtlar

Zedmos eklentisi OPNsense'e ne ekler?

Derin inceleme ve uygulama denetimi, saldırı tespiti ve önleme, TLS incelemesi, veri sızıntısı önleme, bir yapay zekâ ağ geçidi, bağlantılar arasında uygulama başına yönlendirme ve merkezî yönetim; Servisler menüsü altında dokuz sayfa olarak: pano, cihazlar, canlı oturumlar, raporlar, politikalar, ayarlar, bildirimler, güncelleme ve destek.

Zedmos OPNsense'e nasıl kurulur?

Platformun kendi paket yöneticisiyle, bir paket deposundan. Kurulumdan sonra Servisler altında görünür ve ayarlar sayfasından kaldırılır.

Zedmos, OPNsense güvenlik duvarı kurallarımın yerini alır mı?

Hayır. Mevcut kurallar, arayüzler, NAT ve VPN'ler dokunulmadan kalır. Zedmos, onların yerini almak yerine üzerlerine inceleme ve politika ekler.

Zedmos, OPNsense için Zenarmor'a alternatif mi?

Zedmos, OPNsense için aynı ürün kategorisinde bir uygulama incelemesi ve IDS/IPS katmanıdır. Onu ayıran: tek kural tabanıyla tek motorda saldırı önleme ve uygulama incelemesi, kendiniz barındırabileceğiniz bir yönetim konsolu, lisansta donanım olmadan güvenlik duvarı başına lisanslama ve aynı motorun ZedmOS üzerinde eksiksiz bir güvenlik duvarı olarak da bulunması.

OPNsense ve pfSense güvenlik duvarları birlikte yönetilebilir mi?

Evet. OPNsense, pfSense CE ve Zedmos NGFW genelinde tek motor, tek politika modeli ve tek konsol. Karma bir filo bir kez öğrenilir ve aynı biçimde işletilir.

Demo ve fiyatlandırma: info@zedmos.com

Demo talep edin