Integration
Bitdefender GravityZone in IDA: protection status per customer
GravityZone knows which endpoint is protected. IDA brings that information to the customer and to the device - so the service desk can see where protection is missing, rather than finding out when something goes wrong.
What IDA reads from Bitdefender GravityZone
- Managed endpoints per company
- Protection and agent status
- The mapping from company to customer
What IDA does with it
- The customer record shows how many endpoints are protected - no portal switch
- Devices without protection stand out before anyone goes looking
- Device offboarding removes the endpoint along with everything else
Who it is for
Service providers running GravityZone for several customers who need the protection status in their own system.
Setup: Store API access to the GravityZone console; companies are mapped to customers once.
Every integration in IDA has its own switch. Turn it off and it disappears completely - including the columns, filters and reports that belong to it. You only see what you actually use.
Vendor website: Bitdefender GravityZone. Bitdefender GravityZone is a trademark of its respective owner; IDA connects to the system technically, which implies no partnership.
Related
- ESET PROTECT - Security & backup
- Acronis Cyber Protect - Security & backup
- Device offboarding - Processes
Questions about the Bitdefender GravityZone integration
Does IDA map companies automatically?
IDA proposes a mapping, but only writes it once you confirm. A name comparison alone is not proof - it would confuse customers whose company names resemble each other.
Are GravityZone licences billed from here?
The protection status is for visibility. Automatic quantity billing runs through your purchasing source - Crayon, ALSO, Tarox or Cloud Factory, for instance.
Everything in one interface - for you too
30 days free, no payment details. Every integration is included at no extra cost.