CloudPassage Halo — 27 January 2016 Release
The 27 January 2016 Release of CloudPassage® Halo® marks General Availability (GA) of the new Halo user interface, including role-based access controls. The release also includes corrected display of XML log messages for Log-Based Intrusion Detection, new workflow for retiring server groups, and other new features and improvements.
New Features and Improvements
Halo UI Redesign
This release includes many software enhancements that underlie and support the General Availability release of the redesigned Halo portal user interface. The release also includes several adjustments to parts of the legacy interface that require modification to integrate correctly with the new UI.
Note: If you have not yet accessed the new UI and would like to try it out, go to https://support.cloudpassage.com/entries/98741577-Accessing-the-Redesigned-Halo for instructions. To view the Halo UI release notes from the new UI, choose Documentation Library from the Halo portal Main menu.
New workflow for retiring and unretiring server groups
Retiring a server no longer means moving it from one server group to another. "retired" is now a server state, like "active", "deactivated", and "missing". A server must already be deactivated before it can be retired.
When you set a deactivated server's state to "retired", it remains in its server group and is counted as one of the group's servers; however, its agent is not active and it is never scanned by Halo. You can move retired servers among server groups
You can effectively "unretire" a retired server simply by setting its state to "active". It then adopts its current group's policies.
The "Retired" and "Unretired" server groups remain available to hold legacy retired and unretired servers. If you do not use these server groups, you may remove them.
Log-Based Intrusion Detection
Halo properly handles log messages with special characters
Previously, viewing log-based intrusion detection scan results could fail with a timeout if the XML log message that Halo was attempting to display contained certain improperly encoded characters. Halo now re-encodes those characters and can display the XML messages properly.
Please note that the following features have been or may soon be removed from Halo. Please plan to modify any code or procedures that depend on them.
- The use of
daemon-keyas a Halo agent startup parameter is now deprecated in favor of
daemon-keywill continue to be supported for backward compatibility.
The following issues are among those that remain unresolved as of this release. Any known workarounds are described.
- New Halo UI uses browser time instead of user setting. In the legacy Halo UI, a user can select the time zone for which Halo is to display all date-time values. In the new UI, Halo instead displays times according the the user's browser time zone setting.
- Editing file integrity baseline expiration. If you want to change the expiration value when editing or re-baselining an existing baseline, the new expiration date is now calculated from the current date, rather than from the original baseline-creation date. However, if you keep the same setting (number of days) for the expiration value, the re-calculation does not occur and the expiration date remains based on the original creation date.
Workaround: Select a different expiration value and save the baseline. Then re-edit the baseline and specify your desired expiration value.