Security monitoring with TEMERON's Wazuh-based XDR

See what happens on your servers, laptops and cloud services, get the alerts that matter, and have a team behind them — without building a security operations centre.

Citește în română →

TEMERON's XDR is our own Wazuh deployment: an XDR and SIEM we already operate. We use it to deploy and run security monitoring for companies that need continuous visibility over their systems but do not have, or do not want, their own security team. It is also what our work in the EU-funded CIPHER project builds on.

Wazuh is a widely used open-source security platform. We do not sell you a licence or a black box. We bring the setup, the day-to-day operation and the people who look at the alerts, and we agree with you in writing what is monitored, who is notified and what happens when something goes wrong.

What you get

  • Centralised log collection from servers, endpoints, applications and cloud services, so security events are in one place instead of scattered across systems.
  • Correlation and alert configuration tuned with you, so your team sees the alerts that matter, not thousands of messages nobody reads.
  • Incident response workflows agreed with your team: who is called, what is contained first, what is documented.
  • Vulnerability assessment and compliance monitoring against common frameworks such as CIS benchmarks, NIST, GDPR, HIPAA and PCI DSS.
  • Detections mapped to MITRE ATT&CK, and integration with your existing firewall and IDS/IPS.
  • Regular reporting that management can read, not only engineers.

How we start

  • Scope: we list the systems and data that matter most and decide what to monitor first.
  • Deploy: agents go on the selected systems, and existing sources such as firewalls and cloud services are connected.
  • Tune: during the first weeks we adjust rules and thresholds with you to cut noise.
  • Agree: alert channels, response times and coverage hours are written into the contract, so you know exactly what is covered and what is not.

Monitoring and NIS2

NIS2 requires covered entities to handle incidents (Art. 21(2)(b)) and to send an early warning to the competent authority or CSIRT within 24 hours of becoming aware of a significant incident, followed by a notification within 72 hours (Art. 23(4)). Meeting those deadlines is hard without monitoring that detects incidents in time. Monitoring alone does not make a company compliant; combined with our NIS2 audit preparation, risk assessment and reporting workflows, it gives you the evidence auditors and customers ask for.

Built by a company that does security research

TEMERON is a beneficiary in CIPHER (Digital Europe Programme, grant 101249732), where we develop risk-monitoring and integration components building on TEMERON's XDR, and in CROSSMARE (Horizon Europe, grant 101225981). The monitoring we operate for clients and the components we build in research share the same base.

More

Frequently asked questions

What is XDR?

Extended detection and response: security monitoring that collects and correlates events from many sources — endpoints, servers, network devices and cloud services — so attacks are detected across systems, not one machine at a time.

Is TEMERON's XDR your own product?

It is our own Wazuh deployment, an XDR we already operate. It is not a separate commercial product and not a fork of Wazuh: the value we add is the setup, the tuning and the people who operate it and respond.

Do we need our own security team?

No. We operate the monitoring and look at the alerts; your team is involved when a decision or an action on your systems is needed, as agreed in the incident workflow.

Is the monitoring 24/7?

Coverage hours and response times are agreed in the contract for each client. We tell you before you sign exactly what is covered and what is not.

Where is our monitoring data stored?

Before go-live we agree in writing where monitoring data is stored, for how long and who can access it.

Does monitoring make us NIS2 compliant?

Not on its own. It supports incident handling and the 24-hour and 72-hour reporting deadlines under NIS2 Art. 23. Compliance also needs risk management, policies, supplier security and governance, which we cover in our NIS2 work.

Are you a Wazuh partner?

We are not part of Wazuh's partner programme. We deploy and operate the open-source Wazuh platform as TEMERON's XDR.

Sources

  • Directive (EU) 2022/2555 (NIS2), Art. 21(2)(b) and Art. 23(4)
  • Grant Agreement 101249732 (CIPHER); CORDIS, project 101225981 (CROSSMARE)

Talk to us

Tell us what you need to protect or comply with. We reply by email.

Get in touch