IP Library Granted Patent US 10,956,563
Granted Patent B2
US 10,956,563 · App. 15/821,255 · Granted Mar 23, 2021

System for securing software containers with embedded agent

Inventors: Amir Gerebe (Givatayim, IL); Rani Osnat (Tel Aviv, IL)
G06F21/54G06F21/44G06F21/51H04L9/3226G06F2221/033
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,956,563
App. No.
15/821,255
Granted
Mar 23, 2021
Kind
B2
Abstract

A computer-implemented method of providing security for a software container, according to an example of the present disclosure includes, receiving a software container image with a software application and security agent that is separate from the software application. An execution entry point of the software container image that was previously configured to launch the software application has been modified to instead launch the security agent. The method includes receiving a request to instantiate the software container image as a software container, launching the security agent based on the request, authenticating the contents of the software container image, and controlling operation of the software application based on the authenticating.

Claims (60)

1. A computer-implemented method of providing security for a software container, comprising:

receiving a software container image comprising a software application and security agent that is separate from the software application, wherein an execution entry point of the software container image that was previously configured to launch the software application has been modified to instead launch the security agent;

receiving a request to instantiate the software container image as a software container;

launching the security agent based on the request;

authenticating the contents of the software container image;

preventing launch of the software application based on the authentication failing; and

based on the authentication succeeding:

launching the software application; and

controlling runtime operation of the software application from within the software container based on a security policy of the software application, wherein the controlling comprises:

implementing operating system hooks that are configured to intercept requests from the software application, wherein the operating system hooks are implemented prior to said launching the software application; and

controlling, from within the software container, whether intercepted requests of the software application are granted based on the security policy.

2. The computer-implemented method of claim 1 , wherein the operating system hooks are configured to detect one or more of:

file system access requested by the software application;

processes requested by the software application; and

network access requested by the software application.

3. The computer-implemented method of claim 1 , comprising:

receiving the security policy from a security server based on the authenticating;

transmitting a security notification from the security agent to the security server based on the software application attempting an action that violates the security policy; and

maintaining, by the security server, a log of security notifications received for the software application.

4. The computer-implemented method of claim 1 , wherein said authenticating the contents of the software container image comprises:

creating, by the security agent, a second cryptographic fingerprint based on the contents of the software container image and based on the request;

wherein said authenticating is based on a comparison of the second cryptographic fingerprint to a preexisting first cryptographic fingerprint that was previously created by the security agent based on the contents of the software container image.

5. The computer-implemented method of claim 4 , comprising:

transmitting the second cryptographic fingerprint to a security server for comparison against the preexisting first cryptographic fingerprint; and

determining whether the contents of the container image are authenticated based on a response received from the security server.

6. The computer-implemented method of claim 5 , comprising the security server:

receiving the first cryptographic fingerprint during a first time period;

receiving the second cryptographic fingerprint during a subsequent second time period;

comparing the first and second cryptographic fingerprints;

transmitting a notification to the security agent indicating that the software container image is authenticated based on the first and second cryptographic signatures matching; and

transmitting a notification to the security agent that the software container image is not authenticated based on the first and second cryptographic signatures not matching.

7. The computer-implemented method of claim 6 , comprising the security server:

transmitting a security policy for the software application to the security agent based on the first and second cryptographic signatures matching.

8. The computer-implemented method of claim 7 , comprising the security server:

determining an application type of the software application; and

selecting the security policy based on the application type.

9. The computer-implemented method of claim 8 , wherein said selecting the security policy based on the application type comprises:

selecting a default security policy of the application type for the software application based on a specific security policy for the software application not being received at the security server.

10. A computing device comprising:

memory configured to store a software container image that includes a software application and a security agent that is separate from the software application, wherein an execution entry point of the software container image that was previously configured to launch the software application has been modified to instead launch the security agent; and

a processor operatively connected to the memory and configured to:

receive a request to instantiate the software container image as a software container;

launch the security agent based on the request;

authenticate the contents of the software container image;

prevent launch of the software application based on the authentication failing; and

based on the authentication succeeding:

launch the software application; and

control runtime operation of the software application from within the software container based on a security policy of the software application, wherein to control runtime operation of the software application, the processor is configured to operate the security agent to:

implement operating system hooks that intercept requests from the software application, wherein the operating system hooks are implemented prior to launch of the software application; and

control, from within the software container, whether intercepted requests of the software application are granted based on the security policy.

11. The computing device of claim 10 , wherein the operating system hooks are configured to detect one or more of:

file system access requested by the software application;

processes requested by the software application; and

network access requested by the software application.

12. The computing device of claim 10 , wherein the processor is configured to:

operate the security agent to create a second cryptographic fingerprint based on the contents of the software container image and based on the request;

wherein the authentication is based on a comparison of the second cryptographic fingerprint to a preexisting first cryptographic fingerprint that was previously created by the security agent based on the contents of the software container image.

13. The computing device of claim 12 , wherein the processor is configured to:

transmit the second cryptographic fingerprint to a security server for comparison against the preexisting first cryptographic fingerprint; and

determine whether the contents of the container image are authenticated based on a response received from the security server.

Assignments (7)
RELEASE OF SECURITY INTEREST Recorded Aug 3, 2026
From: BANK LEUMI LE-ISRAEL B.M.
To: AQUA SECURITY SOFTWARE LTD.
Reel/Frame 075495/0666 →
SECURITY INTEREST Recorded Jul 29, 2026
From: AQUA SECURITY SOFTWARE LTD
To: HSBC BANK PLC
Reel/Frame 075441/0921 →
SECURITY INTEREST Recorded Jul 30, 2023
From: AQUA SECURITY SOFTWARE LTD
To: KREOS CAPITAL VII AGGREGATOR SCSP
Reel/Frame 064429/0026 →
SECURITY INTEREST Recorded Nov 7, 2022
From: AQUA SECURITY SOFTWARE LTD.
To: BANK LEUMI LE-ISRAEL B.M.
Reel/Frame 061668/0709 →
RELEASE OF SECURITY INTEREST Recorded Oct 27, 2022
From: SILICON VALLEY BANK
To: AQUA SECURITY SOFTWARE LTD
Reel/Frame 061567/0852 →
SECURITY INTEREST Recorded Oct 21, 2020
From: AQUA SECURITY SOFTWARE LTD.
To: SILICON VALLEY BANK
Reel/Frame 054130/0822 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2017
From: GEREBE, AMIR; OSNAT, RANI
To: AQUA SECURITY SOFTWARE, LTD.
Reel/Frame 044497/0095 →
Continuity (1)
Related Publication 20190156023A1 · May 23, 2019
Cited By (1)
US 12,450,080