Granted Patent B2

US 12,452,291 · App. 18/742,570 · Granted Oct 21, 2025

Inventor: Yoav Landman (Netanya, IL)

Assignee: JFrog Ltd.

H04L63/1433G06F8/65H04L63/20

Abstract

Claims (48)

1. A method for securely updating a software release across a network, the method comprising:

compiling, by one or more processors, information sufficient to identify at least one node in the network to which the software release has been transmitted;

analyzing, by the one or more processors, one or more files comprising the software release based on vulnerability information associated with the software release;

identifying, by the one or more processors, one or more nodes at which at least one file is deployed;

analyzing, by the one or more processors, a corrective action based on the vulnerability information to verify that the corrective action does not pose a risk, the corrective action analyzed prior to initiation of the corrective action; and

initiating, by the one or more processors, the corrective action.

2. The method of claim 1 , further comprising:

initiating, by the one or more processors, transmission of a notification to an entity, where the notification includes a recommendation of one or more options for the corrective action; and

receiving, by the one or more processors, an instruction from the entity, the instruction indicating the corrective action selected from the one or more options.

3. The method of claim 2 , where the one or more options comprise generating a new software release that does not include the at least one file, rolling back the software release to a previous version, requesting a more recent version of the software release, updating a license associated with the software release, or a combination thereof.

4. The method of claim 1 , where the corrective action is automatically initiated by the one or more processors based on identification of the at least one file that poses the risk.

5. The method of claim 1 , where initiating the corrective action comprises:

generating, by the one or more processors, a new version of the software release that does not include the at least one file; and

initiating, by the one or more processors, transmission of the new version of the software release to the one or more nodes.

6. The method of claim 1 , where initiating the corrective action comprises initiating, by the one or more processors, transmission of an instruction to roll back the software release to a previous version to the one or more nodes.

7. The method of claim 1 , where initiating the corrective action comprises initiating, by the one or more processors, transmission of an instruction to download a more recent version of the software release to the one or more nodes.

8. The method of claim 1 , where initiating the corrective action comprises:

initiating, by the one or more processors, transmission of a notification to a first node of the one or more nodes that is capable of receiving user input to select between options, where the notification includes a recommendation of one or more options for the corrective action; and

initiating, by the one or more processors, transmission of a different version of the software release or an instruction for automatic performance to a second node of the one or more nodes that is not capable of receiving user input to select between the options.

9. The method of claim 1 , where entry in a transaction log indicates a set of nodes that received the software release and a set of nodes that failed to receive the software release.

10. The method of claim 1 , where compiling a transaction log comprises generating, by the one or more processors, entry in the transaction log corresponding to the software release, the entry comprising a software release identifier corresponding to the software release, a version number corresponding to the software release, release information corresponding to the software release, a time corresponding to the software release, a set of target nodes corresponding to the software release, a set of nodes that received the software release, a set of nodes that failed to receive the software release, a set of nodes operating the software release, or any combination thereof.

11. A system for securely updating a software release across a network, the system comprising:

at least one memory storing instructions; and

one or more processors coupled to the at least one memory, the one or more processors configured to execute the instructions to cause the processor to:

compile information sufficient to identify at least one node in the network to which the software release has been transmitted;

analyze one or more files comprising the software release based on vulnerability information associated with the software release;

identify one or more nodes at which at least one file is deployed;

analyze a corrective action based on the vulnerability information to verify that the corrective action does not pose a risk, the corrective action analyzed prior to initiation of the corrective action; and

initiate, the corrective action.

12. The system of claim 11 , where the vulnerability information comprises one or more checksums and license information.

13. The system of claim 11 , where the vulnerability information comprises an indication that at least one of the one or more files failed to complete one or more development stages of a development process of the software release.

14. The system of claim 11 , where a transaction log records release information associated with the software release, the release information comprising:

for at least one of the one or more files, a corresponding checksum;

a bundle checksum for an entirety of the one or more files; and

metadata associated with the software release.

15. The system of claim 11 , where a transaction log comprises a software release log, a node log, and an artifact version log.

16. The system of claim 11 , where the one or more processors are configured to analyze the one or more files periodically or upon receipt of a request from an entity.

17. A non-transitory computer-readable storage medium storing instructions that, when executed by one or more processors, cause the one or more processors to perform operations for securely updating a software release across a network, the operations comprising:

compiling information sufficient to identify at least one node in the network to which the software release has been transmitted;

analyzing one or more files comprising the software release based on vulnerability information associated with the software release;

identifying one or more nodes at which at least one file is deployed;

analyzing a corrective action based on the vulnerability information to verify that the corrective action does not pose a risk, the corrective action analyzed prior to initiation of the corrective action; and

initiating the corrective action.

18. The non-transitory computer-readable storage medium of claim 17 , where analyzing the one or more files is performed based on detection of a vulnerability-related event, the vulnerability-related event comprising receipt of additional vulnerability information, detection of a change in a license, or a combination thereof.

19. The non-transitory computer-readable storage medium of claim 17 , where the operations further comprise receiving a confirmation from the at least one node, the confirmation indicating acceptance of the software release at the at least one node.

20. The non-transitory computer-readable storage medium of claim 17 , where the operations further comprise:

receiving additional vulnerability information from a third-party data source; and

combining the additional vulnerability information with the vulnerability information, where analyzing the one or more files is performed in response to combining the additional vulnerability information with the vulnerability information.

Assignments (1)

Continuity (5)

References Cited (149)