Monthly Archives: April 2014

Nava SIEM Agent 1.1 – Retrieve, retain, and analyze cloud audit logs

We’re happy to announce an update to Nava SIEM Agent, our cloud security and audit log retrieval solution. Since Nava SIEM Agent is a relatively new product, we want to answer some frequently asked questions about it in this post.

Many of the changes in this release (Nava SIEM Agent 1.1) are internal but important, including:

Updated to work with with the latest version of the Google Admin SDK libraries
Ability to “Service Account” authentication as opposed to 3-legged OAuth
Selective backlog retrieval

The changes will cumulatively result in better security, improved stability, and scalability to millions of events. For full release notes, please visit this page: Nava SIEM Agent 1.1 release notes.
What are some common use cases for Nava SIEM Agent?
There are several reasons why you might use it:

Google Apps retains audit logs only for 180 days, after which they are gone.
Help perform IP reputation analysis, by comparing IP addresses in audit logs with a database of known malicious IPs.
Help perform offline forensics, without requiring access to the cloud provider.
Help aggregate logs in a centralized logging server.

Nava Certus now supports migration to AODocs (beta)

With Nava Certus, cloud storage migration has never been easier. Today, we’re expanding our features to include another migration target, AODocs a document management solution for Google Apps.

While the functionality is still in Beta and we’re actively testing and getting this version ready for shipment, you are welcome to contact us and we’ll be happy to give you an advance version to test.

Here is a more complete list of changes in Nava Certus 1.5:

Migration to AODocs
File size filter
Job conversion and upgrade support

With version 1.5, we will be supporting nearly 35 unique migrations.

X = regular migration, P = migration with permission support, D = distributed migration, C = conversion
How does the migration to AODocs work?
We’ve put a lot of time and thought into supporting the AODocs functionality. To begin with, all of the sources currently available in the product are also supported for migration to AODocs. For instance, if you are a Google Apps reseller, you can now win more Microsoft customers by offering to migrate the customer’s data from Sharepoint to AODocs or from SkyDrive/OneDrive to AODocs.

Not only will you be able to migrate to AODocs, but in some cases, you may be interested in sending very large files somewhere else. For the AODocs destination, we now support a secondary Google Cloud Storage location. Files smaller or equal to a certain size will go to AODocs (which is actually built on top of Google Drive).  Files greater than the configured size filter will be sent to Google Cloud Storage.
Size filter for Google Drive
Many customers frequently want […]