Search and SQL analytics
Filter by fields and original text, group events, calculate aggregates and plot activity over time. Open matching events from a result group with the same filters and period. Save searches and analytics settings for reuse.
SIEM, antifraud and Service Desk in one solution
At Cybrexon, we combine SIEM and antifraud rules, event analytics, vulnerability management and a built-in Service Desk. Use the visual rule editor, event correlation, SQL queries and shared dashboards. Your team can inspect the data behind a detection, the affected server’s status, incident assignments and action history.
Get a free trialFilter by fields and original text, group events, calculate aggregates and plot activity over time. Open matching events from a result group with the same filters and period. Save searches and analytics settings for reuse.
Field conditions, regular expressions, reference lists, thresholds and time windows. Link several event sets by shared fields and a defined sequence, such as failed logins followed by a successful login.
An alert retains rule details and the triggering events. An incident contains linked alerts and vulnerabilities, an assignee, deadlines, discussions and files. History shows status and assignment changes.
Configure external HTTP actions and notifications by email, Telegram, Slack and Microsoft Teams. Action and delivery results are available for review. Automatic alert closure requires a confirmed successful action, when this setting is enabled.
CMDB shows each server’s purpose, owners, sources and latest event arrival. Configure notifications when collection stops or resumes; internal IPs and packages are available when inventory collection is enabled.
Link a rule to a knowledge base article. Its detection result provides the selected runbook with investigation and response steps. Article permissions are defined by role and category.
DETECTION RULES
Create a rule from a search or in the editor. Conditions have visual and text views; configure sources, thresholds, time windows, grouping and detection results separately. Test a rule against saved events before enabling it.
AND/OR groups, value comparisons, regular expressions, field existence checks and reference lists. Nested groups determine which conditions an exclusion applies to.
Event counts, unique counts and numeric aggregates. Separate counters by user, address or server. Link several event sets and check their order within a time window.
Preview shows matches, examples of accepted and excluded events, and condition evaluation results. The test does not create live alerts or perform external actions.
Set the result type, severity, category, assignee and runbook in the rule. Merge repeated matches for a group into one record; enable linked incident creation separately.
Select grouping fields, metrics and a result view in the builder. SQL lets you specify filters, grouping, aggregates and sorting in a query. For example, count errors by server, count unique client addresses or calculate average API response time for a selected period.
An incident brings together related alerts and vulnerabilities; service requests track help and configuration work. Each record has a number, assignee, priority and deadline. Discussions retain comments and attachments; history records changes to assignee and status, with an author and timestamp.
Scanner reports provide the affected asset, severity, CVE/CVSS where available, evidence and recommendations. Repeat scans add to the finding’s history. The owner records remediation, risk acceptance or a false positive decision; absence from a single report does not close the finding automatically.
Store investigation instructions, response procedures, notes and contacts in the knowledge base. Select a specific runbook in a rule for reviewers to open when handling a detection. Materials have versions and access restrictions.
Our service provides lists of malicious addresses and indicators of compromise, including CERT data. Rules compare event fields against these lists and create detections for investigation.
Shared dashboards display tables, metrics, rankings and time series. Open source data from a widget with the same filters. Select periods, sections and fields for reports. The audit log records the actor, time, action type and affected object.
An example review: a dashboard shows an increase in errors, the chart opens the corresponding events, the alert shows the triggering data, and the incident shows the assignee and work history. An automated action has its own result and execution time.
INTEGRATIONS AND CONFIGURATION
Parsers extract fields from infrastructure and custom application logs. Configure field names and types for search, SQL analytics and rules. The visual editor lets you define conditions, thresholds and event sequences using this data; access, notifications and external actions are configured separately.
Configure format recognition, fields and transformations in the visual parser editor. Test a sample to see the parsing result before publishing. The event record provides extracted fields and the saved original.
Define field conditions and exclusions in the visual editor or a text expression. Configure thresholds, grouping, time windows, event sequences and the rule’s active schedule with a time zone.
Roles restrict access to event streams, categories and individual operations. Viewing, editing and export can be permitted separately. The audit log records the actor, time, action and affected object.
RULE CONFIGURATION EXAMPLE
To detect web application reconnaissance, select characteristic paths, group requests by source address and server, and set a threshold over five minutes. Exclude trusted scanners using a reference list. Testing shows which events satisfy the conditions.
The parser extracts the client address, server, path and request result. Testing shows the field values alongside the original event.
Combine paths in an OR group. Use AND to add other conditions and exclude trusted scanner addresses.
Count events or unique paths within the window for each address–server pair. Set the threshold and the period for merging repeated detections.
Preview shows matches, excluded examples and condition evaluation results. After review, enable the rule and its selected actions.
Select delivery channels and a configured HTTP request to an external system for a rule. The alert shows success, failure or a skipped action; delivery history shows the message result. When automatic closure is configured, the alert closes after the external action has confirmed success.
CYBREXON ENGINEERING TEAM
We connect sources and configure parsers, SIEM and antifraud rules, dashboards and notifications. We help review detections and scan results; Enterprise includes monitoring and response. We report identified critical issues and vulnerabilities as part of the service.
ANTIFRAUD
Rules use authentication, operation and API events: account, address, amount, result and operation ID. Count repeats and unique actions, compare sums against thresholds and correlate event sequences. Detections retain data for review and can automatically create linked incidents.
A sequence of failed logins and a subsequent successful login are linked by user and server. Set the threshold, time window and event order in the rule; source events remain available for review.
Rules count events and unique operations, check sums and action sequences. With a stable operation ID, repeated messages about the same operation can count once in a unique-value calculation.
Group requests by address, account or service. Conditions use the path, method, result and request frequency; reference lists define exclusions for trusted sources.
RULE CREATION AND TESTING
Use the visual editor to define conditions, grouping and event sequences. Testing against saved history shows matches and explains which conditions excluded sample events. SQL queries and access to original records support further analysis.
REVIEW OPERATIONS AND TEAM ACTIVITY
Use SQL and visual analytics to count operations by user, address and period, then open the events in a selected group. Add related alerts to an incident. History shows assignee and status changes, the discussion holds comments and attachments, and the alert shows automated action results.
The rule set depends on the fields supplied by the application. Integrations and actions in transaction systems are defined separately for each implementation.
Discuss antifraudPLANS
From help with the first sources to monitoring and response by our team. Each plan defines the available capabilities and specialist involvement; your IT team retains the tools for independent analysis and incident handling.
Test threat detection with your own data.
Start detecting threats and managing incidents with ready-to-use rules and support from our engineers.
Detect threats and fraud, find connections between events and track vulnerability remediation.
Entrust monitoring, threat detection and response to the team that develops the solution.
eLearning
Our own learning management system, ready-made courses and programmes tailored to your company’s needs. We help make employee training an ongoing process: from onboarding new hires to regularly refreshing their knowledge.
Make training part of employee onboarding, preparation for new tasks and updates to internal rules. Ready-made and custom courses — in one system.
Find a training programmeHelp employees recognise common threats and handle corporate information safely. Foundational training for the entire team, focused on situations people encounter every day.
Give employees the knowledge they need in their work. Courses in specific areas of information security for different roles, tasks and levels of experience. Including secure development using established industry practices.
Prepare employees to work with information security and personal data protection requirements. Training helps them apply the necessary rules in their daily work, taking your industry and company’s activities into account.
Train employees using your company’s rules and workplace situations. We develop courses based on internal policies, processes and materials.
Discuss specific sources, event formats, detection rules, analytics queries and incident handling. These requirements define the configuration, integrations and specialist involvement needed.
Infrastructure, applications and available events
Visual rule editor, correlation and SQL analytics
Vulnerabilities, investigations, automation and monitoring
We develop the detection engine, visual rule and parser editors, analytics, CMDB and Service Desk. Discuss event formats, detection conditions and integrations directly with our engineering team.
Our specialists help connect systems, configure SIEM and antifraud, investigate incidents and work with scan results. Enterprise includes monitoring and response by our team; the plan defines the extent of our involvement.
We review monitoring arrangements, configurations and security practices. The result is a set of identified issues, recommendations and materials for planning remediation.