Attackers do not take breaks.
Neither do we.
A Croatian cybersecurity team: incident response and 24/7 SOC monitoring, compliance with NIS2, ZKS and ISO standards, and penetration testing and red team. When something happens, we are on the case in minutes, not the next morning.
- DetectionEDR blocks encryption on FS-02. XDR links it to a VPN login the same night. The alert reaches our SOC.EDR · XDR
- Triage and enrichmentAI checks the reputation of the IP address and the file, the user's history and whether the same traces appear on other devices. Risk 92/100, escalated.AI · AUTOMATION
- Analyst decisionThe analyst on shift reviews the case and confirms: a real incident, not a false positive. The on-call lead is notified.ANALYST
- ContainmentFS-02 isolated through EDR. Sessions revoked, account blocked in Entra ID, VPN access shut off, IP blocked.ANALYST · EDR
- Notification and ticketA call to your on-call IT. A Jira ticket with the steps. Assessment of whether the incident is significant under ZKS: the 24 h clock starts now.IR LEAD
- Cause, recovery, closureCause: a VPN account without MFA. MFA switched on, passwords changed, backups checked. Report to your IT and management. A new rule in monitoring.IR LEAD · YOUR IT
- CategorisationEssential or important entity, and the obligations that follow.CONSULTANT
- GAP analysisMeasures from the Cybersecurity Regulation (Uredba), interviews and documentation. Maturity score by domain.CONSULTANT
- Action planPriorities, deadlines and owners. Presentation to management.MANAGEMENT
- DeliveryPolicies, risk assessment, asset register, incident response plan, business continuity.YOUR TEAM · RESILIX
- EvidencePentest and SOC findings feed into the plan. Management training under Article 29.AUTOMATION
- Ready for supervisionMaturity tracked month by month, evidence in one place.vCISO
- ReconnaissanceExposed services, subdomains and public information about employees. A VPN appliance with outdated firmware is found.OSINT · SCANNER
- Initial accessA publicly known VPN vulnerability exploited from an announced static IP address, within the agreed scope.PENTESTER
- Privilege escalationA service account with a weak password (Kerberoasting) gives administrator rights on a server.AI AGENT · PENTESTER
- Domain administratorA path through Active Directory to domain administrator. We stop there and do not touch data. We report the critical finding at once.PENTESTER
- ReportEvery finding with evidence, a CVSS score and a recommendation. A summary and fix priorities for management.REPORT
- RetestFixes verified. The same attack path no longer works.PENTESTER
Our technology
We also work with your existing tools, whatever the vendor.
Before an attack, during an attack, and for the regulator.
One team covers the whole path: it finds weaknesses, monitors 24/7, responds to incidents and runs compliance. Our pentesters know what the SOC sees, and the SOC knows how attackers get in.
We find weaknesses before attackers do.
We monitor 24/7 and respond in minutes.
NIS2, ZKS and ISO, with people who know what a real attack looks like.
What an attacker does overnight.
Figures from global and Croatian reports for 2026, each with its source. We state nothing we cannot show.
The same people test, monitor and respond.
Our red team knows how attackers get in, so our SOC knows what to look for. When you call, you reach an analyst who can act at once, and one person leads each incident and each project from start to finish.
Who is in the unit
Team members hold certifications from SANS, OffSec, EC-Council and other recognised issuers. We provide names and certifications per person on request, with our offer.
How we work
With a retainer, the response time is set in the contract and we measure it. Without a retainer, the on-call lead answers the same number, and when work starts depends on our current workload.
We isolate devices and block accounts under rules agreed in advance, without waiting. Shutting down servers or stopping a service is always your decision, with our recommendation and the consequences.
The incident lead is your only contact. You do not explain the situation three times to three people.
An incident is over when the way in is closed, the cause is known, the reports are sent and your IT knows what to do next. Not when office hours end.
Every incident becomes a new rule in our SOC, for you and for all our clients.
We are certified ourselves.
Resilix d.o.o. holds ISO/IEC 27001:2022 (information security), ISO 9001:2015 (quality) and ISO/IEC 20000-1:2018 (IT service management) certificates, issued by the certification body URS (United Registrar of Systems). The standards we implement for clients apply to us too, including how we protect our access to your systems. Certificates are available on request.
Under attack? We answer 24/7.
An on-call analyst straight away, an incident lead within minutes, the spread stopped within the first hour. Crisis team and CSIRT reporting within the legal deadlines. Even if you are not yet a client.
- Emergency call without a contract, or a retainer with agreed response times
- Forensics and a report for your insurer
- Early warning in 24 h, notification in 72 h
We attack you before the attackers do.
Networks, Active Directory, web applications, cloud and people. Manual testing, sped up by an AI agent under a tester's supervision, from an announced static IP address so you can tell us from real attackers.
- PTES, NIST SP 800-115, OWASP and MITRE ATT&CK
- Critical findings reported immediately, not just in the report
- Technical report, management summary and retest
AI alone, people alone, or both.
AI sorts faster than a person. A person decides better than AI. The problem is having only one of the two, or having nobody accountable for the outcome.
| Resilix | AI-only SOC | Traditional MSSP | In-house IT | |
|---|---|---|---|---|
| Alert triage | AI + analyst on shift | AI only | people only, in queue order | during office hours |
| Response at night and at weekends | analyst acts at once | automation, no decision | notification, you react | next morning |
| Accountability for the incident until closure | one lead, in the contract | none | until it is reported to you | you |
| ZKS reports on time | we prepare, you sign | none | rarely | if you know how |
| Forensics and crisis team | same team | none | subcontractor | none |
| Lessons from real incidents fed back into monitoring | yes, same people | model | depends on the provider | rarely |
| Independence from tool vendors | we work with your tools | their platform only | limited | yes |
| Croatian language, on-site visits | yes, same day | no | it depends | yes |
What we saw and what we did.
We do not name clients, which is standard in this business. Cases are anonymised by industry and published with the client's consent.
Ransomware on a file server, at night
- Way in
- stolen VPN password without MFA
- Detected
- EDR blocked deletion of Windows shadow copies, SOC escalated
- Done
- 4 servers isolated and the account blocked in the first minutes, crisis team in 30 min, early warning to CSIRT in 6 h (legal deadline 24 h)
0 encrypted files. Services to citizens did not stop.
From a phishing e-mail to domain administrator
- Scope
- internal pentest, Active Directory and phishing campaign
- Found
- password entered on a fake page, service account with a weak password, flat network without segmentation
- Done
- path to domain administrator documented, critical findings reported the same day, retest after 30 days
On the retest, the path was closed.
Threat Hunting before a contract with a new client
- Trigger
- a customer's request for proof of security
- Found
- 2 inactive supplier administrator accounts, an unpatched VPN appliance with a known vulnerability
- Done
- accounts removed, patch applied, action plan for ZKS
Contract signed. Monitoring in place within 8 days.
Deadlines and fines are set by law. We keep track of them for you.
The Act has been in force since 15 February 2024, and the reporting deadlines under the Cybersecurity Regulation (Uredba) since 30 November 2024. The figures come from the legislation, not from our estimates.
Deadlines for reporting a significant incident
Fines for offences
The higher amount applies. The management body approves the measures, oversees their implementation and completes training (Article 29).
Frequently asked questions
Who provides cyber incident response and penetration testing in Croatia?
Resilix d.o.o. from Bjelovar has an incident response team with a 24/7 on-call line at +385 98 1900 984, for clients and for organisations without a contract, and a red team for penetration testing. It also provides 24/7 SOC monitoring, forensics, Threat Hunting and compliance with NIS2, ZKS and ISO standards.
How often should we run penetration testing?
At least once a year and after major changes: new applications, cloud migrations or network changes. Resilix tests networks, Active Directory, web applications, cloud and people, following PTES, OWASP and MITRE ATT&CK, with a retest of fixed findings.
What should we do if ransomware hits us?
Do not shut computers down but disconnect them from the network, do not pay or write to the attackers, note the time you found out and call an incident response team. The detailed steps are on the Under attack page.
What are the incident reporting deadlines under ZKS?
Early warning to the CSIRT within 24 hours of becoming aware, incident notification within 72 hours and final report 30 days after the notification, as set by the Cybersecurity Regulation (Uredba).
How much does a SOC cost?
It is billed monthly or annually, and the price depends on the number of devices, log sources, platform and level of response. We send a quote after a short call about your environment.
Is Resilix certified?
Yes: ISO/IEC 27001:2022, ISO 9001:2015 and ISO/IEC 20000-1:2018, issued by the certification body URS. Team members hold certifications from SANS, OffSec and EC-Council.
Better to meet us before the attackers do.
30 minutes with a specialist, not a salesperson. We go through your environment, your last pentest and your NIS2 obligations and tell you what we would do first.