opvizor-log-compliance-extension

Our Log Compliance extension has been adopted at lightning speed by our customers and it’s being used to full-text-search in ESXi and vCSA events, tasks and of course syslog data or as charts within our dashboards (including alerting).

Log Analyzer extension

Existing customers can simply contact us through the typical channels like chat or email.

If you want to try the Log Analyzer extension for the first time, simply download the current release on this website.

Components

The Log Compliance extension consists of multiple components that are seemlessly integrated.

That combination allows an unique set of functionalities:

  • full-text search within any data type (Tasks, Events, Logs)
  • vSphere navigation as usual (vCSA, Cluster, Host,…)
  • support for non-vSphere systems or Guest OS (Windows, Linux, applications)
  • integration of common queries within existing or log-focussed dashboards
  • Mix log entry search with event search (i. e. storage vmotion event and related vmkernel log error)

Compliance

Last but not least – you can’t rely on log files, if they are not stored in a secure and tamperproof way. Therefore, we’re using immudb to immutably store raw syslog data and the cryptographic proof of origin.

When it comes to compliance (PCI and others) you need to make sure:

  • Ensuring security of log data so that it cannot be tampered, changed or deleted
  • Notifying system administrator personnel about any change or suspicious activity on crucial, confidential files

Configuration

After deploying the appliance for the first time or adding the license key that supports log compliance, all vSphere related tasks and events are captured automatically.

To receive the log files of your ESXi hosts and vCSA as well, you can use our appliance administration to setup syslog forwarding:

Configure VMware ESXi to forward syslog data

Note: we respect existing syslog entries and only append our configuration.

If you want to configure the Syslog forwarding manually, please check out the following VMware KB article:

VMware ESXi: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.esxi.upgrade.doc/GUID-9F67DB52-F469-451F-B6C8-DAE8D95976E7.html

VMware vCSA: https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vcsa.doc/GUID-9633A961-A5C3-4658-B099-B81E0512DC21.html

Full Text Search

After some minutes you’re already able to search through the log entries. Simply click the log analyzer icon to enter the full-text-search:

When starting Log Analyzer for the first time you’ll see an empty search bar and a cheat sheet in the main window:

  1. Navigation: select the vCSA, ESXi or cluster to run the query against. The better you preselect, the less overhead logs will be shown
  2. Log Labels: you can further filter the log result using labels (i. e. severity, VM, …)
  3. The log search bar and the cheat sheet below. You can also find more information about the search in our guidelines:
    https://github.com/opvizor/log-guide/blob/master/README.md
  4. Timerange selection: you can either go for an absolute or relative timerange to filter the search result
  5. Run the query immediately or set a refresh frequency to automatically run the query continuously
  6. Change the entry limit. 1000 entries is the default that is visible in the main screen, but you can go up to several thousand if you like

Limit set to 150000 entries

Example queries

Some real life examples, to query certain log data:

# Return only warn log entries for the selected ESXi
{ESXi="esxname",severity="warn"}

# Match a certain string in the log file of the selected ESXi
{ESXi="esxname"} |= "exact match for content"

# Query only ESXi Syslog data
{ESXi="esxname", DataType="ESXi_Syslog"}

# Query SCSI entries (exclude SNMP)
{ESXi=~".+"} |~ "SCSI|NMP|ScsiDeviceIO|scsiCorrelator|vmk-iscsi|iscsi|iscsiCorrelator" != "SNMP"

# Query SCSI sence codes
{ESXi=~".+"}|="Valid sense data"

Check compliance

We use immudb to store all log data that has been received in a tamperproof way. Our goal is to make the auditing part as easy as possible and being compliant with all important European and US regulations.

When you want to check the integrity and immutability of the log entry, you can simply click the verification button:

The shown result contains all log entry details and the verification of the whole immudb database as well as the individual entry.

Audit single log entries

That way the Opvizor appliance is not only storing syslog data using simple checksum chain technology – it’s built on top of the most innovative immutability data structure (immudb.io). That technology uses an append-only datastructure and a merkle-tree to guarantee the integrity with a cryptographic proof.

The additional index allows to detect deleted log entries as well.

Log and event Dashboards

You can also find 4 different dashboards that allow to detect and alert on common "problematic" log entries.

Lets look at the ESXi Storage Overview as an example:

That way you don’t need to remember the search query at all and simply use the predefined charts (search) or add new charts with your own queries.

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.