Using Expected Behavior of an Entity When Prepopulating an Adaptive Trust Profile

BACKGROUND OF THE INVENTION
Field of the Invention

The present invention relates in general to the field of computers and similar technologies, and in particular to software utilized in this field. Still more particularly, it relates to a method, system and computer-usable medium for prepopulating an adaptive trust profile.

Description of the Related Art

Users interact with physical, system, data, and services resources of all kinds, as well as each other, on a daily basis. Each of these interactions, whether accidental or intended, poses some degree of security risk, depending on the behavior of the user. In particular, the actions of a formerly trusted user may become malicious as a result of being subverted, compromised or radicalized due to any number of internal or external factors or stressors. For example, financial pressure, political idealism, irrational thoughts, or other influences may adversely affect a user's intent and/or behavior.

SUMMARY OF THE INVENTION

In one embodiment the invention relates to a method for generating a prepopulated adaptive trust profile, comprising: receiving a request to generate a prepopulated adaptive trust profile for a target entity; accessing adaptive trust profile data, the adaptive trust profile data comprising a plurality of adaptive trust profiles; identifying an adaptive trust profile relevant to the entity from the plurality of adaptive trust profiles, the adaptive trust profile relevant to the entity comprising at least one substantively similar entity characteristic to an entity characteristic of the target entity; and, generating an adaptive trust profile for the target entity using the adaptive trust profile relevant to the target entity.

In another embodiment the invention relates to a system comprising a processor; a data bus coupled to the processor; and a non-transitory, computer-readable storage medium embodying computer program code, the non-transitory, computer-readable storage medium being coupled to the data bus, the computer program code interacting with a plurality of computer operations and comprising instructions executable by the processor and configured for: receiving a request to generate a prepopulated adaptive trust profile for a target entity; accessing adaptive trust profile data, the adaptive trust profile data comprising a plurality of adaptive trust profiles; identifying an adaptive trust profile relevant to the entity from the plurality of adaptive trust profiles, the adaptive trust profile relevant to the entity comprising at least one substantively similar entity characteristic to an entity characteristic of the target entity; and, generating an adaptive trust profile for the target entity using the adaptive trust profile relevant to the target entity.

In another embodiment the invention relates to a computer-readable storage medium embodying computer program code, the computer program code comprising computer executable instructions configured for: receiving a request to generate a prepopulated adaptive trust profile for a target entity; accessing adaptive trust profile data, the adaptive trust profile data comprising a plurality of adaptive trust profiles; identifying an adaptive trust profile relevant to the entity from the plurality of adaptive trust profiles, the adaptive trust profile relevant to the entity comprising at least one substantively similar entity characteristic to an entity characteristic of the target entity; and, generating an adaptive trust profile for the target entity using the adaptive trust profile relevant to the target entity.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings. The use of the same reference number throughout the several figures designates a like or similar element.

FIG. 1 depicts an exemplary client computer in which the present invention may be implemented;

FIG. 2 is a simplified block diagram of an edge device;

FIG. 3 is a simplified block diagram of an endpoint agent;

FIG. 4 is a simplified block diagram of a security analytics system;

FIG. 5 is a simplified block diagram of a security analytics system;

FIGS. 6a and 6b show a simplified block diagram of an adaptive trust profile (ATP) and a prepopulated ATP;

FIG. 7 is simplified block diagram of process flows associated with the operation of an ATP system;

FIGS. 8a and 8b show a block diagram of a security analytics system environment;

FIG. 9 shows a functional block diagram of the operation of an ATP system;

FIG. 10 is a table showing components of an ATP;

FIG. 11 is a table showing analytic utility actions occurring during a session;

FIG. 12 is a simplified block diagram of an ATP system environment;

FIG. 13 is a generalized flowchart of the performance of session-based fingerprint generation operations;

FIGS. 14a and 14b are a generalized flowchart of the performance of ATP definition and management operations;

FIG. 15 is a simplified block diagram of a security analytics system implemented to adaptively assess risk associated with an entity behavior;

FIG. 16 is a simplified block diagram of the operation of a security analytics system to adaptively respond to an entity request;

FIG. 17 is a generalized flowchart of the performance of security analytics system operations for adaptively managing entity behavior risk;

FIG. 18 is a simplified block diagram of an ATP system to modify an existing, or generate a new, ATP.

FIGS. 19a through 19d are a generalized flowchart of the performance of ATP operations to modify an existing, or generate a new, prepopulated ATP; and

FIGS. 20a through 20c are a generalized flowchart of the performance of ATP operations to modify an existing, or generate a new, ATP for an associated entity.

DETAILED DESCRIPTION

A method, system and computer-usable medium are disclosed for using entity profile attributes to adaptively mitigate risk. Certain aspects of the invention include an appreciation that the existence of any entity, whether it is an individual user, a group of users, an organization, a device, a system, a network, an account, a domain, an operation, a process, a software application, or a service, represents some degree of security risk. Various aspects of the invention likewise include an appreciation that certain non-user entities, such as computing, communication, and surveillance devices can be a source for telemetry associated with certain events and entity behaviors. Likewise, various aspects of the invention include an appreciation that certain accounts may be global, spanning multiple devices, such as a domain-level account allowing an entity access to multiple systems. Certain aspects of the invention likewise include an appreciation that a particular account may be shared by multiple entities.

Accordingly, certain aspects of the invention include an appreciation that a particular entity can be assigned a measure of risk according to its respective attributes, associated behavioral models, and resultant inferences contained in an associated profile. As an example, a first profile may have an attribute that its corresponding entity works in the human resource department, while a second profile may have an attribute that its corresponding entity is an email server. To continue the example, the first profile may have an associated behavioral model that indicates its corresponding entity is not acting as they did the day before, while the second profile may have an associated behavioral model that indicates its corresponding entity is connecting to a suspicious IP address. To further continue the example, the first profile may have a resultant inference that its corresponding entity is likely to be leaving the company, while the second profile may have a resultant inference that there is a high probability its corresponding entity is compromised. Certain embodiments of the invention likewise include an appreciation that the measure of risk assigned to a particular entity can be adaptively revised according to corresponding changes in its respective attributes, associated behavioral models, and resultant inferences contained in an associated profile.

For the purposes of this disclosure, an information handling system may include any instrumentality or aggregate of instrumentalities operable to compute, classify, process, transmit, receive, retrieve, originate, switch, store, display, manifest, detect, record, reproduce, handle, or utilize any form of information, intelligence, or data for business, scientific, control, entertainment, or other purposes. For example, an information handling system may be a personal computer, a mobile device such as a tablet or smartphone, a consumer electronic device, a connected “smart device,” a network appliance, a network storage device, a network gateway device, a server or collection of servers or any other suitable device and may vary in size, shape, performance, functionality, and price. The information handling system may include volatile and/or non-volatile memory, and one or more processing resources such as a central processing unit (CPU) or hardware or software control logic. Additional components of the information handling system may include one or more storage systems, one or more wired or wireless interfaces for communicating with other networked devices, external devices, and various input and output (I/O) devices, such as a keyboard, a mouse, a microphone, speakers, a track pad, a touchscreen and a display device (including a touch sensitive display device). The information handling system may also include one or more buses operable to transmit communication between the various hardware components.

For the purposes of this disclosure, computer-readable media may include any instrumentality or aggregation of instrumentalities that may retain data and/or instructions for a period of time. Computer-readable media may include, without limitation, storage media such as a direct access storage device (e.g., a hard disk drive or solid state drive), a sequential access storage device (e.g., a tape disk drive), optical storage device, random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), and/or flash memory; as well as communications media such as wires, optical fibers, microwaves, radio waves, and other electromagnetic and/or optical carriers; and/or any combination of the foregoing.

FIG. 1 is a generalized illustration of an information handling system 100 that can be used to implement the system and method of the present invention. The information handling system 100 includes a processor (e.g., central processor unit or “CPU”) 102, input/output (I/O) devices 104, such as a display, a keyboard, a mouse, and associated controllers, a storage system 106, and various other subsystems 108. In various embodiments, the information handling system 100 also includes network port 110 operable to connect to a network 140, which is likewise accessible by a service provider server 142. The information handling system 100 likewise includes system memory 112, which is interconnected to the foregoing via one or more buses 114. System memory 112 further includes operating system (OS) 116 and in various embodiments may also include a security analytics system 118. In one embodiment, the information handling system 100 is able to download the security analytics system 118 from the service provider server 142. In another embodiment, the security analytics system 118 is provided as a service from the service provider server 142.

In various embodiments, the security analytics system 118 performs a security analytics operation. In certain embodiments, the security analytics operation improves processor efficiency, and thus the efficiency of the information handling system 100, by facilitating security analytics functions. As will be appreciated, once the information handling system 100 is configured to perform the security analytics operation, the information handling system 100 becomes a specialized computing device specifically configured to perform the security analytics operation and is not a general purpose computing device. Moreover, the implementation of the security analytics system 118 on the information handling system 100 improves the functionality of the information handling system 100 and provides a useful and concrete result of performing security analytics functions to mitigate security risk.

In certain embodiments, the security analytics system 118 may be implemented to include an adaptable trust profile (ATP) system 120. In certain embodiments, the ATP system 120 may be implemented to perform various ATP operations, described in greater detail herein. In certain embodiments, the ATP system 120 may be implemented to include an ATP generator 122 module, a prepopulated ATP generator 124 module, an entity data anonymization 126 module, or a combination thereof. In certain embodiments, the ATP generator 122 and prepopulated ATP generator 124 modules may be respectively implemented to generate an ATP and a prepopulated ATP, as described in greater detail herein.

In certain embodiments, the ATP generator 122 module may be implemented to use one or more prepopulated ATPs generated by the prepopulated ATP generator 124 module to generate an ATP, as likewise described in greater detail herein. In various embodiments, the entity data anonymization 126 module may be implemented to anonymize, as described in greater detail herein, certain ATP elements contained in an ATP generated by the ATP generator 122 module. In various embodiments, the entity data anonymization 126 module may be implemented to anonymize, as likewise described in greater detail herein, certain prepopulated ATP elements generated by the prepopulated ATP generator 124 module.

FIG. 2 is a simplified block diagram of an edge device implemented in accordance with an embodiment of the invention. As used herein, an edge device, such as the edge device 202 shown in FIG. 2, broadly refers to a device providing an entry point into a network 140. Examples of such edge devices 202 may include routers, routing switches, integrated access devices (IADs), multiplexers, wide-area network (WAN) access devices, and network security appliances. In certain embodiments, the network 140 may be a private network (e.g., an enterprise network), a semi-public network (e.g., a service provider core network), or a public network (e.g., the Internet).

Skilled practitioners of the art will be aware that edge devices 202 are often implemented as routers that provide authenticated access to faster, more efficient backbone and core networks. Furthermore, current industry trends include making edge devices 202 more intelligent, which allows core devices to operate at higher speed as they are not burdened with additional administrative overhead. Accordingly, such edge devices 202 often include Quality of Service (QoS) and multi-service functions to manage different types of traffic. Consequently, it is common to design core networks with switches that use routing protocols such as Open Shortest Path First (OSPF) or Multiprotocol Label Switching (MPLS) for reliability and scalability. Such approaches allow edge devices 202 to have redundant links to the core network, which not only provides improved reliability, but enables enhanced, flexible, and scalable security capabilities as well.

In certain embodiments, the edge device 202 may be implemented to include a communications/services architecture 204, various pluggable capabilities 212, a traffic router 210, and a pluggable hosting framework 208. In certain embodiments, the communications/services architecture 202 may be implemented to provide access to and from various networks 140, cloud services 206, or a combination thereof In certain embodiments, the cloud services 206 may be provided by a cloud infrastructure familiar to those of skill in the art. In certain embodiments, the edge device 202 may be implemented to provide support for a variety of generic services, such as directory integration, logging interfaces, update services, and bidirectional risk/context flows associated with various analytics. In certain embodiments, the edge device 202 may be implemented to provide temporal information, described in greater detail herein, associated with the provision of such services.

In certain embodiments, the edge device 202 may be implemented as a generic device configured to host various network communications, data processing, and security management capabilities. In certain embodiments, the pluggable hosting framework 208 may be implemented to host such capabilities in the form of pluggable capabilities 212. In certain embodiments, the pluggable capabilities 212 may include capability ‘1’ 214 (e.g., basic firewall), capability ‘2’ 216 (e.g., general web protection), capability ‘3’ 218 (e.g., data sanitization), and so forth through capability ‘n’ 220, which may include capabilities needed for a particular operation, process, or requirement on an as-needed basis. In certain embodiments, such capabilities may include the performance of operations associated with managing an adaptive trust Profile (ATP), described in greater detail herein. In certain embodiments, such operations may include the provision of associated temporal information (e.g., time stamps).

In certain embodiments, the pluggable capabilities 212 may be sourced from various cloud services 206. In certain embodiments, the pluggable hosting framework 208 may be implemented to provide certain computing and communication infrastructure components, and foundation capabilities, required by one or more of the pluggable capabilities 212. In certain embodiments, the pluggable hosting framework 208 may be implemented to allow the pluggable capabilities 212 to be dynamically invoked. Skilled practitioners of the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 3 is a simplified block diagram of an endpoint agent implemented in accordance with an embodiment of the invention. As used herein, an endpoint agent 306 broadly refers to a software agent used in combination with an endpoint device 304 to establish a protected endpoint 302. Skilled practitioners of the art will be familiar with software agents, which are computer programs that perform actions on behalf of a user or another program. In various approaches, a software agent may be autonomous or work together with another agent or a user. In certain of these approaches the software agent is implemented to autonomously decide if a particular action is appropriate for a given event, such as an observed entity behavior.

An endpoint device 304, as likewise used herein, refers to an information processing system such as a personal computer, a laptop computer, a tablet computer, a personal digital assistant (PDA), a smart phone, a mobile telephone, a digital camera, a video camera, or other device capable of storing, processing and communicating data. In certain embodiments, the communication of the data may take place in real-time or near-real-time. As used herein, real-time broadly refers to processing and providing information within a time interval brief enough to not be discernable by a user. As an example, a cellular phone conversation may be used to communicate information in real-time, while an instant message (IM) exchange may be used to communicate information in near real-time. In certain embodiments, the communication of the information may take place asynchronously. For example, an email message may be stored on an endpoint device 304 when it is offline. In this example, the information may be communicated to its intended recipient once the endpoint device 304 gains access to a network 140.

A protected endpoint 302, as likewise used herein, broadly refers to a policy-based approach to network security that typically requires endpoint devices 304 to comply with certain criteria before they are granted access to network resources. As an example, a given endpoint device 304 may be required to have a particular operating system (OS), or version thereof, a Virtual Private Network (VPN) client, anti-virus software with current updates, and so forth. In certain embodiments, the protected endpoint 302 may be implemented to perform operations associated with providing real-time resolution of the identity of an entity at a particular point in time, as described in greater detail herein. In certain embodiments, the protected endpoint 302 may be implemented to provide temporal information, such as timestamp information, associated with such operations.

In certain embodiments, the real-time resolution of the identity of an entity at a particular point in time may be based upon contextual information associated with a given entity behavior. As used herein, contextual information broadly refers to any information, directly or indirectly, individually or in combination, related to a particular entity behavior. In certain embodiments, entity behavior may include an entity's physical behavior, cyber behavior, or a combination thereof. As likewise used herein, physical behavior broadly refers to any entity behavior occurring within a physical realm. More particularly, physical behavior may include any action enacted by an entity that can be objectively observed, or indirectly inferred, within a physical realm.

As an example, a user may attempt to use an electronic access card to enter a secured building at a certain time. In this example, the use of the access card to enter the building is the action and the reading of the access card makes the user's physical behavior electronically-observable. As another example, a first user may physically transfer a document to a second user, which is captured by a video surveillance system. In this example, the physical transferal of the document from the first user to the second user is the action. Likewise, the video record of the transferal makes the first and second user's physical behavior electronically-observable. As used herein, electronically-observable entity behavior broadly refers to any behavior exhibited or enacted by an entity that can be electronically observed.

Cyber behavior, as used herein, broadly refers to any behavior occurring in cyberspace, whether enacted by an individual user, a group of users, or a system acting at the behest of an individual user, a group of users, or an entity. More particularly, cyber behavior may include physical, social, or mental actions that can be objectively observed, or indirectly inferred, within cyberspace. As an example, a user may use an endpoint device 304 to access and browse a particular website on the Internet. In this example, the individual actions performed by the user to access and browse the website constitute a cyber behavior. As another example, a user may use an endpoint device 304 to download a data file from a particular system at a particular point in time. In this example, the individual actions performed by the user to download the data file, and associated temporal information, such as a time-stamp associated with the download, constitute a cyber behavior. In these examples, the actions are enacted within cyberspace, in combination with associated temporal information, which makes them electronically-observable.

As likewise used herein, cyberspace broadly refers to a network 140 environment capable of supporting communication between two or more entities. In certain embodiments, the entity may be a user, an endpoint device 304, or various resources, described in greater detail herein. In certain embodiments, the entities may include various endpoint devices 304 or resources operating at the behest of an entity, such as a user. In certain embodiments, the communication between the entities may include audio, image, video, text, or binary data.

As described in greater detail herein, the contextual information may include a user's authentication factors. Contextual information may likewise include various temporal identity resolution factors, such as identification factors associated with the entity, the date/time/frequency of various entity behaviors, the entity's location, the entity's role or position in an organization, their associated access rights, and certain user gestures employed by a user in the enactment of a user behavior. Other contextual information may likewise include various user interactions, whether the interactions are with an endpoint device 304, a network 140, a resource, or another user. In certain embodiments, entity behaviors, and their related contextual information, may be collected at particular points of observation, and at particular points in time, described in greater detail herein. In certain embodiments, a protected endpoint 302 may be implemented as a point of observation for the collection of entity behavior and contextual information.

In certain embodiments, the endpoint agent 306 may be implemented to universally support a variety of operating systems, such as Apple Macintosh®, Microsoft Windows®, Linux®, Android® and so forth. In certain embodiments, the endpoint agent 306 may be implemented to interact with the endpoint device 304 through the use of low-level hooks 312 at the operating system level. It will be appreciated that the use of low-level hooks 312 allows the endpoint agent 306 to subscribe to multiple events through a single hook. Consequently, multiple functionalities provided by the endpoint agent 306 can share a single data stream, using only those portions of the data stream they may individually need. Accordingly, system efficiency can be improved and operational overhead reduced.

In certain embodiments, the endpoint agent 306 may be implemented to provide a common infrastructure for pluggable feature packs 308. In various embodiments, the pluggable feature packs 308 may provide certain security management functionalities. Examples of such functionalities may include various anti-virus and malware detection, data loss protection (DLP), insider threat detection, and so forth. In certain embodiments, the security management functionalities may include one or more functionalities associated with providing real-time resolution of the identity of an entity at a particular point in time, as described in greater detail herein.

In certain embodiments, a particular pluggable feature pack 308 is invoked as needed by the endpoint agent 306 to provide a given functionality. In certain embodiments, individual features of a particular pluggable feature pack 308 are invoked as needed. It will be appreciated that the ability to invoke individual features of a pluggable feature pack 308, without necessarily invoking all such features, will likely improve the operational efficiency of the endpoint agent 306 while simultaneously reducing operational overhead. Accordingly, the endpoint agent 306 can self-optimize in certain embodiments by using the common infrastructure and invoking only those pluggable components that are applicable or needed for a given user behavior.

In certain embodiments, the individual features of a pluggable feature pack 308 are invoked by the endpoint agent 306 according to the occurrence of a particular user behavior. In certain embodiments, the individual features of a pluggable feature pack 308 are invoked by the endpoint agent 306 according to the occurrence of a particular temporal event, described in greater detail herein. In certain embodiments, the individual features of a pluggable feature pack 308 are invoked by the endpoint agent 306 at a particular point in time. In these embodiments, the method by which a given user behavior, temporal event, or point in time is selected is a matter of design choice.

In certain embodiments, the individual features of a pluggable feature pack 308 may be invoked by the endpoint agent 306 according to the context of a particular user behavior. As an example, the context may be the user enacting the user behavior, their associated risk classification, which resource they may be requesting, the point in time the user behavior is enacted, and so forth. In certain embodiments, the pluggable feature packs 308 may be sourced from various cloud services 206. In certain embodiments, the pluggable feature packs 308 may be dynamically sourced from various cloud services 206 by the endpoint agent 306 on an as-need basis.

In certain embodiments, the endpoint agent 306 may be implemented with additional functionalities, such as event analytics 310. In certain embodiments, the event analytics 310 functionality may include analysis of various user behaviors, described in greater detail herein. In certain embodiments, the endpoint agent 306 may be implemented with a thin hypervisor 314, which can be run at Ring -1, thereby providing protection for the endpoint agent 306 in the event of a breach. As used herein, a thin hypervisor broadly refers to a simplified, OS-dependent hypervisor implemented to increase security. As likewise used herein, Ring-1 broadly refers to approaches allowing guest operating systems to run Ring 0 (i.e., kernel) operations without affecting other guests or the host OS. Those of skill in the art will recognize that many such embodiments and examples are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 4 is a simplified block diagram of a security analytics system implemented in accordance with an embodiment of the invention. In certain embodiments, the security analytics system 118 shown in FIG. 4 may include an event queue analytics 404 module, described in greater detail herein. In certain embodiments, the event queue analytics 404 sub-system may be implemented to include an enrichment 406 module and a streaming analytics 408 module. In certain embodiments, the security analytics system 118 may be implemented to provide log storage, reporting, and analytics capable of performing streaming 408 and on-demand 410 analytics operations. In certain embodiments, such operations may be associated with defining and managing an adaptive trust profile (ATP), detecting entity behavior that may be of analytic utility, adaptively responding to mitigate risk, or a combination thereof, as described in greater detail herein. In certain embodiments, entity behavior of analytic utility may be determined to be anomalous, abnormal, unexpected, malicious, or some combination thereof, as described in greater detail herein.

In certain embodiments, the security analytics system 118 may be implemented to provide a uniform platform for storing events and contextual information associated with various entity behaviors and performing longitudinal analytics. As used herein, longitudinal analytics broadly refers to performing analytics of entity behaviors occurring over a particular period of time. As an example, an entity may iteratively attempt to access certain proprietary information stored in various locations. In addition, the attempts may occur over a brief period of time. To continue the example, the fact that the information the entity is attempting to access is proprietary, that it is stored in various locations, and the attempts are occurring in a brief period of time, in combination, may indicate the entity behavior enacted by the entity is suspicious. As another example, certain entity identifier information (e.g., a user name) associated with an entity may change over time. In this example, a change in the entity's user name, during a particular period of time or at a particular point in time, may represent suspicious entity behavior.

In certain embodiments, the security analytics system 118 may be implemented to be scalable. In certain embodiments, the security analytics system 118 may be implemented in a centralized location, such as a corporate data center. In these embodiments, additional resources may be added to the security analytics system 118 as needs grow. In certain embodiments, the security analytics system 118 may be implemented as a distributed system. In these embodiments, the security analytics system 118 may span multiple information handling systems. In certain embodiments, the security analytics system 118 may be implemented in a cloud environment. In certain embodiments, the security analytics system 118 may be implemented in a virtual machine (VM) environment. In such embodiments, the VM environment may be configured to dynamically and seamlessly scale the security analytics system 118 as needed. Skilled practitioners of the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

In certain embodiments, an event stream collector 402 may be implemented to collect event and related contextual information, described in greater detail herein, associated with various entity behaviors. In these embodiments, the method by which the event and contextual information is selected to be collected by the event stream collector 402 is a matter of design choice. In certain embodiments, the event and contextual information collected by the event stream collector 402 may be processed by an enrichment module 406 to generate enriched entity behavior information. In certain embodiments, the enrichment may include certain contextual information related to a particular entity behavior or event. In certain embodiments, the enrichment may include certain temporal information, such as timestamp information, related to a particular entity behavior or event.

In certain embodiments, enriched entity behavior information may be provided by the enrichment module 406 to a streaming 408 analytics module. In turn, the streaming 408 analytics module may provide some or all of the enriched entity behavior information to an on-demand 410 analytics module. As used herein, streaming 408 analytics broadly refers to analytics performed in near real-time on enriched entity behavior information as it is received. Likewise, on-demand 410 analytics broadly refers herein to analytics performed, as they are requested, on enriched entity behavior information after it has been received. In certain embodiments, the enriched entity behavior information may be associated with a particular event. In certain embodiments, the enrichment 406 and streaming analytics 408 modules may be implemented to perform event queue analytics 404 operations, as described in greater detail herein.

In certain embodiments, the on-demand 410 analytics may be performed on enriched entity behavior associated with a particular interval of, or point in, time. In certain embodiments, the streaming 408 or on-demand 410 analytics may be performed on enriched entity behavior associated with a particular user, group of users, one or more non-user entities, or a combination thereof. In certain embodiments, the streaming 408 or on-demand 410 analytics may be performed on enriched entity behavior associated with a particular resource, such as a facility, system, datastore, or service. Those of skill in the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

In certain embodiments, the results of various analytics operations performed by the streaming 408 or on-demand 410 analytics modules may be provided to a storage Application Program Interface (API) 414. In turn, the storage API 412 may be implemented to provide access to various datastores ‘1’ 416 through ‘n’ 418, which in turn are used to store the results of the analytics operations. In certain embodiments, the security analytics system 118 may be implemented with a logging and reporting front-end 412, which is used to receive the results of analytics operations performed by the streaming 408 analytics module. In certain embodiments, the datastores ‘1’ 416 through ‘n’ 418 may variously include a datastore of entity identifiers, temporal events, or a combination thereof.

In certain embodiments, the security analytics system 118 may include a risk scoring 420 module implemented to perform risk scoring operations, described in greater detail herein. In certain embodiments, functionalities of the risk scoring 420 module may be provided in the form of a risk management service 422. In certain embodiments, the risk management service 422 may be implemented to perform operations associated with defining and managing an adaptive trust profile (ATP), as described in greater detail herein. In certain embodiments, the risk management service 422 may be implemented to perform operations associated with detecting entity behavior that may be of analytic utility and adaptively responding to mitigate risk, as described in greater detail herein. In certain embodiments, the risk management service 422 may be implemented to provide the results of various analytics operations performed by the streaming 406 or on-demand 408 analytics modules. In certain embodiments, the risk management service 422 may be implemented to use the storage API 412 to access various enhanced cyber behavior and analytics information stored on the datastores ‘1’ 414 through ‘n’ 416. Skilled practitioners of the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 5 is a simplified block diagram of the operation of a security analytics system implemented in accordance with an embodiment of the invention. In certain embodiments, the security analytics system 118 may be implemented to perform operations associated with detecting entity behavior that may be of analytic utility, as described in greater detail herein. In certain embodiments, the security analytics system 118 may be implemented in combination with one or more endpoint agents 306, one or more edge devices 202, various cloud services 206, and a network 140 to perform such operations.

In certain embodiments, the network edge device 202 may be implemented in a bridge, a firewall, or a passive monitoring configuration. In certain embodiments, the edge device 202 may be implemented as software running on an information handling system. In certain embodiments, the network edge device 202 may be implemented to provide integrated logging, updating and control. In certain embodiments, the edge device 202 may be implemented to receive network requests and context-sensitive user behavior information in the form of enriched user behavior information 510, described in greater detail herein, from an endpoint agent 306, likewise described in greater detail herein.

In certain embodiments, the security analytics system 118 may be implemented as both a source and a sink of user behavior information. In certain embodiments, the security analytics system 118 may be implemented to serve requests for user/resource risk data. In certain embodiments, the edge device 202 and the endpoint agent 306, individually or in combination, may provide certain entity behavior information to the security analytics system 118 using either push or pull approaches familiar to skilled practitioners of the art.

As described in greater detail herein, the edge device 202 may be implemented in certain embodiments to receive enriched user behavior information 510 from the endpoint agent 306. It will be appreciated that such enriched user behavior information 510 will likely not be available for provision to the edge device 202 when an endpoint agent 306 is not implemented for a corresponding endpoint device 304. However, the lack of such enriched user behavior information 510 may be accommodated in various embodiments, albeit with reduced functionality related to operations associated with defining and managing an entity profile, detecting entity behavior that may be normal or of analytic utility, mitigating associated risk, or a combination thereof.

In certain embodiments, a given user behavior may be enriched by an associated endpoint agent 306 attaching contextual information to a request. In certain embodiments, the context is embedded within a network request, which is then provided as enriched user behavior information 510. In certain embodiments, the contextual information may be concatenated, or appended, to a request, which in turn may be provided as enriched user behavior information 510. In these embodiments, the enriched user behavior information 510 may be unpacked upon receipt and parsed to separate the request and its associated contextual information. Certain embodiments of the invention reflect an appreciation that one possible disadvantage of such an approach is that it may perturb certain Intrusion Detection System and/or Intrusion Detection Prevention (IDS/IDP) systems implemented on a network 140.

In certain embodiments, new flow requests may be accompanied by a contextual information packet sent to the edge device 202. In these embodiments, the new flow requests may be provided as enriched user behavior information 510. In certain embodiments, the endpoint agent 306 may also send updated contextual information to the edge device 202 once it becomes available. As an example, an endpoint agent 306 may share a list of files that have been read by a current process at any point in time once the information has been collected. To continue the example, such a list of files may be used to determine which data the endpoint agent 306 may be attempting to exfiltrate.

In certain embodiments, point analytics processes executing on the edge device 202 may request a particular service. As an example, risk scores associated with a particular event on a per-user basis may be requested. In certain embodiments, the service may be requested from the security analytics system 118. In certain embodiments, the service may be requested from various cloud services 206.

In certain embodiments, contextual information associated with a particular entity behavior may be attached to various network service requests. In certain embodiments, the request may be wrapped and then handled by proxy. In certain embodiments, a small packet of contextual information associated with an entity behavior may be sent with a service request. In certain embodiments, service requests may be related to Domain Name Service (DNS), web browsing activity, email, and so forth, all of which are essentially requests for service by an endpoint device 304. In certain embodiments, such service requests may be associated with temporal event information, described in greater detail herein. Consequently, such requests can be enriched by the addition of entity behavior contextual information (e.g., UserAccount, interactive/automated, data-touched, temporal event information, etc.). Accordingly, the edge device 202 can then use this information to manage the appropriate response to submitted requests.

In certain embodiments, the security analytics system 118 may be implemented in different operational configurations. In certain embodiments, the security analytics system 118 may be implemented by using the endpoint agent 306. In certain embodiments, the security analytics system 118 may be implemented by using endpoint agent 306 in combination with the edge device 202. In certain embodiments, the cloud services 206 may likewise be implemented for use by the endpoint agent 306, the edge device 202, and the security analytics system 118, individually or in combination. In these embodiments, the security analytics system 118 may be primarily oriented to performing risk assessment operations related to entity actions, software program actions, data accesses, or a combination thereof. In certain embodiments, software program actions may be treated as a proxy for the entity.

In certain embodiments, the endpoint agent 306 may be implemented to update the security analytics system 118 with user behavior and associated contextual information, thereby allowing an offload of certain analytics processing overhead. In certain embodiments, this approach allows for longitudinal risk scoring, which assesses risk associated with certain user behavior during a particular interval of time. In certain embodiments, the security analytics system 118 may be implemented to access risk scores associated with the same user account, but accrued on different endpoint devices 304. It will be appreciated that such an approach may prove advantageous when an adversary is “moving sideways” through a network environment, using different endpoint devices 304 to collect information.

In certain embodiments, the security analytics system 118 may be primarily oriented to applying risk mitigations in a way that maximizes security effort return-on-investment (ROI). In certain embodiments, this approach may be accomplished by providing additional contextual and entity behavior information associated with entity requests. As an example, a web gateway may not concern itself with why a particular file is being requested by a certain entity at a particular point in time. Accordingly, if the file cannot be identified as malicious or harmless, there is no context available to determine how, or if, to proceed. To extend the example, the edge device 202 and security analytics system 118 may be coupled such that requests can be contextualized and fitted into a framework that evaluates their associated risk. Certain embodiments of the invention reflect an appreciation that such an approach works well with web-based data loss protection (DLP) approaches, as each transfer is no longer examined in isolation, but in the broader context of an identified entity's actions, at a particular time, on the network 140.

As another example, the security analytics system 118 may be implemented to perform risk scoring processes to decide whether to block or allow unusual flows. In various embodiments, the risk scoring processes may be implemented to include certain aspects of eXtensible Access Control Markup Language (XACML) approaches known to skilled practitioners of the art. In certain embodiments, XACML obligations may be implemented to block or allow unusual flows. In certain embodiments, an XACML obligation may be implemented as a directive from a policy decision point (PDP) to a policy enforcement point (PEP) regarding what must be performed before or after a flow is approved. Certain embodiments of the invention reflect an appreciation that such an approach is highly applicable to defending against point-of-sale (POS) malware, a breach technique that has become increasingly more common in recent years. Certain embodiments of the invention likewise reflect an appreciation that while various edge device 202 implementations may not stop all such exfiltrations, they may be able to complicate the task for the attacker.

In certain embodiments, the security analytics system 118 may be primarily oriented to maximally leverage contextual information associated with various entity behaviors within the system. In certain embodiments, data flow tracking is performed by one or more endpoint agents 306, which allows the quantity and type of information associated with particular hosts to be measured. In turn, this information may be used to determine how the edge device 202 handles requests. By contextualizing such entity behavior on the network 140, the security analytics system 118 can provide intelligent protection, making decisions that make sense in the broader context of an organization's activities. Certain embodiments of the invention reflect an appreciation that one advantage to such an approach is that information flowing through an organization, and the networks they employ, should be trackable, and substantial data breaches preventable. Skilled practitioners of the art will recognize that many such embodiments and examples are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIGS. 6a and 6b show a simplified block diagram of an adaptive trust profile and a prepopulated adaptive trust profile implemented in accordance with an embodiment of the invention. As used herein, an adaptive trust profile (ATP) 638 broadly refers to a collection of information that uniquely describes an entity's identity and their associated behavior, whether the behavior occurs within a physical realm or cyberspace. In certain embodiments, an ATP 638 may be used to adaptively draw inferences regarding the trustworthiness of an entity. In certain embodiments, as described in greater detail herein, the drawing of the inferences may involve comparing a new entity behavior to known past behaviors enacted by the entity. In certain embodiments, new entity behavior of analytic utility may represent entity behavior that represents a security risk. As likewise used herein, an entity broadly refers to something that exists as itself, whether physically or abstractly. In certain embodiments, an entity may be a user entity, a non-user entity, or a combination thereof. In certain embodiments, the identity of an entity may be known or unknown.

As used herein, a user entity broadly refers to an entity capable of enacting a user behavior, as described in greater detail herein. Examples of a user entity include an individual person, a group of people, an organization, or a government. As likewise used herein, a non-user entity broadly refers to an entity whose identity can be described and may exhibit certain behavior, but is incapable of enacting a user behavior. Examples of a non-user entity include an item, a device, such as endpoint and edge devices, a network, an account, a domain, an operation, a process, and an event. Other examples of a non-user entity include a resource, such as a geographical location or formation, a physical facility, a venue, a system, a software application, a data store, and a service, such as a service operating in a cloud environment.

Certain embodiments of the invention reflect an appreciation that being able to uniquely identity a device may assist in establishing whether or not a particular login is legitimate. As an example, user impersonations may not occur at the user's endpoint, but rather, from another device or system. Certain embodiments of the invention likewise reflect an appreciation that profiling the behavior of a particular device or system may assist in determining whether or not it is acting suspiciously.

In certain embodiments, an account may be local account, which runs on a single machine. In certain embodiments, an account may be a global account, providing access to multiple resources. In certain embodiments, a process may be implemented to run in an unattended mode, such as when backing up files or checking for software updates. Certain embodiments of the invention reflect an appreciation that it is often advantageous to track events at the process level as a method of determining which events are associated with background processes and which are initiated by a user entity.

In certain embodiments, an ATP 638 may be implemented to include a user entity profile 602, an associated user entity mindset profile 630, a non-user entity profile 632, and an entity state 636. As used herein, a user entity profile 602 broadly refers to a collection of information that uniquely describes a user entity's identity and their associated behavior, whether the behavior occurs within a physical realm or cyberspace. In certain embodiments, as described in greater detail herein, the user entity profile 602 may include user profile attributes 604, user behavior factors 610, user mindset factors 622, or a combination thereof. In certain embodiments, the user profile attributes 604 may include certain user authentication factors 606, described in greater detail herein, and personal information 608.

As used herein, a user profile attribute 604 broadly refers to data or metadata that can be used, individually or in combination with other user profile attributes 604, user behavior factors 610, or user mindset factors 622, to ascertain the identity of a user entity. In various embodiments, certain user profile attributes 604 may be uniquely associated with a particular user entity. In certain embodiments, the personal information 608 may include non-sensitive personal information associated with a user entity, such as their name, title, position, role, and responsibilities. In certain embodiments, the personal information 608 may likewise include technical skill level information, peer information, expense account information, paid time off (PTO) information, data analysis information, insider information, misconfiguration information, third party information, or a combination thereof. In certain embodiments, the personal information 608 may contain sensitive personal information associated with a user entity. As used herein, sensitive personal information (SPI), also commonly referred to as personally identifiable information (PII), broadly refers to any information usable to ascertain the identity of a user entity, either by itself, or in combination with other information, such as contextual information described in greater detail herein.

Examples of SPI may include the full or legal name of a user entity, initials or nicknames, place and date of birth, home and business addresses, personal and business telephone numbers, their gender, and other genetic information. Additional examples of SPI may include government-issued identifiers, such as a Social Security Number (SSN) or a passport number, vehicle registration plate and serial numbers, and driver's license numbers. Other examples of SPI may include certain email addresses and social media identifiers, credit and debit card numbers, and other digital identity information. Yet other examples of SPI may include employer-issued identifiers, financial transaction information, credit scores, electronic medical records (EMRs), insurance claim information, personal correspondence, and so forth. Further examples of SPI may include user authentication factors 606, such as biometrics, user identifiers and passwords, and personal identification numbers (PINs).

In certain embodiments, the SPI may include information considered by an individual user, a group of users, or an organization (e.g., a company, a government or non-government organization, etc.), to be confidential or proprietary. One example of such confidential information is protected health information (PHI). As used herein, PHI broadly refers to any information associated with the health status, provision of health care, or payment for health care that is created or collected by a “covered entity,” or an associate thereof, that can be linked to a particular individual. As used herein, a “covered entity” broadly refers to health plans, healthcare clearinghouses, healthcare providers, and others, who may electronically communicate any health-related information associated with a particular individual. Examples of such PHI may include any part of a patient's medical record, healthcare record, or payment history for medical or healthcare services.

As used herein, a user behavior factor 610 broadly refers to information associated with a user entity's behavior, whether the behavior occurs within a physical realm or cyberspace. In certain embodiments, user behavior factors 610 may include the user entity's access rights 612, the user entity's interactions 614, and the date/time/frequency 616 of when the interactions 614 are enacted. In certain embodiments, the user behavior factors 610 may likewise include the user entity's location 618, and the gestures 620 used by the user entity to enact the interactions 614.

In certain embodiments, the user entity gestures 620 may include key strokes on a keypad, a cursor movement, a mouse movement or click, a finger swipe, tap, or other hand gesture, an eye movement, or some combination thereof. In certain embodiments, the user entity gestures 620 may likewise include the cadence of the user's keystrokes, the motion, force and duration of a hand or finger gesture, the rapidity and direction of various eye movements, or some combination thereof. In certain embodiments, the user entity gestures 620 may include various audio or verbal commands performed by the user.

As used herein, user mindset factors 622 broadly refer to information used to make inferences regarding the mental state of a user entity at a particular point in time, during the occurrence of an event or an enactment of a user behavior, or a combination thereof. As likewise used herein, mental state broadly refers to a hypothetical state corresponding to the way a user entity may be thinking or feeling. Likewise, as used herein, an event broadly refers to the occurrence of action performed by an entity. In certain embodiments, the user entity mindset factors 622 may include a personality type 624. Examples of known approaches for determining a personality type 624 include Jungian types, Myers-Briggs type indicators, Keirsy Temperament Sorter, Socionics, Enneagram of Personality, and Eyseneck's three-factor model.

In certain embodiments, the user mindset factors 622 may include various behavioral biometrics 628. As used herein, a behavioral biometric 628 broadly refers to a physiological indication of a user entity's mental state. Examples of behavioral biometrics 628 may include a user entity's blood pressure, heart rate, respiratory rate, eye movements and iris dilation, facial expressions, body language, tone and pitch of voice, speech patterns, and so forth.

Certain embodiments of the invention reflect an appreciation that certain user behavior factors 610, such as user entity gestures 620, may provide additional information related to inferring a user entity's mental state. As an example, a user entering text at a quick pace with a rhythmic cadence may indicate intense focus. Likewise, an individual user intermittently entering text with forceful keystrokes may indicate the user is in an agitated state. As another example, the user may intermittently enter text somewhat languorously, which may indicate being in a thoughtful or reflective state of mind. As yet another example, the user may enter text with a light touch with an uneven cadence, which may indicate the user is hesitant or unsure of what is being entered.

Certain embodiments of the invention likewise reflect an appreciation that while the user entity gestures 620 may provide certain indications of the mental state of a particular user entity, they may not provide the reason for the user entity to be in a particular mental state. Likewise, certain embodiments of the invention include an appreciation that certain user entity gestures 620 and behavioral biometrics 628 are reflective of an individual user's personality type 624. As an example, aggressive, forceful keystrokes combined with an increased heart rate may indicate normal behavior for a particular user when composing end-of-month performance reviews. In various embodiments, certain user entity behavior factors 610, such as user gestures 620, may be correlated with certain contextual information, as described in greater detail herein.

In certain embodiments, a security analytics system 118, described in greater detail herein, may be implemented to include an adaptive trust profile (ATP) system 120. In certain embodiments, the ATP system 120 may be implemented to use a user entity profile 602 in combination with an entity state 636 to generate a user entity mindset profile 630. As used herein, entity state 636 broadly refers to the context of a particular event or entity behavior. In certain embodiments, the entity state 636 may be a long-term entity state or a short-term entity state. As used herein, a long-term entity state 636 broadly relates to an entity state 636 that persists for an extended interval of time, such as six months or a year. As likewise used herein, a short-term entity state 636 broadly relates to an entity state 636 that occurs for a brief interval of time, such as a few minutes or a day. In various embodiments, the method by which an entity state's 636 associated interval of time is considered to be long-term or short-term is a matter of design choice.

As an example, a particular user may have a primary work location, such as a branch office, and a secondary work location, such as their company's corporate office. In this example, the user's primary and secondary offices respectively correspond to the user's location 618, whereas the presence of the user at either office corresponds to an entity state 636. To continue the example, the user may consistently work at their primary office Monday through Thursday, but at their company's corporate office on Fridays. To further continue the example, the user's presence at their primary work location may be a long-term entity state 636, while their presence at their secondary work location may be a short-term entity state 636. Accordingly, a date/time/frequency 616 user entity behavior factor 614610 can likewise be associated with user behavior respectively enacted on those days, regardless of their corresponding locations. Consequently, the long-term user entity state 636 on Monday through Thursday will typically be “working at the branch office” and the short-term entity state 636 on Friday will likely be “working at the corporate office.”

As likewise used herein, a user entity mindset profile 630 broadly refers to a collection of information that reflects an inferred mental state of a user entity at a particular time during the occurrence of an event or an enactment of a user behavior. As an example, certain information may be known about a user entity, such as their name, their title and position, and so forth, all of which are user profile attributes 604. Likewise, it may be possible to observe a user entity's associated user behavior factors 610, such as their interactions with various systems, when they log-in and log-out, when they are active at the keyboard, the rhythm of their keystrokes, and which files they typically use.

Certain embodiments of the invention reflect an appreciation these behavior factors 610 can be considered to be a behavioral fingerprint. In certain embodiments, the user behavior factors 610 may change, a little or a lot, from day to day. These changes may be benign, such as when a user entity begins a new project and accesses new data, or they may indicate something more concerning, such as a user entity who is actively preparing to steal data from their employer. In certain embodiments, the user behavior factors 610 may be implemented to ascertain the identity of a user entity. In certain embodiments, the user behavior factors 610 may be uniquely associated with a particular entity.

In certain embodiments, observed user behaviors may be used to build a user entity profile 602 for a particular user or other entity. In addition to creating a model of a user's various attributes and observed behaviors, these observations can likewise be used to infer things that are not necessarily explicit. Accordingly, in certain embodiments, a behavioral fingerprint may be used in combination with an ATP 638 to generate an inference regarding an associated user entity. As an example, a particular user may be observed eating a meal, which may or may not indicate the user is hungry. However, if it is also known that the user worked at their desk throughout lunchtime and is now eating a snack during a mid-afternoon break, then it can be inferred they are indeed hungry.

As likewise used herein, a non-user entity profile 632 broadly refers to a collection of information that uniquely describes a non-user entity's identity and their associated behavior, whether the behavior occurs within a physical realm or cyberspace. In various embodiments, the non-user entity profile 632 may be implemented to include certain non-user profile attributes 634. As used herein, a non-user profile attribute 634 broadly refers to data or metadata that can be used, individually or in combination with other non-user profile attributes 634, to ascertain the identity of a non-user entity. In various embodiments, certain non-user profile attributes 634 may be uniquely associated with a particular non-user entity.

In certain embodiments, the non-user profile attributes 634 may be implemented to include certain identity information, such as a non-user entity's network, Media Access Control (MAC), or physical address, its serial number, associated configuration information, and so forth. In various embodiments, the non-user profile attributes 634 may be implemented to include non-user behavior information associated with interactions between certain user and non-user entities, the type of those interactions, the data exchanged during the interactions, the date/time/frequency of such interactions, and certain services accessed or provided.

In certain embodiments, the ATP system 120 may be implemented to include an event enrichment 680 module, an analytic utility detection 682 module, a contextualization 684 module, and a meaning derivation 686 module, or a combination thereof. In various embodiments, the event enrichment 680 module may be implemented to perform certain event enrichment operations, described in greater detail herein. In various embodiments, the analytic utility detection 682 module may be implemented to perform certain analytic utility detection operations, as likewise described in greater detail herein. In various embodiments, as described in greater detail herein, the contextualization 684 module may be implemented to perform certain contextualization operations. As likewise described in greater detail herein, the meaning derivation 686 module may be implemented to perform certain meaning derivation operations. In various embodiments, the event enrichment 680 module, the meaning derivation 686 module, the contextualization 684 module, and the analytic utility detection 686 module provide an ATP reference architecture for performing various ATP operations, described in greater detail herein.

In various embodiments, as described in greater detail herein, the ATP system 120 may be implemented to use certain data associated with an ATP 638 to derive an inference for contextualizing an electronically-observable behavior of a corresponding entity. In certain embodiments, the ATP system 120 may be implemented to use a user entity profile 602 in combination with a user entity mindset profile 632 and an associated entity state 636 to infer a user entity's intent. In certain embodiments, the ATP system 120 may be implemented to use various data stored in a repository of ATP data 690 to perform such an inference. In certain embodiments, the repository of ATP data 690 may include various ATPs 638 and associated contextual information, described in greater detail herein.

In various embodiments, the ATP system 120 may be implemented to use certain data associated with an ATP 638 to provide a probabilistic measure of whether a particular electronically-observable event is of analytic utility. In certain embodiments, an electronically-observable event that is of analytic utility may be determined to be anomalous, abnormal, unexpected, or malicious. To continue the prior example, a user may typically work out of their company's corporate office on Fridays. Furthermore, various mindset factors 622 within their associated user entity profile 602 may indicate that the user is typically relaxed and methodical when working with customer data. Moreover, the user's user entity profile 602 indicates that such interactions 614 with customer data typically occur on Monday mornings and the user rarely, if ever, copies or downloads customer data. However, the user may decide to interact with certain customer data late at night, on a Friday, while in their company's corporate office. As they do so, they exhibit an increased heart rate, rapid breathing, and furtive keystrokes while downloading a subset of customer data to a flash drive.

Consequently, their user entity mindset profile 630 may reflect a nervous, fearful, or guilty mindset, which is inconsistent with the entity state 634 of dealing with customer data in general. More particularly, downloading customer data late at night on a day the user is generally not in their primary office results in an entity state 634 that is likewise inconsistent with the user's typical user behavior. As a result, the ATP system 120 may infer that the user's behavior may represent a security threat. Those of skill in the art will recognize that many such embodiments and examples are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

Certain embodiments of the invention reflect an appreciation that the quantity, and relevancy, of information contained in a particular ATP 638 may have a direct bearing on its analytic utility when attempting to determine the trustworthiness of an associated entity and whether or not they represent a security risk. As used herein, the quantity of information contained in a particular ATP 638 broadly refers to the variety and volume of ATP elements it may contain, and the frequency of their respective instances, or occurrences, related to certain aspects of an associated entity's identity and behavior. As used herein, an ATP element broadly refers to any data element stored in an ATP 638, as described in greater detail herein. In various embodiments, an ATP element may be used to describe a particular aspect of an ATP, such as certain user profile attributes 604, user behavior factors 610, user mindset factors 622, user entity mindset profile 630, non-user profile attributes 634, and entity state 636.

In certain embodiments, statistical analysis may be performed on the information contained in a particular ATP 638 to determine the trustworthiness of its associated entity and whether or not they represent a security risk. For example, a particular authentication factor 606, such as a biometric, may be consistently used by a user entity for authenticating their identity to their endpoint device. To continue the example, a user ID and password may be used by the same, or a different user entity, in an attempt to access the endpoint device. As a result, the use of a user ID and password may indicate a security risk due to its statistical infrequency. As another example, a user entity may consistently access three different systems on a daily basis in their role as a procurement agent. In this example, the three systems may include a financial accounting system, a procurement system, and an inventory control system. To continue the example, an attempt by the procurement agent to access a sales forecast system may appear suspicious if never attempted before, even if the purpose for accessing the system is legitimate.

As likewise used herein, the relevancy of information contained in a particular ATP 638 broadly refers to the pertinence of the ATP elements it may contain to certain aspects of an associated entity's identity and behavior. To continue the prior example, an ATP 638 associated with the procurement agent may contain certain user profile attributes 604 related to their title, position, role, and responsibilities, all or which may be pertinent to whether or not they have a legitimate need to access the sales forecast system. In certain embodiments, the user profile attributes 604 may be implemented to include certain job description information. To further continue the example, such job description information may have relevance when attempting to determine whether or not the associated entity's behavior is suspicious. In further continuance of the example, job description information related to the procurement agent may include their responsibility to check sales forecast data, as needed, to ascertain whether or not to procure certain items. In these embodiments, the method by which it is determined whether the information contained in a particular ATP 638 is of sufficient quantity and relevancy is a matter of design choice.

Various embodiments of the invention likewise reflect an appreciation that accumulating sufficient information in an ATP 638 to make such a determination may take a certain amount of time. Likewise, various embodiments of the invention reflect an appreciation that the effectiveness or accuracy of such a determination may rely upon certain entity behaviors occurring with sufficient frequency, or in identifiable patterns, or a combination thereof, during a particular period of time. As an example, there may not be sufficient occurrences of a particular type of entity behavior to determine if a new entity behavior is inconsistent with known past occurrences of the same type of entity behavior.

Various embodiments of the invention reflect an appreciation that a sparsely-populated ATP 638 may likewise result in exposure to certain security vulnerabilities. Various embodiments of the invention likewise reflect an appreciation that an ATP 638 may be particularly sparsely populated when first implemented. Furthermore, the relevance of such sparsely-populated information initially contained in an ATP 638 first implemented may not prove very useful when using an ATP 638 to determine the trustworthiness of an associated entity and whether or not they represent a security risk. Accordingly, certain embodiments reflect an appreciation that the implementation of a prepopulated ATP 678 may provide a sufficient quantity of relevant information to improve the analytic utility of an ATP 638 when initially implemented. As used herein, a prepopulated ATP 678 broadly refers to a collection of information that generically describes a particular entity's expected behavior, whether the behavior occurs within a physical realm or cyberspace.

In certain embodiments, an entity's expected behavior may be determined by using one or more existing ATPs 638 associated with similarly situated entities as a reference when generating a prepopulated ATP 678. As used herein, similarly situated entities broadly refer to entities whose associated ATP 638 contain one or more ATP elements sharing substantively similar entity characteristics associated with a target entity. As likewise used herein, entity characteristics broadly refer to characteristics that can be used to distinguish certain attributes associated with a particular entity. Likewise, substantively similar entity characteristics, as used herein, broadly refer to at least one equivalent entity characteristic, such as the same job title, same job description, same role, one or more of the same duties or responsibilities, and so forth.

In various embodiments, certain personal information 608, described in greater detail herein, may be anonymized, as likewise described in greater detail herein, and used as an entity characteristic. Examples of such anonymized entity characteristics may include name, gender, geographic location, citizenship, country of origin, and so forth. In certain embodiments, certain user mindset factors 622, such as an entity's personality type 624, may likewise be anonymized and used as an entity characteristic. In certain embodiments, ATPs 638 respectively associated with a collection of distinct entities may be processed to determine their respective entity characteristics. In certain embodiments, the resulting entity characteristics may be used to segment the collection of distinct entities into one or more groups of similarly situated entities.

In various embodiments, a particular entity characteristic may correspond to a user profile attribute, a user behavior factor, or a user mindset factor contained in an ATP 638 associated with one or more similarly situated entities. As an example, an organization may employ five financial analysts, each of which has an associated ATP 638 containing information related to their observed behavior. In this example, the information respectively related to the observed behavior of the financial analysts may be aggregated and normalized to determine, in general, the expected behavior of a financial analyst.

To continue the example, the resulting information related to the expected behavior of a financial analyst can then be used as baseline behavior information for populating a prepopulated ATP 678, which in turn can be associated with a newly-hired financial analyst as their ATP 638. It will be appreciated that the implementation of such baseline behavioral information in certain embodiments may provide a basis for comparing an entity's expected behavior to their observed behavior, and as a result, assist in the identification of suspicious behavior.

As another example, a security analytics system 118 may be implemented to provide various security services, described in greater detail herein, for a large public school system. In this example, one of the employees of the school system is their head dietician. One entity characteristic of the head dietician is they are a senior administrator in a public school system. Another entity characteristic is they are responsible for defining cost-effective, nutritional meals for students. Yet another entity characteristic is they are responsible for managing a multi-million dollar budget. Yet still another entity characteristic is they manage a staff numbering in the hundreds. An additional entity characteristic is they are authorized to access the school districts enterprise resource planning (ERP) system and make adjustments to budget projections.

In this example, the first entity characteristic may be used to identify a group of similarly situated entities whose associated ATP 638 signify they are an administrator in a public school system. Likewise, the second entity characteristic may be used to further refine the group of similarly situated entities to identify those entities whose associated ATP 638 signify they have the role of dietician in a school system, with associated meal planning responsibilities. In turn, the third entity characteristic may likewise be used to yet further refine the group of similarly situated entities to identify those entities whose associated ATP 638 signify they have a yearly budget responsibility exceeding one million dollars.

Additionally, the fourth entity characteristic may be used to yet still further refine the group of similarly situated entities to identify those entities whose associated ATP 638 signify they manage at least one hundred staff members. Finally, the fifth entity characteristic may be used to yet still further refine the group of similarly situated entities to identify those entities whose associated ATP 638 signify they have the right to access systems related to making revisions to their budget projections. To continue the example, the ATPs 638 associated with the resulting group of similarly situated entities may then be used as the basis to generate a prepopulated ATP 678 for the head dietician that matches their associated entity characteristics.

Certain embodiments of the invention reflect an appreciation that it may not always be possible to identify a similarly situated entity who's associated ATP 638 signify they have the same entity characteristics as a target entity. Accordingly, the ATPs 638 associated with two or more similarly situated entities may be used in certain embodiments to generate a prepopulated ATP 678 when their respective ATPs 638 signify they have at least one of the same entity characteristics as the target entity.

To continue the preceding example, a first similarly situated entity may have an associated ATP 638 signifying they are an administrator in a public school system, they have the role of dietician in a school system, with associated meal planning responsibilities, and they have a yearly budget responsibility exceeding one million dollars. Likewise, a second similarly situated entity may have an associated ATP 638 signifying they are an administrator in a public school system, they manage at least one hundred staff members, and they have the right to access systems related to making revisions to their budget projections. In continuance of this example the ATPs 638 respectively associated with the first and second similarly situated entities may be processed to generate a prepopulated ATP 678 for the head dietician that matches their associated entity characteristics.

Certain embodiments of the invention reflect an appreciation that the two or more similarly situated entities whose respective ATPs 638 are used to generate a prepopulated ATP 678 may or may not be associated. In further continuance of the preceding example, the first and second similarly situated entities may be associated with the same school system. Conversely, the first and second similarly situated entities may be associated with different school systems. Skilled practitioners of the art will recognize that many such embodiments and examples are possible. Accordingly, the foregoing is not intended to limit the spirit, scope, or intent of the invention.

In various embodiments, a prepopulated ATP 678 may be implemented to include certain parameters describing an entity's expected behavior. In various embodiments, certain entity characteristic information, such as job titles, descriptions, roles, duties, responsibilities, and so forth, may be used to define such parameters in a prepopulated ATP 678. In certain embodiments, such entity information may be stored in a repository of entity data 692. In various embodiments, a prepopulated ATP 678 may be implemented as an ATP 638 template. In certain of these embodiments, the ATP 638 template defines which information related to an entity's identity and behavioral will be collected by the ATP 638.

In certain embodiments, the information contained in, or referenced by, a prepopulated ATP 678 may be normalized across multiple entities. In various embodiments, certain personally-identifiable information (PII), described in greater detail herein, associated with such entities may be anonymized before its inclusion in a prepopulated ATP 678. In certain embodiments, the anonymization of such PII information may be performed by an entity data anonymization 126 module.

In certain embodiments, a prepopulated ATP 678 may be implemented to mirror the structure of a corresponding ATP 638. For example, as shown in FIG. 6a, an ATP 638 may be implemented to contain a user entity profile 602, a user entity mindset profile 630, a non-user entity profile 632, and an entity state 636. As likewise shown in FIG. 6b, a corresponding prepopulated ATP 678 may be implemented to contain a prepopulated user entity profile 642, a prepopulated user entity mindset profile 670, a prepopulated non-user entity profile 672, and a prepopulated entity state 676.

As shown in FIG. 6a, the user entity profile 602 of the ATP 638 may include certain user profile attributes 604, user behavior factors 610 and user mindset factors 622. Likewise, as shown in FIG. 6b, the corresponding prepopulated ATP 738 may include certain prepopulated user profile attributes 644, prepopulated user behavior factors 650, and prepopulated user mindset factors 662. Likewise, as shown in FIG. 6a, the user profile attributes 604 may include certain ATP elements related to authentication factors 606 and personal information 608.

As likewise shown in FIG. 6a, the user behavior factors 610 may include certain ATP elements related to user access rights 612, user interactions 614, date/time/frequency 616, user location 618, and user gestures 620. Likewise, the user mindset factors 622 shown in FIG. 6a may include certain ATP elements related to personality type 624 and behavioral biometrics 626, while the non-user entity profile 632 may include certain ATP elements related to non-user profile attributes 634. Likewise, as shown in FIG. 6b, the prepopulated user profile attributes 604 may include certain prepopulated ATP elements related to prepopulated authentication factors 606 and prepopulated personal information 608.

As likewise shown in FIG. 6b, the prepopulated user behavior factors 610 may include certain prepopulated ATP elements related to prepopulated user access rights 612, prepopulated user interactions 614, prepopulated date/time/frequency 616, prepopulated user location 618, and prepopulated user gestures 620. Likewise, the prepopulated user mindset factors 622 shown in FIG. 6b may include certain prepopulated ATP elements related to prepopulated personality type 624 and prepopulated behavioral biometrics 626, while the prepopulated non-user entity profile 632 may include certain prepopulated ATP elements related to prepopulated non-user profile attributes 634.

As used herein, a prepopulated ATP element broadly refers to any data element stored in a prepopulated ATP 678. In certain embodiments, an ATP element stored in an ATP 638 associated with a particular entity may be used as a prepopulated ATP element in a corresponding prepopulated ATP 678. In certain embodiments one or more ATP elements respectively stored in one or more associate ATPs 638 may be used, individually or in combination, as prepopulated ATP elements in a prepopulated ATP 678. In certain embodiments, the entity data anonymization 126 module may be used to perform anonymization operations to anonymize certain ATP elements prior to being used as prepopulated ATP elements in a prepopulated ATP 678. Skilled practitioners of the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope, or intent of the invention.

FIG. 7 is simplified block diagram of process flows associated with the operation of an adaptive trust profile (ATP) system implemented in accordance with an embodiment of the invention. In certain embodiments, the ATP system 120 may be implemented to define and manage an ATP 638, as described in greater detail herein. In certain embodiments, the ATP 638 may be implemented to comprise a user entity profile 602, likewise described in greater detail herein. In certain embodiments, the ATP system 120 may be implemented use the resulting user entity profile 602 in combination with a particular entity state 634 to generate a user entity mindset profile 630, likewise described in greater detail herein. In certain embodiments, the ATP system 120 may be implemented to use the resulting user entity mindset profile 630 in combination with an associated user entity profile 602, non-user entity profile 632, and entity state 634 to detect entity behavior of analytic utility.

In certain embodiments, the ATP system 120 may be implemented to process certain entity information associated with defining and managing an ATP 638. As used herein, entity information broadly refers to information associated with a particular entity. In various embodiments, the entity information may include certain types of content. In certain embodiments, such content may include text, unstructured data, structured data, graphical images, photographs, audio recordings, video recordings, biometric information, and so forth. In certain embodiments, the entity information may include metadata. In certain embodiments, the metadata may include entity attributes, which in turn may include certain entity identifier types or classifications.

In various embodiments, the ATP system 120 may be implemented to use certain entity identifier information to ascertain the identity of an associated entity at a particular point in time. As used herein, entity identifier information broadly refers to an information element associated with an entity that can be used to ascertain or corroborate the identity of its corresponding entity at a particular point in time. In certain embodiments, the entity identifier information may include user authentication factors, user profile attributes, user behavior factors, user mindset factors, information associated with various endpoint and edge devices, networks, resources, or a combination thereof.

In certain embodiments, the entity identifier information may include temporal information. As used herein, temporal information broadly refers to a measure of time (e.g., a date, timestamp, etc.), a measure of an interval of time (e.g., a minute, hour, day, etc.), or a measure of an interval of time (e.g., two consecutive weekdays days, or between Jun. 3, 2017 and Mar. 4, 2018, etc.). In certain embodiments, the temporal information may be associated with an event associated with a particular point in time. As used herein, such a temporal event broadly refers to an occurrence, action or activity enacted by, or associated with, an entity at a particular point in time.

Examples of such temporal events include making a phone call, sending a text or an email, using a device, such as an endpoint device, accessing a system, and entering a physical facility. Other examples of temporal events include uploading, transferring, downloading, modifying, or deleting data, such as data stored in a datastore, or accessing a service. Yet other examples of temporal events include interactions between two or more users, interactions between a user and a device, interactions between a user and a network, and interactions between a user and a resource, whether physical or otherwise. Yet still other examples of temporal events include a change in name, address, physical location, occupation, position, role, marital status, gender, association, affiliation, or assignment.

As likewise used herein, temporal event information broadly refers to temporal information associated with a particular event. In various embodiments, the temporal event information may include certain types of content. In certain embodiments, such types of content may include text, unstructured data, structured data, graphical images, photographs, audio recordings, video recordings, and so forth. In certain embodiments, the entity information may include metadata. In various embodiments, the metadata may include temporal event attributes, which in turn may include certain entity identifier types or classifications, described in greater detail herein.

In certain embodiments, the ATP system 120 may be implemented to use information associated with such temporal resolution of an entity's identity to assess the risk associated with a particular entity, at a particular point in time, and adaptively respond with an associated response. In certain embodiments, the ATP system 120 may be implemented to respond to such assessments in order to reduce operational overhead and improve system efficiency while maintaining security integrity. In certain embodiments, the response to such assessments may be performed by a security administrator. Accordingly, certain embodiments of the invention may be directed towards assessing the risk associated with the affirmative resolution of the identity of an entity at a particular point in time in combination with its associated contextual information. Consequently, the ATP system 120 may be more oriented in various embodiments to risk adaptation than to security administration.

In certain embodiments, ATP 638 definition and management operations are begun with the receipt of information associated with event i 706. In certain embodiments, information associated with an initial event i 706 may include user profile attributes, user behavior factors, user mindset factors, entity state information, contextual information, described in greater detail herein, or a combination thereof. In various embodiments, certain user entity profile 602, user entity mindset profile 630, non-user entity profile 632, and entity state 634 data stored in a repository of ATP data 690 may be retrieved and then used to perform event enrichment 712 operations to enrich the information associated with event i 706. In certain embodiment, event enrichment 712 operations are performed by the event enrichment module 680 of the ATP system 120. Analytic utility detection 714 operations are then performed on the resulting enriched information associated with event i 706 to determine whether it is of analytic utility. In certain embodiments, analytic utility detection 714 operations are performed by the analytic utility detection module 682 of the ATP system 120.

In various embodiments, certain contextualization information stored in the repository of ATP data 690 may be retrieved and then used to perform contextualization 716 operations to provide context, based upon the entity's user entity profile 602 or non-user entity profile 632, and its associated entity state 634. In certain embodiments, contextualization 716 operations are performed by the contextualization module 684 of the ATP system 120. In certain embodiments, meaning derivation 718 operations are then performed on the contextualized information associated with event i 706 to derive meaning. In certain embodiments, meaning derivation 718 operations are performed by the meaning derivation module 686 of the ATP system. In certain embodiments, the derivation of meaning may include inferring the intent of an entity associated with event i 706. In certain embodiments, the resulting information associated with event i 706 is then used to update the user entity profile 602 or non-user entity profile 632 corresponding to the entity associated with event i 706. In certain embodiments, the process is iteratively repeated, proceeding with information associated with event i+1 708 through event i+n 710.

From the foregoing, skilled practitioners of the art will recognize that a user entity profile 602, or a non-user entity profile 632, or the two in combination, as implemented in certain embodiments, not only allows the identification of events associated with a particular entity that may be of analytic utility, but also provides higher-level data that allows for the contextualization of observed events. Accordingly, by viewing individual sets of events both in context and with a view to how they may be of analytic utility, it is possible to achieve a more nuanced and higher-level comprehension of an entity's intent.

FIGS. 8a and 8b show a block diagram of a security analytics environment implemented in accordance with an embodiment of the invention. In certain embodiments, analyses performed by a security analytics system 118 may be used to identify behavior associated with a particular entity that may be of analytic utility. In certain embodiments, the entity behavior of analytic utility may be identified at a particular point in time, during the occurrence of an event, the enactment of a user or non-user behavior, or a combination thereof

As used herein, an entity broadly refers to something that exists as itself, whether physically or abstractly. In certain embodiments, an entity may be a user entity, a non-user entity, or a combination thereof. In certain embodiments, a user entity may be an individual user, such as user ‘A’ 802 or ‘B’ 872, a group, an organization, or a government. In certain embodiments, a non-user entity may likewise be an item, a device, such as endpoint 304 and edge 202 devices, a network, such as an internal 844 and external 846 networks, a domain, an operation, or a process. In certain embodiments, a non-user entity may be a resource 850, such as a geographical location or formation, a physical facility 852, such as a venue, various physical security devices 854, a system 856, shared devices 858, such as printer, scanner, or copier, a data store 860, or a service 862, such as a service 862 operating in a cloud environment.

As likewise used herein, an event broadly refers to the occurrence of an action performed by an entity. In certain embodiments, the action may be directly associated with a user behavior, described in greater detail herein. As an example, a first user may attach a binary file infected with a virus to an email that is subsequently sent to a second user. In this example, the act of attaching the binary file to the email is directly associated with a user behavior enacted by the first user. In certain embodiments, the action may be indirectly associated with a user behavior. To continue the example, the recipient of the email may open the infected binary file, and as a result, infect their computer with malware. To further continue the example, the act of opening the infected binary file is directly associated with a user behavior enacted by the second user. However, the infection of the email recipient's computer by the infected binary file is indirectly associated with the described user behavior enacted by the second user.

In various embodiments, certain user authentication factors 606 may be used to authenticate the identity of a user entity. In certain embodiments, the user authentication factors 606 may be used to ensure that a particular user, such as user ‘A’ 802 or ‘B’ 872, is associated with their corresponding user entity profile, rather than a user entity profile associated with another user. In certain embodiments, the user authentication factors 606 may include a user's biometrics 606 (e.g., a fingerprint or retinal scan), tokens 608 (e.g., a dongle containing cryptographic keys), user identifiers and passwords (ID/PW) 610, and personal identification numbers (PINs).

In certain embodiments, information associated with such user behavior may be stored in a user entity profile, described in greater detail herein. In certain embodiments, the user entity profile may be stored in a repository of adaptive trust profile (ATP) data 690. In certain embodiments, as likewise described in greater detail herein, the user entity profile may include user profile attributes 604, user behavior factors 610, user mindset factors 622, or a combination thereof. As used herein, a user profile attribute 604 broadly refers to data or metadata that can be used, individually or in combination with other user profile attributes 604, user behavior factors 610, or user mindset factors 622, to ascertain the identity of a user entity. In various embodiments, certain user profile attributes 604 may be uniquely associated with a particular user entity.

As likewise used herein, a user behavior factor 610 broadly refers to information associated with a user's behavior, whether the behavior occurs within a physical realm or cyberspace. In certain embodiments, the user behavior factors 610 may include the user's access rights 612, the user's interactions 614, and the date/time/frequency 616 of those interactions 614. In certain embodiments, the user behavior factors 610 may likewise include the user's location 618 when the interactions 614 are enacted, and the user gestures 620 used to enact the interactions 614.

In various embodiments, certain date/time/frequency 616 user behavior factors 610 may be implemented as ontological or societal time, or a combination thereof. As used herein, ontological time broadly refers to how one instant in time relates to another in a chronological sense. As an example, a first user behavior enacted at 12:00 noon on May 17, 2017 may occur prior to a second user behavior enacted at 6:39 PM on May 18, 2018. Skilled practitioners of the art will recognize one value of ontological time is to determine the order in which various user behaviors have been enacted.

As likewise used herein, societal time broadly refers to the correlation of certain user profile attributes 604, user behavior factors 610, user mindset factors 622, or a combination thereof, to one or more instants in time. As an example, user ‘A’ 802 may access a particular system 856 to download a customer list at 3:47 PM on Nov. 3, 2017. Analysis of their user behavior profile indicates that it is not unusual for user ‘A’ 802 to download the customer list on a weekly basis. However, examination of their user behavior profile also indicates that user ‘A’ 802 forwarded the downloaded customer list in an email message to user ‘B’ 872 at 3:49 PM that same day. Furthermore, there is no record in their user behavior profile that user ‘A’ 802 has ever communicated with user ‘B’ 872 in the past. Moreover, it may be determined that user ‘B’ 872 is employed by a competitor. Accordingly, the correlation of user ‘A’ 806 downloading the customer list at one point in time, and then forwarding the customer list to user ‘B’ 872 at a second point in time shortly thereafter, is an example of societal time.

In a variation of the prior example, user ‘A’ 802 may download the customer list at 3:47 PM on Nov. 3, 2017. However, instead of immediately forwarding the customer list to user ‘B’ 872, user ‘A’ 802 leaves for a two week vacation. Upon their return, they forward the previously-downloaded customer list to user ‘B’ 872 at 9:14 AM on Nov. 20, 2017. From an ontological time perspective, it has been two weeks since user ‘A’ 802 accessed the system 856 to download the customer list. However, from a societal time perspective, they have still forwarded the customer list to user ‘B’ 872, despite two weeks having elapsed since the customer list was originally downloaded.

Accordingly, the correlation of user ‘A’ 802 downloading the customer list at one point in time, and then forwarding the customer list to user ‘B’ 872 at a much later point in time, is another example of societal time. More particularly, it may be inferred that the intent of user ‘A’ 802 did not change during the two weeks they were on vacation. Furthermore, user ‘A’ 802 may have attempted to mask an intended malicious act by letting some period of time elapse between the time they originally downloaded the customer list and when they eventually forwarded it to user ‘B’ 872. From the foregoing, those of skill in the art will recognize that the use of societal time may be advantageous in determining whether a particular entity behavior is of analytic utility. As used herein, mindset factors 622 broadly refer to information used to infer the mental state of a user at a particular point in time, during the occurrence of an event, an enactment of a user behavior, or combination thereof.

In certain embodiments, the security analytics system 118 may be implemented to process certain entity information, described in greater detail herein, associated with providing resolution of the identity of an entity at a particular point in time. In various embodiments, the security analytics system 118 may be implemented to use certain entity identifier information, likewise described in greater detail herein, to ascertain the identity of an associated entity at a particular point in time. In various embodiments, the entity identifier information may include certain temporal information, described in greater detail herein. In certain embodiments, the temporal information may be associated with an event associated with a particular point in time.

In certain embodiments, the security analytics system 118 may be implemented to use information associated with certain user behavior elements to resolve the identity of an entity at a particular point in time. A user behavior element, as used herein, broadly refers to a discrete element of a user entity's behavior during the performance of a particular operation in a physical realm, cyberspace, or a combination thereof. In certain embodiments, such user behavior elements may be associated with a user/device 830, a user/network 842, a user/resource 848, a user/user 860 interaction, or a combination thereof.

As an example, user ‘A’ 802 may use an endpoint device 304 to browse a particular web page on a news site on an external system 876. In this example, the individual actions performed by user ‘A’ 802 to access the web page are user behavior elements that constitute a user behavior. As another example, user ‘A’ 802 may use an endpoint device 304 to download a data file from a particular system 856. In this example, the individual actions performed by user ‘A’ 802 to download the data file, including the use of one or more user authentication factors 606 for user authentication, are user behavior elements that constitute a user behavior. In certain embodiments, the user/device 830 interactions may include an interaction between a user, such as user ‘A’ 802 or ‘B’ 872, and an endpoint device 304.

In certain embodiments, the user/device 830 interaction may include interaction with an endpoint device 304 that is not connected to a network at the time the interaction occurs. As an example, user ‘A’ 802 or ‘B’ 872 may interact with an endpoint device 304 that is offline, using applications 832, accessing data 834, or a combination thereof, it may contain. Those user/device 830 interactions, or their result, may be stored on the endpoint device 304 and then be accessed or retrieved at a later time once the endpoint device 304 is connected to the internal 844 or external 846 networks. In certain embodiments, an endpoint agent 306 may be implemented to store the user/device 830 interactions when the user device 304 is offline.

In certain embodiments, an endpoint device 304 may be implemented with a device camera 828. In certain embodiments, the device camera 828 may be integrated into the endpoint device 304. In certain embodiments, the device camera 828 may be implemented as a separate device configured to interoperate with the endpoint device 304. As an example, a webcam familiar to those of skill in the art may be implemented receive and communicate various image and audio signals to an endpoint device 304 via a Universal Serial Bus (USB) interface.

In certain embodiments, the device camera 828 may be implemented to capture and provide user/device 830 interaction information to an endpoint agent 306. In various embodiments, the device camera 828 may be implemented to provide surveillance information related to certain user/device 830 or user/user 870 interactions. In certain embodiments, the surveillance information may be used by the security analytics system 118 to detect behavior associated with a user entity, such as user ‘A’ 802 or user ‘B’ 872 that may be of analytic utility.

In certain embodiments, the endpoint device 304 may be used to communicate data through the use of an internal network 844, an external network 846, or a combination thereof. In certain embodiments, the internal 844 and the external 846 networks may include a public network, such as the Internet, a physical private network, a virtual private network (VPN), or any combination thereof. In certain embodiments, the internal 844 and external 846 networks may likewise include a wireless network, including a personal area network (PAN), based on technologies such as Bluetooth. In various embodiments, the wireless network may include a wireless local area network (WLAN), based on variations of the IEEE 802.11 specification, commonly referred to as WiFi. In certain embodiments, the wireless network may include a wireless wide area network (WWAN) based on an industry standard including various 3G, 4G and 5G technologies.

In certain embodiments, the user/user 870 interactions may include interactions between two or more user entities, such as user ‘A’ 802 and ‘B’ 872. In certain embodiments, the user/user interactions 870 may be physical, such as a face-to-face meeting, via a user/device 830 interaction, a user/network 842 interaction, a user/resource 648 interaction, or some combination thereof In certain embodiments, the user/user 870 interaction may include a face-to-face verbal exchange. In certain embodiments, the user/user 870 interaction may include a written exchange, such as text written on a sheet of paper. In certain embodiments, the user/user 870 interaction may include a face-to-face exchange of gestures, such as a sign language exchange.

In certain embodiments, temporal event information associated with various user/device 830, user/network 842, user/resource 848, or user/user 870 interactions may be collected and used to provide real-time resolution of the identity of an entity at a particular point in time. Those of skill in the art will recognize that many such examples of user/device 830, user/network 842, user/resource 848, and user/user 870 interactions are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

In various embodiments, the security analytics system 118 may be implemented to process certain contextual information in the performance of certain security analytic operations. As used herein, contextual information broadly refers to any information, directly or indirectly, individually or in combination, related to a particular entity behavior. In certain embodiments, entity behavior may include a user entity's physical behavior, cyber behavior, or a combination thereof. As likewise used herein, a user entity's physical behavior broadly refers to any user behavior occurring within a physical realm, such as speaking, gesturing, facial patterns or expressions, walking, and so forth. More particularly, such physical behavior may include any action enacted by an entity user that can be objectively observed, or indirectly inferred, within a physical realm. In certain embodiments, the objective observation, or indirect inference, of the physical behavior may be performed electronically.

As an example, a user may attempt to use an electronic access card to enter a secured building at a certain time. In this example, the use of the access card to enter the building is the action and the reading of the access card makes the user's physical behavior electronically-observable. As another example, a first user may physically transfer a document to a second user, which is captured by a video surveillance system. In this example, the physical transferal of the document from the first user to the second user is the action. Likewise, the video record of the transferal makes the first and second user's physical behavior electronically-observable. As used herein, electronically-observable user behavior broadly refers to any behavior exhibited or enacted by a user entity that can be observed through the use of an electronic device (e.g., an electronic sensor), a computing device or system (e.g., an endpoint 304 or edge 202 device, a physical security device 854, a system 856, a shared device 858, etc.), computer instructions (e.g., a software application), or a combination thereof.

Cyber behavior, as used herein, broadly refers to any behavior occurring in cyberspace, whether enacted by an individual user, a group of users, or a system acting at the behest of an individual user, a group of users, or other entity. More particularly, cyber behavior may include physical, social, or mental actions that can be objectively observed, or indirectly inferred, within cyberspace. As an example, a user may use an endpoint device 304 to access and browse a particular website on the Internet. In this example, the individual actions performed by the user to access and browse the website constitute a cyber behavior. As another example, a user may use an endpoint device 304 to download a data file from a particular system 856 at a particular point in time. In this example, the individual actions performed by the user to download the data file, and associated temporal information, such as a time-stamp associated with the download, constitute a cyber behavior. In these examples, the actions are enacted within cyberspace, in combination with associated temporal information, which makes them electronically-observable.

In certain embodiments, the contextual information may include location data 836. In certain embodiments, the endpoint device 304 may be configured to receive such location data 836, which is used as a data source for determining the user's location 618. In certain embodiments, the location data 836 may include Global Positioning System (GPS) data provided by a GPS satellite 838. In certain embodiments, the location data 836 may include location data 836 provided by a wireless network, such as from a cellular network tower 840. In certain embodiments (not shown), the location data 836 may include various Internet Protocol (IP) or other network address information assigned to the endpoint 304 or edge 202 device. In certain embodiments (also not shown), the location data 836 may include recognizable structures or physical addresses within a digital image or video recording.

In certain embodiments, the endpoint devices 304 may include an input device (not shown), such as a keypad, magnetic card reader, token interface, biometric sensor, and so forth. In certain embodiments, such endpoint devices 304 may be directly, or indirectly, connected to a particular facility 852, physical security device 854, system 856, or shared device 858. As an example, the endpoint device 304 may be directly connected to an ingress/egress system, such as an electronic lock on a door or an access gate of a parking garage. As another example, the endpoint device 304 may be indirectly connected to a physical security device 854 through a dedicated security network.

In certain embodiments, the security analytics system 118 may be implemented to perform various risk-adaptive protection operations. Risk-adaptive, as used herein, broadly refers to adaptively responding to risks associated with an electronically-observable entity behavior. In various embodiments, the security analytics system 118 may be implemented to perform certain risk-adaptive protection operations by monitoring certain entity behaviors, assess the corresponding risk they may represent, individually or in combination, and respond with an associated response. In certain embodiments, such responses may be based upon contextual information, described in greater detail herein, associated with a given entity behavior.

In certain embodiments, various risk-adaptive behavior factors 674, likewise described in greater detail herein, may be used to perform the risk-adaptive protection operations. In certain embodiments, the risk-adaptive behavior factors 674 may include user profile attributes 604, user behavior factors 610, user mindset factors 622, or a combination thereof. In these embodiments, the risk-adaptive behavior factors 674 used to perform the risk-adaptive protection operations is a matter of design choice.

In certain embodiments, the security analytics system 118 may be implemented as a stand-alone system. In certain embodiments, the security analytics system 118 may be implemented as a distributed system. In certain embodiment, the security analytics system 118 may be implemented as a virtual system, such as an instantiation of one or more virtual machines (VMs). In certain embodiments, the security analytics system 118 may be implemented as a security analytics service 864. In certain embodiments, the security analytics service 864 may be implemented in a cloud environment familiar to those of skill in the art. In various embodiments, the security analytics system 118 may use data stored in a repository of security analytics data 880 in the performance of certain security analytics operations, described in greater detail herein. Those of skill in the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

FIG. 9 shows a functional block diagram of an adaptive trust profile (ATP) system implemented in accordance with an embodiment of the invention. In various embodiments, certain ATP-related information, described in greater detail herein, may be provided by endpoint devices 304, edge devices 202, and third party sources 906. In certain embodiments, the receipt of ATP information provided by third party sources 906 may be facilitated through the implementation of one or more Apache NiFi connectors 908, familiar to skilled practitioners of the art. In certain embodiments, sessionalization operations are performed in block 910 on the ATP-related information provided by the endpoint devices 304, edge devices 202, and third party sources 906 to generate discrete sessions. In these embodiments, the method by which ATP-related information is selected to be used in the generation of a particular session, and the method by which the session is generated, is a matter of design choice.

As used herein, a session broadly refers to an interval of time during which one or more user or non-user behaviors are respectively enacted by a user or non-user entity. In certain embodiments, the user or non-user behaviors enacted during a session may be respectively associated with one or more events, described in greater detail herein. In certain embodiments, a session may be implemented to determine whether or not user or non-user behaviors enacted during the session are of analytic utility. As an example, certain user or non-user behaviors enacted during a particular session may indicate the behaviors were enacted by an impostor. As another example, certain user or non-user behaviors enacted during a particular session may be performed by an authenticated entity, but the behaviors may be unexpected or out of the norm.

In certain embodiments, two or more sessions may be contiguous. In certain embodiments, two or more sessions may be noncontiguous, but associated. In certain embodiments, a session may be associated with two or more other sessions. In certain embodiments, a session may be a subset of another session. In certain embodiments, the interval of time corresponding to a first session may overlap an interval of time corresponding to a second session. In certain embodiments, a session may be associated with two or more other sessions whose associated intervals of time may overlap one another. Skilled practitioners of the art will recognize that many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope or intent of the invention.

The resulting sessions are then ingested in block 916, followed by the performance of data enrichment operations familiar to those of skill in the art in block 914. In certain embodiments, user identifier information (ID) information provided by a user ID management system 912 may be used in block 914 to perform the data enrichment operations. In various embodiments, certain contextual information related to a particular entity behavior or event may be used in block 914 to perform the data enrichment operations. In various embodiments, certain temporal information, such as timestamp information, related to a particular entity behavior or event may be used in block 914 to perform the data enrichment operations. In certain embodiments, a repository of ATP data 970 may be implemented to include repositories of entity attribute data 920 and behavioral model data 924. In various embodiments, certain information stored in the repository of entity attribute data 920 may be used to perform the data enrichment operations in block 914.

In certain embodiments, the resulting enriched sessions may be stored in a repository of raw event data 918. In certain embodiments, the resulting enriched sessions may be provided to a risk services 422 module, described in greater detail herein. In certain embodiments, as likewise described in greater detail herein, the risk services 422 module may be implemented to generate inferences, risk models, and risk scores, or a combination thereof. In certain embodiments, the resulting inferences, risk models, or risk scores may then be stored in the repository of behavioral model data.

In certain embodiments, the risk services 422 module may be implemented to provide input data associated with the inferences, risk models, and risk scores it may generate to a policy service 928. In certain embodiments, the policy service 928 may be implemented to use the inferences, risk models, and risk scores to generate policies. In turn, the policy service 928 may be implemented in certain embodiments to export the resulting policies to endpoint agents, edge devices, or other security mechanisms, where they may be used to limit risk, as described in greater detail herein. In certain embodiments, a user interface (UI) or front-end 926 familiar to skilled practitioners of the art may be implemented to provide administrative access to various components of the ATP system 120, as shown in FIG. 9.

FIG. 10 is a table showing components of an adaptive trust profile (ATP) implemented in accordance with an embodiment of the invention. In various embodiments, an ATP 638 may be implemented to certain include entity attributes 1004, behavioral models 1006, and inferences 1008, along with entity state 634. In certain embodiments, an ATP's 638 entity state 634 may be short-term, or reflect the state of an entity at a particular point or interval in time. In certain embodiments, an ATP's 638 entity state 634 may be long-term, or reflect the state of an entity at recurring points or intervals in time.

In certain embodiments, an ATP's 638 associated entity attributes 1004 may be long-lived. As an example, a particular user entity may have a name, an employee ID, an assigned office, and so forth, all of which are facts rather than insights. In certain embodiments, a particular entity state 634 may be sufficiently long-termed to be considered an entity attribute 1004. As an example, a first user and a second user may both have an entity state 634 of being irritable. However, the first user may have a short-term entity state 634 of being irritable on an infrequent basis, while the second user may have a long-term entity state 634 of be irritable on a recurring basis. In this example, the long-term entity state 634 of the second user being irritable may be considered to be an entity attribute. In various embodiments, the determination of what constitutes an entity state 634 and an entity attribute 1004 is a matter of design choice. In certain embodiments, various knowledge representation approaches may be implemented in combination with an ATP system to understand the ontological interrelationship of entity attributes 1004 one or more ATP's 638 may contain. In these embodiments, the method by which certain entity attributes 1004 are selected to be tracked by an ATP system, and the method by which they are managed within a corresponding ATP 638, is a matter of design choice.

In certain embodiments, the ATP 638 evolves over time as new events and entity behavior is detected. In certain embodiments, an ATP's 638 associated behavioral models 1006, and thus the ATP 638 itself may evolve over time. In certain embodiments, an ATP's 638 behavioral models 1006 may be used by an ATP system to provide insight into how unexpected a set of events may be. As an example, a behavioral model 1006 may include information related to where a particular user entity works, which devices they may use and locations they may login from, who they may communicate with, and so forth. Certain embodiments of the invention reflect an appreciation that such behavioral models 1006 can be useful when comparing observe user and non-user behaviors to past observations in order to determine how unusual a particular action may be.

For example, a user may have more than one ATP 638 associated with a particular channel, which as used herein broadly refers to a medium capable of supporting the electronic observation of a user or non-user behavior, such as a keyboard, a network, a video stream, and so forth. To continue the example, the user may have a particular set of people he sends emails to from his desktop computer, and does so in an orderly and methodical manner, carefully choosing his words, and writing longer than average messages compared to his peers. Consequently, analysis of such an email message will likely indicate it was authored by the user and not someone else.

However, the same user may also send emails from a second channel, which is his mobile telephone. When using his mobile telephone, the user's emails are typically short, contains typos and emojis, and his writing style is primarily limited to simple confirmations or denials. Consequently, analysis of one such email would likely not reveal whether the user was the author or not, due to its brevity. Accordingly, the use of the same channel, which in this example is email, demonstrates the use of different devices will likely generate different behavioural models 1006, which in turn could affect the veracity of associated inferences 1008.

In certain embodiments, a behavioral model 1006 may be implemented as a session-based fingerprint. As used herein, a session-based fingerprint broadly refers to a unique identifier of an enactor of user or non-user behavior associated with a session. In certain embodiments, the session-based fingerprint may be implemented to determine how unexpected an event may be, based upon an entity's history as it relates to the respective history of their peer entities. In certain embodiments, the session-based fingerprint may be implemented to determine whether an entity associated with a particular session is truly who they or it claims to be or if they are being impersonated. In certain embodiments, the session-based fingerprint may be implemented to determine whether a particular event, or a combination thereof, may be of analytic utility. In certain embodiments, the session-based fingerprint may include a risk score, be used to generate a risk score, or a combination thereof

As likewise used herein, a fingerprint, as it relates to a session, broadly refers to a collection of information providing one or more distinctive, characteristic indicators of the identity of an enactor of one or more corresponding user or non-user entity behaviors during the session. In certain embodiments, the collection of information may include one or more user or non-user profile elements. A user or non-user profile element, as used herein, broadly refers to a collection of user or non-user entity behavior elements, described in greater detail herein.

As used herein, inferences 1008 broadly refer to things that can be inferred about an entity based upon observations. In certain embodiments the observations may be based upon electronically-observable behavior, described in greater detail herein. In certain embodiments, the behavior may be enacted by a user entity, a non-user entity, or a combination thereof. In certain embodiments, inferences 1008 may be used to provide insight into a user entity's mindset or affective state.

As an example, an inference 1008 may be made that a user is unhappy in their job or that they are facing significant personal financial pressures. Likewise, based upon the user's observed behavior, an inference 1008 may be made that they are at a higher risk of being victimized by phishing schemes due to a propensity for clicking on random or risky website links. In certain embodiments, such inferences 1008 may be implemented to generate a predictive quantifier of risk associated with an entity's behavior.

In certain embodiments, entity state 636, described in greater detail herein, may be implemented such that changes in state can be accommodated quickly while reducing the overall volatility of a particular ATP 638. As an example, a user may be traveling by automobile. Accordingly, the user's location is changing quickly. Consequently, location data is short-lived. As a result, while the location of the user may not be updated within their associated ATP 638 as it changes, the fact their location is changing may prove to be useful in terms of interpreting other location-based data from other sessions. To continue the example, knowing the user is in the process of changing their location may assist in explaining why the user appears to be in two physical locations at once.

FIG. 11 is a table showing analytic utility actions occurring during a session implemented in accordance with an embodiment of the invention. In certain embodiments, an adaptive trust profile (ATP) system, described in greater detail herein, may be implemented to capture and record various actions 1104 enacted by an entity during a session 1102, likewise described in greater detail herein. In certain embodiments, the actions, and their associated sessions, may be stored in an ATP corresponding to a particular entity. In various embodiments, the ATP system may be implemented to process information stored in an ATP to determine, as described in greater detail herein, which actions 1104 enacted by a corresponding entity during a particular session 1102 may be of analytic utility 1108.

Certain embodiments of the invention reflect an appreciation that multiple sessions 1102, each of which may be respectively associated with a corresponding entity, may occur within the same interval of time 1106. Certain embodiments of the invention likewise reflect an appreciation that a single action of analytic utility 1108 enacted by an entity occurring during a particular interval of time 1106 may not appear to be suspicious behavior by an associated entity. Likewise, certain embodiments of the invention reflect an appreciation that the occurrence of multiple actions of analytic utility 1108 enacted by an entity during a particular session 1102 may be an indicator of suspicious behavior.

Certain embodiments reflect an appreciation that a particular entity may be associated with two or more sessions 1102 that occur concurrently over a period of time 1106. Certain embodiments of the invention likewise reflect an appreciation that a single action of analytic utility 1108 enacted by an entity occurring during a first session 1102 may not appear to be suspicious. Conversely, certain embodiments of the invention reflect an appreciation that multiple actions of analytic utility 1108 during a second session 1102 may.

As an example, a user may log into the same system from two different IP addresses, one associated with their laptop computer and the other their mobile phone. In this example, actions 1104 enacted by the user using their laptop computer may be associated with a first session 1102 (e.g. session ‘2’), and actions 1104 enacted by the user using their mobile phone may be associated with a second session 1102 (e.g., session ‘3’). To continue the example, only one action of analytic utility 1108 may be associated with the first session 1102, while three actions of analytic utility 1108 may be associated with the second session 1102. Accordingly, it may be inferred the preponderance of actions of analytic utility 1108 enacted by the user during the second session 1102 may indicate suspicious behavior being enacted with their mobile phone.

FIG. 12 is a simplified block diagram of an adaptive trust profile (ATP) system environment implemented in accordance with an embodiment of the invention. In certain embodiments, the ATP system environment may be implemented to detect user or non-user entity behavior of analytic utility and adaptively respond to mitigate risk. In certain embodiments, the ATP system environment may be implemented to include a security analytics system 118. In certain embodiments, the security analytics system 118 may be implemented to include an ATP system 120.

In certain embodiments, the ATP system 120, as described in greater detail herein, may be implemented to use session-based security information to generate an ATP, likewise describe in greater detail herein. As used herein, session-based security information broadly refers to any information associated with a session that can be used to detect entity behavior of analytic utility and mitigate its associated risk. In certain embodiments, the session-based security information may include a session-based fingerprint, described in greater detail herein.

In certain embodiments, the security analytics system 118 may be implemented to use one or more session-based fingerprints to perform security analytics operations to detect such user or non-user entity behavior. In certain embodiments, the security analytics system 118 may be implemented to monitor user behavior associated with a user entity, such as a user 802. In certain embodiments, the user or non-user entity behavior is monitored during user/device 830, user/network 842, user/resource 848, and user/user 860 interactions. In certain embodiments, the user/user 860 interactions may occur between a first user, such as a first user 802 and a second user 802.

In certain embodiments, as described in greater detail herein, an endpoint agent 306 may be implemented on the endpoint device 304 to perform user or non-user entity behavior monitoring. In certain embodiments, the user or non-user entity behavior may be monitored by the endpoint agent 306 during user/device 830 interactions between a user entity, such as a user 802, and an endpoint device 304. In certain embodiments, the user or non-user entity behavior may be monitored by the endpoint agent 306 during user/network 842 interactions between user ‘A’ 902 and a network, such as an internal 844 or external 846 network. In certain embodiments, the monitoring of user or non-user entity behavior by the endpoint agent 306 may include the monitoring of electronically-observable actions respectively enacted by a particular user or non-user entity. In certain embodiments, the endpoint agent 306 may be implemented in combination with the security analytics system 118 and the ATP system 120 to detect entity behavior of analytic utility and adaptively respond to mitigate risk.

In certain embodiments, the endpoint agent 306 may be implemented to include an analytics 310 module and an ATP feature pack 1208. In certain embodiments, the ATP feature pack 1208 may be further implemented to include an event data detector 1210 module, an entity behavior detector 1212 module, and a session correlation 1214 module. In certain embodiments, the event data detector 1210 module may be implemented to detect event data, described in greater detail herein, resulting from user/device 830, user/network 842, user/resource 848, and user/user 860 interactions. In various embodiments, the entity behavior detector 1212 module may be implemented to detect certain user and non-user entity behaviors, described in greater detail herein, resulting from user/device 830, user/network 842, user/resource 848, and user/user 860 interactions.

In various embodiments, the session correlation 1214 module may be implemented to generate session data by correlating certain event behavior data detected by the event data detector 1210 module with a particular session. In various embodiments, the session correlation 1214 module may be implemented to generate session data by correlating certain user and non-user entity behavior data detected by the entity behavior detector 1212 module with a particular session. In certain embodiments, the endpoint agent 306 may be implemented to communicate the event data detected by the event data detector 1210 module, the user and non-user entity behavior data detected by the entity behavior detector 1212 module, the session data generated by the session data detector 1214 module, or a combination thereof, to the security analytics 118 system.

In certain embodiments, the security analytics system 118 may be implemented to receive the event data, the user and non-user entity behavior data, and the session data provided by the endpoint agent 306. In certain embodiments, the security analytics system 118 may be implemented to provide the event data, the user and non-user entity behavior data, and the session data to the ATP system 120 for processing. In certain embodiment, the ATP system 120 may be implemented to include an ATP element collector 1282 module, an ATP element analytics 1284 module, a session generator 1286 module, a session-based fingerprint generator 1288 module, an ATP generator 122 module, or a combination thereof.

In certain embodiments, the ATP element collector 1282 module may be implemented to process the event data, the user and non-user entity behavior data, and the session data provided by the endpoint agent 306 to generate ATP elements, described in greater detail herein. In various embodiments, the ATP element analytics 1284 module may be implemented to analyze certain ATP elements to detect possible user or non-user entity behavior of analytic utility associated with a particular event. In certain embodiments, the ATP session generator 1286 module may be implemented to process the ATP elements collected by the ATP element collector 1282 module to generate one or more associated sessions. In certain embodiments, the session-based fingerprint generator 1288 module may be implemented to process the sessions generated by the session generator 1286 module to generate one or more session-based fingerprints. In certain embodiments, the ATP generator 122 module may be implemented to process the sessions generated by the ATP session generator 1286 module, the session-based fingerprints generated by the session-based fingerprint generator 1288 module, or a combination thereof, to generate am ATP profile, as described in greater detail herein.

FIG. 13 is a generalized flowchart of session-based fingerprint generation operations performed in accordance with an embodiment of the invention. In this embodiment, session-based fingerprint generation operations are begun in step 1302, followed by the selection of an entity in step 1304 for associated adaptive trust profile (ATP) element generation. As used herein, an ATP element broadly refers to any data element stored in an ATP, as described in greater detail herein. In certain embodiments, an ATP element may be used to describe a particular aspect of an ATP. Ongoing monitoring operations are then performed in step 1306 to entity behavior data associated with the entity selected in step 1304.

A determination is then made in step 1308 whether entity behavior data has been detected. If not, then a determination is made in step 1326 whether to continue monitoring the entity's behavior to detect associated entity behavior data. If so, then the process is continued, proceeding with step 1306. Otherwise, session-based fingerprint generation operations are ended in step 1328. However, if it was determined in step 1308 that entity behavior data was detected, then the detected entity data is processed in step 1310 to generate an associated ATP element.

A determination is then made in step 1312 whether to generate a new ATP for the entity. If not, then a target ATP associated with the entity is selected in step 1314. Otherwise, a new ATP for the entity is generated in step 1316. Thereafter, or once a target ATP associated with the entity has been selected in step 1315, the previously-generated ATP element is added to the selected or newly-generated ATP in step 1318.

The ATP elements within the ATP are then processed in step 1320 to generate a session, described in greater detail herein. The resulting session is in turn processed in step 1322 to generate a corresponding session-based fingerprint. The session and its corresponding session-based fingerprint are then associated with the ATP in step 1324 that is likewise associated with the entity. The process is then continued, proceeding with step 1326.

FIGS. 14a and 14b are a generalized flowchart of the performance of adaptive trust profile (ATP) definition and management operations implemented in accordance with an embodiment of the invention. In this embodiment, ATP definition and management operations are begun in step 1402, followed by ongoing operations being performed by an ATP system in step 1404 to ATP elements, as described in greater detail herein. A determination is then made in step 1406 whether an ATP element has been received by the ATP system.

If not, then a determination is made in step 1436 to determine whether to continue monitoring for ATP elements. If so, then the process is continued, proceeding with step 1404. Otherwise, a determination is made in step 1438 whether to end transportable cyberprofile generation operations. If not, then the process is continued, proceeding with step 1404. Otherwise, ATP definition and management operations are ended in step 1438.

However, if it was determined in step 1406 that an ATP element was received, then it is processed in step 1408 to determine its associated entity. A determination is then made in step 1410 whether to generate a new ATP for the entity. If not, then an ATP associated with the entity is selected in step 1412 and then updated with the ATP element in step 1414. However, if it was determined in step 1410 to generate a new ATP for the entity, then it is generated in step 1416 and populated with the ATP element in step 1418.

Thereafter, or after the selected ATP is updated in step 1414, the ATP is processed in step 1420 to perform data enrichment operations, described in greater detail herein. Analytic utility detection operations, likewise described in greater detail herein, are then performed on the enriched ATP in step 1422 to identify entity behavior that may be of analytic utility. Thereafter, a determination is made in step 1424 to determine whether the entity behavior is of analytic utility. If not, then a determination is made in step 1434 whether to continue ATP definition and management operations. If so, then the process is continued, proceeding with step 1404. Otherwise, ATP definition and management operations are ended in step 1438.

However, if it was determined in step 1424 that the entity behavior was of analytic utility, the contextual information is retrieved in step 1426 and then processed in step 1428 with entity attributes stored in the ATP with a behavioral model to generate one or more inferences, described in greater detail herein. A determination is then made in step 1430 whether the one or more inferences indicate behavior by the entity is of analytic utility. If not, the process is continued, proceeding with step 1434. Otherwise, appropriate risk mitigation operations are performed in step 1432 and the process is then continued, proceeding with step 1434.

FIG. 15 is a simplified block diagram of the operation of a security analytics system implemented in accordance with an embodiment of the invention to adaptively assess risk associated with an entity behavior. In this embodiment, entity behavior is monitored and compared to known good behavior 1502 and known bad behavior 1504. In typical risk assessment 1506 approaches, low 1508, moderate 1510, or high 1512 risk entity behavior is generally determined by using fairly inflexible security policies, which are typically used to enact relatively static responses.

As an example, a security policy implemented for access control may have a list of actions a particular entity can do and a list of things they cannot. Ordinarily, the actions in those lists are static and don't change, regardless of the particular entity behavior being enacted. However, perhaps they should change, or adapt, if it is determined the entity behavior being enacted by the entity has changed, and as a result, represents a higher risk.

To continue the example, a user may be perusing various resources and happens to access a webpage, such as a shopping site, that contains certain objects. Typical security approaches assume some portion of those objects to be good, a small number are known to be bad, and the remainder suspicious. Consequently, there is a continuum of objects, some assumed to be good, some undetermined, and the rest known to be bad. It will be appreciated that the determination of what is considered to be good, undetermined, or bad is oftentimes fairly arbitrary.

In certain embodiments, contextual information associated with the entity behavior is collected and processed to adaptively respond to changes in the entity's current behavior. In continuance of the example, the user may change their behavior to access internal business resources. In this example, accessing internal business resources is contextual information that may represent the potential for higher risk. As a result, a risk-adaptive behavior system may be implemented in certain embodiments to respond with an adaptive high risk assessment 1514. In certain embodiments, the adaptive high risk assessment 1514 is generated by a security analytics system, described in greater detail herein. Consequently, the adaptive high risk assessment 1514 may indicate a larger percentage of certain entity behavior as high 1520 risk, and a smaller percentage as low 1516 or moderate 1518 risk.

In further continuance of the example, the user may further change their behavior to access an external news site. As before, the user's access of an external news site is contextual information that may represent the likelihood of lower risk. As a result, the risk-adaptive behavior system may be implemented to respond with an adaptive low risk assessment 1522, which may indicate a larger percentage of certain entity behavior as low 1524 risk, and a smaller percentage as moderate 1526 or high 1528 risk.

Certain embodiments of the invention reflect an appreciation that without the described adaptive behavior, the operational overhead administering entity security would be high, as all entity interactions related to their behavior would continue to be monitored. However, the cost of administering entity security would decrease when the entity was no longer interacting with internal resources. Consequently, risk tolerance can be dynamically adjusted according to the context of a given entity activity.

More particularly, if the entity's activity is primarily internal to the organization, then some risk can be tolerated. However, if the entity's activity is primarily external to the organization, then it is possible that essentially all risk can be tolerated. Furthermore, the user experience may be more pleasant during non-organization activities, as fewer security controls may be applied or experienced. Moreover, the risk assessment becomes dynamic, according to the identity of the entity, the resources being accessed, their respective behavior, and corresponding points of observation.

FIG. 16 is a simplified block diagram of the operation of a security analytics system implemented in accordance with an embodiment of the invention to adaptively respond to an entity request. In this embodiment, an entity may place a request 1606 to download a file from a file source 1608 to a file destination 1604, such as a USB drive. In traditional security approaches, the owner of the requested file may have a single security rule, which would be a granted 1612, or denied 1614, request response 1610 as to whether the entity was allowed to download the file.

In certain embodiments, a risk-adaptive security policy may be implemented such that the entity's request 1606 to download the requested file is typically granted 1612. However, as an example, a user may have recently updated their online resume as well as begun to take random days off, which may imply a flight risk. By extension, the user behavior and other actions associated with the user may likewise imply the user's intent to take proprietary information with them to a new job. Consequently, various risk-adaptive behavior approaches may yield a denied 1614 request response 1610 due to the associated context of their behavior, other actions, or a combination thereof

Alternatively, a risk-adaptive security policy may be implemented in various embodiments to provide a conditional 1616 request response 1610. As an example, a requested file may be encrypted such that it can only be opened on a corporate computer. Furthermore, attempting to open the file on a non-corporate computer may result in a message being sent to a security administrator. Likewise, a single file being downloaded may appear as good behavior, yet multiple sequential downloads may appear suspicious, especially if the files do not appear to be related, or possibly, if they do. From the foregoing, it will be appreciated that risk-adaptive behavior is not necessarily based upon an atomic action, but rather a multiplicity of factors, such as contextual information associated with particular entity behavior.

FIG. 17 is a generalized flowchart of the performance of security analytics system operations implemented in accordance with an embodiment of the invention to adaptively manage entity behavior risk. In this embodiment, risk-adaptive behavior operations are begun in step 1702, followed by the performance of entity authentication operations, familiar to those of skill in the art, in step 1704. A determination is then made in step 1706 whether the entity has one or more associated risk-adaptive security policies. If so, then they are retrieved for use in step 1708. Thereafter, or if it was determined in step 1706 the entity has no associated risk-adaptive security policies, the entity's behavior is monitored in step 1710.

The entity's current user behavior is then processed in step 1712 to identify any applicable risk-adaptive security policies that may apply. A determination is then made in step 1714 whether any applicable risk-adaptive security policies have been identified. If not, a determination is made in step 1726 whether to end risk-adaptive behavior system operations. If not, then the process is continued, proceeding with step 1710. Otherwise, risk-adaptive behavior system operations are ended in step 1728.

However, if it is determined in step 1714 that one or more applicable risk-adaptive security policies have been identified, then they are used in step 1716 to process the entity's current user behavior to determine an appropriate risk-adaptive behavior response. The appropriate risk-adaptive behavior response is then enacted in step 1718, followed by a determination being made in step 1720 whether the risk-adaptive behavior response enacted in step 1718 indicates acceptable user behavior.

If so, then the process is continued, proceeding with step 1726. Otherwise the entity's current behavior is determined to be of analytic utility and marked accordingly in step 1722. Entity behavior of analytic utility notification operations are then performed in step 1724. In one embodiment, entity behavior of analytic utility is stored for later review. In another embodiment, a security administrator is notified of the enactment of entity behavior of analytic utility. Thereafter, the process is continued, proceeding with step 1726.

FIG. 18 is a simplified block diagram of an adaptive trust profile (ATP) system implemented in accordance with an embodiment of the invention to modify an existing, or generate a new, ATP. Certain aspects of the invention reflect an appreciation that the block diagram shown in this figure provides additional detail in support of the flowchart steps shown in FIGS. 19a-d and FIGS. 20a-c. In certain embodiments, as described in greater detail herein, a security analytics system 118 may be implemented to include an ATP system 120. In certain embodiments, the ATP system 120 may be implemented to include an ATP generator 122 module, a prepopulated ATP generator 124 module, and an entity anonymization 126 module, or a combination thereof.

In certain embodiments, the ATP system 120 may be implemented to receive a request 1802 to modify an existing, or generate a new, ATP 638. In certain embodiments, the request 1802 may be processed by the ATP generator 124 module to generate a modified 1806 ATP or an entity-specific 1808 ATP. As used herein, a modified 1806 ATP broadly refers to an existing ATP 638 associated with a particular entity 1804 whose information collection parameters have been revised. In certain embodiments, the revisions to the ATP's 638 information collection parameters may include increasing, decreasing, or otherwise changing the amount, type, or nature of information that is collected.

As an example, a user entity 1804 may be employed as a claims processor for an insurance company and have an associated ATP 638 containing information related to their identity and behavior in that role. In this example, the user entity 1894 may accept a new position as a claims adjustor, which in turn may involve accessing certain additional information resources. As a result, the user entity's 1804 associated ATP 638 may be processed by the ATP generator 122 module to generate a modified ATP 1806, which is then processed to contain certain ATP elements associated with the new information resources. Once the modified ATP 1806 is generated, it can then be associated with the user entity 1804 as their current ATP 638.

In various embodiments, the ATP's 638 information collection parameters may be associated with certain ATP elements, described in greater detail herein. In certain of these embodiments, the information collected by a particular ATP 638, whether directly or indirectly, may be related to its associated entity's 1804 identity and behavior, as likewise described in greater detail herein. In certain embodiments, a modified ATP 1808 generated by the ATP generator 122 module from an existing ATP 638 associated with a particular entity 1804 may be implemented to replace the entity's 1804 existing ATP 638.

In certain embodiments, a modified ATP 1808 generated by the ATP generator 122 module from an existing ATP 638 associated with a particular entity 1804 may be implemented to be associated with the same entity 1804 in addition to its existing ATP 638. As an example, a user entity 1804 may have a primary role in an organization, and as a result have a primary ATP 638. However, the same user entity 1804 may be assigned a secondary role. As a result, the user entity's 1804 existing ATP 638 may be processed by the ATP generator 122 module to generate a modified ATP 1806, which in turn is revised to accommodate behavior information related to the user entity's 1804 secondary role. The resulting modified ATP 1806 can then be associated with the user entity 1804 as a second ATP 638.

In certain embodiments, a modified ATP 1808 generated by the ATP generator 122 module from a particular ATP 638 associated with a first entity 1804 may be implemented to be associated with a second entity 1804. For example, a user entity 1804 may be employed by a company as an account executive. As a result, information related to their associated behavior may be stored in an associated ATP 638. In this example, another user entity 1804 may be hired as a second account executive. To continue the example, the first user entity's 1804 existing ATP 638 may be processed by the ATP generator 122 module to generate a modified ATP 1806, which in turn can then be associated with the second user entity 1804 as their initial ATP 638.

In various embodiments, a prepopulated ATP 678 may be implemented to contain certain prepopulated ATP elements that have been anonymized. In certain of these embodiments, the entity data anonymization 126 module may be implemented to perform the anonymization of the prepopulated ATP elements. In various embodiments, a modified ATP 1808 generated by the ATP generator 122 module from a particular ATP 638 associated with a first entity 1804 may be implemented to contain certain ATP elements that have been anonymized prior to being associated with a second entity 1804. To continue the prior example, any personally-identifiable information (PII) associated with the first user entity 1804 in the modified ATP 1806 is anonymized by the entity data anonymization 126 module. Once all PII has been anonymized, the resulting modified ATP 1806 can then be associated with the second user entity 1804 as a their initial ATP 638.

As likewise used herein, an entity-specific 1808 ATP broadly refers to an ATP 638 that may contain certain ATP elements related to a particular entity 1804, but not yet associated with the entity 1804. For example, a user entity 1804 may join an organization, and as a result, provide certain PII, which in turn may be processed with certain entity data to generate user credentials, authentication factors, access rights and so forth. In this example the resulting ATP elements may then be used to populate an entity-specific ATP 1808, which in turn may then be associated with the user entity 1804 as their initial ATP 638. In this example, information related to the user entity's behavior is then added to their ATP 638 over time.

In various embodiments, an entity-specific 1808 ATP implemented as an ATP 638 may be associated with a user entity 1804 whose identity may not be initially known. As an example, an unknown user entity 1804 may begin navigating the website of an organization. In this embodiment, an entity-specific 1808 may be implemented as an ATP 638, which is then associated with the unknown user entity 1804. From that point forward, the unknown user entities 1804 behavior is captured and stored in its associated ATP 638.

In certain of these embodiments, the identity of an entity 1804 associated with an ATP 638 may be established over time. To continue the prior example, at some point in time the unknown user entity 1804 may be requested to provide some form of identity information. If there is a positive response to the request, then the identity information is added to the ATP 638 associated with the user entity 1804.

In certain embodiments, the prepopulated ATP generator 124 module may be implemented to generate a prepopulated ATP 678, described in greater detail herein. In various embodiments, the ATP generator 122 module may be implemented to process one or more prepopulated ATPs 678 generated by the prepopulated ATP generator 124 module to generate an ATP 638. In certain of these embodiments, the resulting ATP 638 may then be associated with one or more entities 1804. In these embodiments, the method by which the entity 1804 is selected, and the resulting ATP 638 is associated with it, is a matter of design choice.

In certain embodiments, a prepopulated ATP 678 may be implemented as a universal 1810, a segmented 1812, an entity-pertinent 1814, or entity-specific 1816 prepopulated ATP. As used herein, a universal 1810 prepopulated ATP broadly refers to a prepopulated ATP 678 implemented to accommodate certain prepopulated ATP elements, as described in greater detail herein. In certain embodiments, the universal 1810 prepopulated ATP may be implemented to accommodate prepopulated ATP elements corresponding to ATP elements supported by a particular ATP 638.

As an example, an ATP 638 may be implemented in certain embodiments to include ATP elements associated with a user entity profile, a user entity mindset profile, a non-user entity profile, and an entity state, as described in greater detail herein. Accordingly, a corresponding universal 1810 prepopulated ATP may be implemented in certain embodiments to include prepopulated ATP elements associated with a prepopulated user entity profile, a prepopulated user entity mindset profile, a prepopulated non-user entity profile, and a prepopulated entity state.

In certain embodiments, prepopulated ATP elements associated with a prepopulated user entity profile may include prepopulated user profile attributes, prepopulated user behavior attributes, and prepopulated user mindset factors, as likewise describe in greater detail herein. In various embodiments, prepopulated ATP elements associated with a prepopulated non-user entity profile may likewise include certain prepopulated non-user profile attributes, as described in greater detail herein. In these embodiments, the prepopulated ATP elements selected for inclusion in a universal 1810 prepopulated ATP, and the method by which they are selected, is a matter of design choice.

As used herein, a segmented 1812 prepopulated ATP broadly refers to a prepopulated ATP 678 implemented to be composed of distinct groups, or segments, of prepopulated ATP elements. In certain embodiments, one or more segments of a segmented 1812 prepopulated ATP may be used, individually or in combination, by the ATP generator 122 module to generate an ATP 638. In various embodiments, the prepopulated ATP elements selected for use as segment of a segmented 1812 ATP, and the method by which they are selected, is a matter of design choice.

As an example, in certain embodiments, the segments of a prepopulated ATP 678 selected for use as a segmented 1812 prepopulated ATP may include prepopulated ATP elements associated with a prepopulated user entity profile, a prepopulated user entity mindset profile, a prepopulated non-user entity profile, or a prepopulated entity state, or a combination thereof. As another example, in certain embodiments, the segments of a prepopulated ATP 678 selected for use as a segmented 1812 prepopulated ATP may include prepopulated ATP elements associated with prepopulated user profile attributes, prepopulated user behavior attributes, prepopulated user mindset factors, and prepopulated non-user profile attributes. Those of skill in the art will recognize many such embodiments are possible. Accordingly, the foregoing is not intended to limit the spirit, scope, or intent of the invention.

As used herein, an entity-pertinent 1814 prepopulated ATP broadly refers to a prepopulated ATP 678 that contains one or more prepopulated ATP elements commonly associated with a particular type or class of entity 1804. As an example, a cloud service provider may currently have three servers of the same manufacturer and configuration providing email service. Over time, the number of email accounts being serviced may grow and the capacity of the three current servers may begin to surpass their optimum operational parameters. As a result the service provider may decide to purchase and deploy two additional servers from the same manufacturer with the same configuration to maintain optimum service levels.

In this example, all five servers are from the same manufacturer, have the same configuration, and are used for the same purpose. As a result, they can be considered a class of non-user entities, described in greater detail herein. To continue the example, the three original servers may each have an associated ATP 638. In further continuance of this example, certain ATP elements contained in the original ATPs 638 may be processed by the prepopulated ATP generation 124 module to generate a normalized set of ATP elements. In this example, the resulting set of normalized ATP elements can then be used as prepopulated ATP elements, likewise described in greater detail herein, by the prepopulated ATP generation 124 module to generate an entity-pertinent 1814 prepopulated ATP. In turn, the resulting entity-pertinent 1814 prepopulated ATP can be associated with the two new servers as their respective ATPs 638.

As used herein, an entity-specific 1816 prepopulated ATP broadly refers to a prepopulated ATP 678 that contains one or more prepopulated ATP elements associated with a particular entity 1804. As an example, a company may have a vice president of sales, a senior sales executive, and an inside sales associate, all of which have an associated ATP 638 reflecting their associated user entity's identity, access rights, and behavior. In this example, the company decides to hire an additional inside sales associate. Since there is only one other inside sales associate, their current ATP 638 may be retrieved and processed to generate an entity-specific 1816 prepopulated ATP. In certain embodiments, the entity data anonymization 126 module may be implemented to anonymize PII in the resulting entity-specific 1816 prepopulated ATP. Once any PII the entity-specific 1816 prepopulated ATP may contain has been anonymized, it can be associated with the newly-hired inside sales associate as their ATP 638.

In certain embodiments, the prepopulated ATP generator 124 module may be implemented to process a particular modified 1810 ATP for conversion into a prepopulated 678 ATP. In various embodiments, the prepopulated ATP generator 124 module may be implemented to use an entity data anonymization 1820 module when converting a modified ATP 1810 into a prepopulated ATP 678 to anonymize certain entity data 692 associated with an entity 1804. In certain embodiments, the ATP elements contained in a prepopulated ATP 678 may be implemented to contain, or reference, structured data, non-structured data, or a combination thereof.

In various embodiments, prepopulated ATP 678 modification and generation operations may be initiated by the receipt of a request 1802 to perform certain ATP operations to modify an existing, or generate a new, prepopulated ATP 1802. In certain of these embodiments, the request 1802 is processed to retrieve relevant entity 692 and ATP 690 data associated with one or more entities 1804. If the request 1802 is to modify an existing prepopulated ATP 678, then the request 1802 may be processed in certain embodiments with the retrieved entity 692 and ATP 690 data, and the existing prepopulated ATP 678, to determine which modifications are to be made. If it is decided to use one or more other prepopulated ATPs 678 relevant to making the modifications, then the request 1802, the retrieved entity 692 and ATP 690 data, and the existing prepopulated ATP 678 is processed to identify other relevant prepopulated ATPs 678 that may be used to make the modifications.

Once identified, the identified prepopulated ATPs 678 are retrieved and then processed with the request 1802, the retrieved entity 692 and ATP 690 data, and the existing prepopulated ATP 678, to generate a modified prepopulated ATP 678. In certain embodiments, the modified prepopulated ATP 678 may be generated as a universal 1810, a segmented 1812, an entity-pertinent 1814, or an entity-specific 1816 prepopulated ATP. The resulting prepopulated ATP 678 may then be stored in a repository of prepopulated ATPs 694.

In certain embodiments, it may be decided to not use one or more other prepopulated ATPs 678 relevant to making the modifications. If so, then the request 1802, the retrieved entity 692 and ATP 690 data, and the existing prepopulated ATP 678 are processed to generate a modified prepopulated ATP 678 as previously described. As likewise previously described, the resulting prepopulated ATP 678 may then be stored in a repository of prepopulated ATPs 694.

In various embodiments, it may be decided to use a universal 1810 ATP to generate a new prepopulated ATP 678 instead of modifying an existing prepopulated ATP 678. In certain of these embodiments, the request 1802, the retrieved entity 692 and ATP 690 data, and a target universal 1810 prepopulated ATP are then processed to generate a new prepopulated ATP 678. As previously described, the resulting prepopulated ATP 678 may then be stored in a repository of prepopulated ATPs 694.

In various embodiments, it may be decided to use a segmented 1812 ATP to generate a new prepopulated ATP 678 instead of modifying an existing prepopulated ATP 678. In certain of the embodiments, the request 1802, along with relevant entity 692 and ATP 690 data, is processed to identify relevant segments of one or more target segmented 1812 prepopulated ATPs. In turn, the request 1802, the relevant entity 692 and ATP 690 data, and the identified relevant ATP segments are then processed to generate a new prepopulated ATP 678. As previously described, the resulting prepopulated ATP 678 may then be stored in a repository of prepopulated ATPs 694.

In various embodiments, it may be decided to use an entity-pertinent 1814 ATP to generate a new prepopulated ATP 678 instead of modifying an existing prepopulated ATP 678. In certain of these embodiments, the request 1802, the retrieved entity 692 and ATP 690 data, and a target entity-pertinent 1814 prepopulated ATP are then processed to generate a new prepopulated ATP 678. As previously described, the resulting prepopulated ATP 678 may then be stored in a repository of prepopulated ATPs 694.

In various embodiments, it may be decided to use an entity-specific 1816 ATP to generate a new prepopulated ATP 678 instead of modifying an existing prepopulated ATP 678. In certain of these embodiments, the request 1802, the retrieved entity 692 and ATP 690 data, and a target entity-specific 1816 prepopulated ATP are then processed to generate a new prepopulated ATP 678. As previously described, the resulting prepopulated ATP 678 may then be stored in a repository of prepopulated ATPs 694.

In various embodiments, ATP 638 modification and generation operations may be initiated by the receipt of a request 1802 to perform certain ATP operations to modify an existing, or generate a new, prepopulated ATP 638 for a target entity 1804. In certain of these embodiments, the request 1802 is processed to retrieve relevant entity 692 and ATP 690 data associated with one or more entities 1804.

If the request 1802 is to modify an existing ATP 638, then the request 1802 may be processed in certain embodiments with the retrieved entity 692 and ATP 690 data, and the existing ATP 638, to determine which modifications are to be made. If it is decided to use one or more other ATPs 638 relevant to making the modifications, then the request 1802, the retrieved entity 692 and ATP 690 data, and the existing ATP 638 is processed to identify other relevant ATPs 638 that may be used to make the modifications. In certain embodiments, the relevant ATPs 638 that may be used to make the modifications may be stored in a repository of ATP data 690.

Once identified, the identified other ATPs 638 are retrieved and then processed with the request 1802, the retrieved entity 692 and ATP 690 data, and the existing ATP 638, to generate a modified ATP 638. The resulting modified ATP 638 may then be associated with the entity 1804. In certain embodiments, it may be decided to not use one or more other ATPs 638 relevant to making the modifications. If so, then the request 1802, the retrieved entity 692 and ATP 690 data, and the existing ATP 638 are processed to generate a modified ATP 6378 as previously described. As previously described, the resulting modified ATP 638 may then be associated with the entity 1804.

In various embodiments, it may be decided to use a universal 1810 ATP to generate a new ATP 638 instead of modifying an existing ATP 638. In certain of these embodiments, the request 1802, the retrieved entity 692 and ATP 690 data, and a target universal 1810 prepopulated ATP are then processed to generate a new ATP 638. As previously described, the resulting new ATP 638 may then be associated with the entity 1804.

In various embodiments, it may be decided to use a segmented 1812 ATP to generate a new ATP 638 instead of modifying an existing ATP 638. In certain of the embodiments, the request 1802, along with relevant entity 692 and ATP 690 data, is processed to identify relevant segments of one or more target segmented 1812 prepopulated ATPs. In turn, the request 1802, the relevant entity 692 and ATP 690 data, and the identified relevant ATP segments are then processed to generate a new ATP 638. As previously described, the resulting new ATP 638 may then be associated with the entity 1804.

In various embodiments, it may be decided to use an entity-pertinent 1814 ATP to generate a new ATP 638 instead of modifying an existing ATP 638. In certain of these embodiments, the request 1802, the retrieved entity 692 and ATP 690 data, and a target entity-pertinent 1814 prepopulated ATP are then processed to generate a new ATP 638. As previously described, the resulting new ATP 638 may then be associated with the entity 1804.

In various embodiments, it may be decided to use an entity-specific 1816 ATP to generate a new ATP 638 instead of modifying an existing ATP 638. In certain of these embodiments, the request 1802, the retrieved entity 692 and ATP 690 data, and a target entity-specific 1816 prepopulated ATP are then processed to generate a new ATP 638. As previously described, the resulting new ATP 638 may then be associated with the entity 1804.

FIGS. 19a through 19c are a generalized flowchart of adaptive trust profile (ATP) system operations performed in accordance with an embodiment of the invention to generate a new, or modify an existing, prepopulated ATP. In this embodiment, prepopulated ATP modification and generation operations are begun in step 1902, followed by the receipt of a request in step 1904 to perform certain ATP operations to modify an existing, or generate a new, prepopulated ATP. In turn, the request is processed in step 2006 to retrieve relevant entity and ATP data, as described in greater detail herein.

A determination is then made in step 1908 whether the request received in step 1904 is to modify an existing prepopulated ATP. If so, then the request is processed in step 1910 with the retrieved entity and ATP data, and the existing prepopulated ATP, to determine which modifications are to be made. A determination is then made in step 1912 whether to use one or more other prepopulated ATPs relevant to making the modifications. If so, the request, the retrieved entity and ATP data, and the existing prepopulated ATP is processed in step 1914 to identify other relevant prepopulated ATPs that may be used to make the modifications.

Once identified, the identified prepopulated ATPs are retrieved in step 1916 and then processed in step 1918 with the request, the retrieved entity and ATP data, and the existing prepopulated ATP, to generate a modified prepopulated ATP. The resulting prepopulated ATP is then stored in a repository of prepopulated ATPs in step 1946, followed by a determination being made in step 1948 whether to continue operations to modify an existing, or generating a new, prepopulated ATP. If not, then the process is continued, proceeding with step 1904.

Otherwise, operations to modify an existing, or generating a new, prepopulated ATP are ended in step 1950. However, if it was determined in step 1912 not to use one or more other prepopulated ATPs relevant to making the modifications, then the request, the retrieved entity and ATP data, and the existing prepopulated ATP are processed in step 1920 to generate a modified prepopulated ATP. The process is then continued, proceeding with step 1946.

However, if it was determined in step 1908 not to modify an existing prepopulated ATP, then a determination is made in step 1922 whether to use a universal prepopulated ATP to generate a new prepopulated ATP. If so, the request, the retrieved entity and ATP data, and a target universal prepopulated ATP are processed in step 1924 to generate a new prepopulated ATP. The process is then continued, proceeding with step 1946.

However, if it was determined in step 1922 not to use a universal prepopulated ATP, then a determination is made in step 1926 whether to use a segmented prepopulated ATP to generate a new prepopulated ATP. If so, the request, along with the retrieved entity and ATP data, is then processed in step 1928 to determine relevant segments of one or more segmented prepopulated ATPs. The request, the retrieved entity and ATP data, and the identified relevant ATP segments are then processed in step 1932 to generate a new prepopulated ATP. The process is then continued, proceeding with step 1946.

However, if it was determined in step 1926 not to use a segmented prepopulated ATP, then a determination is made in step 1934 whether to use an entity-pertinent prepopulated ATP to generate a new prepopulated ATP. If so, the request, along with the retrieved entity and ATP data, is processed in step 1936 to identify one or more entity-pertinent prepopulated ATPs. The request, along with the retrieved entity and ATP data, and the one or more identified entity-pertinent prepopulated ATPs are processed in step 1938 to generate a new ATP for the target entity. The process is then continued, proceeding with step 1946.

However, if it was determined in step 1934 not to use an entity-pertinent prepopulated ATP, then a determination is made in step 1940 whether to use an entity-specific prepopulated ATP to generate a new prepopulated ATP. If so, the request, along with the retrieved entity and ATP data, is processed in step 1944 to identify one or more entity-specific prepopulated ATPs. The request, along with the retrieved entity and ATP data, and the one or more identified entity-specific ATPs are processed in step 1944 to generate a new prepopulated ATP. The process is then continued, proceeding with step 1946.

FIGS. 20a through 20d are a generalized of adaptive trust profile (ATP) system operations performed in accordance with an embodiment of the invention to generate a new, or modify an existing, ATP for an associated entity. In this embodiment, ATP modification and generation operations are begun in step 2002, followed by the receipt of a request in step 2004 to perform certain ATP operations to modify an existing, or generate a new, ATP for a target entity. In turn, the request is processed in step 2006 to retrieve relevant entity and AP data associated with the entity, as described in greater detail herein.

A determination is then made in step 2008 whether the request received in step 2004 is to modify an existing ATP associated with the target entity. If so, then the request is processed in step 2010 with the retrieved entity and ATP data, and the existing ATP, to determine which modifications are to be made. A determination is then made in step 2012 whether to use one or more other prepopulated ATPs relevant to making the modifications. If so, the request, the retrieved entity and ATP data, and the existing ATP is processed in step 2014 to identify other relevant prepopulated ATPs that may be used to make the modifications.

Once identified, the identified prepopulated ATPs are retrieved in step 2016 and then processed in step 2018 with the request, the retrieved entity and ATP data, and the existing ATP, to generate a modified ATP. The resulting modified ATP is then associated with the entity in step 2048, followed by a determination being made in step 2050 whether to continue operations to modify an existing, or generating a new, ATP. If not, then the process is continued, proceeding with step 2004. Otherwise, operations to modify an existing, or generating a new, ATP are ended in step 2052.

However, if it was determined in step 2008 not to modify an existing ATP associated with an entity, then a determination is made in step 2022 whether to use a non-prepopulated ATP to generate a new ATP for the target entity. If so, the request, the retrieved entity and ATP data, and a target non-prepopulated ATP are processed in step 2024 to generate a new ATP for the target entity. The process is then continued, proceeding with step 2048.

However, if it was determined in step 2022 not to use a non-prepopulated ATP, then a determination is made in step 2026 whether to use a universal prepopulated ATP to generate a new ATP for the target entity. If so, the request, the retrieved entity and ATP data, and a target universal prepopulated ATP are processed in step 2028 to generate a new ATP for the target entity. The process is then continued, proceeding with step 2048.

However, if it was determined in step 2026 not to use a universal prepopulated ATP, then a determination is made in step 2030 whether to use a segmented prepopulated ATP to generate a new ATP for the target entity. If so, the request, along with the retrieved entity and ATP data, is then processed in step 2032 to identify relevant segments of one or more segmented prepopulated ATPs. The request, the retrieved entity and ATP data, and the identified relevant ATP segments are then processed in step 2034 to generate a new ATP for the target entity. The process is then continued, proceeding with step 2048.

However, if it was determined in step 2030 not to use a segmented prepopulated ATP, then a determination is made in step 2036 whether to use an entity-pertinent prepopulated ATP to generate a new ATP for the target entity. If so, the request, along with the retrieved entity and ATP data, is processed in step 2038 to identify one or more entity-pertinent prepopulated ATPs. The request, along with the retrieved entity and ATP data, and the one or more identified entity-pertinent prepopulated ATPs are processed in step 2040 to generate a new ATP for the target entity. The process is then continued, proceeding with step 2048.

However, if it was determined in step 2036 not to use an entity-pertinent prepopulated ATP, then a determination is made in step 2042 whether to use an entity-specific prepopulated ATP to generate a new ATP for the target entity. If so, the request, along with the retrieved entity and ATP data, is processed in step 2044 to identify one or more entity-specific prepopulated ATPs. The request, along with the retrieved entity and ATP data, and the one or more identified entity-specific prepopulated ATPs are processed in step 2046 to generate a new ATP for the target entity. The process is then continued, proceeding with step 2048.

As will be appreciated by one skilled in the art, the present invention may be embodied as a method, system, or computer program product. Accordingly, embodiments of the invention may be implemented entirely in hardware, entirely in software (including firmware, resident software, micro-code, etc.) or in an embodiment combining software and hardware. These various embodiments may all generally be referred to herein as a “circuit,” “module,” or “system.” Furthermore, the present invention may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium.

Any suitable computer usable or computer readable medium may be utilized. The computer-usable or computer-readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable medium would include the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, or a magnetic storage device. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.

Computer program code for carrying out operations of the present invention may be written in an object oriented programming language such as Java, Smalltalk, C++ or the like. However, the computer program code for carrying out operations of the present invention may also be written in conventional procedural programming languages, such as the “C” programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

Embodiments of the invention are described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

While particular embodiments of the present invention have been shown and described, it will be obvious to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from this invention and its broader aspects. Therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this invention. Furthermore, it is to be understood that the invention is solely defined by the appended claims. It will be understood by those with skill in the art that if a specific number of an introduced claim element is intended, such intent will be explicitly recited in the claim, and in the absence of such recitation no such limitation is present. For non-limiting example, as an aid to understanding, the following appended claims contain usage of the introductory phrases “at least one” and “one or more” to introduce claim elements. However, the use of such phrases should not be construed to imply that the introduction of a claim element by the indefinite articles “a” or “an” limits any particular claim containing such introduced claim element to inventions containing only one such element, even when the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an”; the same holds true for the use in the claims of definite articles.

The present invention is well adapted to attain the advantages mentioned as well as others inherent therein. While the present invention has been depicted, described, and is defined by reference to particular embodiments of the invention, such references do not imply a limitation on the invention, and no such limitation is to be inferred. The invention is capable of considerable modification, alteration, and equivalents in form and function, as will occur to those ordinarily skilled in the pertinent arts. The depicted and described embodiments are examples only, and are not exhaustive of the scope of the invention.

Consequently, the invention is intended to be limited only by the spirit and scope of the appended claims, giving full cognizance to equivalents in all respects.

	Number	Date	Country
	62839060	Apr 2019	US
	62506300	May 2017	US

	Number	Date	Country
Parent	15963729	Apr 2018	US
Child	16162655		US
Parent	15720788	Sep 2017	US
Child	15878898		US

	Number	Date	Country
Parent	16415726	May 2019	US
Child	16557564		US
Parent	16162655	Oct 2018	US
Child	16415726		US
Parent	15878898	Jan 2018	US
Child	15963729		US

Using Expected Behavior of an Entity When Prepopulating an Adaptive Trust Profile

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims

Provisional Applications (2)

Continuations (2)

Continuation in Parts (3)