SYSTEMS AND METHODS FOR PREDICTING A PLATFORM SECURITY CONDITION
A system may be configured to evaluate a state or condition of a services' stack. Some embodiments may include: monitoring, via first, second, and third sets of security tools configured to generate first, second, and third vulnerability scores, respectively, source code, a base image, and a runtime environment of each of several microservices in a stack. Each of the tools may be selectable and may comprise at least one of a scanner or sensor configured to output historical data. And the microservices may operate with respect to a same business goal or set of rules. The method may further include: iteratively predicting, via a model, a security rating for the stack of microservices based on the first, second, and third scores; and determining, based on the predicted rating, an amount of resources needed for a security team to increase the security rating via implementation of the resources.
1 . A computer-implemented method, comprising:
providing first, second, and third sets of security tools configured to generate first, second, and third vulnerability scores, respectively;
monitoring, via the first, second, and third sets of security tools, (i) source code, (ii) a base image (BI), and (iii) a runtime environment of each of a plurality of microservices in a stack, wherein each of the security tools is selectable and comprises at least one of a scanner or sensor configured to output historical data, and wherein the microservices operate with respect to a same set of operations parameters;
iteratively predicting, via a model, a security rating for the stack of microservices based on two or more of the first, second, and third scores; and
determining, based on the predicted rating, an amount of resources needed to enable a security team to increase security via implementation of the resources.
2 . The method of claim 1 , further comprising:
determining a time at which to implement a reservation of the amount of resources, the reservation comprising an assignment or scheduling of the security team's resources.
3 . The method of claim 1 , further comprising:
determining a security state for a next release of the stack of microservices.
4 . The method of claim 1 , wherein the microservices comprise one or more sets of cloud services.
5 . The method of claim 1 , further comprising:
providing a user interface (UI) configured to obtain a selection of an information technology (IT) risk level over a configurable period of time.
6 . The method of claim 1 , wherein each of the scores is an average.
7 . The method of claim 6 , further comprising:
aggregating or summing the averages with an estimated slope value and with a seasonality value associated with the slope value.
8 . The method of claim 1 , wherein each of the iterative predictions is performed within a first duration, the first duration being greater than a length of time of each of the iterations, the iterations being periodic.
9 . The method of claim 8 , wherein each of the first and second durations is configurable via the UI.
10 . The method of claim 1 , further comprising:
transmitting a notification based on the determination, wherein the amount of resources is determined based on the security rating satisfying a first criterion, and
wherein the notification enables a team of developers to be activated when, at a subsequent iteration, the security rating is predicted to satisfy a second criterion having a greater risk level than the first criterion.
11 . The method of claim 1 , wherein each of the predictions is performed to enable a first amount of false positives to increase and a second amount of false negatives to decrease.
12 . The method of claim 1 , further comprising:
tracking a change of a project state according to a release lifecycle from each layer individually, to automatically apply additional checks that exclude false positive errors in one or more security tool reports.
13 . The method of claim 8 , further comprising:
adjusting the model such that a prediction for a long-term duration is performed in a subsequent iteration, the model being a Holt-Winters model.
14 . The method of claim 1 , further comprising:
adjusting via a UI the periodicity of the iterations.
15 . A system, comprising: a memory having computer-readable instructions stored therein; and a processor configured to:
provide first, second, and third sets of security tools configured to generate first, second, and third vulnerability scores, respectively;
monitor, the via first, second, and third sets of security tools, (i) source code, (ii) a base image (BI), and (iii) a runtime environment of each of a plurality of microservices in a stack, wherein each of the security tools is selectable and comprises at least one of a scanner or sensor configured to output historical data, and wherein the microservices operate with respect to a same set of operations parameters;
iteratively predict, via a model, a security rating for the stack of microservices based on two or more of the first, second, and third scores; and
determine, based on the predicted rating, an amount of resources needed to enable a security team to increase security via implementation of the resources.
16 . The system of claim 15 , wherein the processor is further configured to:
determine a time at which to implement a reservation of the amount of resources, the reservation comprising an assignment or scheduling of the security team's resources.
17 . The system of claim 15 , wherein the processor is further configured to:
determine a security state for a next release of the stack of microservices.
18 . The system of claim 15 , wherein the microservices comprise one or more sets of cloud services.
19 . The system of claim 15 , wherein the processor is further configured to:
provide a user interface (UI) configured to obtain a selection of an information technology (IT) risk level over a configurable period of time.
20 . The system of claim 15 , wherein the processor is further configured to:
aggregate or sum averages with an estimated slope value and with a seasonality value, the seasonality value being associated with the slope value,
wherein each of the scores is one of the averages.