Event sources
We connect device, account and service events. We check incoming data and identify sources missing from the monitoring scope.
We connect device, account and service events. We assess alerts and investigate threats. We carry out agreed protective actions.
Compare monitoring plansWe combine threat detection with operator-led analysis. We assess alerts and agree the next steps.
We connect device, account and service events. We check incoming data and identify sources missing from the monitoring scope.
We assess alerts and connect related signals. We separate duplicate notifications from cases that need further investigation and action.
We investigate events and take agreed protective action. We record what was done and contact the right person to coordinate the next steps.
Reports show events, completed actions and unresolved risks. Recommendations identify the person responsible and the next step to take.
Every plan includes alert analysis and agreed action. We match the scale, data history and response arrangements.
For teams that need alerts assessed, threats investigated and agreed protective action.
net per month1 h of changes per monthUp to 25 devices and 3 integrations
For larger environments that need faster incident handling and a longer alert history.
net per month3 h of changes per monthUp to 50 devices and 5 integrations
For multiple environments needing custom integrations, data coverage and response arrangements.
Project and ongoing care as agreedAgreed change allowanceSources and retention as agreed
New setup starts at PLN 2400 net for Standard and PLN 4800 net for Business. Before work starts, we confirm what we will monitor, the data sources, required licences and total price.
Operators work Monday to Friday, 09:00–17:00 Warsaw time, excluding Polish public holidays. Response targets specify when we begin handling a critical incident.
A fictional example of how we handle an incident.
Signals from several sources.
We link the alert to other events. We check where and when the sign-in occurred, what the account can access and what evidence is missing.
Account activity reviewed.
We check whether there is a legitimate explanation for the sign-in and which resources an unauthorised person may have accessed.
Access restricted.
Once we confirm a threat, we follow the agreed procedure, such as ending the session. We record who acted and when.
Follow-up checks.
We verify the result and share a summary. The case record lists outstanding risks, who is responsible and the deadlines.
See how many devices and integrations each plan covers and how long we retain data. Expand the sections below for response and billing terms.
| Scope of care | Standard | Business | Bespoke |
|---|---|---|---|
| Computers and servers | Up to 25 | Up to 50 | As scoped |
| Ready-made integrations | Up to 3 | Up to 5 | Tailored scope |
| Locations | 1 | Up to 2 | As needed |
| Data volume after measurement | By agreement | By agreement | By agreement |
| Searchable alert history | 30 days | 90 days | Agreed period |
| Archive of accepted events | 30 days | 30 days | Agreed period |
| Automated detection | 24/7 | 24/7 | As scoped |
| Operator review | On working days | On working days | Agreed frequency |
| Summary report | Monthly | Monthly | Agreed frequency |
| Planned changes | 1 hour per month | 3 hours per month | Agreed allowance |
| Critical incident response | Within 4 business hours | Within 60 min in office hours | Agreed SLA |
| Sources we monitor | We check whether we can receive events from the computers, servers, accounts, firewalls and cloud services covered by the agreement. |
|---|---|
| Source inventory | We record what we monitor, who provides access and where data is missing. |
| How we count integrations | One integration is a connection that receives events from a service. We count devices separately. |
| Your current provider | We can monitor your existing environment after checking the tools, permissions and provider capabilities. |
| Detection | Tools receive events and detect agreed types of threats around the clock. |
|---|---|
| Alert review | On working days, an operator connects related signals and investigates cases that need action. |
| Monitoring quality | We check sources and rules, reduce duplicate alerts and flag gaps in the data. |
| Business case review | Each week we review open cases and identify any changes needed to monitoring. |
| Opening a case | We assess significant alerts, open a case and contact you through the agreed channel. |
|---|---|
| Authorisation | We take pre-authorised action, such as ending a session or restricting access. Stopping a critical service requires appropriate authorisation. |
| Actions included in the subscription | Investigation and agreed protective actions do not use the change allowance. Detecting an incident does not incur an extra charge. |
| Work scoped separately | Major recovery, rebuilding an environment and specialist forensic work are scoped separately. |
| Data profile | Before work starts, we measure event volumes from the agreed sources. We use that measurement to confirm the monitoring scope and the cost of processing and storage. |
|---|---|
| Higher event volume | If volumes rise, we check why and agree any changes before charging extra. |
| Searchable alert history | Alerts remain searchable for 30 days on Standard and 90 days on Business. |
| Event archive | We retain accepted events for 30 days on both plans. We agree longer retention separately. |
| Access and recovery | Before work starts, we agree access, recovery, export and deletion arrangements. We set separate rules for events, alerts and backups. |
| Response time | We start handling a critical incident within 4 business hours on Standard and within 60 minutes during office hours on Business. |
|---|---|
| Critical incident | Credible signs of an account takeover, an active attack or a data leak in the monitored environment, where urgent action is needed. |
| How we count response time | We count from whichever happens first: a monitoring alert or receipt of a report through the agreed channel. Only office hours count towards the response time. If the first event occurs outside office hours, the clock starts when the office next opens. |
| Office hours | Monday to Friday, 09:00–17:00 Warsaw time, excluding Polish public holidays. |
| Start of handling | A response is the first investigative or protective action. An automated acknowledgement does not count, and resolution can take longer. |
| Outside office hours | Business receives priority subject to operator availability. Guaranteed round-the-clock response requires a separate agreement and verified staffing and permissions. |
| Choice of tools | We can use suitable tools you already have, our platform or a provider service. Before work starts, we confirm integrations, licences, usage costs and data access. |
|---|---|
| Microsoft 365 data access | We check which events your licence provides and whether processing them carries a charge. |
| Shared responsibilities | If we already look after your safeguards, we agree who is responsible for each part. We charge for the same licences, updates and actions only once. |
| Related events | Monitoring connects signals across services, so cases that span several systems are tracked in one register. |
| Monthly report | We report sources and data gaps, accepted cases, actions, handling times and outstanding risks. Alert counts alone do not measure protection. |
|---|---|
| Recommendations and usage | We identify who is responsible and what happens next. The report also shows use of the data profile and change allowance. |
| What we hand over | At the end of the engagement we hand over agreed reports, the case register, configuration and available exports. |
| Access after handover | We agree how data and notifications transfer and how delegated access is removed. We document deletion times and licence obligations before work starts. |
| New setup | From PLN 2400 net on Standard and PLN 4800 net on Business. Setup includes scoping, source integration, rules, notifications and acceptance checks. |
|---|---|
| Taking over monitoring | After assessing the setup, we may take over a small, working monitoring process without a setup fee. |
| Notice period | One month for a subscription with a setup fee. Three months for a takeover without a setup fee. |
| Change allowance | Standard includes 1 hour per month and Business includes 3 hours. The allowance covers requested configuration changes and agreed extensions. Unused hours do not roll over. |
| Work included in the subscription | Maintenance, investigation, reports and agreed incident actions are included in the subscription outside the change allowance. |
| Extra costs | Additional administration costs PLN 300 net per hour once you approve the budget. Larger builds, custom integrations and existing remediation backlogs are quoted separately. We confirm the full cost before you order. |
We review devices and safeguards. We agree the data sources, access, responsibilities and total price.
We connect the sources and check the flow of events. We set up rules, notifications and a shared case register.
We test the alert path to the operator, response, retention and exports. Ongoing monitoring begins after sign-off.
Yes. Device protection acts on computers and servers. Monitoring brings together signals from devices, accounts and services to assess what happened.
Yes, if we can access the events we need and have permission to take the agreed actions. We start by checking what your current support covers.
Detection and agreed automated actions run around the clock. Outside office hours, Business receives priority subject to operator availability. Guaranteed cover is agreed separately.
We start by reviewing the licences you already have. We itemise extra licences, cloud services and non-standard resources in the quote before you buy.
For example, adding a notification or updating an agreed configuration. Alert investigation, reports and agreed protective actions are included in the subscription.
We check what caused the increase and agree any changes before extra charges apply. Important alerts stay in scope.
Tell us which devices, accounts and services your business uses. We’ll agree which events to collect, how to respond and what ongoing monitoring will cost.
Ask about scope and pricing