System and method for security control over data flows in distributed computing systems
AssigneeCaber Systems, Inc.
InventorRobert Lauro Quiros
Life of this patent
Estimating the term…
Abstract
The present application generally relates to methods, systems, and programming for detecting security issues within a computing environment. In some embodiments, data flows may be analyzed to determine links between data sources and metadata. Using the derived relationships, a determination may be made as to whether the is a security issue, such as a security policy ambiguity, or a potential security issue. If so, one or more actions may be taken to prevent or minimize an impact of the security issue.
Claims1
A method of tracing application programming interface (API) requests to identify API requests made on behalf of a user in a distributed computing system, the method comprising:
- receiving, at a security controller, information regarding a plurality of API requests between multiple entities in a distributed computing system, wherein the entities include multiple microservices executing in the distributed computing system, multiple users associated with multiple client devices, and multiple data sources hosting data to be consumed by any of the entities;
- performing data tracing to identify a set of the API requests received on behalf of a first user of the users, wherein performing the data tracing includes:
- among a first set of connections between a first microservice and the client devices, identifying a first connection corresponding to a first API request from a first client device associated with the first user, wherein the first connection is identified based on user identification information associated with the first user,
- among a second set of connections between the first microservice and a second microservice, identifying a second connection corresponding to a second API request made by the first microservice in response to receiving the first API request from the first user, and
- among a third set of connections between the second microservice and a first data source, identifying a third connection corresponding to a third API request made by the second microservice in response to receiving the second API request from the second microservice, wherein the third API request is for obtaining data from the first data source on behalf of the first user, wherein the first connection, the second connection and the third connection are identified as associated with the first user based on a common connection identifier (ID) associated with the first connection, the second connection and the third connection;
- extracting, via the security controller, from the first data source, a first security policy that is indicative of whether the first user is permitted to access the data from the first data source;
- and
- responsive to determining that the user identification information associated with the first user fails to satisfy the first security policy, generating, via the security controller, an alert indicating a security policy violation.
Dependencies are inferred from the claim text.