Dynamic security service extension based on software bill of materials
Techniques are described herein for dynamic service extension to provide risk mitigation upon detecting a threat. In embodiments, such techniques may be performed by a service provider platform and may comprise receiving information about a security threat, identifying one or more components susceptible to the security threat, determining, based on a software bill of materials, at least one data flow that includes a point of delivery (pod) associated with the one or more components, identifying at least one additional service determined to mitigate the security threat, and implementing the at least one additional service in relation to the at least one data flow.
1. A method comprising:
receiving, at a service provider platform, information about a security threat;
identifying, by the service provider platform, one or more components susceptible to the security threat;
determining, by the service provider platform based on a software bill of materials, at least one data flow that includes a point of delivery (pod) associated with the one or more components;
identifying, by the service provider platform, at least one additional service determined to mitigate the security threat; and
implementing, by the service provider platform, the at least one additional service in relation to the at least one data flow.
2. The method of claim 1 , wherein the information about the security threat is received from a third-party vulnerability management application.
3. The method of claim 1 , wherein the security threat comprises at least one of a software virus or software exploit.
4. The method of claim 1 , further comprising accessing the software bill of materials on a computing device that is separate from the service provider platform.
5. The method of claim 1 , wherein the software bill of materials is accessed on at least one blockchain ledger stored in relation to one or more components.
6. The method of claim 1 , wherein the at least one additional service is implemented via at least one new pod inserted into the at least one data flow, and wherein a portion of the at least one data flow is redirected to the at least one new pod.
7. The method of claim 6 , wherein the at least one additional service comprises multiple additional services, and the at least one new pod comprises multiple separate pods, each of the multiple separate pods corresponding to a respective additional service of the multiple additional services.
8. The method of claim 1 , wherein the at least one additional service is implemented via a sidecar container.
9. The method of claim 8 , wherein the sidecar container is included within a new pod, the new pod being an enhanced version of the pod associated with the one or more components.
10. A service provider computing device comprising:
one or more processors; and
one or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the service provider computing device to perform operations comprising:
receiving information about a security threat;
identifying one or more components susceptible to the security threat;
determining, based on a software bill of materials, at least one data flow that includes a point of delivery (pod) associated with the one or more components;
identifying at least one additional service determined to mitigate the security threat; and
implementing the at least one additional service in relation to the at least one data flow.
11. The service provider computing device of claim 10 , wherein the at least one additional service is implemented via at least one new pod inserted into the at least one data flow, and wherein a portion of the at least one data flow is redirected to the at least one new pod.
12. The service provider computing device of claim 11 , wherein the at least one additional service comprises multiple additional services, and the at least one new pod comprises multiple separate pods, each of the multiple separate pods corresponding to a respective additional service of the multiple additional services.
13. The service provider computing device of claim 10 , wherein the at least one additional service is implemented via a sidecar container.
14. The service provider computing device of claim 13 , wherein the sidecar container is included within a new pod, the new pod being an enhanced version of the pod associated with the one or more components.
15. The service provider computing device of claim 14 , wherein the pod associated with the one or more components is shut down after the new pod is implemented.
16. The service provider computing device of claim 10 , wherein the at least one additional service comprises a virus scanning application.
17. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
receiving information about a security threat;
identifying one or more components susceptible to the security threat;
determining, based on a software bill of materials, at least one data flow that includes a point of delivery (pod) associated with the one or more components;
identifying at least one additional service determined to mitigate the security threat; and
implementing the at least one additional service in relation to the at least one data flow.
18. The one or more non-transitory computer-readable media of claim 17 , wherein the information about the security threat is received from a third-party vulnerability management application.
19. The one or more non-transitory computer-readable media of claim 17 , wherein the security threat comprises at least one of a software virus or software exploit.
20. The one or more non-transitory computer-readable media of claim 17 , wherein the software bill of materials is accessed on at least one blockchain ledger stored in relation to one or more components.