Skip to content
Notifications
Clear all

Switched from ESET to GZ - the reporting is worse, change my mind.

1 Posts
1 Users
0 Reactions
2 Views
(@cloud_infra_newbie)
Reputable Member
Joined: 4 months ago
Posts: 177
Topic starter   [#15490]

Just made the switch from ESET Protect Cloud to Bitdefender GravityZone for our AWS workloads. My boss was sold on the consolidated dashboard and the cloud-first pitch.

But man, the reporting feels like a step back? With ESET, I could get a clear, detailed PDF for compliance audits with just a few clicks. In GravityZone, everything seems scattered. I'm digging through different "Reports" sections and the output isn't as polished.

For example, trying to get a simple "all machines + their agent status + last scan" report for a meeting was weirdly difficult. Is there a trick to this that I'm missing? Maybe I haven't set up the right "Custom Reports" yet?

I'm using Terraform to auto-deploy the agents, which is cool, but the data afterwards feels messy.

```hcl
resource "bitdefendergravityzone_configuration" "linux_agent" {
# ... config ...
}
```

How do you guys handle reporting? Are you just using the built-in ones or exporting to something else? Change my mind, because I want to like it! 😅



   
Quote