When you're managing anything more than a handful of devices for your client, you'll need policies to help you set a framework to monitor them. Policies become increasingly important as the number of clients you manage grow, leading to more complex policies tailored to each network. In SuperOps.ai, you have a flexible policy management system that helps you build policy sets that cover the needs of your clients' networks.
In this section you'll learn how to:
Create policy sets to manage Windows and mac asset networks
Handle patch management for your policies
Monitor devices better using event logs
Things to know
Before we jump into setting things up, here are some cool things about our policy management that you should know:
A policy set is a combination of policies built to cater to a specific set of assets. A policy set typically includes a policy for asset management, alert management, and antivirus management.
Policy sets can be overridden at a client, site, or even an asset level.
For alert management policies, you can define a cool-off period to reduce noise by blocking repeated alerts for a specific event, for a certain amount of time.
Patch approval is handled as a matrix, that combines patch categories and patch severity to define approvals for policies.
Terms we use
As the name suggests, this is a type of policy that follows a hierarchy by deploying policies through distinct levels. The order of levels for the hierarchical policy is as follows: Global → Client → Site → Asset.
Event log monitoring
This helps you track any problems with an asset by monitoring events that take place in the asset using specific event IDs generated by the asset.
This defines the process of how update patches for client assets are approved. You can choose to automatically approve critical patches, and manually approve or even automatically reject others.
Now you have all the context you need to glide through the resources in this module to find the solutions you're looking for!