It’s time for the third and final installment of our series: explainer videos for the new Halo interface. This week we’re breaking down how to manage issues and policies within the new Halo interface. We’ve made some exciting changes so be sure to watch each video to learn more!
In Halo, managing issues means that you have immense control at your fingertips to group and manage common findings in your server fleet. The video below will demonstrate how you can run scans and examine the data generated using the new Halo interface, and categorize and prioritize issues within your servers based on that data.
We begin with the issues screen within the Halo interface. On the left you will see issue metrics, showing you how many issues correspond to what groups, and whether they’re critical (shown in red) or noncritical (shown in yellow). On the right side of the screen you can examine issues that are currently active, or still unresolved. From that same window you can use the search bar to pinpoint issues by criticality, issue type, and date.
The search bar filters allow you to generate a list that can then be assessed. Once you’ve found the issue you’re most interested in examining, you can also select the issue to pull it up and learn about its: criticality, OS type, what servers have similar issues, when the last scan happened, how old the issue is and more.
From there, the video takes you through what issues auto-resolve (including file updates and patches) and what issues must be resolved manually.
To learn more and see additional examples, watch the video below!
Thanks to the new Halo interface, managing policies in Halo is even more straightforward. In the old interface, each type of policy was listed in a separate menu. In the new interface, you can find all policies listed on a single screen. You can also see when a policy was last edited, and by whom. A new feature, group ownership, has been added as well.
This group ownership, which was discussed in a previous post outlining role based access control, is outlined according to scope, giving the branch of the group a specific hierarchy that the user has access to. Users will then only be able to see items within their scope. As a reminder, auditors are not able to modify policies.
Most customers start off by creating policies using some of the templates provided within Halo. These templates may be based on CloudPassage recommendations, or well-known standards.
The video also walks you how to find a policy within your templates, clone it, and properly assign it to the right groups and subgroups.
To learn more, watch the video below.