Indeni 6.4.9 is now generally available

We have added audit log to give you visibility to who has changed what, where and when. We have made changes to help you create reports like device health posture, high availability readiness, security risks and vendor recommended best practices. We’ve added a cold-standby server in case the active primary server is lost, you can quickly activate the standby server.

Onwards to more tidbits about what’s changed with 6.4.9:

Audit log

An audit log is critical to understand what has changed and determine what may have caused interruption to a service. An audit log provides you visibility to changes to Indeni allowing you to restore service quickly.

We are pleased to announce audit logging for Indeni 6.4.9. The audit log stream is the admin activity log and user activity log. Admin activity log contains entries for actions that modify the service such as new backup schedule, disabling rules, changing thresholds, adding LDAP authentication, etc. User activity includes user logon attempts and logon failures.

Interacting with audit logs

You can see a high-level overview of all your audit logs from the user interface. Click on any entry to display a detail view of that event, as shown below.

The table below shows the list of audit log entries.

[table id=19 /]

Custom Report Enhancement

In this release, we added templates to make it easier to create reports. Templates are effectively a list of rules that we group them to support a use case.

Use cases:
1) High Risk devices
This template consists of a sample list of issues where a device may require attention.
2) High Availability readiness
This template consists of a list of rules where Indeni verifies consistency among cluster members.
3) Regulatory Compliance/Security risks
This template consists of a list of common compliance and security rules to check for insecure protocols, password strengths, known vulnerabilities and generally security related best practices.
4) Vendor Best practices
These templates consist of a list of best practices recommended by Check Point, F5 and Palo Alto Networks. Implementing these recommended best practices can avoid unplanned outages.

The table below captures the default rules associated with each template.

[table id=20 /]

Cold Standby

The new cold standby feature is a technique for improving reliability and mitigating risks by preparing an idle backup in the event the primary indeni server fails for any reasons. Data from the primary system will be backup automatically and content is synced from the primary server to the standby server regularly. This is to ensure a quick switchover in case the primary server is unavailable for any reason.

For more information about the new cold standby capability, please refer to the Indeni 6.0 User Guide – Cold Standby.

As always, if you have questions or comments, we’re here to help.