Security risk assessment and control for code

US11822670B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-11822670-B2
Application numberUS-202016824957-A
CountryUS
Kind codeB2
Filing dateMar 20, 2020
Priority dateMay 16, 2019
Publication dateNov 21, 2023
Grant dateNov 21, 2023

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

Disclosed embodiments relate to systems and methods for automatically detecting and addressing security risks in code segments. Techniques include accessing a plurality of code segments developed for execution in a network environment, automatically identifying a first code segment from the plurality of code segments for analysis, automatically performing a first code-level security risk assessment for the first code segment, and determining a first security risk level for the first code segment based on the application programming interface risk level. The first code-level security risk assessment may be performed based on at least one of an application programming interface risk level, an embedded credentials risk level, and a target resource risk level. Further techniques may include determining a second security risk level for a modified version of the first code segment; and enabling a comparison between the first security risk level and the second security risk level.

First claim

Opening claim text (preview).

What is claimed is: 1. A non-transitory computer readable medium including instructions that, when executed by at least one processor, cause the at least one processor to perform operations for automatically detecting and addressing security risks in code segments, the operations comprising: automatically identifying a code segment included in or developed for inclusion in a body of code for execution in a network environment; scanning the code segment to identify one or more credentials coded into the code segment and one or more application programming interface action calls included in the code segment, wherein the one or more credentials are required for accessing at least one target resource; determining an embedded credentials risk level based on a quantity of the identified one or more credentials; determining an application programming interface risk level based on a type of at least one of the identified one or more application programming interface action calls, the at least one application programming interface call being directed to the at least one target resource; determining a security risk level for the code segment based on the embedded credentials risk level and the application programming interface risk level, wherein determining the security risk level includes determining whether at least one of the identified one or more credentials enables access to the at least one target resource via the at least one application programming interface action call without requiring supplemental credentials to be provided by a user; identifying an anomaly in the code segment indicating a security risk associated with the code segment; and applying, based on the identification, a control action associated with at least one of the code segment, the network environment, or an identity associated with the code segment. 2. The non-transitory computer readable medium of claim 1 , wherein identifying the anomaly comprises: identifying at least one additional code segment developed for execution in the network environment; determining a security risk level for the additional code segment; and comparing the security risk levels for the code segment and the additional code segment. 3. The non-transitory computer readable medium of claim 2 , wherein the additional code segment is included in the body of code. 4. The non-transitory computer readable medium of claim 2 , wherein the additional code segment comprises a modification of the code segment. 5. The non-transitory computer readable medium of claim 1 , wherein identifying the anomaly comprises identifying suspicious code injected into the code segment. 6. The non-transitory computer readable medium of claim 1 , wherein automatically identifying the code segment comprises dynamically scanning the network environment in real time. 7. The non-transitory computer readable medium of claim 1 , wherein the identity comprises a creator of the code segment. 8. The non-transitory computer readable medium of claim 1 , wherein the control action comprises modifying at least one authentication requirement associated with the identity. 9. The non-transitory computer readable medium of claim 1 , wherein the control action comprises modifying at least one authentication requirement associated with the code segment. 10. The non-transitory computer readable medium of claim 1 , wherein the control action comprises flagging the one or more credentials. 11. The non-transitory computer readable medium of claim 1 , wherein the control action comprises disabling the one or more credentials. 12. The non-transitory computer readable medium of claim 1 , wherein the control action comprises removing the one or more credentials from the code segment. 13. The non-transitory computer readable medium of claim 1 , wherein the control action comprises reporting the anomaly. 14. A computer-implemented method for automatically detecting and addressing security risks in code segments, the method comprising: automatically identifying a code segment included in or developed for inclusion in a body of code for execution in a network environment; scanning the code segment to identify one or more credentials coded into the code segment and one or more application programming interface action calls included in the code segment, wherein the one or more credentials are required for accessing at least one target resource; determining an embedded credentials risk level based on a quantity of the identified one or more credentials; determining an application programming interface risk level based on a type of at least one of the identified one or more application programming interface action calls, the at least one application programming interface call being directed to the at least one target resource; determining a security risk level for the code segment based on the embedded credentials risk level and the application programming interface risk level, wherein determining the security risk level includes determining whether at least one of the identified one or more credentials enables access to the at least one target resource via the at least one application programming interface action call without requiring supplemental credentials to be provided by a user; identifying an anomaly in the code segment indicating a security risk associated with the code segment; and applying, based on the identification, a control action associated with at least one of the code segment, the network environment, or an identity associated with the code segment. 15. The computer-implemented method of claim 14 , wherein identifying the anomaly comprises: identifying at least one additional code segment developed for execution in the network environment; determining a security risk level for the additional code segment; and comparing the security risk levels for the code segment and the additional code segment. 16. The computer-implemented method of claim 14 , wherein the operations further comprise updating a profile associated with a creator of the first code segment based on the security risk. 17. The computer-implemented method of claim 14 , wherein the application programming interface risk level is based on a determination of whether the one or more application programming interface action calls have security risks. 18. The computer-implemented method of claim 14 , wherein the embedded credentials risk level is determined based on a degree of privileged access associated with the one or more credentials. 19. The computer-implemented method of claim 14 , wherein the target resource risk level is determined based on a determination of whether the target resources are sensitive network resources. 20. The computer-implemented method of claim 14 , wherein applying the control action comprises reporting the anomaly.

Assignees

Inventors

Classifications

  • G06F21/577Primary

    Assessing vulnerabilities and evaluating computer system security · CPC title

  • Interprogram communication · CPC title

  • Test or assess software · CPC title

  • G06F21/563Primary

    by source code analysis · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US11822670B2 cover?
Disclosed embodiments relate to systems and methods for automatically detecting and addressing security risks in code segments. Techniques include accessing a plurality of code segments developed for execution in a network environment, automatically identifying a first code segment from the plurality of code segments for analysis, automatically performing a first code-level security risk assess…
Who is the assignee on this patent?
Cyberark Software Ltd
What technology area does this patent fall under?
Primary CPC classification G06F21/577. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Nov 21 2023 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 12 related publications on this page (citations in our corpus or others sharing the same primary CPC).