US9866592B2 - Policy enforcement system - Google Patents

Policy enforcement system Download PDF

Info

Publication number
US9866592B2
US9866592B2 US14/868,265 US201514868265A US9866592B2 US 9866592 B2 US9866592 B2 US 9866592B2 US 201514868265 A US201514868265 A US 201514868265A US 9866592 B2 US9866592 B2 US 9866592B2
Authority
US
United States
Prior art keywords
data
user credentials
node
policies
request
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US14/868,265
Other versions
US20170093916A1 (en
Inventor
Dilli Dorai Minnal Arumugam
Prasad Mujumdar
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Bluetalon Inc
Original Assignee
Bluetalon Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Bluetalon Inc filed Critical Bluetalon Inc
Priority to US14/868,265 priority Critical patent/US9866592B2/en
Assigned to BlueTalon, Inc. reassignment BlueTalon, Inc. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: ARUMUGAM, DILLI DORAI MINNAL, MUJUMDAR, PRASAD
Publication of US20170093916A1 publication Critical patent/US20170093916A1/en
Application granted granted Critical
Publication of US9866592B2 publication Critical patent/US9866592B2/en
Application status is Active legal-status Critical
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/20Network architectures or network communication protocols for network security for managing network security; network security policies in general
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10File systems; File servers
    • G06F16/11File system administration, e.g. details of archiving or snapshots
    • G06F16/122File system administration, e.g. details of archiving or snapshots using management policies
    • G06F17/30082
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/602Providing cryptographic facilities or services
    • GPHYSICS
    • G06COMPUTING; CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60Protecting data
    • G06F21/62Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0227Filtering policies
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0407Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the identity of one or more communicating identities is hidden
    • H04L63/0421Anonymous communication, i.e. the party's identifiers are hidden from the other party or parties, e.g. using an anonymizer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/02Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
    • H04L63/0281Proxies

Abstract

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for storing, by a policy enforcement system, a plurality of policies and data associating a plurality of user credentials with the plurality of policies; receiving, from a client device, a request for data from a file system, the request further comprising user credentials; forwarding the request for data to a second node that stores the data from the file system; receiving, from the node, the data from the file system; selecting from the plurality of policies, based on the received user credentials and the data associating the plurality of user credentials with the plurality of policies, one or more policies that correspond to the received user credentials; filtering, by the policy enforcement system, the data from the file system based on the one or more policies; and sending the filtered data to the client device.

Description

BACKGROUND

A framework, e.g., Apache Hadoop, can be deployed to manage distributed storage and distributed processing of large data sets on clusters of many computers, i.e., nodes, which may be physical or virtual. The framework can include multiple components to be run on different nodes in the cluster. Each component can be responsible for a different task. For example, a first component, e.g., Hadoop Distributed File System (HDFS), can implement a file system, and a second component, e.g., Hive, can implement a database access layer. The components work together to distribute processing of a workload of files among the nodes in the cluster.

When managing data access at the cluster, a file system component, e.g., HDFS, can include a master node, e.g., a Name Node, that manages a file system namespace and regulates access to files. The master node can store a mapping of data in the files to one or more slave nodes, e.g., Data Nodes. The slave nodes can store the files and serve read and write requests from client devices.

SUMMARY

In general, this specification describes a policy enforcement system.

In general, one innovative aspect of the subject matter described in this specification can be embodied in methods that include the actions of storing, by a policy enforcement system, a plurality of policies and data associating a plurality of user credentials with the plurality of policies; receiving, from a client device by the policy enforcement system, a request for data from a file system, the request further comprising user credentials; forwarding, by the policy enforcement system, the request to a first node; receiving, from the first node, a redirect request comprising data specifying a second node that stores the data from the file system; appending, by the policy enforcement system, the user credentials to the redirect request to generate a custom redirect request; responding to the client device with the custom redirect request; receiving, from the client device, a request for data from the second node, the request for data from the second node having the user credentials; forwarding, by the policy enforcement system, the request for data from the second node to the second node that stores the data from the file system; receiving the data from the file system from the second node; selecting from the plurality of policies, based on the received user credentials and the data associating the plurality of user credentials with the plurality of policies, one or more policies that correspond to the received user credentials; filtering, by the policy enforcement system, the data from the file system based on the one or more policies; and sending the filtered data to the client device.

Implementations can include one or more of the following features. The one or more policies cause the policy enforcement system to only include, in the filtered data, data accessible using the user credentials. Appending the user credentials to the redirect request comprises: encrypting the user credentials; and appending the encrypted user credentials to the redirect request. The data from the file system is organized by a table of columns and rows, wherein filtering the data from the file system comprises: determining, based on the one or more policies associated with the user credentials, that one or more columns of data in the table are restricted; and masking the one or more columns of data. The masking comprises encrypting or tokenizing the data. The user credentials comprise a user id and a group id, and wherein the user id is associated with a first collection of policies, and wherein the group id is associated with a second collection of policies. Prior to the storing, receiving user input at a user interface associated with the policy enforcement system, the user input specifying one or more policies associated with the user credentials. The data specifying the second node that stores the file system is an Internet Protocol address. The first node is a name node and the second node is a data node. The first node stores a database associating a file system with one or more nodes at which the file system is stored.

Another innovative aspect includes storing, by a policy enforcement system, a plurality of policies and data associating a plurality of user credentials with the plurality of policies; receiving, from a client device by the policy enforcement system, a request for data from a file system, the request further comprising user credentials; forwarding, by the policy enforcement system, the request for data to a second node that stores the data from the file system; receiving, from the node, the data from the file system; selecting from the plurality of policies, based on the received user credentials and the data associating the plurality of user credentials with the plurality of policies, one or more policies that correspond to the received user credentials; filtering, by the policy enforcement system, the data from the file system based on the one or more policies; and sending the filtered data to the client device.

Particular embodiments of the subject matter described in this specification can be implemented so as to realize one or more of the following advantages. Traditionally, a file system executes queries for data as long as users providing the queries have proper read or write access. With proper access permissions, the file system returns the data without any filters or modifications. Using policies, the policy enforcement system can mask particular portions of the data that may be sensitive, e.g., personally identifiable information such as social security numbers or dates of birth. This can provide an additional layer of privacy for user data stored in the file system. Also, when communicating with the file system, the system operates without interfering with existing communication protocols between a client and nodes within the file system.

The details of one or more embodiments of the subject matter of this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example architecture for integrating a policy enforcement system with a file system.

FIG. 2 is a diagram of how a request is processed by a policy enforcement system communicating with a file system.

FIG. 3 is a flow diagram of an example method for processing a request for data by the policy enforcement system communicating with a client and two nodes.

FIG. 4 is a flow diagram of example method for processing a request for data by the policy enforcement system communicating with a client and one node.

Like reference numbers and designations in the various drawings indicate like elements.

DETAILED DESCRIPTION

Sensitive data, such as personally identifiable data, can be stored in a file system, e.g., HDFS, in the cloud. There can be restrictions to read or write access for some users due to the sensitivity of the data. Typical file systems can, in response to a request for data without authorized user credentials, send a response indicating unauthorized access to the data. However, it can be desirable for a client device to receive a modified version of the data instead of a response indicating unauthorized access.

Thus, a policy enforcement system communicating with a file system can provide a masked version of the sensitive data. This can enable the users to access portions of the sensitive data without having the sensitive data be entirely exposed. The system is operable even where data is stored in a framework that includes name nodes and data notes, e.g., HDFS.

FIG. 1 illustrates an example architecture for integrating a policy enforcement system 104 with a file system 114. A client device 102 can communicate with the policy enforcement system 104. The client device 102 can include a memory, e.g., a random access memory (RAM), for storing instructions and data and a processor for executing stored instructions. The memory can include both read only and writable memory. For example, the client device 102 can be a computer coupled to the policy enforcement system 104 through a data communication network, e.g., local area network (LAN) or wide area network (WAN), e.g., the Internet, or a combination of networks. Communication over the network can occur using TCP/IP protocols.

The client device 102 can send a request to retrieve data from a file system 114. The request for data can be sent to the policy enforcement system 104. The policy enforcement system 104 can include one or more computers configured to implement policies for the file system.

Policies limit access to portions of data stored in the file system 114. By way of illustration, data in the file system 114 can be stored in a table of rows and columns. Some columns in the table may include data about, e.g., names, dates of birth, phone numbers, credit card information, social security numbers, or other personal information. The rows can include data about the individuals, e.g. sorted by unique identifier. Some policies allow user credentials of one particular person to access data from a column, or can allow user credentials of a group of people to access data from a column. Some other policies prevent any user from accessing complete data from a column. Policies can restrict access to these columns in the data to users with approved user credentials. This will be described in further detail with reference to FIG. 3. In some implementations, policies are applicable to other formats for the data. The other formats can include unstructured data, key-value stores, document stores, or graphs.

Thus, each policy can be associated with user credentials of one or more users. Multiple user credentials can also be associated with one policy. User credentials can include a user identification, a group identification, or both. In some implementations, the user identification is associated with a first collection of policies and the group identification is associated with a second collection of policies. These policies can be stored in an internal database of the policy enforcement system 104. An example policy can be a data structure that specifies a policy identifier, a column, and a function to be executed on the column, e.g., mask everything except the last four characters of data in the column. An example association can be stored in a table with a column for a user credential identifier and a column for a policy identifier with a user credential identifier associated with the policy identifier in the same row.

In some implementations, an administrator can generate a policy using a user interface that communicates with the policy enforcement system 104. The administrator can provide, at the user interface, user input specifying one or more policies associated with particular user credentials, and the policy enforcement system 104 can store the one or more policies and the associations in the internal database.

The policies can be used when the policy enforcement system 104 processes a request from the client device 102, which will be described further below with reference to FIGS. 2 and 3.

The file system 114 includes a name node 106 and data nodes 108-112. The name node 106 can be a master node and the data nodes 108-112 can be slave nodes. The file system 114 can be HDFS.

The name node 106 stores a mapping of data to data nodes that store the respective data. Therefore, when the name node 106 receives a request for a particular portion of data, the name node 106 can respond with a list of addresses, e.g., Internet Protocol (IP) addresses, of data nodes that store the particular portion of data based on the mapping. In some implementations, the name node 106 and the data nodes 108-112 are each on different machines.

FIG. 2 is a diagram of how a request is processed by a policy enforcement system 203 communicating with a file system 209. A client device 201 can send a request for data from the file system 209 to the policy enforcement system 203 (step 202). In some implementations, the client device 201 sends the request intended for a name node 205, but the policy enforcement system 203 intercepts the request, e.g., using IP spoofing. The request can include user credentials. In some implementations, the policy enforcement system 203 stores the user credentials in an internal database for later use. The policy enforcement system 203 can also store multiple policies in the internal database and associations of the one or more of the policies with the user credentials, e.g., using a user interface described in FIG. 1. In some implementations, the file system 209 and the policy enforcement system 203 operate on separate computers.

In some implementations, the user credentials stored in the internal database are independent of or in addition to user credentials in the file system 209 and the client device 201. That is, the policy enforcement system 203 can manage, e.g., through the user interface, user credentials that are not managed by the file system 209 or the client device 201. In some implementations, the user credentials at the policy enforcement system 203 have group identifiers or category identifiers. Policies can apply a masking function, which will be described below, to data associated with user credentials of particular group or category identifiers.

The policy enforcement system 203 can forward the request to the name node 205 of the file system 209 (step 204). The name node 205 can process the request to identify that data node 207 stores the data from the request, e.g., using a mapping of data to nodes. In some implementations, the name node 205 only processes the request upon authenticating the request using the user credentials. The name node 205 generates a redirect request including the identified data node 207 and sends the redirect request to an encryption system 209 of the policy enforcement system 203 (step 206).

The encryption system 209 can append the user credentials to the redirect request to generate a custom redirect request.

In some implementations, the encryption system 209 encrypts the user credentials and then appends the encrypted user credentials to the redirect request. The encryption system 209 can encrypt using conventional cryptographic techniques such as symmetric or public key encryption. The encryption system 209 can send the custom redirect request to the client device 201 (step 208). The client device 201 can generate and send a second request for data from the data node 207 identified by the name node 205 (step 210). The second request can be directed to an IP address for the data node 207.

The policy enforcement system 203 can receive the request for data from the data node 207 and forward the request to the data node 207 (step 212). The data node 207 can process the request by retrieving the data from the request from storage and generate a response with the retrieved data. The data node 207 can send the response to a masking system 211 of the policy enforcement system 203 (step 214).

The masking system 211 can select, e.g., from the internal database, one or more policies that are associated with the user credentials from the initial request of the client device 201, i.e., the user credentials from step 202. For example, the masking system 211 can generate a structured query language (SQL) query that retrieves the policies associated with an identifier for the user credentials. If the internal database stores multiple policies for the user credentials, the masking system 211 can apply each specified function in the respective policy to the data from the data node 207. The masking system 211 can filter the data received from the data node 207 based on the selected policies. This will be described further below with reference to FIG. 3. The policy enforcement system 203 can send the filtered data to the client device (step 201). In some implementations, the name node 205 and data node 207 send requests intended for the client device 201, but the policy enforcement system 203 intercepts the requests, e.g., using IP spoofing.

FIG. 3 is a flow diagram of an example method 300 for processing a request for data by the policy enforcement system communicating with a client and two nodes. For convenience, the method 300 will be described with respect to a system, e.g., the policy enforcement system 104 of FIG. 1, having one or more computing devices that execute software to implement the method 300.

The system stores multiple policies and data associating user credentials with the multiple policies (step 302). This can be stored in an internal database as described above. A client device sends a request for data from a file system, and the system receives the request (step 304). The request includes user credentials.

The system forwards the request to a first node (step 306). The first node can be a name node. The first node generates a redirect request and the system receives, from the first node, the redirect request (step 308). The redirect request includes data specifying at least a second node that stores the data from the file system. The second node can be a data node. The system appends the user credentials to the redirect request to generate a custom redirect request (step 310). In some implementations, the system encrypts the user credentials.

The system responds to the client device with the custom redirect request (step 312). The system receives, from the client device, a request for data from the second node (step 314). The request for data from the second node can have the encrypted user credentials. In some implementations, the system decrypts the user credentials to temporarily store the user credentials. The system forwards the request for data from the second node to the second node, which stores the data from the file system (step 316).

The second node retrieves the data from storage, and the system receives, from the second node, the data from the file system (step 318). The system selects, from multiple policies stored in the database, one or more policies that correspond to the received user credentials based on the received user credentials and the data associating the user credentials with the multiple policies (step 320).

The system filters the data from the file system based on the one or more policies (step 322). In some implementations, the system iterates through each row entry in the data from the second node and executes a string replace as specified by the one or more policies. By way of illustration, the data can be organized in a table of rows and columns in Table 1.

TABLE 1 name social-security-number date-of-birth John Smith 123-45-6789 12-34-56 Jane Smith 111-22-3333 11-22-33

The one or more policies can specify one or more columns of the table that are restricted. For example, the one or more policies can specify columns named “social-security-number” or “date-of-birth” should be masked.

The system can filter the data by masking a portion of the columns. The policy can specify the portion to be masked. Any characters in the masked portion of the column can be replaced by masking characters, e.g., ‘x’, ‘*’ or ‘#’.

The policy can also have a predicate that determines whether the data is filtered or not. For example, the predicate can be whether the data has a particular regular expression in a programming language like JavaScript. If the predicate evaluates to true, the system can mask the data. In some implementations, the system also encrypts or tokenizes the data before sending the data to the client device, e.g., using a custom encryption or tokenization function. The client device can then decrypt or detokenize the data.

By way of illustration, the policy can specify for a “social-security-number” column only a last four characters can be provided to the client device and that for a “date-of-birth” column only the year can be provided to the client device. Therefore, the system can replace any character that is not in the last four characters with an ‘x’. See Table 2.

TABLE 2 name social-security-number date-of-birth John Smith xxx-xx-6789 xx-xx-56 Jane Smith xxx-xx-3333 xx-xx-33

The system can also filter the data by simply not returning one or more columns. For example, a policy can specify that “social-security-number” column will not be provided to the client device.

The system then sends the filtered data to the client device (step 324). In this way, the system, as integrated with the file system, does not interfere with existing file retrieval protocols between client devices and file systems.

Also, the system can provide an additional level of security without requiring the client device to handle a different data structure, which minimizes cost and complexity of integrating the system. By way of illustration, the client device expects a data structure with three columns based on request for data from “name”, “social-security-number”, and “date-of-birth” columns. The system can provide a data structure with the “name”, “social-security-number”, and “date-of-birth” columns, although data within the columns are masked.

FIG. 4 is a flow diagram of example method for processing a request for data by the policy enforcement system communicating with a client and one node. With one node, the system can skip generating and forwarding redirect requests as described in FIG. 3. For convenience, the method 400 will be described with respect to a system, e.g., the policy enforcement system 104 of FIG. 1, having one or more computing devices that execute software to implement the method 400.

The system stores multiple policies and data associating user credentials with the multiple policies (step 402). This can be stored in an internal database as described above. A client device sends a request for data from a file system, and the system receives the request (step 404). The request includes user credentials. The system forwards the request for data to a node that which stores the data (step 406). The node can operate a database.

The node retrieves the data from storage, and the system receives, from the node, the data from the file system (step 408). The system selects, from multiple policies stored in the database, one or more policies that correspond to the received user credentials based on the received user credentials and the data associating the user credentials with the multiple policies (step 410).

The system filters the data from the file system based on the one or more policies (step 412), as described above with reference to FIG. 3. The system then sends the filtered data to the client device (step 414).

Embodiments of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly-embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions encoded on a tangible non-transitory program carrier for execution by, or to control the operation of, data processing apparatus. Alternatively or in addition, the program instructions can be encoded on an artificially-generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. The computer storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of one or more of them. The computer storage medium is not, however, a propagated signal.

The term “data processing apparatus” encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, or multiple processors or computers. The apparatus can include special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit). The apparatus can also include, in addition to hardware, code that creates an execution environment for the computer program in question, e.g., code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of one or more of them.

A computer program (which may also be referred to or described as a program, software, a software application, a module, a software module, a script, or code) can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data, e.g., one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files, e.g., files that store one or more modules, sub-programs, or portions of code. A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network.

As used in this specification, an “engine,” or “software engine,” refers to a software implemented input/output system that provides an output that is different from the input. An engine can be an encoded block of functionality, such as a library, a platform, a software development kit (“SDK”), or an object. Each engine can be implemented on any appropriate type of computing device, e.g., servers, mobile phones, tablet computers, notebook computers, music players, e-book readers, laptop or desktop computers, PDAs, smart phones, or other stationary or portable devices, that includes one or more processors and computer readable media. Additionally, two or more of the engines may be implemented on the same computing device, or on different computing devices.

The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).

Computers suitable for the execution of a computer program include, by way of example, can be based on general or special purpose microprocessors or both, or any other kind of central processing unit. Generally, a central processing unit will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a central processing unit for performing or executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, e.g., a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a Global Positioning System (GPS) receiver, or a portable storage device, e.g., a universal serial bus (USB) flash drive, to name just a few.

Computer-readable media suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks, e.g., internal hard disks or removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, embodiments of the subject matter described in this specification can be implemented on a computer having a display device, e.g., a CRT (cathode ray tube) monitor, an LCD (liquid crystal display) monitor, or an OLED display, for displaying information to the user, as well as input devices for providing input to the computer, e.g., a keyboard, a mouse, or a presence sensitive display or other surface. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, e.g., visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending resources to and receiving resources from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.

Embodiments of the subject matter described in this specification can be implemented in a computing system that includes a back end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front end component, e.g., a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back end, middleware, or front end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”) and a wide area network (“WAN”), e.g., the Internet.

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or of what may be claimed, but rather as descriptions of features that may be specific to particular embodiments of particular inventions. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system modules and components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Particular embodiments of the subject matter have been described. Other embodiments are within the scope of the following claims. For example, the actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain implementations, multitasking and parallel processing may be advantageous.

Claims (19)

What is claimed is:
1. A method, comprising:
storing, by a policy enforcement system, a plurality of policies and data associating a plurality of user credentials with the plurality of policies;
receiving, from a client device by the policy enforcement system, a request for data from a file system, the request further comprising user credentials;
forwarding, by the policy enforcement system, the request to a first node;
receiving, from the first node, a redirect request comprising data specifying a second node that stores the data from the file system;
appending, by the policy enforcement system, the user credentials to the redirect request to generate a custom redirect request;
responding to the client device, including sending the custom redirect request to the client device;
receiving, from the client device, a request for data from the second node, the request for data from the second node having the user credentials;
forwarding, by the policy enforcement system, the request for data from the second node to the second node that stores the data from the file system;
receiving the data from the file system from the second node;
selecting from the plurality of policies, based on the received user credentials and the data associating the plurality of user credentials with the plurality of policies, one or more policies that correspond to the received user credentials;
filtering, by the policy enforcement system, the data from the file system based on the one or more policies; and
sending the filtered data to the client device.
2. The method of claim 1, wherein the one or more policies cause the policy enforcement system to only include, in the filtered data, data accessible using the user credentials.
3. The method of claim 1, wherein appending the user credentials to the redirect request comprises:
encrypting the user credentials; and
appending the encrypted user credentials to the redirect request.
4. The method of claim 1, wherein the data from the file system is organized by a table of columns and rows, wherein filtering the data from the file system comprises:
determining, based on the one or more policies associated with the user credentials, that one or more columns of data in the table are restricted; and
masking the one or more columns of data.
5. The method of claim 4, wherein the masking comprises encrypting or tokenizing the data.
6. The method of claim 1, wherein the user credentials comprise a user id and a group id, and wherein the user id is associated with a first collection of policies, and wherein the group id is associated with a second collection of policies.
7. The method of claim 1, further comprising:
prior to the storing, receiving user input at a user interface associated with the policy enforcement system, the user input specifying one or more policies associated with the user credentials.
8. The method of claim 1, wherein the data specifying the second node that stores the file system is an Internet Protocol address.
9. The method of claim 1, wherein the first node is a name node and the second node is a data node.
10. The method of claim 1, wherein the first node stores a database associating a file system with one or more nodes at which the file system is stored.
11. A system comprising:
a client device;
a file system comprising a first node and a second node;
a policy enforcement system comprising a processor; and a non-transitory computer-readable medium coupled to the processor and having instructions stored thereon, which, when executed by the processor, cause the processor to perform operations comprising:
storing, by the policy enforcement system, a plurality of policies and data associating a plurality of user credentials with the plurality of policies;
receiving, from a client device by the policy enforcement system, a request for data from the file system, the request further comprising user credentials;
forwarding, by the policy enforcement system, the request to the first node;
receiving, from the first node, a redirect request comprising data specifying the second node that stores the data from the file system;
appending, by the policy enforcement system, the user credentials to the redirect request to generate a custom redirect request;
responding to the client device, including sending the custom redirect request to the client device;
receiving, from the client device, a request for data from the second node, the request for data from the second node having the user credentials;
forwarding, by the policy enforcement system, the request for data from the second node to the second node that stores the data from the file system;
receiving the data from the file system from the second node;
selecting from the plurality of policies, based on the received user credentials and the data associating the plurality of user credentials with the plurality of policies, one or more policies that correspond to the received user credentials;
filtering, by the policy enforcement system, the data from the file system based on the one or more policies; and
sending the filtered data to the client device.
12. The system of claim 11, wherein the one or more policies cause the policy enforcement system to only include, in the filtered data, data accessible using the user credentials.
13. The system of claim 11, wherein appending the user credentials to the redirect request comprises:
encrypting the user credentials; and
appending the encrypted user credentials to the redirect request.
14. The system of claim 11, wherein the data from the file system is organized by a table of columns and rows, wherein filtering the data from the file system comprises:
determining, based on the one or more policies associated with the user credentials, that one or more columns of data in the table are restricted; and
masking the one or more columns of data.
15. The system of claim 11, wherein the user credentials comprise a user id and a group id, and wherein the user id is associated with a first collection of policies, and wherein the group id is associated with a second collection of policies.
16. The system of claim 11, further comprising:
prior to the storing, receiving user input at a user interface associated with the policy enforcement system, the user input specifying one or more policies associated with the user credentials.
17. A non-transitory computer-readable medium having instructions stored thereon, which, when executed by a processor, cause the processor to perform operations comprising:
storing, by a policy enforcement system, a plurality of policies and data associating a plurality of user credentials with the plurality of policies;
receiving, from a client device by the policy enforcement system, a request for data from a file system, the request further comprising user credentials;
forwarding, by the policy enforcement system, the request to a first node;
receiving, from the first node, a redirect request comprising data specifying a second node that stores the data from the file system;
appending, by the policy enforcement system, the user credentials to the redirect request to generate a custom redirect request;
responding to the client device, including sending the custom redirect request to the client device;
receiving, from the client device, a request for data from the second node, the request for data from the second node having the user credentials;
forwarding, by the policy enforcement system, the request for data from the second node to the second node that stores the data from the file system;
receiving the data from the file system from the second node;
selecting from the plurality of policies, based on the received user credentials and the data associating the plurality of user credentials with the plurality of policies, one or more policies that correspond to the received user credentials;
filtering, by the policy enforcement system, the data from the file system based on the one or more policies; and
sending the filtered data to the client device.
18. The non-transitory computer-readable medium of claim 17, wherein appending the user credentials to the redirect request comprises:
encrypting the user credentials; and
appending the encrypted user credentials to the redirect request.
19. The non-transitory computer-readable medium of claim 17, wherein the data from the file system is organized by a table of columns and rows, wherein filtering the data from the file system comprises:
determining, based on the one or more policies associated with the user credentials, that one or more columns of data in the table are restricted; and
masking the one or more columns of data.
US14/868,265 2015-09-28 2015-09-28 Policy enforcement system Active 2036-05-11 US9866592B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/868,265 US9866592B2 (en) 2015-09-28 2015-09-28 Policy enforcement system

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US14/868,265 US9866592B2 (en) 2015-09-28 2015-09-28 Policy enforcement system
AU2016332734A AU2016332734A1 (en) 2015-09-28 2016-09-28 Policy enforcement system
CA3000176A CA3000176A1 (en) 2015-09-28 2016-09-28 Policy enforcement system
PCT/US2016/054107 WO2017058868A1 (en) 2015-09-28 2016-09-28 Policy enforcement system
EP16852450.2A EP3356964A4 (en) 2015-09-28 2016-09-28 Policy enforcement system
US15/864,886 US10277633B2 (en) 2015-09-28 2018-01-08 Policy enforcement system
IL258426A IL258426D0 (en) 2015-09-28 2018-03-28 Policy enforcement system
US16/397,750 US20190253460A1 (en) 2015-09-28 2019-04-29 Policy enforcement system

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US15/864,886 Continuation US10277633B2 (en) 2015-09-28 2018-01-08 Policy enforcement system

Publications (2)

Publication Number Publication Date
US20170093916A1 US20170093916A1 (en) 2017-03-30
US9866592B2 true US9866592B2 (en) 2018-01-09

Family

ID=58409449

Family Applications (3)

Application Number Title Priority Date Filing Date
US14/868,265 Active 2036-05-11 US9866592B2 (en) 2015-09-28 2015-09-28 Policy enforcement system
US15/864,886 Active US10277633B2 (en) 2015-09-28 2018-01-08 Policy enforcement system
US16/397,750 Pending US20190253460A1 (en) 2015-09-28 2019-04-29 Policy enforcement system

Family Applications After (2)

Application Number Title Priority Date Filing Date
US15/864,886 Active US10277633B2 (en) 2015-09-28 2018-01-08 Policy enforcement system
US16/397,750 Pending US20190253460A1 (en) 2015-09-28 2019-04-29 Policy enforcement system

Country Status (6)

Country Link
US (3) US9866592B2 (en)
EP (1) EP3356964A4 (en)
AU (1) AU2016332734A1 (en)
CA (1) CA3000176A1 (en)
IL (1) IL258426D0 (en)
WO (1) WO2017058868A1 (en)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10185726B2 (en) 2016-08-26 2019-01-22 BlueTalon, Inc. Access control for nested data fields
US10250723B2 (en) 2017-04-13 2019-04-02 BlueTalon, Inc. Protocol-level identity mapping
US10277633B2 (en) 2015-09-28 2019-04-30 BlueTalon, Inc. Policy enforcement system
US10291602B1 (en) 2017-04-12 2019-05-14 BlueTalon, Inc. Yarn rest API protection
US10367824B2 (en) 2016-03-04 2019-07-30 BlueTalon, Inc. Policy management, enforcement, and audit for data security
US10491635B2 (en) 2017-06-30 2019-11-26 BlueTalon, Inc. Access policies based on HDFS extended attributes

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10404757B1 (en) * 2018-06-21 2019-09-03 Bluebird Labs, Inc. Privacy enforcement in the storage and access of data in computer systems

Citations (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5537548A (en) * 1991-08-08 1996-07-16 International Business Machines Corporation Method of computer conferencing by intercepting commands issued by application programs and redirecting to all stations for execution
US20020007404A1 (en) * 2000-04-17 2002-01-17 Mark Vange System and method for network caching
US20020019828A1 (en) * 2000-06-09 2002-02-14 Mortl William M. Computer-implemented method and apparatus for obtaining permission based data
US6463470B1 (en) * 1998-10-26 2002-10-08 Cisco Technology, Inc. Method and apparatus of storing policies for policy-based management of quality of service treatments of network data traffic flows
US20020169907A1 (en) * 2001-05-10 2002-11-14 Candea George M. Methods and systems for multi-policy resource scheduling
US20030018786A1 (en) * 2001-07-17 2003-01-23 Lortz Victor B. Resource policy management
US20030021283A1 (en) * 2001-07-30 2003-01-30 See Michael E. Distributed network management system using policies
US20030046315A1 (en) * 2000-12-29 2003-03-06 International Business Machines Corporation Latches-links as virtual attachments in documents
US20030115322A1 (en) * 2001-12-13 2003-06-19 Moriconi Mark S. System and method for analyzing security policies in a distributed computer network
US6687229B1 (en) * 1998-11-06 2004-02-03 Lucent Technologies Inc Quality of service based path selection for connection-oriented networks
US20040054791A1 (en) * 2002-09-17 2004-03-18 Krishnendu Chakraborty System and method for enforcing user policies on a web server
US20040073668A1 (en) * 2002-10-10 2004-04-15 Shivaram Bhat Policy delegation for access control
US20040088560A1 (en) * 2000-04-20 2004-05-06 Danks David Hilton Secure system access
US20050021978A1 (en) * 2003-06-26 2005-01-27 Sun Microsystems, Inc. Remote interface for policy decisions governing access control
US20060053216A1 (en) * 2004-09-07 2006-03-09 Metamachinix, Inc. Clustered computer system with centralized administration
US20070124797A1 (en) * 2003-07-25 2007-05-31 Rajiv Gupta Policy based service management
US20070234408A1 (en) * 2006-03-31 2007-10-04 Novell, Inc. Methods and systems for multifactor authentication
US20080301437A1 (en) * 2005-12-13 2008-12-04 Vaccess Method of Controlling Access to a Scrambled Content
US20090049512A1 (en) 2007-08-16 2009-02-19 Verizon Data Services India Private Limited Method and system for masking data
US7542943B2 (en) * 2000-10-30 2009-06-02 Amazon Technologies, Inc. Computer services and methods for collecting payments from and providing content to web users
US7631084B2 (en) * 2001-11-02 2009-12-08 Juniper Networks, Inc. Method and system for providing secure access to private networks with client redirection
US20100024019A1 (en) * 2006-05-03 2010-01-28 Emillion Oy Authentication
US7730089B2 (en) * 1998-11-16 2010-06-01 Punch Networks Corporation Method and system for providing remote access to the facilities of a server computer
US20100281524A1 (en) * 2007-11-26 2010-11-04 Csp Innovazione Nelle Ict Scarl Authentication Method Without Credential Duplication for Users Belonging to Different Organizations
US20110209194A1 (en) * 2010-02-22 2011-08-25 Avaya Inc. Node-based policy-enforcement across mixed media, mixed-communications modalities and extensible to cloud computing such as soa
US20120198467A1 (en) * 2005-03-11 2012-08-02 Adaptive Computing Enterprises, Inc. System and Method for Enforcing Future Policies in a Compute Environment
US20130332982A1 (en) 2012-06-11 2013-12-12 Cisco Technology, Inc. System and method for identity based authentication in a distributed virtual switch network environment
US8613108B1 (en) 2009-03-26 2013-12-17 Adobe Systems Incorporated Method and apparatus for location-based digital rights management
US20140068699A1 (en) * 2012-08-31 2014-03-06 Boris Balacheff Network system for implementing a cloud platform
US20140090085A1 (en) 2012-09-26 2014-03-27 Protegrity Corporation Database access control
US20140128053A1 (en) * 2011-04-27 2014-05-08 Moses Akbar Merchant Accessing and interacting with web content and services using an external device to control a communication device
US20140351573A1 (en) * 2013-05-23 2014-11-27 Phantom Technologies, Inc. Selectively performing man in the middle decryption
US20150113010A1 (en) 2013-10-23 2015-04-23 Netapp, Inc. Distributed file system gateway
US20150128205A1 (en) * 2013-11-04 2015-05-07 Lookout, Inc. Methods and systems for secure network connections
US20160149859A1 (en) * 2006-05-25 2016-05-26 International Business Machines Corporation Managing Authentication Requests when Accessing Networks
US20160342803A1 (en) * 2015-05-19 2016-11-24 Avecto Limited Computer device and method for controlling access to a resource via a security system
US20160366220A1 (en) * 2015-06-15 2016-12-15 Yossi Gottlieb Methods, systems, and media for providing distributed database access during a network split
US20170012962A1 (en) * 2008-09-12 2017-01-12 Salesforce.Com, Inc. System, method and computer program product for enabling access to a resource utilizing a token
US20170093925A1 (en) * 2012-05-07 2017-03-30 Digital Guardian, Inc. Enhanced document and event mirroring for accessing internet content
US20170208033A1 (en) * 2013-03-07 2017-07-20 Google Inc. Low latency server-side redirection of udp-based transport protocols traversing a client-side nat firewall

Family Cites Families (57)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5708780A (en) * 1995-06-07 1998-01-13 Open Market, Inc. Internet server access control and monitoring systems
US6226372B1 (en) * 1998-12-11 2001-05-01 Securelogix Corporation Tightly integrated cooperative telecommunications firewall and scanner with distributed capabilities
JP2001273388A (en) * 2000-01-20 2001-10-05 Hitachi Ltd System and method for security management
US6826609B1 (en) * 2000-03-31 2004-11-30 Tumbleweed Communications Corp. Policy enforcement in a secure data file delivery system
US20020157023A1 (en) * 2001-03-29 2002-10-24 Callahan John R. Layering enterprise application services using semantic firewalls
JP4612779B2 (en) * 2001-06-14 2011-01-12 キヤノン株式会社 Communication device and communication device video display control method
US7317699B2 (en) * 2001-10-26 2008-01-08 Research In Motion Limited System and method for controlling configuration settings for mobile communication devices and services
US20030229848A1 (en) * 2002-06-05 2003-12-11 Udo Arend Table filtering in a computer user interface
US7631089B2 (en) * 2002-12-31 2009-12-08 Intel Corporation System for device-access policy enforcement
US20040267749A1 (en) * 2003-06-26 2004-12-30 Shivaram Bhat Resource name interface for managing policy resources
TWI229525B (en) * 2003-12-30 2005-03-11 Icp Electronic Inc A method for speeding packet filter
US7197502B2 (en) * 2004-02-18 2007-03-27 Friendly Polynomials, Inc. Machine-implemented activity management system using asynchronously shared activity data objects and journal data items
US7721328B2 (en) 2004-10-01 2010-05-18 Salesforce.Com Inc. Application identity design
US8732182B2 (en) 2004-12-02 2014-05-20 Desktopsites Inc. System and method for launching a resource in a network
US9069436B1 (en) * 2005-04-01 2015-06-30 Intralinks, Inc. System and method for information delivery based on at least one self-declared user attribute
US8670544B2 (en) * 2005-04-19 2014-03-11 Shoretel, Inc. Directory features in a distributed telephony system
CA2527550A1 (en) * 2005-11-24 2007-05-24 Oz Communications Method for securely associating data with https sessions
US7716240B2 (en) * 2005-12-29 2010-05-11 Nextlabs, Inc. Techniques and system to deploy policies intelligently
US8621549B2 (en) 2005-12-29 2013-12-31 Nextlabs, Inc. Enforcing control policies in an information management system
TWI298129B (en) 2006-01-20 2008-06-21 Hon Hai Prec Ind Co Ltd System and method for processing files distributively
US8826411B2 (en) * 2006-03-15 2014-09-02 Blue Coat Systems, Inc. Client-side extensions for use in connection with HTTP proxy policy enforcement
EP2002634B1 (en) * 2006-03-27 2014-07-02 Telecom Italia S.p.A. System for enforcing security policies on mobile communications devices
US8639896B2 (en) * 2006-08-02 2014-01-28 International Business Machines Corporation Locating and altering sensitive information in core dumps
US8542671B2 (en) * 2006-09-29 2013-09-24 Oracle International Corporation Service provider functionality with policy enforcement functional layer bound to SIP
US8185931B1 (en) * 2008-12-19 2012-05-22 Quantcast Corporation Method and system for preserving privacy related to networked media consumption activities
US20110313981A1 (en) 2010-06-17 2011-12-22 International Business Machines Corporation Data Privacy, Redaction and Integrity for Relational Databases
US8893215B2 (en) * 2010-10-29 2014-11-18 Nokia Corporation Method and apparatus for providing distributed policy management
US9589145B2 (en) * 2010-11-24 2017-03-07 Oracle International Corporation Attaching web service policies to a group of policy subjects
US8683560B1 (en) * 2010-12-29 2014-03-25 Amazon Technologies, Inc. Techniques for credential generation
US8677447B1 (en) 2011-05-25 2014-03-18 Palo Alto Networks, Inc. Identifying user names and enforcing policies
US8769692B1 (en) * 2011-07-14 2014-07-01 Mcafee, Inc. System and method for detecting malware by transforming objects and analyzing different views of objects
GB201112665D0 (en) * 2011-07-22 2011-09-07 Vodafone Ip Licensing Ltd Data anonymisation
US20140012833A1 (en) * 2011-09-13 2014-01-09 Hans-Christian Humprecht Protection of data privacy in an enterprise system
US20130091266A1 (en) * 2011-10-05 2013-04-11 Ajit Bhave System for organizing and fast searching of massive amounts of data
US9183407B2 (en) * 2011-10-28 2015-11-10 Microsoft Technology Licensing Llc Permission based query processing
US20130117313A1 (en) * 2011-11-08 2013-05-09 Microsoft Corporation Access control framework
JP5929175B2 (en) * 2011-12-27 2016-06-01 株式会社リコー Information processing apparatus, information processing system, and program
US8863297B2 (en) * 2012-01-06 2014-10-14 Mobile Iron, Inc. Secure virtual file management system
US8890375B2 (en) * 2012-07-05 2014-11-18 Aac Acoustic Technologies (Shenzhen) Co., Ltd. Multi-function vibrating device
WO2014022755A2 (en) * 2012-08-02 2014-02-06 Cellsec Limited Automated multi-level federation and enforcement of information management policies in a device network
US9105178B2 (en) * 2012-12-03 2015-08-11 Sony Computer Entertainment Inc. Remote dynamic configuration of telemetry reporting through regular expressions
US9326145B2 (en) * 2012-12-16 2016-04-26 Aruba Networks, Inc. System and method for application usage controls through policy enforcement
US10067917B2 (en) * 2013-01-31 2018-09-04 Bluebeam, Inc. Method for managing and selectively arranging sets of multiple documents and pages within documents
US9258198B2 (en) * 2013-02-12 2016-02-09 International Business Machines Corporation Dynamic generation of policy enforcement rules and actions from policy attachment semantics
US9985991B2 (en) * 2013-02-26 2018-05-29 Red Hat, Inc. HTTP password mediator
US9398102B2 (en) * 2013-03-06 2016-07-19 Netskope, Inc. Security for network delivered services
CN104216907B (en) * 2013-06-02 2018-12-18 上海诺基亚贝尔股份有限公司 It is a kind of for providing the method, apparatus and system of Access and control strategy of database
EP2843585B1 (en) * 2013-09-03 2019-08-14 Vodafone Kabel Deutschland GmbH Method and system for providing anonymised data from a database
US9722895B1 (en) * 2013-11-08 2017-08-01 Skyhigh Networks, Inc. Vendor usage monitoring and vendor usage risk analysis system
US20150221045A1 (en) * 2014-01-31 2015-08-06 Valify, LLC System and method of normalizing vendor data
TW201600997A (en) * 2014-06-30 2016-01-01 萬國商業機器公司 Method, appliance and computer program product of dynamically generating a packet inspection policy for a policy enforcement point in a centralized management environment
US9830475B2 (en) * 2014-07-15 2017-11-28 Sagesurfer Inc. Integrated collaboration platform for contextual communication
US9584517B1 (en) * 2014-09-03 2017-02-28 Amazon Technologies, Inc. Transforms within secure execution environments
US9576147B1 (en) * 2015-01-05 2017-02-21 Amazon Technologies, Inc. Security policy application through data tagging
US10114966B2 (en) * 2015-03-19 2018-10-30 Netskope, Inc. Systems and methods of per-document encryption of enterprise information stored on a cloud computing service (CCS)
US9866592B2 (en) 2015-09-28 2018-01-09 BlueTalon, Inc. Policy enforcement system
US9871825B2 (en) 2015-12-10 2018-01-16 BlueTalon, Inc. Policy enforcement for compute nodes

Patent Citations (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5537548A (en) * 1991-08-08 1996-07-16 International Business Machines Corporation Method of computer conferencing by intercepting commands issued by application programs and redirecting to all stations for execution
US6463470B1 (en) * 1998-10-26 2002-10-08 Cisco Technology, Inc. Method and apparatus of storing policies for policy-based management of quality of service treatments of network data traffic flows
US6687229B1 (en) * 1998-11-06 2004-02-03 Lucent Technologies Inc Quality of service based path selection for connection-oriented networks
US7730089B2 (en) * 1998-11-16 2010-06-01 Punch Networks Corporation Method and system for providing remote access to the facilities of a server computer
US20020007404A1 (en) * 2000-04-17 2002-01-17 Mark Vange System and method for network caching
US20040088560A1 (en) * 2000-04-20 2004-05-06 Danks David Hilton Secure system access
US20020019828A1 (en) * 2000-06-09 2002-02-14 Mortl William M. Computer-implemented method and apparatus for obtaining permission based data
US7542943B2 (en) * 2000-10-30 2009-06-02 Amazon Technologies, Inc. Computer services and methods for collecting payments from and providing content to web users
US20030046315A1 (en) * 2000-12-29 2003-03-06 International Business Machines Corporation Latches-links as virtual attachments in documents
US20020169907A1 (en) * 2001-05-10 2002-11-14 Candea George M. Methods and systems for multi-policy resource scheduling
US20030018786A1 (en) * 2001-07-17 2003-01-23 Lortz Victor B. Resource policy management
US20030021283A1 (en) * 2001-07-30 2003-01-30 See Michael E. Distributed network management system using policies
US7631084B2 (en) * 2001-11-02 2009-12-08 Juniper Networks, Inc. Method and system for providing secure access to private networks with client redirection
US20030115322A1 (en) * 2001-12-13 2003-06-19 Moriconi Mark S. System and method for analyzing security policies in a distributed computer network
US20040054791A1 (en) * 2002-09-17 2004-03-18 Krishnendu Chakraborty System and method for enforcing user policies on a web server
US20040073668A1 (en) * 2002-10-10 2004-04-15 Shivaram Bhat Policy delegation for access control
US20050021978A1 (en) * 2003-06-26 2005-01-27 Sun Microsystems, Inc. Remote interface for policy decisions governing access control
US20070124797A1 (en) * 2003-07-25 2007-05-31 Rajiv Gupta Policy based service management
US20060053216A1 (en) * 2004-09-07 2006-03-09 Metamachinix, Inc. Clustered computer system with centralized administration
US20120198467A1 (en) * 2005-03-11 2012-08-02 Adaptive Computing Enterprises, Inc. System and Method for Enforcing Future Policies in a Compute Environment
US20080301437A1 (en) * 2005-12-13 2008-12-04 Vaccess Method of Controlling Access to a Scrambled Content
US20070234408A1 (en) * 2006-03-31 2007-10-04 Novell, Inc. Methods and systems for multifactor authentication
US20100024019A1 (en) * 2006-05-03 2010-01-28 Emillion Oy Authentication
US20160149859A1 (en) * 2006-05-25 2016-05-26 International Business Machines Corporation Managing Authentication Requests when Accessing Networks
US20090049512A1 (en) 2007-08-16 2009-02-19 Verizon Data Services India Private Limited Method and system for masking data
US20100281524A1 (en) * 2007-11-26 2010-11-04 Csp Innovazione Nelle Ict Scarl Authentication Method Without Credential Duplication for Users Belonging to Different Organizations
US20170012962A1 (en) * 2008-09-12 2017-01-12 Salesforce.Com, Inc. System, method and computer program product for enabling access to a resource utilizing a token
US8613108B1 (en) 2009-03-26 2013-12-17 Adobe Systems Incorporated Method and apparatus for location-based digital rights management
US20110209194A1 (en) * 2010-02-22 2011-08-25 Avaya Inc. Node-based policy-enforcement across mixed media, mixed-communications modalities and extensible to cloud computing such as soa
US20140128053A1 (en) * 2011-04-27 2014-05-08 Moses Akbar Merchant Accessing and interacting with web content and services using an external device to control a communication device
US20170093925A1 (en) * 2012-05-07 2017-03-30 Digital Guardian, Inc. Enhanced document and event mirroring for accessing internet content
US20130332982A1 (en) 2012-06-11 2013-12-12 Cisco Technology, Inc. System and method for identity based authentication in a distributed virtual switch network environment
US20140068699A1 (en) * 2012-08-31 2014-03-06 Boris Balacheff Network system for implementing a cloud platform
US20140090085A1 (en) 2012-09-26 2014-03-27 Protegrity Corporation Database access control
US20170208033A1 (en) * 2013-03-07 2017-07-20 Google Inc. Low latency server-side redirection of udp-based transport protocols traversing a client-side nat firewall
US20140351573A1 (en) * 2013-05-23 2014-11-27 Phantom Technologies, Inc. Selectively performing man in the middle decryption
US20150113010A1 (en) 2013-10-23 2015-04-23 Netapp, Inc. Distributed file system gateway
US20150128205A1 (en) * 2013-11-04 2015-05-07 Lookout, Inc. Methods and systems for secure network connections
US20160342803A1 (en) * 2015-05-19 2016-11-24 Avecto Limited Computer device and method for controlling access to a resource via a security system
US20160366220A1 (en) * 2015-06-15 2016-12-15 Yossi Gottlieb Methods, systems, and media for providing distributed database access during a network split

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
International Application No. PCT/US2016/054107, Notification of Transmittal of the International Search Report and the Written Opinion of the International Searching Authority, dated Jan. 9, 2017, 13 pages.

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10277633B2 (en) 2015-09-28 2019-04-30 BlueTalon, Inc. Policy enforcement system
US10367824B2 (en) 2016-03-04 2019-07-30 BlueTalon, Inc. Policy management, enforcement, and audit for data security
US10185726B2 (en) 2016-08-26 2019-01-22 BlueTalon, Inc. Access control for nested data fields
US10291602B1 (en) 2017-04-12 2019-05-14 BlueTalon, Inc. Yarn rest API protection
US10250723B2 (en) 2017-04-13 2019-04-02 BlueTalon, Inc. Protocol-level identity mapping
US10491635B2 (en) 2017-06-30 2019-11-26 BlueTalon, Inc. Access policies based on HDFS extended attributes

Also Published As

Publication number Publication date
US20170093916A1 (en) 2017-03-30
EP3356964A1 (en) 2018-08-08
US20190253460A1 (en) 2019-08-15
AU2016332734A1 (en) 2018-04-26
IL258426D0 (en) 2018-05-31
EP3356964A4 (en) 2018-08-08
WO2017058868A1 (en) 2017-04-06
US20180131727A1 (en) 2018-05-10
US10277633B2 (en) 2019-04-30
CA3000176A1 (en) 2017-04-06

Similar Documents

Publication Publication Date Title
US9348648B2 (en) Providing a routing framework for facilitating dynamic workload scheduling and routing of message queues for fair management of resources for application servers in an on-demand services environment
US10257196B2 (en) Access control for a document management and collaboration system
Sun et al. Data security and privacy in cloud computing
US9294719B2 (en) Systems, methods, and apparatuses for implementing in-app live support functionality
US9202078B2 (en) Data perturbation and anonymization using one way hash
US8615528B2 (en) Cloud database sharing
EP2731041B1 (en) Computer system for storing and retrieval of encrypted data items, client computer, computer program product and computer-implemented method
US9294485B2 (en) Controlling access to shared content in an online content management system
US9069947B2 (en) Privileged account manager, access management
US8973106B2 (en) Computer implemented methods and apparatus for providing permissions to users in an on-demand service environment
US9253055B2 (en) Transparently enforcing policies in hadoop-style processing infrastructures
US9460311B2 (en) Method and system for on-the-fly anonymization on in-memory databases
US8612710B2 (en) Permissions of objects in hosted storage
CN103118053A (en) Building data security in a networked computing environment
US9160710B2 (en) Methods and systems for context-based application firewalls
Sharma et al. Securing big data hadoop: a review of security issues, threats and solution
US9176994B2 (en) Content analytics system configured to support multiple tenants
US9501762B2 (en) Application recommendation using automatically synchronized shared folders
US20110302277A1 (en) Methods and apparatus for web-based migration of data in a multi-tenant database system
US9087209B2 (en) Database access control
US8646048B2 (en) System, method and computer program product for authenticating and authorizing an external entity
US9817987B2 (en) Restricting access to content
US9647922B2 (en) Computer implemented methods and apparatus for trials onboarding
JP2019510304A (en) Technologies for discovering and managing application security
US20150121456A1 (en) Exploiting trust level lifecycle events for master data to publish security events updating identity management

Legal Events

Date Code Title Description
AS Assignment

Owner name: BLUETALON, INC., CALIFORNIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:ARUMUGAM, DILLI DORAI MINNAL;MUJUMDAR, PRASAD;SIGNING DATES FROM 20151029 TO 20151216;REEL/FRAME:037345/0461

STCF Information on status: patent grant

Free format text: PATENTED CASE