Naverisk Integration

[aaspeer]

After many years, we have finally decided to move from Solarwinds RMM (GFIMax) to Naverisk. Are there any other Naeverisk users out there? The product seems solid and does alot more than GFIMax seems to.

We really want more than just ticket integration, we heavily use assets and want that level of sync. Is anyone interested in assisting with the development of an integration - or maybe Commit wants to create an integration? (being hopeful)

Thanks,

Austin Riggs

[adent-ctc]

Re: Naverisk Integration

Hello

We use Naverisk. Great platform and a fantastic & friendly support team.
Just today we released the first version of our "SOAP Server for CommitCRM".
https://dentaur.com.au/it-solutions/...for-commitcrm/

Two of the reasons for embarking on this project were
1. To integrate the management of our Webroot customers into CommitCRM using the Webroot GSM API.
2. To improve the communication with Naverisk into and out of CommitCRM.

Naverisk have a API.
We haven't yet started with that, but plan to make use of our "SOAP Server for CommitCRM" to develop tools to get the Naverisk, Webroot and CommitCRM platforms talking to each other.

Kind regards

Andrew Dent
Dentaur Pty Ltd

[aaspeer]

Re: Naverisk Integration

Hi Andrew,

Let me know how you come along on this, we would definitely be interested.

[stephan]

Re: Naverisk Integration

How is the Naverisk integration looking?

[stephan]

Re: Naverisk Integration

We are also interested in Webroot

[adent-ctc]

Re: Naverisk Integration

Progress is coming along nicely.
We are currently working on the Updating feature in the SOAP Server for CommiCRM.
On the Webroot front, our internal tool (Linux Web App) is now able to use the Webroot API and the SOAP Server we developed, together.
We can now compare at a glance our CommitCRM customers that have a contract record with WR in the name, to the list of our customers in the Webroot GSM.
This informs us which customers are active in Webroot GSM, but do not have a contract listed in CommitCRM, and which customers are deactived in the Webroot GSM, but still have a active or expired contract in CommitCRM.

We are also using our internal tool to send out
1. Webroot alerts to our customers whenever their endpoint receives a threat
2. Naverisk monthly reports.
It is true that both the Webroot GSM and the Naverisk platforms can be configured to send out those things to our customers.
However, that would require maintaining the correct email addresses in both the Webroot GSM and Naverisk portals.
Using our internal tool, means we can now ensure that the email address used to send emails about Webroot and Naverisk is the email address in the CommitCRM email field on the Accounts tab.
Further benefits are that now we can have
1. the emails looking exactly the same for both Webroot and Naverisk, and properly embed the PDF file from the Naverisk reports in the emails.
2. The emails coming from our domain, instead of a Naverisk or Webroot domain.

At the moment, unlike the SOAP Server for CommitCRM, our internal Web Linux App is not being written for sale. We might do that in the future, perhaps as a VM or Cloud server, not really sure, or port the whole App to a Windows 10 App and bundle it with the SOAP Server for CommitCRM.

For the moment, our focus is to make our Contract Management and Renewal processes more automated, and to finish the SOAP Server for CommitCRM.

A problem we have realised is that the official CommitCRM API does not support deleting a record. We have contacted CommitCRM Support and they have confirmed this.

The only way we can think to get around this is to create a delete feature for our SOAP Server which under the hood uses the Update features to wipe/randomise data fields in a record, and then set the record to inactive (where possible).
Thoughts?

Kind regards

Andrew Dent
andrew@dentaur.com
Dentaur Pty Ltd

[stephan]

Re: Naverisk Integration

Any update on this work?

[adent-ctc]

Re: Naverisk Integration

Yes, the SOAP Server for CommitCRM is complete and released to our website today.

See this post.

[adent-ctc]

Re: Naverisk Integration

Our "SOAP server for CommitCRM" product we have replaced with a new product called Jupiter Server.

The Jupiter Server integrates with both Webroot and CommitCRM.
https://dentaur.com.au/jupiter-server/
You can use the provided client application or you can write code to connect to the Jupiter Server.
Sample code is on the website.
Video is on the website.

There is a free trial, no time limit trial.
The paid version allows the Webroot and CommitCRM data to be seen in a single data UI table (assuming you create Webroot contracts in the CommitCRM Contracts table).

More integrations will be added. Currently working on IMAP and Naverisk.
Enhancements to the Webroot and CommitCRM integrations will be worked on as well.

[adent-ctc]

Re: Naverisk Integration

Stephan,
As per the other posts.
Webroot API support in our Jupiter Server is completed (for Anti Virus).
We also support the CommitCRM API.
Next will be the Naverisk API, which should hopefully be quick as it is currently smaller than the Webroot API or the CommitCRM API.

Kind regards

Andrew Dent

[adent-ctc]

Re: Naverisk Integration

Hello Stephan

Support for the Naverisk API is now complete except for ChangeDeviceMaintenanceMode.
We will work with Naverisk Support on that.
Apart from that if you want to glue Naverisk to CommitCRM and/or to Webroot, then the Jupiter Server will allow you to do that in Powershell or in .NET

The trial version of the Jupiter Server should allow you to get a customer list using Powershell from all 3 APIs. To gain Full Access to all the 3 APIs via our Jupiter Server will require you purchase the Full version.
One of the benefits of the Jupiter Server is that Powershell scripts can now be written to talk to CommitCRM. Another benefit is that if that same Powershell script needs to talk to either or both Webroot and Naverisk, you no longer need to store usernames and passwords for Naverisk or Webroot inside of the Powershell scripts.

The next API we are likely to support is SimpleHelp, possibly followed by Sophos.
From the other posts I've read today, I have added Quotewerks, 3CX and Quickbooks cloud to our roadmap.
We have considered writing a mobile app to support CommitCRM, Naverisk and Webroot. Such mobile apps are on our roadmap. The requests of current paying customers determines the roadmap priority.
In the meantime anyone can develop a native mobile app that uses our Jupiter Server to provide what ever functionality that the CommitCRM API provides.

Feel free to email me on andrew@dentaur.com if you have any questions.

Kind regards

Andrew Dent