A computer system for security of components includes at least one processor. For a new version of a component, the processor determines, based on a dataset of release events over time, a historical behavioral analysis of (i) a project that is released with prior versions of the component, and/or (ii) historical committer behavior of a committer that committed the new version of the component, and/or (iii) historical behavior of a publisher of the project. The dataset of release events includes event data collected over time regarding open source project, committers, and repository. The processor determines whether the new version of the component presents an unusual risk profile, based on the historical behavioral analysis. The processor facilitates delayed consumption of the new version of the component in response to determining that the new version of the component presents the unusual risk profile.
Legal claims defining the scope of protection, as filed with the USPTO.
2. The computer system of claim 1, wherein the processor is further configured to determine a profile of the new version of the component.
3. The computer system of claim 1, wherein the processor is further configured to determine whether the new version presents the unusual risk in response to a publish event incorporating the new version of the component.
4. The computer system of claim 3, wherein the publish event is a commit, or a release.
5. The computer system of claim 1, wherein the processor is further configured to, on a periodic basis, monitor to discover existence of the new version in a software repository, and determine whether the new version that exists presents the unusual risk responsive to discovering the existence of the new version.
6. The computer system of claim 1, wherein the processor is further configured to perform adaptive access control which facilitates delayed consumption of the new version which is determined to present the unusual risk profile.
7. The computer system of claim 1, wherein the processor is further configured to, in response to determining that the new version of the component presents the unusual risk profile, block, quarantine, or flag use of the new version.
8. The computer system of claim 1, wherein the processor is further configured to determine whether the new version of the component presents the unusual risk based on a classification change of the new version of the component, wherein the classification change includes one or both of a source code differential classification and a dependency change classification.
10. The method of claim 9, further comprising determining, by the processor, a profile of the new version of the component.
11. The method of claim 9, wherein the determining, by the processor, whether the new version presents the unusual risk is performed in response to a publish event incorporating the new version of the component.
12. The method of claim 11, wherein the publish event that triggers the determining of the unusual risk is a commit, or a release.
13. The method of claim 9, further comprising monitoring, by the processor, on a periodic basis, to discover existence of the new version in a software repository, and determining whether the new version that exists presents the unusual risk responsive to discovering the existence of the new version.
14. The method of claim 9, further comprising performing, by the processor, adaptive access control which facilitates delayed consumption of the new version which is determined to present the unusual risk profile.
15. The method of claim 9, further comprising, by the processor, in response to determining that the new version of the component presents the unusual risk profile, blocking, quarantining, or flagging use of the new version.
16. The method of claim 9, further comprising, by the processor, determining whether the new version of the component presents the unusual risk based on a classification change of the new version of the component, wherein the classification change includes one or both of a source code differential classification and a dependency change classification.
18. The non-transitory computer-readable medium of claim 17, further comprising determining a profile of the new version of the component.
19. The non-transitory computer-readable medium of claim 17, wherein the determining whether the new version presents the unusual risk is performed in response to a publish event incorporating the new version of the component.
20. The non-transitory computer-readable medium of claim 19, wherein the publish event that triggers the determining of the unusual risk is a commit, or a release.
21. The non-transitory computer-readable medium of claim 17, further comprising monitoring, on a periodic basis, to discover existence of the new version in a software repository, and determining whether the new version that exists presents the unusual risk responsive to discovering the existence of the new version.
22. The non-transitory computer-readable medium of claim 17, further comprising performing adaptive access control which facilitates delayed consumption of the new version which is determined to present the unusual risk profile.
23. The non-transitory computer-readable medium of claim 17, further comprising determining whether the new version of the component presents the unusual risk based on a classification change of the new version of the component, wherein the classification change includes one or both of a source code differential classification and a dependency change classification.
Cooperative Patent Classification codes for this invention. Click any code to explore related patents in that topic.
August 22, 2019
September 27, 2022
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.