Endpoint-level SLA evaluation in managed networks
An embodiment includes a method of real-time, endpoint-specific SLA compliance evaluation in a managed network. The method includes receiving SLA definition input that indicates an SLA definition of the managed network. Responsive to detection of a trigger event, the method includes initiating a scan of endpoints including retrieval of endpoint-level state data. The method includes identifying a portion of the retrieved state data relevant to the SLA definition. The method includes aggregating the portions of the retrieved state data. The method includes determining whether the managed network is SLA compliant at an endpoint-level of granularity based on the aggregated portions. Responsive to the managed network being noncompliant, the method includes identifying a subset of endpoints failing to meet the SLA definition and implementing a product modification process to address a metric of the SLA definition and change a product to bring the first endpoint into compliance.
1. A method of real-time, endpoint-specific SLA compliance evaluation in a managed network, the method comprising:
receiving, at a management device, SLA definition input configured to indicate an SLA definition for an SLA standard of a managed network;
responsive to detection of a trigger event in the managed network, initiating a scan of a plurality of endpoints of the managed network, the scan including retrieval of endpoint-level state data of each of the plurality of endpoints;
identifying a portion of the retrieved state data that is relevant to the SLA definition for each of the plurality of endpoints;
aggregating the portions of the retrieved state data from each of the plurality of endpoints;
based on the aggregated portions, determining whether the managed network is compliant with the SLA standard at an endpoint-level of granularity;
responsive to the managed network being noncompliant:
identifying a subset of endpoints of the plurality of endpoints that fail to meet the SLA definition; and
implementing at a first endpoint of the subset of endpoints, a product modification process to address a metric of the SLA definition and change a product or the first endpoint to bring the product or the first endpoint into compliance with the SLA standard.
2. The method of claim 1 , wherein:
the SLA definition input includes a specification of an endpoint-level metric;
the metric includes installation of a product update at the first endpoint; and
the product modification process includes distribution of the product update to the first endpoint.
3. The method of claim 2 , wherein the SLA endpoint-level metric includes a percentage or portion of the plurality of endpoints being compliant with the SLA standard.
4. The method of claim 1 , wherein the endpoint-level state data includes:
an identifier of each of the plurality of endpoints; and
a patch state of each of the plurality of endpoints related to at least one product update.
5. The method of claim 1 , wherein the determining whether the managed network is compliant occurs in real time responsive to the scanning of the plurality of endpoints.
6. The method of claim 1 , further comprising responsive to the managed network being compliant, causing display of an SLA compliance notification.
7. The method of claim 1 , wherein:
the trigger includes a first trigger;
the subset of endpoints is a first subset of endpoints; and
the method further comprises:
responsive to a second trigger, further scanning the plurality of endpoints;
further identifying a further portion of the retrieved state data relevant to the SLA definition;
aggregating the further portions of the retrieved state data;
based on the aggregated further portions, determining whether the managed network is compliant with the SLA standard at a time of the second trigger;
responsive to the managed network being noncompliant:
identifying a second subset of endpoints of the plurality of endpoints that fail to meet the SLA definition; and
generating from the first and second subsets of endpoints a pattern of compliance indicative of changes in the states of the endpoints between the first trigger and the second trigger.
8. The method of claim 7 , further comprising causing display, in a user interface, SLA compliance data as a function of time, the SLA compliance data being representative of the managed network as SLA compliant or SLA non-complaint at a time of the scan.
9. The method of claim 8 , further comprising defining an SLA group including a subset of endpoints in one or both of the managed network wherein:
the scan includes automated scans of the SLA group; and
the SLA compliance data further includes data representative of whether each endpoint of the SLA group is SLA compliant or SLA non-complaint at a time of the scan.
10. The method of claim 1 , wherein the product modification process includes transmission of at least one product update to a product installed at the first endpoint.
11. The method of claim 1 , wherein the trigger event includes:
an update to content or to the product;
a notification by a service in a cloud network that is pushed to the endpoint, the notification indicating that content has been updated;
an update published to a patch catalog;
an unauthorized change to a software inventory of the endpoint in the managed network; or
an unauthorized change to a software inventory of an additional endpoint having a similar defined state.
12. The method of claim 1 , wherein the SLA definition input includes:
a product update status;
a product version preference;
a preferred product being installed at the endpoint;
a vendor update installation status;
a particular patch;
implementation of an update list;
implementation of updates categorized in a particular way;
an outstanding patch; or
an outstanding vulnerability.
13. A non-transitory computer-readable medium having encoded therein programming code executable by one or more processors to perform or control performance of operations of real-time, endpoint-specific SLA compliance evaluation in a managed network, the operations comprising:
receiving, at a management device, SLA definition input configured to indicate an SLA definition for an SLA standard of a managed network;
responsive to detection of a trigger event in the managed network, initiating a scan of a plurality of endpoints of the managed network, the scan including retrieval of endpoint-level state data of each of the plurality of endpoints;
identifying a portion of the retrieved state data that is relevant to the SLA definition for each of the plurality of endpoints;
aggregating the portions of the retrieved state data from each of the plurality of endpoints;
based on the aggregated portions, determining whether the managed network is compliant with the SLA standard at an endpoint-level of granularity;
responsive to the managed network being noncompliant:
identifying a subset of endpoints of the plurality of endpoints that fail to meet the SLA definition; and
implementing at a first endpoint of the subset of endpoints, a product modification process to address a metric of the SLA definition and change a product or the first endpoint to bring the product or the first endpoint into compliance with the SLA standard.
14. The non-transitory computer-readable medium of claim 13 , wherein:
the SLA definition input includes a specification of an endpoint-level metric;
the metric includes installation of a product update at the first endpoint;
the product modification process includes distribution of the product update to the first endpoint; and
the SLA endpoint-level metric includes a percentage or portion of the plurality of endpoints being compliant with the SLA standard.
15. The non-transitory computer-readable medium of claim 13 , wherein the endpoint-level state data includes:
an identifier of each of the plurality of endpoints; and
a patch state of each of the plurality of endpoints related to at least one product update.
16. The non-transitory computer-readable medium of claim 13 , wherein the determining whether the managed network is compliant occurs in real time responsive to the scanning of the plurality of endpoints.
17. The non-transitory computer-readable medium of claim 13 , wherein the operations further comprise responsive to the managed network being compliant, causing display of an SLA compliance notification.
18. The non-transitory computer-readable medium of claim 13 , wherein:
the trigger includes a first trigger;
the subset of endpoints is a first subset of endpoints; and
the operation further comprises:
responsive to a second trigger, further scanning the plurality of endpoints;
further identifying a further portion of the retrieved state data relevant to the SLA definition;
aggregating the further portions of the retrieved state data;
based on the aggregated further portions, determining whether the managed network is compliant with the SLA standard at a time of the second trigger;
responsive to the managed network being noncompliant:
identifying a second subset of endpoints of the plurality of endpoints that fail to meet the SLA definition; and
generating from the first and second subsets of endpoints a pattern of compliance indicative of changes in the states of the endpoints between the first trigger and the second trigger; and
causing display, in a user interface, SLA compliance data as a function of time, the SLA compliance data being representative of the managed network as SLA compliant or SLA non-complaint at a time of the scan.
19. The non-transitory computer-readable medium of claim 18 , wherein:
the operations further comprise defining an SLA group including a subset of endpoints in one or both of the managed network;
the scan includes automated scans of the SLA group; and
the SLA compliance data further includes data representative of whether each endpoint of the SLA group is SLA compliant or SLA non-complaint at a time of the scan.
20. The non-transitory computer-readable medium of claim 13 , wherein the product modification process includes transmission of at least one product update to a product installed at the first endpoint.
21. The non-transitory computer-readable medium of claim 13 , wherein:
the trigger event includes:
an update to content or to the product;
a notification by a service in a cloud network that is pushed to the endpoint, the notification indicating that content has been updated;
an update published to a patch catalog;
an unauthorized change to a software inventory of the endpoint in the managed network; or
an unauthorized change to a software inventory of an additional endpoint having a similar defined state; and
the SLA definition input includes:
a product update status;
a product version preference;
a preferred product being installed at the endpoint;
a vendor update installation status;
a particular patch;
implementation of an update list;
implementation of updates categorized in a particular way;
an outstanding patch; or
an outstanding vulnerability.