Cronzy Watch

Deployment

Hosted by us. A collector inside the network when you need one.

Cronzy Watch is a hosted service, so there is nothing to build or patch. When a client network cannot be reached from the Internet, a small site collector runs inside it and only connects outward.

What you get

SaaS and the site collector, in practice

SaaS first

No servers to run. Connect your sources and start with the ranked list.

Outbound-only collector

The collector makes outbound connections only, so no inbound firewall port is opened at the client.

Signed updates

The collector updates itself from signed releases and checks the signature before applying one.

Read-only by default

Cronzy reads your systems. Write actions are a short defined list and need a second person to approve.

Credentials stay encrypted

Client credentials are entered in encrypted fields in the app, never in code, chat or logs.

How it works

From connected to done

  1. Direct sources, such as AWS, connect straight from the platform.
  2. For firewalls and switches behind a perimeter, install the collector on a host in the site.
  3. The collector reads the local systems and sends the data out to Cronzy.
  4. It is optional and per site: use it only where you need it.

Questions

Frequently asked questions

Do I need to open a port?

No. The collector only makes outbound connections.

Is there an on-premises version?

Cronzy Watch is offered as SaaS. Ask us if you have a requirement beyond that.

Terms used on this page

Site collectorWazuh

See it on a demo estate

Tell us about your environment and we will show Cronzy Watch with data that matches it.

Request a demo