Every event. One stream.
Collect syslog, CEF, LEEF and JSON over UDP, TCP, TLS, RELP and HTTP. Connect native Linux, Windows and macOS agents, distributed collectors and cloud sources.
Turn your event stream into a clear picture of threats.
Logs, behavior analytics and response
—
one platform, on your
infrastructure.
Syslog / RFC 3164 · 5424
FQL / SEARCH & ANALYTICS
Sigma / DETECTION
UEBA / BEHAVIOR
SOAR / RESPONSE
01 /THE COMPLETE PICTURE
From the first event to the full investigation.
FrySIEM
connects logs, users and assets
so you
can see the story behind every signal.
Collect what mattersNetworks, endpoints, clouds and applications.
Connect the dotsEvents, behavior and the context behind every entity.
Move from insight to actionInvestigations, playbooks and notifications.
02 /CAPABILITIES
Collect syslog, CEF, LEEF and JSON over UDP, TCP, TLS, RELP and HTTP. Connect native Linux, Windows and macOS agents, distributed collectors and cloud sources.
Parser packs, normalized fields and GeoIP / ASN enrichment turn raw messages into data you can investigate.
Search with FQL, build aggregations and drill down from the big picture to the individual event.
host:fw* and severity<=3
| stats
count() by src_ip
| sort -count
| limit 20
Correlation rules, Sigma imports and MITRE ATT&CK mapping. Test detections against history and keep alert noise under control.
UEBA learns how users and hosts normally behave. Anomalies, peer comparisons and risk scores bring unusual activity into focus.
Entity 360 connects users, hosts and addresses. Assign cases, track stages and deadlines, and preserve evidence throughout the investigation.
Playbooks connect enrichment, notifications and actions. Add human approval before blocking an address or changing an account.
Dashboards, maps, heatmaps and a report library. See the security overview, then explore the details of each source.
Tenant isolation, role-based access and audit trails. Connect your enterprise identity provider through LDAP, OIDC or SAML.
Embedded DuckDB or ClickHouse for larger volumes. A disk-backed WAL, retention policies and active-passive HA support resilient operations.
Find your deployment03 /AI INTEGRATION
Connect the assistant your analysts already use.
Keep an eye
on the AI
your company runs.
FrySIEM is an MCP server. Analysts ask what happened last night, who the riskiest users are or why an anomaly fired. The assistant answers from your events, incidents, cases, Entity 360, behavior analytics and reports, and drafts a triage or an entity summary with ready-made prompts.
Ready-made detections you can switch on: removed AWS Bedrock guardrails and invocation logging, unusual model access, local LLM tools and model downloads on endpoints, new AI agents and MCP connections in Notion.
On a consent screen the analyst grants read-only triage or analyst rights, never more than they have. Revoke at any time.
Without the reveal permission the assistant sees stable pseudonyms in behavior analytics, not names. Works council mode included.
Tool, arguments, duration and outcome of every call are logged, with rate limits and response caps per token.
FrySIEM needs no public endpoint and sends nothing out itself. Read-only by default; playbooks start as dry runs. Pick a local model to keep everything in-house.
Product names and logos are trademarks of their respective owners and are shown to indicate compatibility. Third-party AI detections are part of the extended rule packs and may need setup.
04 /FROM SIGNAL TO ACTION
One platform for the entire process.
Every next step carries
the context
of the one before it.
Bring in events from across your infrastructure and normalize their fields.
INGEST → NORMALIZECombine rules, behavior and context to identify the signals that matter.
CORRELATE → PRIORITIZEReconstruct the sequence of events and gather evidence in one place.
EXPLORE → INVESTIGATERun a playbook, notify the team and document the outcome.
RESPOND → DOCUMENT05 / DISTRIBUTED COLLECTION
Keep collection close to the source.
Bring visibility and
management together
across branches, data centers and cloud
environments.
Endpoints & network devices
Servers & applications
Cloud services & workloads
One control point for your distributed collection infrastructure.
Collect locallyBring remote sources into the platform through a nearby collector.
Manage centrallyKeep your collector infrastructure under one management center.
Investigate togetherFollow activity across sites from one security workspace.
Bring endpoint logs into the same workflow. Enroll agents, manage collection policies and monitor their health centrally.
Collect journald and file logs from your Linux servers.
NATIVE AGENTCollect Windows Event Logs and security events from your endpoints.
NATIVE AGENTBring Mac log sources into the same centrally managed fleet.
NATIVE AGENT06 /YOUR ECOSYSTEM
From firewalls and identity directories to cloud services and issue trackers. Collect data and take action through the tools your team already uses.
Works where your data livesREST API + MCP for your integrations and AI agents
07 /YOUR SCALE
Choose the architecture that fits.
The same query language
and interface
stay with you as your
system grows.
For pilots, smaller environments and standalone installations.
For centralized collection and analysis of larger event streams.
For environments that need a standby node and controlled failover.
08 /THE DETAILS
What to know
before your first deployment.
Log collection is just the beginning. FrySIEM adds normalization, FQL search, correlation, UEBA, Entity 360, investigations and response playbooks. Every stage works with shared events and entities.
No. Start with embedded DuckDB and Parquet. When you need more capacity, a migration wizard helps you move to ClickHouse. Both options use the same FQL and interface.
Yes. The import wizard converts supported Sigma rules to FQL and shows conversion coverage. Partially converted and unsupported rules remain disabled. Test the results against historical events before enabling them.
Add an approval step to a playbook, including approvals through Slack or Teams. Protected networks, action limits and an emergency stop help control device actions. Permissions and audit trails keep access accountable.
FrySIEM runs on your infrastructure, where events are stored and processed. You choose and configure external destinations for notifications, forwarding and integrations.
THE BIG PICTURE STARTS WITH ONE EVENT
See how FrySIEM connects events, context and action.
Discover the platformCOLLECT. UNDERSTAND. RESPOND.09 /GET IN TOUCH
Have a question about FrySIEM, a feature in mind or feedback to share? This is where we’ll connect.
Use the form or email info@frysec.com. We read every message.