US11570209B2 - Detecting and mitigating attacks using forged authentication objects within a domain - Google Patents

Detecting and mitigating attacks using forged authentication objects within a domain Download PDF

Info

Publication number
US11570209B2
US11570209B2 US17/169,924 US202117169924A US11570209B2 US 11570209 B2 US11570209 B2 US 11570209B2 US 202117169924 A US202117169924 A US 202117169924A US 11570209 B2 US11570209 B2 US 11570209B2
Authority
US
United States
Prior art keywords
authentication
authentication object
network
data
hashes
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US17/169,924
Other versions
US20210297447A1 (en
Inventor
Jason Crabtree
Andrew Sellers
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Qomplx Inc
Original Assignee
Qomplx Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US14/925,974 external-priority patent/US20170124464A1/en
Priority claimed from US14/986,536 external-priority patent/US10210255B2/en
Priority claimed from US15/091,563 external-priority patent/US10204147B2/en
Priority claimed from US15/141,752 external-priority patent/US10860962B2/en
Priority claimed from US15/166,158 external-priority patent/US20170124501A1/en
Priority claimed from US15/186,453 external-priority patent/US20170124497A1/en
Priority claimed from US15/206,195 external-priority patent/US20170124492A1/en
Priority claimed from US15/237,625 external-priority patent/US10248910B2/en
Priority claimed from US15/616,427 external-priority patent/US20170371726A1/en
Priority claimed from US15/655,113 external-priority patent/US10735456B2/en
Priority claimed from US15/725,274 external-priority patent/US10609079B2/en
Priority claimed from US15/825,350 external-priority patent/US10594714B2/en
Priority claimed from US15/837,845 external-priority patent/US11005824B2/en
Application filed by Qomplx Inc filed Critical Qomplx Inc
Priority to US17/169,924 priority Critical patent/US11570209B2/en
Priority to US17/170,288 priority patent/US11570204B2/en
Assigned to QOMPLX, INC. reassignment QOMPLX, INC. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: CRABTREE, JASON, SELLERS, ANDREW
Publication of US20210297447A1 publication Critical patent/US20210297447A1/en
Priority to US17/567,060 priority patent/US20220201042A1/en
Priority to US17/960,081 priority patent/US20230113332A1/en
Priority to US17/973,520 priority patent/US11799900B2/en
Priority to US17/974,257 priority patent/US11818169B2/en
Priority to US17/986,850 priority patent/US20230171292A1/en
Application granted granted Critical
Publication of US11570209B2 publication Critical patent/US11570209B2/en
Priority to US18/184,548 priority patent/US20230308459A1/en
Priority to US18/333,414 priority patent/US20230362141A1/en
Priority to US18/339,191 priority patent/US20240163261A1/en
Priority to US18/339,214 priority patent/US20230362200A1/en
Priority to US18/361,825 priority patent/US20240022546A1/en
Assigned to QPX, LLC. reassignment QPX, LLC. PATENT ASSIGNMENT AGREEMENT TO ASSET PURCHASE AGREEMENT Assignors: QOMPLX, INC.
Assigned to QPX LLC reassignment QPX LLC CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY PREVIOUSLY RECORDED AT REEL: 064674 FRAME: 0408. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Assignors: QOMPLX, INC.
Assigned to QOMPLX LLC reassignment QOMPLX LLC CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: QPX LLC
Priority to US18/489,003 priority patent/US11968227B2/en
Priority to US18/501,977 priority patent/US12003534B2/en
Priority to US18/402,662 priority patent/US12224992B2/en
Priority to US18/582,519 priority patent/US20240195833A1/en
Priority to US18/619,162 priority patent/US20240244068A1/en
Priority to US18/639,954 priority patent/US20240267402A1/en
Priority to US18/672,024 priority patent/US20240314162A1/en
Priority to US18/779,064 priority patent/US12155693B1/en
Assigned to QOMPLX LLC reassignment QOMPLX LLC CHANGE OF ADDRESS Assignors: QOMPLX LLC
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1441—Countermeasures against malicious traffic
    • H04L63/1466—Active attacks involving interception, injection, modification, spoofing of data unit addresses, e.g. hijacking, packet injection or TCP sequence number attacks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1408—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • H04L63/1416—Event detection, e.g. attack signature detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
    • H04L63/1408—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
    • H04L63/1425—Traffic logging, e.g. anomaly detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
    • H04L9/0643—Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/321—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority
    • H04L9/3213—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials involving a third party or a trusted authority using tickets or tokens, e.g. Kerberos

Definitions

  • the disclosure relates to the field of network security, particularly to the detecting and mitigating attacks involving forged authentication objects.
  • the inventor has conceived, and reduced to practice, a system and method for detecting and mitigating authentication object forgery attacks within a domain.
  • a system for detecting and mitigating forged authentication object attacks acts as an external, and non-blocking validation service for existing implementations using an authentication domain that uses a common identity provider.
  • the system provides services to generate cryptographic hashes to legitimately-generated authentication objects, and also to check incoming authentication objects against a database of cryptographic hashes of previously-generated authentication objects (and detecting fraudulent authentication attempts by detecting attempts whose authentication objects' cryptographic hashes are not present in the database of authentication object hashes).
  • the system may also allow setting of a plurality of rules to trigger events after certain conditions are satisfied.
  • a system for detecting and mitigating attacks using forged authentication objects within a domain comprising: an authentication object inspector comprising at least a processor, a memory, and a plurality of programming instructions stored in the memory and operating on the processor, wherein the programmable instructions, when operating on the processor, cause the processor to: receive network traffic comprising a plurality of network packets, the plurality of network packets comprising at least a plurality of first authentication objects known to be generated by an identity provider associated with an authentication domain; store a record of each received authentication object, with attached metadata comprising at least a timestamp of when the authentication object was received, in a time-series database; calculate a cryptographic hash of each first authentication object using a hashing engine; store the cryptographic hashes of the first authentication objects in a database of hashes for the identity provider; receive a request for access to a network resource within the authentication domain accompanied by a second authentication object; calculate a cryptographic hash of the second authentication object using the hash
  • a method for detecting forged authentication objects within a domain comprising the steps of: (a) receiving an authentication object at an authentication object inspector, the authentication object comprising an authentication ticket for a client device communicating with an identity provider; (b) generating a cryptographic hash for the authentication ticket within the authentication object by performing at least a plurality of calculations and transformations on the authentication object using a hashing engine; (c) comparing the calculated cryptographic hash against a stored cryptographic hashes; and (d) identifying an invalid authentication ticket based on a mismatch between the calculated cryptographic hash and the stored cryptographic hash, is disclosed.
  • FIG. 1 is a diagram of an exemplary architecture of an advanced cyber decision platform according to one aspect.
  • FIG. 2 is a block diagram illustrating an exemplary system architecture for a system for detecting and mitigating forged authentication object attacks according to various embodiments of the invention.
  • FIG. 3 A is a flow diagram of an exemplary function of the business operating system in the detection and mitigation of predetermining factors leading to and steps to mitigate ongoing cyberattacks.
  • FIG. 3 B is a process diagram showing a general flow of the process used to detect rogue devices and analyze them for threats.
  • FIG. 3 C is a process diagram showing a general flow of the process used to detect and prevent privilege escalation attacks on a network.
  • FIG. 3 D is a process diagram showing a general flow of the process used to manage vulnerabilities associated with patches to network software.
  • FIGS. 4 A and 4 B are process diagrams showing business operating system functions in use to mitigate cyberattacks.
  • FIG. 5 is a process flow diagram of a method for segmenting cyberattack information to appropriate corporation parties.
  • FIG. 6 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph, according to one aspect.
  • FIG. 7 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph, according to one aspect.
  • FIG. 8 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph, according to one aspect.
  • FIG. 9 is a diagram of an exemplary architecture for a user and entity behavioral analysis system, according to one aspect.
  • FIG. 10 is a flow diagram of an exemplary method for cybersecurity behavioral analytics, according to one aspect.
  • FIG. 11 is a flow diagram of an exemplary method for measuring the effects of cybersecurity attacks, according to one aspect.
  • FIG. 12 is a flow diagram of an exemplary method for continuous cybersecurity monitoring and exploration, according to one aspect.
  • FIG. 13 is a flow diagram of an exemplary method for mapping a cyber-physical system graph (CPG), according to one aspect.
  • CPG cyber-physical system graph
  • FIG. 14 is a flow diagram of an exemplary method for continuous network resilience scoring, according to one aspect.
  • FIG. 15 is a flow diagram of an exemplary method for cybersecurity privilege oversight, according to one aspect.
  • FIG. 16 is a flow diagram of an exemplary method for cybersecurity risk management, according to one aspect.
  • FIG. 17 is a flow diagram of an exemplary method for mitigating compromised credential threats, according to one aspect.
  • FIG. 18 is a flow diagram of an exemplary method for dynamic network and rogue device discovery, according to one aspect.
  • FIG. 19 is a flow diagram of an exemplary method for Kerberos “golden ticket” attack detection, according to one aspect.
  • FIG. 20 is a flow diagram of an exemplary method for risk-based vulnerability and patch management, according to one aspect.
  • FIG. 21 is a flow diagram of an exemplary method for establishing groups of users according to one aspect.
  • FIG. 22 is a flow diagram of an exemplary method for monitoring groups for anomalous behavior, according to one aspect.
  • FIG. 23 is a flow diagram for an exemplary method for handing a detection of anomalous behavior, according to one aspect.
  • FIG. 24 is a flow diagram illustrating an exemplary method for processing a new user connection, according to one aspect.
  • FIG. 25 is a flow diagram illustrating an exemplary method for verifying the authenticity of an authentication object, according to one aspect.
  • FIG. 26 is a block diagram illustrating an exemplary hardware architecture of a computing device used in various embodiments of the invention.
  • FIG. 27 is a block diagram illustrating an exemplary logical architecture for a client device, according to various embodiments of the invention.
  • FIG. 28 is a block diagram illustrating an exemplary architectural arrangement of clients, servers, and external services, according to various embodiments of the invention.
  • FIG. 29 is another block diagram illustrating an exemplary hardware architecture of a computing device used in various embodiments of the invention.
  • FIG. 30 is a block diagram illustrating a system for detecting and mitigating attacks using forged authentication objects within a domain, according to a preferred embodiment of the invention.
  • FIG. 31 is a flow diagram illustrating a method for detecting “golden ticket” attacks within a domain, according to an aspect of the invention.
  • FIG. 32 is a flow diagram illustrating a method for detecting “silver ticket” attacks within a domain, according to an aspect of the invention.
  • FIG. 33 is a flow diagram illustrating a method for detecting “skeleton key” attacks within a domain, according to an aspect of the invention.
  • FIG. 34 is a flow diagram illustrating a method for detecting compromised credentials within a domain, according to an aspect of the invention.
  • FIG. 35 is a flow diagram illustrating a method for detecting attacks within a domain using a ticket ledger, according to an aspect of the invention.
  • the inventor has conceived, and reduced to practice, a system and method for detecting and mitigating attacks using forged authentication objects within a domain.
  • Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise.
  • devices that are in communication with each other may communicate directly or indirectly through one or more communication means or intermediaries, logical or physical.
  • steps may be performed simultaneously despite being described or implied as occurring non-simultaneously (e.g., because one step is described after the other step).
  • the illustration of a process by its depiction in a drawing does not imply that the illustrated process is exclusive of other variations and modifications thereto, does not imply that the illustrated process or any of its steps are necessary to one or more of the aspects, and does not imply that the illustrated process is preferred.
  • steps are generally described once per aspect, but this does not mean they must occur once, or that they may only occur once each time a process, method, or algorithm is carried out or executed. Some steps may be omitted in some aspects or some occurrences, or some steps may be executed more than once in a given aspect or occurrence.
  • graph is a representation of information and relationships, where each primary unit of information makes up a “node” or “vertex” of the graph and the relationship between two nodes makes up an edge of the graph.
  • Nodes can be further qualified by the connection of one or more descriptors or “properties” to that node. For example, given the node “James R,” name information for a person, qualifying properties might be “183 cm tall”, “DOB Aug. 13, 1965” and “speaks English”. Similar to the use of properties to further describe the information in a node, a relationship between two nodes that forms an edge can be qualified using a “label”.
  • transformation graphs which are highly variable in size and node, edge composition as the system processes data streams.
  • transformation graph may assume many shapes and sizes with a vast topography of edge relationships. The examples given were chosen for illustrative purposes only and represent a small number of the simplest of possibilities. These examples should not be taken to define the possible graphs expected as part of operation of the invention
  • transformation is a function performed on zero or more streams of input data which results in a single stream of output which may or may not then be used as input for another transformation. Transformations may comprise any combination of machine, human or machine-human interactions Transformations need not change data that enters them, one example of this type of transformation would be a storage transformation which would receive input and then act as a queue for that data for subsequent transformations. As implied above, a specific transformation may generate output data in the absence of input data. A time stamp serves as a example. In the invention, transformations are placed into pipelines such that the output of one transformation may serve as an input for another. These pipelines can consist of two or more transformations with the number of transformations limited only by the resources of the system.
  • transformation pipelines have been linear with each transformation in the pipeline receiving input from one antecedent and providing output to one subsequent with no branching or iteration.
  • Other pipeline configurations are possible.
  • the invention is designed to permit several of these configurations including, but not limited to: linear, afferent branch, efferent branch and cyclical.
  • a “database” or “data storage subsystem” (these terms may be considered substantially synonymous), as used herein, is a system adapted for the long-term storage, indexing, and retrieval of data, the retrieval typically being via some sort of querying interface or language.
  • “Database” may be used to refer to relational database management systems known in the art, but should not be considered to be limited to such systems.
  • Many alternative database or data storage system technologies have been, and indeed are being, introduced in the art, including but not limited to distributed non-relational data storage systems such as Hadoop, column-oriented databases, in-memory databases, and the like.
  • any data storage architecture may be used according to the aspects.
  • one or more particular data storage needs are described as being satisfied by separate components (for example, an expanded private capital markets database and a configuration database), these descriptions refer to functional uses of data storage systems and do not refer to their physical architecture.
  • any group of data storage systems of databases referred to herein may be included together in a single database management system operating on a single machine, or they may be included in a single database management system operating on a cluster of machines as is known in the art.
  • any single database (such as an expanded private capital markets database) may be implemented on a single machine, on a set of machines using clustering technology, on several machines connected by one or more messaging systems known in the art, or in a master/slave arrangement common in the art.
  • a “data context”, as used herein, refers to a set of arguments identifying the location of data. This could be a Rabbit queue, a .csv file in cloud-based storage, or any other such location reference except a single event or record. Activities may pass either events or data contexts to each other for processing. The nature of a pipeline allows for direct information passing between activities, and data locations or files do not need to be predetermined at pipeline start.
  • Each batch activity may contain a “source” data context (this may be a streaming context if the upstream activities are streaming), and a “destination” data context (which is passed to the next activity).
  • Streaming activities may have an optional “destination” streaming data context (optional meaning: caching/persistence of events vs. ephemeral), though this should not be part of the initial implementation.
  • FIG. 30 is a block diagram illustrating a system for detecting and mitigating attacks using forged authentication objects (AOs) within a domain, according to a preferred embodiment of the invention.
  • an advanced cyber decision platform (ACDP) 100 may be operated within a domain 3000 , providing analysis and predictive capabilities that are discussed in greater detail below (referring to FIG. 1 ).
  • a plurality of client devices 3010 a - n may connect to a domain controller 3020 for authentication purposes, receiving authentication tickets as appropriate when a client passes authentication (for example, when the client device is known and provides valid credentials for an account).
  • An identity provider such as a Kerberos domain controller (DC) 3020 authenticates devices and accounts before providing an authentication ticket comprising an authentication object to a requesting device, which is then used to access resources 3030 a - n within the domain according to the privileges given to the ticketholder's account.
  • DC Kerberos domain controller
  • This facilitates single sign-on (SSO) within a domain and minimizes the risks associated with passing credentials between devices in a network, as the user authenticates once and is issued a ticket that may then be checked at each resource to determine an access level, rather than requiring the user to sign on at each resource individually.
  • a client device 3010 a - n first requests a SSO ticket (also referred to as a ticket-granting-ticket, or TGT) from the DC 3020 .
  • the DC returns a TGT that is encrypted using a key known only to the DC, which is then stored on the client device.
  • the client device attempts to access a resource 3030 a - n on the network, it provides the TGT to the domain controller where it is checked for validity (for example, ensuring that the account is valid and the ticket has not expired), and if valid the account is checked for access privileges to the requested resource.
  • the DC If access is permitted, the DC returns a ticket and session key specific to the requesting client and the resource being accessed, allowing the user to access the resource transparently without the need for additional sign-on (as the tickets and keys are exchanged in the background without user involvement, and typically the exchange occurs rapidly with no apparent delay in accessing the resource).
  • this architecture is vulnerable to a variety of ticket-based attacks involving forged tickets, such as a “golden ticket” attack wherein a TGT is forged and used to obtain full domain administrator privileges (for example, by manufacturing tickets for falsified accounts with full privileges within the domain), or a “silver ticket” attack where a ticket is forged for a specific account by exploiting information that is ordinarily inaccessible in memory on a client device.
  • a plurality of listeners 3040 a - n may be installed on each of the client devices, the domain controller, and any connected resources within the domain.
  • Each listener passively collects cryptographic hashes for tickets exchanged between the DC and clients, which may then (by the ACDP) be compared against previous hashes for known-issued tickets. Attacks may then be identified based on hash mismatches, such as (for example) detecting a golden ticket attack by identifying a client passing a TGT when no TGT was previously issued to the client, or detecting a silver ticket attack by identifying when a client is passing a service ticket when no such service ticket was issued to that client.
  • hash mismatches such as (for example) detecting a golden ticket attack by identifying a client passing a TGT when no TGT was previously issued to the client, or detecting a silver ticket attack by identifying when a client is passing a service ticket when no such service ticket was issued to that client.
  • FIG. 1 is a diagram of an exemplary architecture of an advanced cyber decision platform (ACDP) 100 according to one aspect.
  • MONGODBTM MONGODBTM
  • COUCHDBTM COUCHDBTM
  • CASSANDRATM CASSANDRATM
  • REDISTM REDISTM
  • the directed computational graph module 155 retrieves one or more streams of data from a plurality of sources, which includes, but is in no way not limited to, a plurality of physical sensors, network service providers, web based questionnaires and surveys, monitoring of electronic infrastructure, crowd sourcing campaigns, and human input device information.
  • data may be split into two identical streams in a specialized pre-programmed data pipeline 155 a , wherein one sub-stream may be sent for batch processing and storage while the other sub-stream may be reformatted for transformation pipeline analysis.
  • the data is then transferred to the general transformer service module 160 for linear data transformation as part of analysis or the decomposable transformer service module 150 for branching or iterative transformations that are part of analysis.
  • the directed computational graph module 155 represents all data as directed graphs where the transformations are nodes and the result messages between transformations edges of the graph.
  • the high volume web crawling module 115 uses multiple server hosted preprogrammed web spiders, which while autonomously configured are deployed within a web scraping framework 115 a of which SCRAPYTM is an example, to identify and retrieve data of interest from web based sources that are not well tagged by conventional web crawling technology.
  • the multiple dimension time series data store module 120 may receive streaming data from a large plurality of sensors that may be of several different types.
  • the multiple dimension time series data store module may also store any time series data encountered by the system such as but not limited to enterprise network usage data, component and system logs, performance data, network service information captures such as, but not limited to news and financial feeds, and sales and service related customer data.
  • the module is designed to accommodate irregular and high volume surges by dynamically allotting network bandwidth and server processing channels to process the incoming data.
  • Inclusion of programming wrappers for languages examples of which are, but not limited to C++, PERL, PYTHON, and ERLANGTM allows sophisticated programming logic to be added to the default function of the multidimensional time series database 120 without intimate knowledge of the core programming, greatly extending breadth of function.
  • Data retrieved by the multidimensional time series database 120 and the high volume web crawling module 115 may be further analyzed and transformed into task optimized results by the directed computational graph 155 and associated general transformer service 150 and decomposable transformer service 160 modules.
  • data from the multidimensional time series database and high volume web crawling modules may be sent, often with scripted cuing information determining important vertexes 145 a , to the graph stack service module 145 which, employing standardized protocols for converting streams of information into graph representations of that data, for example, open graph internet technology although the invention is not reliant on any one standard.
  • the graph stack service module 145 represents data in graphical form influenced by any pre-determined scripted modifications 145 a and stores it in a graph-based data store 145 b such as GIRAPHTM or a key value pair type data store REDISTM, or RIAKTM, among others, all of which are suitable for storing graph-based information.
  • Results of the transformative analysis process may then be combined with further client directives, additional business rules and practices relevant to the analysis and situational information external to the already available data in the automated planning service module 130 which also runs powerful information theory 130 a based predictive statistics functions and machine learning algorithms to allow future trends and outcomes to be rapidly forecast based upon the current system derived results and choosing each a plurality of possible business decisions.
  • the automated planning service module 130 may propose business decisions most likely to result is the most favorable business outcome with a usably high level of certainty.
  • the action outcome simulation module 125 with its discrete event simulator programming module 125 a coupled with the end user facing observation and state estimation service 140 which is highly scriptable 140 b as circumstances require and has a game engine 140 a to more realistically stage possible outcomes of business decisions under consideration, allows business decision makers to investigate the probable outcomes of choosing one pending course of action over another based upon analysis of the current available data.
  • the Information Assurance department is notified by the system 100 that principal X is using credentials K (Kerberos Principal Key) never used by it before to access service Y.
  • Service Y utilizes these same credentials to access secure data on data store Z.
  • Ad hoc simulations of these traffic patterns are run against the baseline by the action outcome simulation module 125 and its discrete event simulator 125 a which is used here to determine probability space for likelihood of legitimacy.
  • the system 100 based on this data and analysis, was able to detect and recommend mitigation of a cyberattack that represented an existential threat to all business operations, presenting, at the time of the attack, information most needed for an actionable plan to human analysts at multiple levels in the mitigation and remediation effort through use of the observation and state estimation service 140 which had also been specifically preprogrammed to handle cybersecurity events 140 b.
  • a forged authentication object detection and mitigation service 910 may be used to detect and mitigate cyberattacks stemming from the use of authentication objects generated by an attacker. Service 910 is discussed in further detail below in FIG. 2 .
  • the advanced cyber decision platform a specifically programmed usage of the business operating system, continuously monitors a client enterprise's normal network activity for behaviors such as but not limited to normal users on the network, resources accessed by each user, access permissions of each user, machine to machine traffic on the network, sanctioned external access to the core network and administrative access to the network's identity and access management servers in conjunction with real-time analytics informing knowledge of cyberattack methodology.
  • the system uses this information for two purposes: First, the advanced computational analytics and simulation capabilities of the system are used to provide immediate disclosure of probable digital access points both at the network periphery and within the enterprise's information transfer and trust structure and recommendations are given on network changes that should be made to harden it prior to or during an attack.
  • the advanced cyber decision platform continuously monitors the network in real-time both for types of traffic and through techniques such as deep packet inspection for pre-decided analytically significant deviation in user traffic for indications of known cyberattack vectors such as, but not limited to, ACTIVE DIRECTORYTM/Kerberos pass-the-ticket attack, ACTIVE DIRECTORYTM/Kerberos pass-the-hash attack and the related ACTIVE DIRECTORYTM/Kerberos overpass-the-hash attack, ACTIVE DIRECTORYTM/Kerberos Skeleton Key, ACTIVE DIRECTORYTM/Kerberos golden and silver ticket attack, privilege escalation attack, compromised user credentials, ransomware disk attacks, and forged authentication object attack (also may be referred to as authentication tickets).
  • known cyberattack vectors such as, but not limited to, ACTIVE DIRECTORYTM/Kerberos pass-the-ticket attack, ACTIVE DIRECTORYTM/Kerberos pass-the-hash attack and the related ACTIVE
  • the system issues action-focused alert information to all predesignated parties specifically tailored to their roles in attack mitigation or remediation and formatted to provide predictive attack modeling based upon historic, current, and contextual attack progression analysis such that human decision makers can rapidly formulate the most effective courses of action at their levels of responsibility in command of the most actionable information with as little distractive data as possible.
  • the system then issues defensive measures in the most actionable form to end the attack with the least possible damage and exposure. All attack data are persistently stored for later forensic analysis.
  • FIG. 2 is a block diagram illustrating an exemplary system architecture 900 for a system 910 for detecting and mitigating forged authentication object attacks according to various embodiments of the invention.
  • Architecture 900 may comprise system 910 acting as a non-blocking intermediary between a connecting user 920 [ a - n ], a plurality of federated service providers (SP) 921 a - n , an identity provider (IdP) 922 , and an administrative user 923 .
  • SP federated service providers
  • IdP identity provider
  • System 910 may be configured to verifying incoming connections when the user has an AO, and also keeps track of legitimately generated AO's.
  • System 910 may comprise an AO inspector 911 , a hashing engine 912 , an event-condition-action (ECA) rules engine 913 , and a data store 914 .
  • ECA event-condition-action
  • AO inspector 911 may be configured to use faculties of ACDP 100 , for example DCG module 155 and associated transformer modules to analyze and process AO's associated with incoming connections, and observation and state estimation services 140 to monitor connections for incoming AO's. Incoming AO's may be retrieved for further analysis by system 910 .
  • Hashing engine 912 may be configured to calculate a cryptographic hash for AOs generated by identity provider 922 using functions of ACDP 100 , such as DCG module 155 , generate a cryptographic hash for both incoming AO's (for analysis purposes), and new AO's created by IdP 922 .
  • a one-way hash may be used to allow protecting of sensitive information contained in the AO, but preserving uniqueness of each AO.
  • Generated hashes may be stored in data store 914 .
  • Hashing engine may also run a hash check function, used for validating incoming AO's.
  • ECA rules engine 913 may be used by a network administrator to create and manage ECA rules that may trigger actions and queries in the event of detection of a forged AO. Rules may be for example, tracking and logging the actions of the suspicious user, deferring the suspicious connection, and the like. Rules may be nested to create a complex flow of various conditional checks and actions to create a set of “circuit breaker” checks to further ascertain the connection, or try and resolve the matter automatically before notifying a human network administrator.
  • Data store 914 may be a graph and time-series hybrid database, such as multidimensional time-series data store 120 or data store 112 , that stores hashes, ECA rules, log data, and the like, and may be quickly and efficiently queried and processed using ACDP 100 .
  • Federated service providers 921 a - n may comprise a group of trusted service partners that may share a common IdP 922 in which user 920 [ a - n ] may wish to access.
  • Federated service providers 921 a - n may be, for instance, services employing MICROSOFT'S ACTIVE DIRECTORY FEDERATED SERVICES (AS DS), AZURE AD, OKTA, many web browser single-sign-on (SSO) implementations, cloud service provides (such as, AMAZON AWS, AZURE, and GOOGLE), and the like.
  • FIG. 3 A is a flow diagram of an exemplary function of the business operating system in the detection and mitigation of predetermining factors leading to and steps to mitigate ongoing cyberattacks 200 .
  • the system continuously retrieves network traffic data 201 which may be stored and preprocessed by the multidimensional time series data store 120 and its programming wrappers 120 a . All captured data are then analyzed to predict the normal usage patterns of network nodes such as internal users, network connected systems and equipment and sanctioned users external to the enterprise boundaries for example off-site employees, contractors and vendors, just to name a few likely participants.
  • network nodes such as internal users, network connected systems and equipment and sanctioned users external to the enterprise boundaries for example off-site employees, contractors and vendors, just to name a few likely participants.
  • normal other network traffic may also be known to those skilled in the field, the list given is not meant to be exclusive and other possibilities would not fall outside the design of the invention.
  • Analysis of network traffic may include graphical analysis of parameters such as network item to network usage using specifically developed programming in the graphstack service 145 , 145 a , analysis of usage by each network item may be accomplished by specifically pre-developed algorithms associated with the directed computational graph module 155 , general transformer service module 160 and decomposable service module 150 , depending on the complexity of the individual usage profile 201 .
  • anomalous activities may include a user attempting to gain access several workstations or servers in rapid succession, or a user attempting to gain access to a domain server of server with sensitive information using random userIDs or another user's userID and password, or attempts by any user to brute force crack a privileged user's password, or replay of recently issued ACTIVE DIRECTORYTM/Kerberos ticket granting tickets, or using a forged Kerberos ticket, or the presence on any known, ongoing exploit on the network or the introduction of known malware to the network, just to name a very small sample of the cyberattack profiles known to those skilled in the field.
  • the invention being predictive as well as aware of known exploits is designed to analyze any anomalous network behavior, formulate probable outcomes of the behavior, and to then issue any needed alerts regardless of whether the attack follows a published exploit specification or exhibits novel characteristics deviant to normal network practice.
  • the system then is designed to get needed information to responding parties 206 tailored, where possible, to each role in mitigating the attack and damage arising from it 207 . This may include the exact subset of information included in alerts and updates and the format in which the information is presented which may be through the enterprise's existing security information and event management system.
  • Network administrators might receive information such as but not limited to where on the network the attack is believed to have originated, what systems are believed currently affected, predictive information on where the attack may progress, what enterprise information is at risk and actionable recommendations on repelling the intrusion and mitigating the damage, whereas a chief information security officer may receive alert including but not limited to a timeline of the cyberattack, the services and information believed compromised, what action, if any has been taken to mitigate the attack, a prediction of how the attack may unfold and the recommendations given to control and repel the attack 207 , although all parties may access any network and cyberattack information for which they have granted access at any time, unless compromise is suspected. Other specifically tailored updates may be issued by the system 206 , 207 .
  • FIG. 3 B is a process diagram showing a general flow of the process used to detect rogue devices and analyze them for threats 220 .
  • the connection is immediately sent to the rogue device detector 222 for analysis.
  • the advanced cyber decision platform uses machine learning algorithms to analyze system-wide data to detect threats.
  • the connected device is analyzed 223 to assess its device type, settings, and capabilities, the sensitivity of the data stored on the server to which the device wishes to connect, network activity, server logs, remote queries, and a multitude of other data to determine the level of threat associated with the device.
  • the device is automatically prevented from accessing the network 225 , and the system administrator is notified of the potential threat, along with contextually-based, tactical recommendations for optimal response based on potential impact 226 . Otherwise, the device is allowed to connect to the network 227 .
  • FIG. 3 C is a process diagram showing a general flow of the process used to detect and prevent privilege escalation attacks on a network (for example, “Golden Ticket” attacks) 240 .
  • a network for example, “Golden Ticket” attacks
  • the connection is immediately sent to the privilege escalation attack detector 242 for analysis.
  • the advanced cyber decision platform uses machine learning algorithms to analyze system-wide data to detect threats.
  • the access request is analyzed 243 to assess the validity of the access request using the digital signature validation, plus other system-wide information such as the sensitivity of the server being accessed, the newness of the digital signature or AO, the digital signature's or AO's prior usage, and other measures of the digital signature's or AO's validity. If the assessment determines that the access request represents a significant threat 244 , even despite the Kerberos validation of the digital signature or validation of a AO, the access request is automatically denied 245 , and the system administrator is notified of the potential threat, along with contextually-based, tactical recommendations for optimal response based on potential impact 246 . Otherwise, the access request is granted 247 .
  • FIG. 3 D is a process diagram showing a general flow of the process used to manage vulnerabilities associated with patches to network software 260 .
  • data is gathered from both sources external to the network 262 and internal to the network 263 .
  • the advanced cyber decision platform uses machine learning algorithms to analyze system-wide data to detect threats.
  • the data is analyzed 264 to determine whether network vulnerabilities exist for which a patch has not yet been created and/or applied. If the assessment determines that such a vulnerability exists 265 , whether or not all software has been patched according to manufacturer recommendations, the system administrator is notified of the potential vulnerability, along with contextually-based, tactical recommendations for optimal response based on potential impact 266 . Otherwise, network activity is allowed to continue normally 267 .
  • FIGS. 4 A and 4 B are process diagrams showing a general flow 300 of business operating system functions in use to mitigate cyberattacks.
  • Input network data which may include network flow patterns 321 , the origin and destination of each piece of measurable network traffic 322 , system logs from servers and workstations on the network 323 , endpoint data 323 a , any security event log data from servers or available security information and event (SIEM) systems 324 , external threat intelligence feeds 324 a , identity or assessment context 325 , external network health or cybersecurity feeds 326 , Kerberos domain controller or ACTIVE DIRECTORYTM server logs or instrumentation 327 and business unit performance related data 328 , among many other possible data types for which the invention was designed to analyze and integrate, may pass into 315 the business operating system 310 for analysis as part of its cyber security function.
  • SIEM security information and event
  • These multiple types of data from a plurality of sources may be transformed for analysis 311 , 312 using at least one of the specialized cybersecurity, risk assessment or common functions of the business operating system in the role of cybersecurity system, such as, but not limited to network and system user privilege oversight 331 , network and system user behavior analytics 332 , attacker and defender action timeline 333 , SIEM integration and analysis 334 , dynamic benchmarking 335 , and incident identification and resolution performance analytics 336 among other possible cybersecurity functions; value at risk (VAR) modeling and simulation 341 , anticipatory vs.
  • VAR value at risk
  • Output 317 can be used to configure network gateway security appliances 361 , to assist in preventing network intrusion through predictive change to infrastructure recommendations 362 , to alert an enterprise of ongoing cyberattack early in the attack cycle, possibly thwarting it but at least mitigating the damage 368 , to record compliance to standardized guidelines or SLA requirements 363 , to continuously probe existing network infrastructure and issue alerts to any changes which may make a breach more likely 364 , suggest solutions to any domain controller ticketing weaknesses detected 365 , detect presence of malware 366 , and perform one time or continuous vulnerability scanning depending on client directives 367 .
  • These examples are, of course, only a subset of the possible uses of the system, they are exemplary in nature and do not reflect any boundaries in the capabilities of the invention.
  • FIG. 5 is a process flow diagram of a method for segmenting cyberattack information to appropriate corporation parties 400 .
  • one of the strengths of the advanced cyber-decision platform is the ability to finely customize reports and dashboards to specific audiences, concurrently is appropriate. This customization is possible due to the devotion of a portion of the business operating system's programming specifically to outcome presentation by modules which include the observation and state estimation service 140 with its game engine 140 a and script interpreter 140 b .
  • issuance of specialized alerts, updates and reports may significantly assist in getting the correct mitigating actions done in the most timely fashion while keeping all participants informed at predesignated, appropriate granularity.
  • Examples of groups that may receive specialized information streams include but may not be limited to front line responders during the attack 404 , incident forensics support both during and after the attack 405 , chief information security officer 406 and chief risk officer 407 the information sent to the latter two focused to appraise overall damage and to implement both mitigating strategy and preventive changes after the attack.
  • Front line responders may use the cyber-decision platform's analyzed, transformed and correlated information specifically sent to them 404 a to probe the extent of the attack, isolate such things as: the predictive attacker's entry point onto the enterprise's network, the systems involved or the predictive ultimate targets of the attack and may use the simulation capabilities of the system to investigate alternate methods of successfully ending the attack and repelling the attackers in the most efficient manner, although many other queries known to those skilled in the art are also answerable by the invention. Simulations run may also include the predictive effects of any attack mitigating actions on normal and critical operation of the enterprise's IT systems and corporate users.
  • a chief information security officer may use the cyber-decision platform to predictively analyze 406 a what corporate information has already been compromised, predictively simulate the ultimate information targets of the attack that may or may not have been compromised and the total impact of the attack what can be done now and in the near future to safeguard that information.
  • the forensic responder may use the cyber-decision platform 405 a to clearly and completely map the extent of network infrastructure through predictive simulation and large volume data analysis.
  • the forensic analyst may also use the platform's capabilities to perform a time series and infrastructural spatial analysis of the attack's progression with methods used to infiltrate the enterprise's subnets and servers.
  • the chief risk officer would perform analyses of what information 407 a was stolen and predictive simulations on what the theft means to the enterprise as time progresses. Additionally, the system's predictive capabilities may be employed to assist in creation of a plan for changes of the IT infrastructural that should be made that are optimal for remediation of cybersecurity risk under possibly limited enterprise budgetary constraints in place at the company so as to maximize financial outcome.
  • FIG. 6 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph 500 , according to one aspect.
  • a DCG 500 may comprise a pipeline orchestrator 501 that may be used to perform a variety of data transformation functions on data within a processing pipeline, and may be used with a messaging system 510 that enables communication with any number of various services and protocols, relaying messages and translating them as needed into protocol-specific API system calls for interoperability with external systems (rather than requiring a particular protocol or service to be integrated into a DCG 500 ).
  • Pipeline orchestrator 501 may spawn a plurality of child pipeline clusters 502 a - b , which may be used as dedicated workers for streamlining parallel processing. In some arrangements, an entire data processing pipeline may be passed to a child cluster 502 a for handling, rather than individual processing tasks, enabling each child cluster 502 a - b to handle an entire data pipeline in a dedicated fashion to maintain isolated processing of different pipelines using different cluster nodes 502 a - b .
  • Pipeline orchestrator 501 may provide a software API for starting, stopping, submitting, or saving pipelines. When a pipeline is started, pipeline orchestrator 501 may send the pipeline information to an available worker node 502 a - b , for example using AKKATM clustering.
  • a reporting object with status information may be maintained.
  • Streaming activities may report the last time an event was processed, and the number of events processed.
  • Batch activities may report status messages as they occur.
  • Pipeline orchestrator 501 may perform batch caching using, for example, an IGFSTM caching filesystem. This allows activities 512 a - d within a pipeline 502 a - b to pass data contexts to one another, with any necessary parameter configurations.
  • a pipeline manager 511 a - b may be spawned for every new running pipeline, and may be used to send activity, status, lifecycle, and event count information to the pipeline orchestrator 501 .
  • a plurality of activity actors 512 a - d may be created by a pipeline manager 511 a - b to handle individual tasks, and provide output to data services 522 a - d .
  • Data models used in a given pipeline may be determined by the specific pipeline and activities, as directed by a pipeline manager 511 a - b .
  • Each pipeline manager 511 a - b controls and directs the operation of any activity actors 512 a - d spawned by it.
  • a pipeline process may need to coordinate streaming data between tasks.
  • a pipeline manager 511 a - b may spawn service connectors to dynamically create TCP connections between activity instances 512 a - d .
  • Data contexts may be maintained for each individual activity 512 a - d , and may be cached for provision to other activities 512 a - d as needed.
  • a data context defines how an activity accesses information, and an activity 512 a - d may process data or simply forward it to a next step. Forwarding data between pipeline steps may route data through a streaming context or batch context.
  • a client service cluster 530 may operate a plurality of service actors 521 a - d to serve the requests of activity actors 512 a - d , ideally maintaining enough service actors 521 a - d to support each activity per the service type. These may also be arranged within service clusters 520 a - d , in a manner similar to the logical organization of activity actors 512 a - d within clusters 502 a - b in a data pipeline.
  • a logging service 530 may be used to log and sample DCG requests and messages during operation while notification service 540 may be used to receive alerts and other notifications during operation (for example to alert on errors, which may then be diagnosed by reviewing records from logging service 530 ), and by being connected externally to messaging system 510 , logging and notification services can be added, removed, or modified during operation without impacting DCG 500 .
  • a plurality of DCG protocols 550 a - b may be used to provide structured messaging between a DCG 500 and messaging system 510 , or to enable messaging system 510 to distribute DCG messages across service clusters 520 a - d as shown.
  • a service protocol 560 may be used to define service interactions so that a DCG 500 may be modified without impacting service implementations. In this manner it can be appreciated that the overall structure of a system using an actor-driven DCG 500 operates in a modular fashion, enabling modification and substitution of various components without impacting other operations or requiring additional reconfiguration.
  • FIG. 7 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph 500 , according to one aspect.
  • a variant messaging arrangement may utilize messaging system 510 as a messaging broker using a streaming protocol 610 , transmitting and receiving messages immediately using messaging system 510 as a message broker to bridge communication between service actors 521 a - b as needed.
  • individual services 522 a - b may communicate directly in a batch context 620 , using a data context service 630 as a broker to batch-process and relay messages between services 522 a - b.
  • FIG. 8 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph 500 , according to one aspect.
  • a variant messaging arrangement may utilize a service connector 710 as a central message broker between a plurality of service actors 521 a - b , bridging messages in a streaming context 610 while a data context service 630 continues to provide direct peer-to-peer messaging between individual services 522 a - b in a batch context 620 .
  • FIG. 9 is a diagram of an exemplary architecture 800 for a user and entity behavioral analysis system, according to one aspect.
  • Architecture 800 may comprise a plurality of users 805 a - n , which may be individuals or connected devices, connecting to a user and entity behavioral analysis system 810 .
  • System 810 may comprise a grouping engine 813 , a behavioral analysis engine 819 , a monitoring service 822 , and a multidimensional time series data store 120 for storing gathered and processed data.
  • Grouping engine 813 may be configured to gather and identify user interactions and related metrics, which may include volume of interaction, frequency of interaction, and the like. Grouping engine 813 may use graph stack service 145 and DCG module 155 to convert and analyze the data in graph format. The interaction data may then be used to split users 805 a - n into a plurality of groups 816 a - n . Groupings may be based on department, project teams, interaction frequency, and other metrics which may be user-defined. Groupings may not be permanent, and may be adjusted and changed in real-time as group dynamics change. This may be automated by system 810 , or an administrative user may manually change the groupings.
  • Behavioral analysis engine 819 may batch process and aggregate overall usage logs, access logs, KERBEROS session data, or data collected through the use of other network monitoring tools commonly used in the art such as BRO or SURICATA. The aggregated data may then be used to generate a behavioral baseline for each group established by grouping engine 813 .
  • Behavioral analysis engine 819 may use graph stack service 145 and DCG module 155 to convert and analyze the data in graph format using various machine learning models, and may also process the data using parallel computing to quickly process large amounts of data. Models may be easily added to the system.
  • Behavioral analysis engine 819 may also be configured to process internal communications, such as email, using natural language processing. This may provide additional insight into current group dynamics so that a more accurate baseline may be established, or may provide an insight into health and mood of users.
  • Monitoring service 822 may actively monitor groups for anomalous behavior, as based the established baseline. For example, monitoring service 822 may use the data pipelines of ACDP system 100 or multidimensional time series data store 120 to conduct real-time monitoring of various network resource sensors. Aspects that may be monitored may include, but is not limited to, anomalous web browsing, for example, the number of distinct domains visited exceeding a predefined threshold; anomalous data exfiltration, for example, the amount of outgoing data exceeding a predefined threshold; unusual domain access, for example, a subgroup consisting a few members within an established group demonstrating unusual browsing behavior by accessing an unusual domain a predetermined number of times within a certain timeframe; anomalous login times, for example, a user logging into a workstation during off-hours; unlikely login locations, for example, a user logging in using an account from two distinct locations that may be physically impossible within a certain timeframe; anomalous service access, for example, unusual application access or usage pattern; and new machines, for example, a user logging into a machine or server not
  • FIG. 31 is a flow diagram illustrating a method for detecting “golden ticket” attacks within a domain, according to an aspect of the invention.
  • a malicious actor forges a TGT using compromised information (such as information dumped from memory on a client device connected to the domain, regardless of the authentication tickets actually issued to that client device), and then uses this falsified TGT to grant themselves domain administrator access.
  • a DC 3020 configured with a passive listener (as described above, with reference to FIG. 30 ) receives a request for a service ticket from a client (also known as a “principal” according to the Kerberos authentication protocol) 3101 , the request including a TGT.
  • client also known as a “principal” according to the Kerberos authentication protocol
  • the listener calculates a hash for the included TGT 3102 , and sends the hash to ACDP 100 .
  • ACDP 100 then checks 3103 for a stored hash for the requesting client, which would indicate that the TGT is valid and was previously issued to this client for use in requesting service tickets for resource access. If no existing hash is found, or an existing hash does not match the one provided, this indicates that the TGT has been forged or altered and there is a high risk that the service ticket request is part of a golden ticket attack being used to obtain illicit access to domain resources 3104 . If an existing hash is found that does match the one provided, this indicates that the TGT is valid for the requesting client, and the service ticket requests may be authorized and authentication proceeds as normal 3105 .
  • FIG. 32 is a flow diagram illustrating a method for detecting “silver ticket” attacks within a domain, according to an aspect of the invention.
  • a silver ticket attack involves a malicious actor forging a service ticket, rather than the TGT involved in a golden ticket attack.
  • a resource configured with a passive listener receives a service ticket from a client (also known as a “principal” according to the Kerberos authentication protocol) 3201 .
  • the listener calculates a hash for the service ticket 3202 , and sends the hash to ACDP 100 .
  • ACDP 100 then checks 3203 for a stored hash for the client, which would indicate that the service ticket is valid and was previously issued to this client for use in accessing the respective resource. If no existing hash is found, or an existing hash does not match the one provided, this indicates that the service ticket has been forged or altered and there is a high risk that the service ticket is part of a silver ticket attack being used to obtain illicit access to domain resources 3204 . If an existing hash is found that does match the one provided, this indicates that the service ticket is valid for the client and resource, and the client may be authorized to access the resource as normal 3205 .
  • Golden and silver ticket attacks may be detected using this hash-based approach, as forged tickets generated by malicious software contain formatting anomalies such as empty fields that would be populated if the TGT was properly-issued and valid. These anomalies result in a different hash being created than the one created for a valid TGT issued by the DC, thereby making the forged ticket obvious upon inspection.
  • care must be taken not to alert the malicious actor that they have been discovered, as they may abandon the attack prematurely and prevent the collection of important information such as from where the attack originated or what access paths were used, what was accessed using the forged ticket, or what the intent of the attack may have been.
  • a domain administrator may identify compromised accounts involved in the attack and choose to disable all but a selection of low-risk accounts; this may prevent the attacker from accessing sensitive information or causing damage to internal resources, while still allowing them some degree of activity to conceal their discovery while the administrator continues to analyze the attack.
  • FIG. 33 is a flow diagram illustrating a method for detecting “skeleton key” attacks within a domain, according to an aspect of the invention.
  • a skeleton key attack a malicious actor modifies stored keys on a DC to grant themselves the ability to change the master password, enabling additional attacks as they can take control of the DC and perform such actions as granting tickets or creating new accounts with full privileges within the domain.
  • a listener operating on a client device may inspect the client's advertised encryption types within a ticket request to determine if AES is supported 3301 .
  • a listener operating on a DC may similarly inspect the DC's advertised encryption types for AES support 3302 , as well as inspecting the encryption that appears in a DC response 3303 to the ticket request to determine whether AES encryption is used 3304 . If AES is used in the response, operation continues as normal 3305 . However, if AES is supported by both the client and DC yet does not appear in the response, this indicates that the keys stored by the DC have been tampered with 3306 , potentially as part of a skeleton key attack wherein an attacker manipulates stored keys to implant a modified key that allows use of a new master password to grant them access.
  • FIG. 34 is a flow diagram illustrating a method for detecting compromised credentials within a domain, according to an aspect of the invention.
  • a malicious actor takes control of a domain account and uses that account to access resources and perform actions while masquerading as the accountholder.
  • a listener operating on a DC may collect metadata on received requests 3401 , such as (for example, including but not limited to) username, timestamp, location, device ID, or success/failure of each request. This information may then be stored in a multidimensional time-series database (MDTSDB) 3402 with associated timestamp information.
  • MDTSDB multidimensional time-series database
  • This stored time-series data may then be analyzed using a directed computational graph (DCG) 3403 to identify regular patterns of user behavior 3404 and establish a baseline of “safe” behavior 3405 .
  • DCG analysis indicates activity outside the normal parameters, this may indicate a compromised user account 3406 , such as when a malicious actor connects using stolen credentials and behaves in a manner inconsistent with the actual accountholder.
  • FIG. 35 is a flow diagram illustrating a method for detecting attacks within a domain using a ticket ledger, according to an aspect of the invention.
  • These attacks may include exploits known as “DCSync”, “DCShadow”, and “Kerberoasting”.
  • DCSync a malicious actor that has already obtained administrator privileges (such as through a golden ticket attack) mimics a valid domain admin account in order to request additional information from the DC, such as user passwords and account information.
  • a DCShadow attack a malicious actor that has already obtained administrator privileges (such as through a golden ticket attack) mimics a domain controller to inject new data into the domain records while bypassing the normal security protocols that would prevent a nonprivileged account from modifying records.
  • Both of these attack types require administrator access and can be identified using a ticket ledger collected over time using listeners within a domain.
  • a malicious actor does not require a compromised account or any obtained privileges (unlike with DCSync and DCShadow).
  • a malicious actor also does not need to send any packets to a DC or client in order to effect the compromise; information may be collected in memory by simply connecting a device to a domain, and then it may be dumped from memory and compromised offline. The actor may then reconnect and use obtained information such as account credentials, to obtain access within the domain and potentially continue with additional attacks (for example, escalating to a silver or golden ticket attack to obtain administrator access).
  • a listener operating on a DC may collect traffic information within the domain 3501 , allowing an ACDP to compile the traffic data and build a ledger of issued tickets within the domain 3502 .
  • This ledger may be analyzed by the ACDP to identify trust relationships between domain controllers and clients 3503 . Any unusual activity, such as a DC admin account request from an account that is ordinarily unused or has no involvement with the clients for which is requesting data, may be identified as falling outside the known relationships 3504 . This unusual activity may then indicate that an administrator account is acting unusually (such as requesting information for users with which it has no established trust relationship), or new information may suddenly appear that may indicate that records have been modified as part of a DCShadow attack.
  • Spikes in activity levels may be used as an indicator of a Kerberoasting attack, indicating an account requesting or being issued more tickets than normal, which may serve as an indicator of a compromised account that may have had its credentials cracked in a Kerberoasting exploit.
  • FIG. 10 is a flow diagram of an exemplary method 1000 for cybersecurity behavioral analytics, according to one aspect.
  • behavior analytics may utilize passive information feeds from a plurality of existing endpoints (for example, including but not limited to user activity on a network, network performance, or device behavior) to generate security solutions.
  • a web crawler 115 may passively collect activity information, which may then be processed 1002 using a DCG 155 to analyze behavior patterns.
  • anomalous behavior may be recognized 1003 (for example, based on a threshold of variance from an established pattern or trend) such as high-risk users or malicious software operators such as bots.
  • anomalous behaviors may then be used 1004 to analyze potential angles of attack and then produce 1005 security suggestions based on this second-level analysis and predictions generated by an action outcome simulation module 125 to determine the likely effects of the change.
  • the suggested behaviors may then be automatically implemented 1006 as needed.
  • Passive monitoring 1001 then continues, collecting information after new security solutions are implemented 1006 , enabling machine learning to improve operation over time as the relationship between security changes and observed behaviors and threats are observed and analyzed.
  • This method 1000 for behavioral analytics enables proactive and high-speed reactive defense capabilities against a variety of cyberattack threats, including anomalous human behaviors as well as nonhuman “bad actors” such as automated software bots that may probe for, and then exploit, existing vulnerabilities.
  • Using automated behavioral learning in this manner provides a much more responsive solution than manual intervention, enabling rapid response to threats to mitigate any potential impact.
  • Utilizing machine learning behavior further enhances this approach, providing additional proactive behavior that is not possible in simple automated approaches that merely react to threats as they occur.
  • FIG. 11 is a flow diagram of an exemplary method 1100 for measuring the effects of cybersecurity attacks, according to one aspect.
  • impact assessment of an attack may be measured using a DCG 155 to analyze a user account and identify its access capabilities 1101 (for example, what files, directories, devices or domains an account may have access to). This may then be used to generate 1102 an impact assessment score for the account, representing the potential risk should that account be compromised.
  • the impact assessment score for any compromised accounts may be used to produce a “blast radius” calculation 1103 , identifying exactly what resources are at risk as a result of the intrusion and where security personnel should focus their attention.
  • simulated intrusions may be run 1104 to identify potential blast radius calculations for a variety of attacks and to determine 1105 high risk accounts or resources so that security may be improved in those key areas rather than focusing on reactive solutions.
  • FIG. 12 is a flow diagram of an exemplary method 1200 for continuous cybersecurity monitoring and exploration, according to one aspect.
  • a state observation service 140 may receive data from a variety of connected systems 1201 such as (for example, including but not limited to) servers, domains, databases, or user directories. This information may be received continuously, passively collecting events and monitoring activity over time while feeding 1202 collected information into a graphing service 145 for use in producing time-series graphs 1203 of states and changes over time. This collated time-series data may then be used to produce a visualization 1204 of changes over time, quantifying collected data into a meaningful and understandable format.
  • connected systems 1201 such as (for example, including but not limited to) servers, domains, databases, or user directories.
  • This information may be received continuously, passively collecting events and monitoring activity over time while feeding 1202 collected information into a graphing service 145 for use in producing time-series graphs 1203 of states and changes over time.
  • This collated time-series data may then be used to produce
  • FIG. 13 is a flow diagram of an exemplary method 1300 for mapping a cyber-physical system graph (CPG), according to one aspect.
  • a cyber-physical system graph may comprise a visualization of hierarchies and relationships between devices and resources in a security infrastructure, contextualizing security information with physical device relationships that are easily understandable for security personnel and users.
  • behavior analytics information (as described previously, referring to FIG. 10 ) may be received at a graphing service 145 for inclusion in a CPG.
  • impact assessment scores (as described previously, referring to FIG. 11 ) may be received and incorporated in the CPG information, adding risk assessment context to the behavior information.
  • time-series information (as described previously, referring to FIG. 12 ) may be received and incorporated, updating CPG information as changes occur and events are logged.
  • This information may then be used to produce 1304 a graph visualization of users, servers, devices, and other resources correlating physical relationships (such as a user's personal computer or smartphone, or physical connections between servers) with logical relationships (such as access privileges or database connections), to produce a meaningful and contextualized visualization of a security infrastructure that reflects the current state of the internal relationships present in the infrastructure.
  • FIG. 14 is a flow diagram of an exemplary method 1400 for continuous network resilience scoring, according to one aspect.
  • a baseline score can be used to measure an overall level of risk for a network infrastructure, and may be compiled by first collecting 1401 information on publicly-disclosed vulnerabilities, such as (for example) using the Internet or common vulnerabilities and exploits (CVE) process. This information may then 1402 be incorporated into a CPG as described previously in FIG. 13 , and the combined data of the CPG and the known vulnerabilities may then be analyzed 1403 to identify the relationships between known vulnerabilities and risks exposed by components of the infrastructure. This produces a combined CPG 1404 that incorporates both the internal risk level of network resources, user accounts, and devices as well as the actual risk level based on the analysis of known vulnerabilities and security risks.
  • CVE common vulnerabilities and exploits
  • FIG. 15 is a flow diagram of an exemplary method 1500 for cybersecurity privilege oversight, according to one aspect.
  • time-series data (as described above, referring to FIG. 12 ) may be collected 1501 for user accounts, credentials, directories, and other user-based privilege and access information.
  • This data may then 1502 be analyzed to identify changes over time that may affect security, such as modifying user access privileges or adding new users.
  • the results of analysis may be checked 1503 against a CPG (as described previously in FIG. 13 ), to compare and correlate user directory changes with the actual infrastructure state.
  • CPG as described previously in FIG. 13
  • This comparison may be used to perform accurate and context-enhanced user directory audits 1504 that identify not only current user credentials and other user-specific information, but changes to this information over time and how the user information relates to the actual infrastructure (for example, credentials that grant access to devices and may therefore implicitly grant additional access due to device relationships that were not immediately apparent from the user directory alone).
  • FIG. 16 is a flow diagram of an exemplary method 1600 for cybersecurity risk management, according to one aspect.
  • multiple methods described previously may be combined to provide live assessment of attacks as they occur, by first receiving 1601 time-series data for an infrastructure (as described previously, in FIG. 12 ) to provide live monitoring of network events.
  • This data is then enhanced 1602 with a CPG (as described above in FIG. 13 ) to correlate events with actual infrastructure elements, such as servers or accounts.
  • an event for example, an attempted attack against a vulnerable system or resource
  • the event is logged in the time-series data 1604 , and compared against the CPG 1605 to determine the impact.
  • This is enhanced with the inclusion of impact assessment information 1606 for any affected resources, and the attack is then checked against a baseline score 1607 to determine the full extent of the impact of the attack and any necessary modifications to the infrastructure or policies.
  • FIG. 17 is a flow diagram of an exemplary method 1700 for mitigating compromised credential threats, according to one aspect.
  • impact assessment scores (as described previously, referring to FIG. 11 ) may be collected 1701 for user accounts in a directory, so that the potential impact of any given credential attack is known in advance of an actual attack event.
  • This information may be combined with a CPG 1702 as described previously in FIG. 13 , to contextualize impact assessment scores within the infrastructure (for example, so that it may be predicted what systems or resources might be at risk for any given credential attack).
  • a simulated attack may then be performed 1703 to use machine learning to improve security without waiting for actual attacks to trigger a reactive response.
  • a blast radius assessment (as described above in FIG. 11 ) may be used in response 1704 to determine the effects of the simulated attack and identify points of weakness, and produce a recommendation report 1705 for improving and hardening the infrastructure against future attacks.
  • FIG. 18 is a flow diagram of an exemplary method 1800 for dynamic network and rogue device discovery, according to one aspect.
  • an advanced cyber decision platform may continuously monitor a network in real-time 1801 , detecting any changes as they occur.
  • a CPG may be updated 1803 with the new connection information, which may then be compared against the network's resiliency score 1804 to examine for potential risk.
  • the blast radius metric for any other devices involved in the connection may also be checked 1805 , to examine the context of the connection for risk potential (for example, an unknown connection to an internal data server with sensitive information may be considered a much higher risk than an unknown connection to an externally-facing web server). If the connection is a risk, an alert may be sent to an administrator 1806 with the contextual information for the connection to provide a concise notification of relevant details for quick handling.
  • FIG. 19 is a flow diagram of an exemplary method 1900 for Kerberos “golden ticket” attack detection, according to one aspect.
  • behavioral analytics may be employed to detect erroneously-issued authentication tickets or forged AO's, whether from incorrect configuration or from an attack.
  • an advanced cyber decision platform may continuously monitor a network 1901 , informing a CPG in real-time of all traffic associated with people, places, devices, or services 1902 .
  • Machine learning algorithms detect behavioral anomalies as they occur in real-time 1903 , notifying administrators with an assessment of the anomalous event 1904 as well as a blast radius score for the particular event and a network resiliency score to advise of the overall health of the network.
  • a compromised ticket is immediately detected when a new authentication connection is made.
  • FIG. 20 is a flow diagram of an exemplary method 2000 for risk-based vulnerability and patch management, according to one aspect.
  • an advanced cyber decision platform may monitor all information about a network 2001 , including (but not limited to) device telemetry data, log files, connections and network events, deployed software versions, or contextual user activity information. This information is incorporated into a CPG 2002 to maintain an up-to-date model of the network in real-time.
  • a blast radius score may be assessed 2003 and the network's resiliency score may be updated 2004 as needed.
  • a security alert may then be produced 2005 to notify an administrator of the vulnerability and its impact, and a proposed patch may be presented 2006 along with the predicted effects of the patch on the vulnerability's blast radius and the overall network resiliency score. This determines both the total impact risk of any particular vulnerability, as well as the overall effect of each vulnerability on the network as a whole.
  • This continuous network assessment may be used to collect information about new vulnerabilities and exploits to provide proactive solutions with clear result predictions, before attacks occur.
  • FIG. 21 is a flow diagram of an exemplary method 2100 for establishing groups of users according to one aspect.
  • data pertaining to network interaction between users and devices are gathered by a grouping engine.
  • the grouping engine may then process the gathered information by converting it to a graph format and using DCG module to establish groupings for users.
  • a system administrator may provide additional input, and fine-tune the groupings if required.
  • a behavioral baseline is established for each group that may be based on the interaction information, network logs, connected devices, and the like.
  • groups are continuous monitored for anomalous behavior.
  • FIG. 22 is a flow diagram of an exemplary method 2200 for monitoring groups for anomalous behavior, according to one aspect.
  • a system gathers network-related data. This data may comprise usage logs, Kerberos session data, computers and other devices connected to the network, active users, software installed, and the like.
  • a behavioral analysis engine may process the data. Parallel computing may be used to speed up the processing of the data. The data may then be sorted by, and associated to, previously established groupings.
  • a behavioral baseline score is generated for each group based on the results of the data processing.
  • the data is stored into a time-series graph database.
  • the process repeats periodically to create snapshots of various moments in time, and stored into the database. This may allow the system to retrain the baseline to take into considering non-anomalous baseline variances that may occur over time, as well as forecast changes in group dynamics using predictive analysis functions of ACDP system 100 .
  • FIG. 23 is a flow diagram for an exemplary method 2300 for handing a detection of anomalous behavior, according to one aspect.
  • the system detects anomalous user behavior from a group. This may be based on comparison to established baselines, or a high priority incident caught during routine monitoring, for example a device accessing a blacklisted domain.
  • the system investigates the group in which the anomalous behavior originated. This may include a more thorough analysis of usage and access logs. If applicable, users or devices with higher access privileges may be investigated before those with lower access privileges.
  • the source or sources of the anomalous behavior is identified, and some corrective measures may be taken.
  • the offending device or user account may be automatically locked out of the network until a solution has been implemented.
  • group members and system administrators may be notified.
  • the system may utilize the various techniques discussed above to recommend a corrective action, or the system may take action automatically.
  • FIG. 24 is a flow diagram illustrating an exemplary method 2400 for processing a new user connection, according to one aspect.
  • system 910 detects a user connecting to a monitored service provider.
  • step 2406 if the user is connecting with an existing AO, the process leads to the method discussed in FIG. 25 at step 2409 .
  • the service provider forwards the user to an identity provider at step 2412 .
  • the identity provider prompts the user for identifying information, such as a username and password.
  • the IdP after successful verification, the IdP generates a unique AO for the user.
  • system 910 retrieves the AO and uses a hashing engine to calculate a cryptographic hash for the newly generated AO, and stores the hash in a data store.
  • FIG. 25 is a flow diagram illustrating an exemplary method 2500 for verifying the authenticity of an authentication object, according to one aspect.
  • a user with an AO connects to a monitored service provider.
  • system 910 detects the connection request, retrieves the AO, and generates a cryptographic hash for the AO.
  • System 910 may now compare the newly generated hashes with previous generated hashes stored in memory.
  • step 2509 if the AO is found to be authentic, the connect proceeds as normal and method 2500 ends at step 2512 as no further action for this session is required.
  • step 2515 ECA rules may be triggered to perform their preset functions, and perform “circuit breaker” checks within a user-configurable time period.
  • step 2518 a network administrator at step may be notified, and sent any relevant information, such as blast radius, access logs for the forged AO connection, and the like.
  • the techniques disclosed herein may be implemented on hardware or a combination of software and hardware. For example, they may be implemented in an operating system kernel, in a separate user process, in a library package bound into network applications, on a specially constructed machine, on an application-specific integrated circuit (ASIC), or on a network interface card.
  • ASIC application-specific integrated circuit
  • Software/hardware hybrid implementations of at least some of the aspects disclosed herein may be implemented on a programmable network-resident machine (which should be understood to include intermittently connected network-aware machines) selectively activated or reconfigured by a computer program stored in memory.
  • a programmable network-resident machine which should be understood to include intermittently connected network-aware machines
  • Such network devices may have multiple network interfaces that may be configured or designed to utilize different types of network communication protocols.
  • a general architecture for some of these machines may be described herein in order to illustrate one or more exemplary means by which a given unit of functionality may be implemented.
  • At least some of the features or functionalities of the various aspects disclosed herein may be implemented on one or more general-purpose computers associated with one or more networks, such as for example an end-user computer system, a client computer, a network server or other server system, a mobile computing device (e.g., tablet computing device, mobile phone, smartphone, laptop, or other appropriate computing device), a consumer electronic device, a music player, or any other suitable electronic device, router, switch, or other suitable device, or any combination thereof.
  • at least some of the features or functionalities of the various aspects disclosed herein may be implemented in one or more virtualized computing environments (e.g., network computing clouds, virtual machines hosted on one or more physical computing machines, or other appropriate virtual environments).
  • Computing device 10 may be, for example, any one of the computing machines listed in the previous paragraph, or indeed any other electronic device capable of executing software- or hardware-based instructions according to one or more programs stored in memory.
  • Computing device 10 may be configured to communicate with a plurality of other computing devices, such as clients or servers, over communications networks such as a wide area network a metropolitan area network, a local area network, a wireless network, the Internet, or any other network, using known protocols for such communication, whether wireless or wired.
  • communications networks such as a wide area network a metropolitan area network, a local area network, a wireless network, the Internet, or any other network, using known protocols for such communication, whether wireless or wired.
  • computing device 10 includes one or more central processing units (CPU) 12 , one or more interfaces 15 , and one or more busses 14 (such as a peripheral component interconnect (PCI) bus).
  • CPU 12 may be responsible for implementing specific functions associated with the functions of a specifically configured computing device or machine.
  • a computing device 10 may be configured or designed to function as a server system utilizing CPU 12 , local memory 11 and/or remote memory 16 , and interface(s) 15 .
  • CPU 12 may be caused to perform one or more of the different types of functions and/or operations under the control of software modules or components, which for example, may include an operating system and any appropriate applications software, drivers, and the like.
  • CPU 12 may include one or more processors 13 such as, for example, a processor from one of the Intel, ARM, Qualcomm, and AMD families of microprocessors.
  • processors 13 may include specially designed hardware such as application-specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), field-programmable gate arrays (FPGAs), and so forth, for controlling operations of computing device 10 .
  • ASICs application-specific integrated circuits
  • EEPROMs electrically erasable programmable read-only memories
  • FPGAs field-programmable gate arrays
  • a local memory 11 such as non-volatile random access memory (RAM) and/or read-only memory (ROM), including for example one or more levels of cached memory
  • RAM non-volatile random access memory
  • ROM read-only memory
  • Memory 11 may be used for a variety of purposes such as, for example, caching and/or storing data, programming instructions, and the like. It should be further appreciated that CPU 12 may be one of a variety of system-on-a-chip (SOC) type hardware that may include additional hardware such as memory or graphics processing chips, such as a QUALCOMM SNAPDRAGONTM or SAMSUNG EXYNOSTM CPU as are becoming increasingly common in the art, such as for use in mobile devices or integrated devices.
  • SOC system-on-a-chip
  • processor is not limited merely to those integrated circuits referred to in the art as a processor, a mobile processor, or a microprocessor, but broadly refers to a microcontroller, a microcomputer, a programmable logic controller, an application-specific integrated circuit, and any other programmable circuit.
  • interfaces 15 are provided as network interface cards (NICs).
  • NICs control the sending and receiving of data packets over a computer network; other types of interfaces 15 may for example support other peripherals used with computing device 10 .
  • the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, graphics interfaces, and the like.
  • interfaces may be provided such as, for example, universal serial bus (USB), Serial, Ethernet, FIREWIRETM, THUNDERBOLTTM, PCI, parallel, radio frequency (RF), BLUETOOTHTM, near-field communications (e.g., using near-field magnetics), 802.11 (WiFi), frame relay, TCP/IP, ISDN, fast Ethernet interfaces, Gigabit Ethernet interfaces, Serial ATA (SATA) or external SATA (ESATA) interfaces, high-definition multimedia interface (HDMI), digital visual interface (DVI), analog or digital audio interfaces, asynchronous transfer mode (ATM) interfaces, high-speed serial interface (HSSI) interfaces, Point of Sale (POS) interfaces, fiber data distributed interfaces (FDDIs), and the like.
  • USB universal serial bus
  • RF radio frequency
  • BLUETOOTHTM near-field communications
  • near-field communications e.g., using near-field magnetics
  • WiFi wireless FIREWIRETM
  • Such interfaces 15 may include physical ports appropriate for communication with appropriate media. In some cases, they may also include an independent processor (such as a dedicated audio or video processor, as is common in the art for high-fidelity AN hardware interfaces) and, in some instances, volatile and/or non-volatile memory (e.g., RAM).
  • an independent processor such as a dedicated audio or video processor, as is common in the art for high-fidelity AN hardware interfaces
  • volatile and/or non-volatile memory e.g., RAM
  • FIG. 26 illustrates one specific architecture for a computing device 10 for implementing one or more of the aspects described herein, it is by no means the only device architecture on which at least a portion of the features and techniques described herein may be implemented.
  • architectures having one or any number of processors 13 may be used, and such processors 13 may be present in a single device or distributed among any number of devices.
  • a single processor 13 handles communications as well as routing computations, while in other aspects a separate dedicated communications processor may be provided.
  • different types of features or functionalities may be implemented in a system according to the aspect that includes a client device (such as a tablet device or smartphone running client software) and server systems (such as a server system described in more detail below).
  • the system of an aspect may employ one or more memories or memory modules (such as, for example, remote memory block 16 and local memory 11 ) configured to store data, program instructions for the general-purpose network operations, or other information relating to the functionality of the aspects described herein (or any combinations of the above).
  • Program instructions may control execution of or comprise an operating system and/or one or more applications, for example.
  • Memory 16 or memories 11 , 16 may also be configured to store data structures, configuration data, encryption data, historical system operations information, or any other specific or generic non-program information described herein.
  • At least some network device aspects may include nontransitory machine-readable storage media, which, for example, may be configured or designed to store program instructions, state information, and the like for performing various operations described herein.
  • nontransitory machine-readable storage media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as optical disks, and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM), flash memory (as is common in mobile devices and integrated systems), solid state drives (SSD) and “hybrid SSD” storage drives that may combine physical components of solid state and hard disk drives in a single hardware device (as are becoming increasingly common in the art with regard to personal computers), memristor memory, random access memory (RAM), and the like.
  • ROM read-only memory
  • flash memory as is common in mobile devices and integrated systems
  • SSD solid state drives
  • hybrid SSD hybrid SSD
  • such storage means may be integral and non-removable (such as RAM hardware modules that may be soldered onto a motherboard or otherwise integrated into an electronic device), or they may be removable such as swappable flash memory modules (such as “thumb drives” or other removable media designed for rapidly exchanging physical storage devices), “hot-swappable” hard disk drives or solid state drives, removable optical storage discs, or other such removable media, and that such integral and removable storage media may be utilized interchangeably.
  • swappable flash memory modules such as “thumb drives” or other removable media designed for rapidly exchanging physical storage devices
  • hot-swappable hard disk drives or solid state drives
  • removable optical storage discs or other such removable media
  • program instructions include both object code, such as may be produced by a compiler, machine code, such as may be produced by an assembler or a linker, byte code, such as may be generated by for example a JAVATM compiler and may be executed using a Java virtual machine or equivalent, or files containing higher level code that may be executed by the computer using an interpreter (for example, scripts written in Python, Perl, Ruby, Groovy, or any other scripting language).
  • interpreter for example, scripts written in Python, Perl, Ruby, Groovy, or any other scripting language.
  • FIG. 27 there is shown a block diagram depicting a typical exemplary architecture of one or more aspects or components thereof on a standalone computing system.
  • Computing device 20 includes processors 21 that may run software that carry out one or more functions or applications of aspects, such as for example a client application 24 .
  • Processors 21 may carry out computing instructions under control of an operating system 22 such as, for example, a version of MICROSOFT WINDOWSTM operating system, APPLE macOSTM or iOSTM operating systems, some variety of the Linux operating system, ANDROIDTM operating system, or the like.
  • an operating system 22 such as, for example, a version of MICROSOFT WINDOWSTM operating system, APPLE macOSTM or iOSTM operating systems, some variety of the Linux operating system, ANDROIDTM operating system, or the like.
  • one or more shared services 23 may be operable in system 20 , and may be useful for providing common services to client applications 24 .
  • Services 23 may for example be WINDOWSTM services, user-space common services in a Linux environment, or any other type of common service architecture used with operating system 21 .
  • Input devices 28 may be of any type suitable for receiving user input, including for example a keyboard, touchscreen, microphone (for example, for voice input), mouse, touchpad, trackball, or any combination thereof.
  • Output devices 27 may be of any type suitable for providing output to one or more users, whether remote or local to system 20 , and may include for example one or more screens for visual output, speakers, printers, or any combination thereof.
  • Memory 25 may be random-access memory having any structure and architecture known in the art, for use by processors 21 , for example to run software.
  • Storage devices 26 may be any magnetic, optical, mechanical, memristor, or electrical storage device for storage of data in digital form (such as those described above, referring to FIG. 26 ). Examples of storage devices 26 include flash memory, magnetic hard drive, CD-ROM, and/or the like.
  • systems may be implemented on a distributed computing network, such as one having any number of clients and/or servers.
  • FIG. 28 there is shown a block diagram depicting an exemplary architecture 30 for implementing at least a portion of a system according to one aspect on a distributed computing network.
  • any number of clients 33 may be provided.
  • Each client 33 may run software for implementing client-side portions of a system; clients may comprise a system 20 such as that illustrated in FIG. 27 .
  • any number of servers 32 may be provided for handling requests received from one or more clients 33 .
  • Clients 33 and servers 32 may communicate with one another via one or more electronic networks 31 , which may be in various aspects any of the Internet, a wide area network, a mobile telephony network (such as CDMA or GSM cellular networks), a wireless network (such as WiFi, WiMAX, LTE, and so forth), or a local area network (or indeed any network topology known in the art; the aspect does not prefer any one network topology over any other).
  • Networks 31 may be implemented using any known network protocols, including for example wired and/or wireless protocols.
  • servers 32 may call external services 37 when needed to obtain additional information, or to refer to additional data concerning a particular call. Communications with external services 37 may take place, for example, via one or more networks 31 .
  • external services 37 may comprise web-enabled services or functionality related to or installed on the hardware device itself. For example, in one aspect where client applications 24 are implemented on a smartphone or other electronic device, client applications 24 may obtain information stored in a server system 32 in the cloud or on an external service 37 deployed on one or more of a particular enterprise's or user's premises.
  • clients 33 or servers 32 may make use of one or more specialized services or appliances that may be deployed locally or remotely across one or more networks 31 .
  • one or more databases 34 may be used or referred to by one or more aspects. It should be understood by one having ordinary skill in the art that databases 34 may be arranged in a wide variety of architectures and using a wide variety of data access and manipulation means.
  • one or more databases 34 may comprise a relational database system using a structured query language (SQL), while others may comprise an alternative data storage technology such as those referred to in the art as “NoSQL” (for example, HADOOP CASSANDRATM, GOOGLE BIGTABLETM, and so forth).
  • SQL structured query language
  • variant database architectures such as column-oriented databases, in-memory databases, clustered databases, distributed databases, or even flat file data repositories may be used according to the aspect. It will be appreciated by one having ordinary skill in the art that any combination of known or future database technologies may be used as appropriate, unless a specific database technology or a specific arrangement of components is specified for a particular aspect described herein. Moreover, it should be appreciated that the term “database” as used herein may refer to a physical database machine, a cluster of machines acting as a single database system, or a logical database within an overall database management system.
  • security and configuration management are common information technology (IT) and web functions, and some amount of each are generally associated with any IT or web systems. It should be understood by one having ordinary skill in the art that any configuration or security subsystems known in the art now or in the future may be used in conjunction with aspects without limitation, unless a specific security 36 or configuration system 35 or approach is specifically required by the description of any specific aspect.
  • IT information technology
  • FIG. 29 shows an exemplary overview of a computer system 40 as may be used in any of the various locations throughout the system. It is exemplary of any computer that may execute code to process data. Various modifications and changes may be made to computer system 40 without departing from the broader scope of the system and method disclosed herein.
  • Central processor unit (CPU) 41 is connected to bus 42 , to which bus is also connected memory 43 , nonvolatile memory 44 , display 47 , input/output (I/O) unit 48 , and network interface card (NIC) 53 .
  • I/O unit 48 may, typically, be connected to keyboard 49 , pointing device 50 , hard disk 52 , and real-time clock 51 .
  • NIC 53 connects to network 54 , which may be the Internet or a local network, which local network may or may not have connections to the Internet. Also shown as part of system 40 is power supply unit 45 connected, in this example, to a main alternating current (AC) supply 46 . Not shown are batteries that could be present, and many other devices and modifications that are well known but are not applicable to the specific novel functions of the current system and method disclosed herein.
  • AC alternating current
  • functionality for implementing systems or methods of various aspects may be distributed among any number of client and/or server components.
  • various software modules may be implemented for performing various functions in connection with the system of any particular aspect, and such modules may be variously implemented to run on server and/or client components.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Power Engineering (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

A system for detecting and mitigating attacks using forged authentication objects within a domain is provided, comprising an authentication object inspector configured to observe a new authentication object generated by an identity provider, and retrieve the new authentication object; and a hashing engine configured to retrieve the new authentication object from the authentication object inspector, calculate a cryptographic hash for the new authentication object, and store the cryptographic hash for the new authentication object in a data store; wherein subsequent access requests accompanied by authentication objects are validated by comparing hashes for each authentication object to previous generated hashes.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
Application
No. Date Filed Title
Current Herewith DETECTING AND MITIGATING
application ATTACKS USING FORGED
AUTHENTICATION OBJECTS WITHIN
A DOMAIN
Is a continuation-in-part of:
15/837,845 Dec. 11, 2017 DETECTING AND MITIGATING
FORGED AUTHENTICATION OBJECT
ATTACKS USING AN ADVANCED
CYBER DECISION PLATFORM
which claims benefit of and priority to:
62/596,105 Dec. 7, 2017 DETECTING AND MITIGATING
FORGED AUTHENTICATION OBJECT
ATTACKS USING AN ADVANCED
CYBER DECISION PLATFORM
and is a continuation-in-part of:
15/825,350 Nov. 29, 2017 USER AND ENTITY BEHAVIORAL
patent Issue Date ANALYSIS USING AN ADVANCED
10,594,714 Mar. 17, 2020 CYBER DECISION PLATFORM
which is a continuation-in-part of:
15/725,274 Oct. 4, 2017 APPLICATION OF ADVANCED
patent Issue Date CYBERSECURITY THREAT
10,609,079 Mar. 31, 2020 MITIGATION TO ROGUE DEVICES,
PRIVILEGE ESCALATION, AND
RISK-BASED VULNERABILITY
AND PATCH MANAGEMENT
which is a continuation-in-part of:
15/655,113 Jul. 20, 2017 ADVANCED CYBERSECURITY
patent Issue Date THREAT MITIGATION USING
10,735,456 Aug. 4, 2020 BEHAVIORAL AND DEEP
ANALYTICS
which is a continuation-in-part of:
15/616,427 Jun. 7, 2017 RAPID PREDICTIVE ANALYSIS OF
VERY LARGE DATA SETS USING AN
ACTOR-DRIVEN DISTRIBUTED
COMPUTATIONAL GRAPH
which is a continuation-in-part of:
14/925,974 Oct. 28, 2015 DETECTION MITIGATION AND
REMEDIATION OF CYBERATTACKS
EMPLOYING AN ADVANCED
CYBER-DECISION PLATFORM
which is a continuation-in-part of:
15/237,625 Aug. 15, 2016 DETECTION MITIGATION AND
patent Issue Date REMEDIATION OF CYBERATTACKS
10,248,910 Apr. 2, 2019 EMPLOYING AN ADVANCED
CYBER-DECISION PLATFORM
which is a continuation-in-part of:
15/206,195 Jul. 8, 2016 ACCURATE AND DETAILED
MODELING OF SYSTEMS WITH
LARGE COMPLEX DATASETS USING
A DISTRIBUTED SIMULATION
ENGINE
which is a continuation-in-part of:
15/186,453 Jun. 18, 2016 SYSTEM FOR AUTOMATED
CAPTURE AND ANALYSIS OF
BUSINESS INFORMATION FOR
RELIABLE BUSINESS VENTURE
OUTCOME PREDICTION
which is a continuation-in-part of:
15/166,158 May 26, 2016 SYSTEM FOR AUTOMATED
CAPTURE AND ANALYSIS OF
BUSINESS INFORMATION FOR
SECURITY AND CLIENT-FACING
INFRASTRUCTURE RELIABILITY
which is a continuation-in-part of:
15/141,752 Apr. 28, 2016 SYSTEM FOR FULLY INTEGRATED
patent Issue Date CAPTURE, AND ANALYSIS OF
10,860,962 Dec. 8, 2020 BUSINESS INFORMATION
RESULTING IN PREDICTIVE
DECISION MAKING AND
SIMULATION
which is a continuation-in-part of:
15/091,563 Apr. 5, 2016 SYSTEM FOR CAPTURE, ANALYSIS
patent Issue Date AND STORAGE OF TIME SERIES
10,204,147 Feb. 12, 2019 DATA FROM SENSORS WITH
HETEROGENEOUS REPORT
INTERVAL PROFILES
and is also a continuation-in-part of:
14/986,536 Dec. 31, 2015 DISTRIBUTED SYSTEM FOR LARGE
patent Issue Date VOLUME DEEP WEB DATA
10,210,255 Feb. 19, 2019 EXTRACTION
and is also a continuation-in-part of:
14/925,974 Oct. 28, 2015 RAPID PREDICTIVE ANALYSIS OF
VERY LARGE DATA SETS USING
THE DISTRIBUTED
COMPUTATIONAL GRAPH
the entire specification of each of which is incorporated herein by reference.
BACKGROUND OF THE INVENTION Field of the Invention
The disclosure relates to the field of network security, particularly to the detecting and mitigating attacks involving forged authentication objects.
Discussion of the State of the Art
Maintaining the security of computer systems is a matter of great economic significance in the modern world. At the same time, computer users within large enterprises, which maintain one or several protected computing domains each comprising many computers and other devices, often require secure access on many devices across the domain. A common way of providing this securely is to use domain controllers to provide authentication objects for users—after they successfully authenticate themselves—so that they can access those devices, applications, and services within the domain that are authorized for their particular user profile. Unfortunately, even with strong authentication systems such as KERBEROS, which is used within Microsoft Active Directory domains, security lapses do occur. In particular, a variety of KERBEROS-based attack vectors have been shown to be possible, including “golden ticket” and “silver ticket” attacks, which may grant to hostile attackers potentially unlimited access to and control of vital domain assets if not detected quickly.
What is needed is a system that can detect, in real-time, ticket-based KERBEROS attacks in enterprise domains.
SUMMARY OF THE INVENTION
Accordingly, the inventor has conceived, and reduced to practice, a system and method for detecting and mitigating authentication object forgery attacks within a domain.
In a typical embodiment, a system for detecting and mitigating forged authentication object attacks acts as an external, and non-blocking validation service for existing implementations using an authentication domain that uses a common identity provider. The system provides services to generate cryptographic hashes to legitimately-generated authentication objects, and also to check incoming authentication objects against a database of cryptographic hashes of previously-generated authentication objects (and detecting fraudulent authentication attempts by detecting attempts whose authentication objects' cryptographic hashes are not present in the database of authentication object hashes). The system may also allow setting of a plurality of rules to trigger events after certain conditions are satisfied.
In one aspect of the invention, a system for detecting and mitigating attacks using forged authentication objects within a domain, comprising: an authentication object inspector comprising at least a processor, a memory, and a plurality of programming instructions stored in the memory and operating on the processor, wherein the programmable instructions, when operating on the processor, cause the processor to: receive network traffic comprising a plurality of network packets, the plurality of network packets comprising at least a plurality of first authentication objects known to be generated by an identity provider associated with an authentication domain; store a record of each received authentication object, with attached metadata comprising at least a timestamp of when the authentication object was received, in a time-series database; calculate a cryptographic hash of each first authentication object using a hashing engine; store the cryptographic hashes of the first authentication objects in a database of hashes for the identity provider; receive a request for access to a network resource within the authentication domain accompanied by a second authentication object; calculate a cryptographic hash of the second authentication object using the hashing engine; compare the hash of the second authentication object with the hashes of the first authentication objects stored in the database of hashes to determine whether the hash of the second authentication object already exists in the database; where the hash of the second authentication object does not exist in the database, generate a notification that the identity provider may be compromised; and a hashing engine comprising a second plurality of programming instructions stored in the memory of, and operating on the processor of, the computing device, wherein the second plurality of programmable instructions, when operating on the processor, cause the computing device to: receive authentication objects from the authentication object inspector; calculate a cryptographic hash for each authentication object received by performing at least a plurality of calculations and transformations on each authentication object received; and return the cryptographic hash of each authentication object received to the authentication object inspector, is disclosed.
In another aspect of the invention, a method for detecting forged authentication objects within a domain, comprising the steps of: (a) receiving an authentication object at an authentication object inspector, the authentication object comprising an authentication ticket for a client device communicating with an identity provider; (b) generating a cryptographic hash for the authentication ticket within the authentication object by performing at least a plurality of calculations and transformations on the authentication object using a hashing engine; (c) comparing the calculated cryptographic hash against a stored cryptographic hashes; and (d) identifying an invalid authentication ticket based on a mismatch between the calculated cryptographic hash and the stored cryptographic hash, is disclosed.
BRIEF DESCRIPTION OF THE DRAWING FIGURES
The accompanying drawings illustrate several aspects and, together with the description, serve to explain the principles of the invention according to the aspects. It will be appreciated by one skilled in the art that the particular arrangements illustrated in the drawings are merely exemplary, and are not to be considered as limiting of the scope of the invention or the claims herein in any way.
FIG. 1 is a diagram of an exemplary architecture of an advanced cyber decision platform according to one aspect.
FIG. 2 is a block diagram illustrating an exemplary system architecture for a system for detecting and mitigating forged authentication object attacks according to various embodiments of the invention.
FIG. 3A is a flow diagram of an exemplary function of the business operating system in the detection and mitigation of predetermining factors leading to and steps to mitigate ongoing cyberattacks.
FIG. 3B is a process diagram showing a general flow of the process used to detect rogue devices and analyze them for threats.
FIG. 3C is a process diagram showing a general flow of the process used to detect and prevent privilege escalation attacks on a network.
FIG. 3D is a process diagram showing a general flow of the process used to manage vulnerabilities associated with patches to network software.
FIGS. 4A and 4B are process diagrams showing business operating system functions in use to mitigate cyberattacks.
FIG. 5 is a process flow diagram of a method for segmenting cyberattack information to appropriate corporation parties.
FIG. 6 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph, according to one aspect.
FIG. 7 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph, according to one aspect.
FIG. 8 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph, according to one aspect.
FIG. 9 is a diagram of an exemplary architecture for a user and entity behavioral analysis system, according to one aspect.
FIG. 10 is a flow diagram of an exemplary method for cybersecurity behavioral analytics, according to one aspect.
FIG. 11 is a flow diagram of an exemplary method for measuring the effects of cybersecurity attacks, according to one aspect.
FIG. 12 is a flow diagram of an exemplary method for continuous cybersecurity monitoring and exploration, according to one aspect.
FIG. 13 is a flow diagram of an exemplary method for mapping a cyber-physical system graph (CPG), according to one aspect.
FIG. 14 is a flow diagram of an exemplary method for continuous network resilience scoring, according to one aspect.
FIG. 15 is a flow diagram of an exemplary method for cybersecurity privilege oversight, according to one aspect.
FIG. 16 is a flow diagram of an exemplary method for cybersecurity risk management, according to one aspect.
FIG. 17 is a flow diagram of an exemplary method for mitigating compromised credential threats, according to one aspect.
FIG. 18 is a flow diagram of an exemplary method for dynamic network and rogue device discovery, according to one aspect.
FIG. 19 is a flow diagram of an exemplary method for Kerberos “golden ticket” attack detection, according to one aspect.
FIG. 20 is a flow diagram of an exemplary method for risk-based vulnerability and patch management, according to one aspect.
FIG. 21 is a flow diagram of an exemplary method for establishing groups of users according to one aspect.
FIG. 22 is a flow diagram of an exemplary method for monitoring groups for anomalous behavior, according to one aspect.
FIG. 23 is a flow diagram for an exemplary method for handing a detection of anomalous behavior, according to one aspect.
FIG. 24 is a flow diagram illustrating an exemplary method for processing a new user connection, according to one aspect.
FIG. 25 is a flow diagram illustrating an exemplary method for verifying the authenticity of an authentication object, according to one aspect.
FIG. 26 is a block diagram illustrating an exemplary hardware architecture of a computing device used in various embodiments of the invention.
FIG. 27 is a block diagram illustrating an exemplary logical architecture for a client device, according to various embodiments of the invention.
FIG. 28 is a block diagram illustrating an exemplary architectural arrangement of clients, servers, and external services, according to various embodiments of the invention.
FIG. 29 is another block diagram illustrating an exemplary hardware architecture of a computing device used in various embodiments of the invention.
FIG. 30 is a block diagram illustrating a system for detecting and mitigating attacks using forged authentication objects within a domain, according to a preferred embodiment of the invention.
FIG. 31 is a flow diagram illustrating a method for detecting “golden ticket” attacks within a domain, according to an aspect of the invention.
FIG. 32 is a flow diagram illustrating a method for detecting “silver ticket” attacks within a domain, according to an aspect of the invention.
FIG. 33 is a flow diagram illustrating a method for detecting “skeleton key” attacks within a domain, according to an aspect of the invention.
FIG. 34 is a flow diagram illustrating a method for detecting compromised credentials within a domain, according to an aspect of the invention.
FIG. 35 is a flow diagram illustrating a method for detecting attacks within a domain using a ticket ledger, according to an aspect of the invention.
 DETAILED DESCRIPTION
The inventor has conceived, and reduced to practice, a system and method for detecting and mitigating attacks using forged authentication objects within a domain.
One or more different aspects may be described in the present application. Further, for one or more of the aspects described herein, numerous alternative arrangements may be described; it should be appreciated that these are presented for illustrative purposes only and are not limiting of the aspects contained herein or the claims presented herein in any way. One or more of the arrangements may be widely applicable to numerous aspects, as may be readily apparent from the disclosure. In general, arrangements are described in sufficient detail to enable those skilled in the art to practice one or more of the aspects, and it should be appreciated that other arrangements may be utilized and that structural, logical, software, electrical and other changes may be made without departing from the scope of the particular aspects. Particular features of one or more of the aspects described herein may be described with reference to one or more particular aspects or figures that form a part of the present disclosure, and in which are shown, by way of illustration, specific arrangements of one or more of the aspects. It should be appreciated, however, that such features are not limited to usage in the one or more particular aspects or figures with reference to which they are described. The present disclosure is neither a literal description of all arrangements of one or more of the aspects nor a listing of features of one or more of the aspects that must be present in all arrangements.
Headings of sections provided in this patent application and the title of this patent application are for convenience only, and are not to be taken as limiting the disclosure in any way.
Devices that are in communication with each other need not be in continuous communication with each other, unless expressly specified otherwise. In addition, devices that are in communication with each other may communicate directly or indirectly through one or more communication means or intermediaries, logical or physical.
A description of an aspect with several components in communication with each other does not imply that all such components are required. To the contrary, a variety of optional components may be described to illustrate a wide variety of possible aspects and in order to more fully illustrate one or more aspects. Similarly, although process steps, method steps, algorithms or the like may be described in a sequential order, such processes, methods and algorithms may generally be configured to work in alternate orders, unless specifically stated to the contrary. In other words, any sequence or order of steps that may be described in this patent application does not, in and of itself, indicate a requirement that the steps be performed in that order. The steps of described processes may be performed in any order practical. Further, some steps may be performed simultaneously despite being described or implied as occurring non-simultaneously (e.g., because one step is described after the other step). Moreover, the illustration of a process by its depiction in a drawing does not imply that the illustrated process is exclusive of other variations and modifications thereto, does not imply that the illustrated process or any of its steps are necessary to one or more of the aspects, and does not imply that the illustrated process is preferred. Also, steps are generally described once per aspect, but this does not mean they must occur once, or that they may only occur once each time a process, method, or algorithm is carried out or executed. Some steps may be omitted in some aspects or some occurrences, or some steps may be executed more than once in a given aspect or occurrence.
When a single device or article is described herein, it will be readily apparent that more than one device or article may be used in place of a single device or article. Similarly, where more than one device or article is described herein, it will be readily apparent that a single device or article may be used in place of the more than one device or article.
The functionality or the features of a device may be alternatively embodied by one or more other devices that are not explicitly described as having such functionality or features. Thus, other aspects need not include the device itself.
Techniques and mechanisms described or referenced herein will sometimes be described in singular form for clarity. However, it should be appreciated that particular aspects may include multiple iterations of a technique or multiple instantiations of a mechanism unless noted otherwise. Process descriptions or blocks in figures should be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process. Alternate implementations are included within the scope of various aspects in which, for example, functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those having ordinary skill in the art.
Definitions
As used herein, “graph” is a representation of information and relationships, where each primary unit of information makes up a “node” or “vertex” of the graph and the relationship between two nodes makes up an edge of the graph. Nodes can be further qualified by the connection of one or more descriptors or “properties” to that node. For example, given the node “James R,” name information for a person, qualifying properties might be “183 cm tall”, “DOB Aug. 13, 1965” and “speaks English”. Similar to the use of properties to further describe the information in a node, a relationship between two nodes that forms an edge can be qualified using a “label”. Thus, given a second node “Thomas G,” an edge between “James R” and “Thomas G” that indicates that the two people know each other might be labeled “knows.” When graph theory notation (Graph=(Vertices, Edges)) is applied this situation, the set of nodes are used as one parameter of the ordered pair, V and the set of 2 element edge endpoints are used as the second parameter of the ordered pair, E. When the order of the edge endpoints within the pairs of E is not significant, for example, the edge James R, Thomas G is equivalent to Thomas G, James R, the graph is designated as “undirected.” Under circumstances when a relationship flows from one node to another in one direction, for example James R is “taller” than Thomas G, the order of the endpoints is significant. Graphs with such edges are designated as “directed.” In the distributed computational graph system, transformations within transformation pipeline are represented as directed graph with each transformation comprising a node and the output messages between transformations comprising edges. Distributed computational graph stipulates the potential use of non-linear transformation pipelines which are programmatically linearized. Such linearization can result in exponential growth of resource consumption. The most sensible approach to overcome possibility is to introduce new transformation pipelines just as they are needed, creating only those that are ready to compute. Such method results in transformation graphs which are highly variable in size and node, edge composition as the system processes data streams. Those familiar with the art will realize that transformation graph may assume many shapes and sizes with a vast topography of edge relationships. The examples given were chosen for illustrative purposes only and represent a small number of the simplest of possibilities. These examples should not be taken to define the possible graphs expected as part of operation of the invention
As used herein, “transformation” is a function performed on zero or more streams of input data which results in a single stream of output which may or may not then be used as input for another transformation. Transformations may comprise any combination of machine, human or machine-human interactions Transformations need not change data that enters them, one example of this type of transformation would be a storage transformation which would receive input and then act as a queue for that data for subsequent transformations. As implied above, a specific transformation may generate output data in the absence of input data. A time stamp serves as a example. In the invention, transformations are placed into pipelines such that the output of one transformation may serve as an input for another. These pipelines can consist of two or more transformations with the number of transformations limited only by the resources of the system. Historically, transformation pipelines have been linear with each transformation in the pipeline receiving input from one antecedent and providing output to one subsequent with no branching or iteration. Other pipeline configurations are possible. The invention is designed to permit several of these configurations including, but not limited to: linear, afferent branch, efferent branch and cyclical.
A “database” or “data storage subsystem” (these terms may be considered substantially synonymous), as used herein, is a system adapted for the long-term storage, indexing, and retrieval of data, the retrieval typically being via some sort of querying interface or language. “Database” may be used to refer to relational database management systems known in the art, but should not be considered to be limited to such systems. Many alternative database or data storage system technologies have been, and indeed are being, introduced in the art, including but not limited to distributed non-relational data storage systems such as Hadoop, column-oriented databases, in-memory databases, and the like. While various aspects may preferentially employ one or another of the various data storage subsystems available in the art (or available in the future), the invention should not be construed to be so limited, as any data storage architecture may be used according to the aspects. Similarly, while in some cases one or more particular data storage needs are described as being satisfied by separate components (for example, an expanded private capital markets database and a configuration database), these descriptions refer to functional uses of data storage systems and do not refer to their physical architecture. For instance, any group of data storage systems of databases referred to herein may be included together in a single database management system operating on a single machine, or they may be included in a single database management system operating on a cluster of machines as is known in the art. Similarly, any single database (such as an expanded private capital markets database) may be implemented on a single machine, on a set of machines using clustering technology, on several machines connected by one or more messaging systems known in the art, or in a master/slave arrangement common in the art. These examples should make clear that no particular architectural approaches to database management is preferred according to the invention, and choice of data storage technology is at the discretion of each implementer, without departing from the scope of the invention as claimed.
A “data context”, as used herein, refers to a set of arguments identifying the location of data. This could be a Rabbit queue, a .csv file in cloud-based storage, or any other such location reference except a single event or record. Activities may pass either events or data contexts to each other for processing. The nature of a pipeline allows for direct information passing between activities, and data locations or files do not need to be predetermined at pipeline start.
A “pipeline”, as used herein and interchangeably referred to as a “data pipeline” or a “processing pipeline”, refers to a set of data streaming activities and batch activities. Streaming and batch activities can be connected indiscriminately within a pipeline. Events will flow through the streaming activity actors in a reactive way. At the junction of a streaming activity to batch activity, there will exist a StreamBatchProtocol data object. This object is responsible for determining when and if the batch process is run. One or more of three possibilities can be used for processing triggers: regular timing interval, every N events, or optionally an external trigger. The events are held in a queue or similar until processing. Each batch activity may contain a “source” data context (this may be a streaming context if the upstream activities are streaming), and a “destination” data context (which is passed to the next activity). Streaming activities may have an optional “destination” streaming data context (optional meaning: caching/persistence of events vs. ephemeral), though this should not be part of the initial implementation.
Conceptual Architecture
FIG. 30 is a block diagram illustrating a system for detecting and mitigating attacks using forged authentication objects (AOs) within a domain, according to a preferred embodiment of the invention. According to the embodiment, an advanced cyber decision platform (ACDP) 100 may be operated within a domain 3000, providing analysis and predictive capabilities that are discussed in greater detail below (referring to FIG. 1 ). A plurality of client devices 3010 a-n may connect to a domain controller 3020 for authentication purposes, receiving authentication tickets as appropriate when a client passes authentication (for example, when the client device is known and provides valid credentials for an account). An identity provider such as a Kerberos domain controller (DC) 3020 authenticates devices and accounts before providing an authentication ticket comprising an authentication object to a requesting device, which is then used to access resources 3030 a-n within the domain according to the privileges given to the ticketholder's account. This facilitates single sign-on (SSO) within a domain and minimizes the risks associated with passing credentials between devices in a network, as the user authenticates once and is issued a ticket that may then be checked at each resource to determine an access level, rather than requiring the user to sign on at each resource individually.
More particularly, a client device 3010 a-n first requests a SSO ticket (also referred to as a ticket-granting-ticket, or TGT) from the DC 3020. The DC returns a TGT that is encrypted using a key known only to the DC, which is then stored on the client device. When the client device attempts to access a resource 3030 a-n on the network, it provides the TGT to the domain controller where it is checked for validity (for example, ensuring that the account is valid and the ticket has not expired), and if valid the account is checked for access privileges to the requested resource. If access is permitted, the DC returns a ticket and session key specific to the requesting client and the resource being accessed, allowing the user to access the resource transparently without the need for additional sign-on (as the tickets and keys are exchanged in the background without user involvement, and typically the exchange occurs rapidly with no apparent delay in accessing the resource).
In traditional arrangements, this architecture is vulnerable to a variety of ticket-based attacks involving forged tickets, such as a “golden ticket” attack wherein a TGT is forged and used to obtain full domain administrator privileges (for example, by manufacturing tickets for falsified accounts with full privileges within the domain), or a “silver ticket” attack where a ticket is forged for a specific account by exploiting information that is ordinarily inaccessible in memory on a client device. To detect and mitigate this category of threats, a plurality of listeners 3040 a-n may be installed on each of the client devices, the domain controller, and any connected resources within the domain. Each listener passively collects cryptographic hashes for tickets exchanged between the DC and clients, which may then (by the ACDP) be compared against previous hashes for known-issued tickets. Attacks may then be identified based on hash mismatches, such as (for example) detecting a golden ticket attack by identifying a client passing a TGT when no TGT was previously issued to the client, or detecting a silver ticket attack by identifying when a client is passing a service ticket when no such service ticket was issued to that client. The specific threat identification methods are described below in greater detail, with reference to FIGS. 31-37 .
FIG. 1 is a diagram of an exemplary architecture of an advanced cyber decision platform (ACDP) 100 according to one aspect. Client access to the system 105 for specific data entry, system control and for interaction with system output such as automated predictive decision making and planning and alternate pathway simulations, occurs through the system's distributed, extensible high bandwidth cloud interface 110 which uses a versatile, robust web application driven interface for both input and display of client-facing information via network 107 and operates a data store 112 such as, but not limited to MONGODB™, COUCHDB™, CASSANDRA™ or REDIS™ according to various arrangements. Much of the business data analyzed by the system both from sources within the confines of the client business, and from cloud based sources, also enter the system through the cloud interface 110, data being passed to the connector module 135 which may possess the API routines 135 a needed to accept and convert the external data and then pass the normalized information to other analysis and transformation components of the system, the directed computational graph module 155, high volume web crawler module 115, multidimensional time series database 120 and the graph stack service 145. The directed computational graph module 155 retrieves one or more streams of data from a plurality of sources, which includes, but is in no way not limited to, a plurality of physical sensors, network service providers, web based questionnaires and surveys, monitoring of electronic infrastructure, crowd sourcing campaigns, and human input device information. Within the directed computational graph module 155, data may be split into two identical streams in a specialized pre-programmed data pipeline 155 a, wherein one sub-stream may be sent for batch processing and storage while the other sub-stream may be reformatted for transformation pipeline analysis. The data is then transferred to the general transformer service module 160 for linear data transformation as part of analysis or the decomposable transformer service module 150 for branching or iterative transformations that are part of analysis. The directed computational graph module 155 represents all data as directed graphs where the transformations are nodes and the result messages between transformations edges of the graph. The high volume web crawling module 115 uses multiple server hosted preprogrammed web spiders, which while autonomously configured are deployed within a web scraping framework 115 a of which SCRAPY™ is an example, to identify and retrieve data of interest from web based sources that are not well tagged by conventional web crawling technology. The multiple dimension time series data store module 120 may receive streaming data from a large plurality of sensors that may be of several different types. The multiple dimension time series data store module may also store any time series data encountered by the system such as but not limited to enterprise network usage data, component and system logs, performance data, network service information captures such as, but not limited to news and financial feeds, and sales and service related customer data. The module is designed to accommodate irregular and high volume surges by dynamically allotting network bandwidth and server processing channels to process the incoming data. Inclusion of programming wrappers for languages examples of which are, but not limited to C++, PERL, PYTHON, and ERLANG™ allows sophisticated programming logic to be added to the default function of the multidimensional time series database 120 without intimate knowledge of the core programming, greatly extending breadth of function. Data retrieved by the multidimensional time series database 120 and the high volume web crawling module 115 may be further analyzed and transformed into task optimized results by the directed computational graph 155 and associated general transformer service 150 and decomposable transformer service 160 modules. Alternately, data from the multidimensional time series database and high volume web crawling modules may be sent, often with scripted cuing information determining important vertexes 145 a, to the graph stack service module 145 which, employing standardized protocols for converting streams of information into graph representations of that data, for example, open graph internet technology although the invention is not reliant on any one standard. Through the steps, the graph stack service module 145 represents data in graphical form influenced by any pre-determined scripted modifications 145 a and stores it in a graph-based data store 145 b such as GIRAPH™ or a key value pair type data store REDIS™, or RIAK™, among others, all of which are suitable for storing graph-based information.
Results of the transformative analysis process may then be combined with further client directives, additional business rules and practices relevant to the analysis and situational information external to the already available data in the automated planning service module 130 which also runs powerful information theory 130 a based predictive statistics functions and machine learning algorithms to allow future trends and outcomes to be rapidly forecast based upon the current system derived results and choosing each a plurality of possible business decisions. The using all available data, the automated planning service module 130 may propose business decisions most likely to result is the most favorable business outcome with a usably high level of certainty. Closely related to the automated planning service module in the use of system derived results in conjunction with possible externally supplied additional information in the assistance of end user business decision making, the action outcome simulation module 125 with its discrete event simulator programming module 125 a coupled with the end user facing observation and state estimation service 140 which is highly scriptable 140 b as circumstances require and has a game engine 140 a to more realistically stage possible outcomes of business decisions under consideration, allows business decision makers to investigate the probable outcomes of choosing one pending course of action over another based upon analysis of the current available data.
For example, the Information Assurance department is notified by the system 100 that principal X is using credentials K (Kerberos Principal Key) never used by it before to access service Y. Service Y utilizes these same credentials to access secure data on data store Z. This correctly generates an alert as suspicious lateral movement through the network and will recommend isolation of X and Y and suspension of K based on continuous baseline network traffic monitoring by the multidimensional time series data store 120 programmed to process such data 120 a, rigorous analysis of the network baseline by the directed computational graph 155 with its underlying general transformer service module 160 and decomposable transformer service module 150 in conjunction with the AI and primed machine learning capabilities 130 a of the automated planning service module 130 which had also received and assimilated publicly available from a plurality of sources through the multi-source connection APIs of the connector module 135. Ad hoc simulations of these traffic patterns are run against the baseline by the action outcome simulation module 125 and its discrete event simulator 125 a which is used here to determine probability space for likelihood of legitimacy. The system 100, based on this data and analysis, was able to detect and recommend mitigation of a cyberattack that represented an existential threat to all business operations, presenting, at the time of the attack, information most needed for an actionable plan to human analysts at multiple levels in the mitigation and remediation effort through use of the observation and state estimation service 140 which had also been specifically preprogrammed to handle cybersecurity events 140 b.
A forged authentication object detection and mitigation service 910 may be used to detect and mitigate cyberattacks stemming from the use of authentication objects generated by an attacker. Service 910 is discussed in further detail below in FIG. 2 .
According to one aspect, the advanced cyber decision platform, a specifically programmed usage of the business operating system, continuously monitors a client enterprise's normal network activity for behaviors such as but not limited to normal users on the network, resources accessed by each user, access permissions of each user, machine to machine traffic on the network, sanctioned external access to the core network and administrative access to the network's identity and access management servers in conjunction with real-time analytics informing knowledge of cyberattack methodology. The system then uses this information for two purposes: First, the advanced computational analytics and simulation capabilities of the system are used to provide immediate disclosure of probable digital access points both at the network periphery and within the enterprise's information transfer and trust structure and recommendations are given on network changes that should be made to harden it prior to or during an attack. Second, the advanced cyber decision platform continuously monitors the network in real-time both for types of traffic and through techniques such as deep packet inspection for pre-decided analytically significant deviation in user traffic for indications of known cyberattack vectors such as, but not limited to, ACTIVE DIRECTORY™/Kerberos pass-the-ticket attack, ACTIVE DIRECTORY™/Kerberos pass-the-hash attack and the related ACTIVE DIRECTORY™/Kerberos overpass-the-hash attack, ACTIVE DIRECTORY™/Kerberos Skeleton Key, ACTIVE DIRECTORY™/Kerberos golden and silver ticket attack, privilege escalation attack, compromised user credentials, ransomware disk attacks, and forged authentication object attack (also may be referred to as authentication tickets). When suspicious activity at a level signifying an attack (for example, including but not limited to skeleton key attacks, pass-the-hash attacks, or attacks via compromised user credentials) is determined, the system issues action-focused alert information to all predesignated parties specifically tailored to their roles in attack mitigation or remediation and formatted to provide predictive attack modeling based upon historic, current, and contextual attack progression analysis such that human decision makers can rapidly formulate the most effective courses of action at their levels of responsibility in command of the most actionable information with as little distractive data as possible. The system then issues defensive measures in the most actionable form to end the attack with the least possible damage and exposure. All attack data are persistently stored for later forensic analysis.
FIG. 2 is a block diagram illustrating an exemplary system architecture 900 for a system 910 for detecting and mitigating forged authentication object attacks according to various embodiments of the invention. Architecture 900 may comprise system 910 acting as a non-blocking intermediary between a connecting user 920[a-n], a plurality of federated service providers (SP) 921 a-n, an identity provider (IdP) 922, and an administrative user 923.
System 910 may be configured to verifying incoming connections when the user has an AO, and also keeps track of legitimately generated AO's. System 910 may comprise an AO inspector 911, a hashing engine 912, an event-condition-action (ECA) rules engine 913, and a data store 914.
AO inspector 911 may be configured to use faculties of ACDP 100, for example DCG module 155 and associated transformer modules to analyze and process AO's associated with incoming connections, and observation and state estimation services 140 to monitor connections for incoming AO's. Incoming AO's may be retrieved for further analysis by system 910.
Hashing engine 912 may be configured to calculate a cryptographic hash for AOs generated by identity provider 922 using functions of ACDP 100, such as DCG module 155, generate a cryptographic hash for both incoming AO's (for analysis purposes), and new AO's created by IdP 922. A one-way hash may be used to allow protecting of sensitive information contained in the AO, but preserving uniqueness of each AO. Generated hashes may be stored in data store 914. Hashing engine may also run a hash check function, used for validating incoming AO's.
ECA rules engine 913 may be used by a network administrator to create and manage ECA rules that may trigger actions and queries in the event of detection of a forged AO. Rules may be for example, tracking and logging the actions of the suspicious user, deferring the suspicious connection, and the like. Rules may be nested to create a complex flow of various conditional checks and actions to create a set of “circuit breaker” checks to further ascertain the connection, or try and resolve the matter automatically before notifying a human network administrator.
Data store 914 may be a graph and time-series hybrid database, such as multidimensional time-series data store 120 or data store 112, that stores hashes, ECA rules, log data, and the like, and may be quickly and efficiently queried and processed using ACDP 100.
Federated service providers 921 a-n may comprise a group of trusted service partners that may share a common IdP 922 in which user 920[a-n] may wish to access. Federated service providers 921 a-n may be, for instance, services employing MICROSOFT'S ACTIVE DIRECTORY FEDERATED SERVICES (AS DS), AZURE AD, OKTA, many web browser single-sign-on (SSO) implementations, cloud service provides (such as, AMAZON AWS, AZURE, and GOOGLE), and the like.
FIG. 3A is a flow diagram of an exemplary function of the business operating system in the detection and mitigation of predetermining factors leading to and steps to mitigate ongoing cyberattacks 200. The system continuously retrieves network traffic data 201 which may be stored and preprocessed by the multidimensional time series data store 120 and its programming wrappers 120 a. All captured data are then analyzed to predict the normal usage patterns of network nodes such as internal users, network connected systems and equipment and sanctioned users external to the enterprise boundaries for example off-site employees, contractors and vendors, just to name a few likely participants. Of course, normal other network traffic may also be known to those skilled in the field, the list given is not meant to be exclusive and other possibilities would not fall outside the design of the invention. Analysis of network traffic may include graphical analysis of parameters such as network item to network usage using specifically developed programming in the graphstack service 145, 145 a, analysis of usage by each network item may be accomplished by specifically pre-developed algorithms associated with the directed computational graph module 155, general transformer service module 160 and decomposable service module 150, depending on the complexity of the individual usage profile 201. These usage pattern analyses, in conjunction with additional data concerning an enterprise's network topology; gateway firewall programming; internal firewall configuration; directory services protocols and configuration; and permissions profiles for both users and for access to sensitive information, just to list a few non-exclusive examples may then be analyzed further within the automated planning service module 130, where machine learning techniques which include but are not limited to information theory statistics 130 a may be employed and the action outcome simulation module 125, specialized for predictive simulation of outcome based on current data 125 a may be applied to formulate a current, up-to-date and continuously evolving baseline network usage profile 202. This same data would be combined with up-to-date known cyberattack methodology reports, possibly retrieved from several divergent and exogenous sources through the use of the multi-application programming interface aware connector module 135 to present preventative recommendations to the enterprise decision makers for network infrastructure changes, physical and configuration-based to cost effectively reduce the probability of a cyberattack and to significantly and most cost effectively mitigate data exposure and loss in the event of attack 203, 204.
While some of these options may have been partially available as piecemeal solutions in the past, we believe the ability to intelligently integrate the large volume of data from a plurality of sources on an ongoing basis followed by predictive simulation and analysis of outcome based upon that current data such that actionable, business practice efficient recommendations can be presented is both novel and necessary in this field.
Once a comprehensive baseline profile of network usage using all available network traffic data has been formulated, the specifically tasked business operating system continuously polls the incoming traffic data for activities anomalous to that baseline as determined by pre-designated boundaries 205. Examples of anomalous activities may include a user attempting to gain access several workstations or servers in rapid succession, or a user attempting to gain access to a domain server of server with sensitive information using random userIDs or another user's userID and password, or attempts by any user to brute force crack a privileged user's password, or replay of recently issued ACTIVE DIRECTORY™/Kerberos ticket granting tickets, or using a forged Kerberos ticket, or the presence on any known, ongoing exploit on the network or the introduction of known malware to the network, just to name a very small sample of the cyberattack profiles known to those skilled in the field. The invention, being predictive as well as aware of known exploits is designed to analyze any anomalous network behavior, formulate probable outcomes of the behavior, and to then issue any needed alerts regardless of whether the attack follows a published exploit specification or exhibits novel characteristics deviant to normal network practice. Once a probable cyberattack is detected, the system then is designed to get needed information to responding parties 206 tailored, where possible, to each role in mitigating the attack and damage arising from it 207. This may include the exact subset of information included in alerts and updates and the format in which the information is presented which may be through the enterprise's existing security information and event management system. Network administrators, then, might receive information such as but not limited to where on the network the attack is believed to have originated, what systems are believed currently affected, predictive information on where the attack may progress, what enterprise information is at risk and actionable recommendations on repelling the intrusion and mitigating the damage, whereas a chief information security officer may receive alert including but not limited to a timeline of the cyberattack, the services and information believed compromised, what action, if any has been taken to mitigate the attack, a prediction of how the attack may unfold and the recommendations given to control and repel the attack 207, although all parties may access any network and cyberattack information for which they have granted access at any time, unless compromise is suspected. Other specifically tailored updates may be issued by the system 206, 207.
FIG. 3B is a process diagram showing a general flow of the process used to detect rogue devices and analyze them for threats 220. Whenever a device is connected to the network 221, the connection is immediately sent to the rogue device detector 222 for analysis. As disclosed below at 300, the advanced cyber decision platform uses machine learning algorithms to analyze system-wide data to detect threats. The connected device is analyzed 223 to assess its device type, settings, and capabilities, the sensitivity of the data stored on the server to which the device wishes to connect, network activity, server logs, remote queries, and a multitude of other data to determine the level of threat associated with the device. If the threat reaches a certain level 224, the device is automatically prevented from accessing the network 225, and the system administrator is notified of the potential threat, along with contextually-based, tactical recommendations for optimal response based on potential impact 226. Otherwise, the device is allowed to connect to the network 227.
FIG. 3C is a process diagram showing a general flow of the process used to detect and prevent privilege escalation attacks on a network (for example, “Golden Ticket” attacks) 240. When access to a server within the network is requested using a digital signature or AO 241, the connection is immediately sent to the privilege escalation attack detector 242 for analysis. As disclosed below at 300, the advanced cyber decision platform uses machine learning algorithms to analyze system-wide data to detect threats. The access request is analyzed 243 to assess the validity of the access request using the digital signature validation, plus other system-wide information such as the sensitivity of the server being accessed, the newness of the digital signature or AO, the digital signature's or AO's prior usage, and other measures of the digital signature's or AO's validity. If the assessment determines that the access request represents a significant threat 244, even despite the Kerberos validation of the digital signature or validation of a AO, the access request is automatically denied 245, and the system administrator is notified of the potential threat, along with contextually-based, tactical recommendations for optimal response based on potential impact 246. Otherwise, the access request is granted 247.
FIG. 3D is a process diagram showing a general flow of the process used to manage vulnerabilities associated with patches to network software 260. As part of a continuously-operating risk-based vulnerability and patch management monitor 261, data is gathered from both sources external to the network 262 and internal to the network 263. As disclosed below at 300, the advanced cyber decision platform uses machine learning algorithms to analyze system-wide data to detect threats. The data is analyzed 264 to determine whether network vulnerabilities exist for which a patch has not yet been created and/or applied. If the assessment determines that such a vulnerability exists 265, whether or not all software has been patched according to manufacturer recommendations, the system administrator is notified of the potential vulnerability, along with contextually-based, tactical recommendations for optimal response based on potential impact 266. Otherwise, network activity is allowed to continue normally 267.
FIGS. 4A and 4B are process diagrams showing a general flow 300 of business operating system functions in use to mitigate cyberattacks. Input network data which may include network flow patterns 321, the origin and destination of each piece of measurable network traffic 322, system logs from servers and workstations on the network 323, endpoint data 323 a, any security event log data from servers or available security information and event (SIEM) systems 324, external threat intelligence feeds 324 a, identity or assessment context 325, external network health or cybersecurity feeds 326, Kerberos domain controller or ACTIVE DIRECTORY™ server logs or instrumentation 327 and business unit performance related data 328, among many other possible data types for which the invention was designed to analyze and integrate, may pass into 315 the business operating system 310 for analysis as part of its cyber security function. These multiple types of data from a plurality of sources may be transformed for analysis 311, 312 using at least one of the specialized cybersecurity, risk assessment or common functions of the business operating system in the role of cybersecurity system, such as, but not limited to network and system user privilege oversight 331, network and system user behavior analytics 332, attacker and defender action timeline 333, SIEM integration and analysis 334, dynamic benchmarking 335, and incident identification and resolution performance analytics 336 among other possible cybersecurity functions; value at risk (VAR) modeling and simulation 341, anticipatory vs. reactive cost estimations of different types of data breaches to establish priorities 342, work factor analysis 343 and cyber event discovery rate 344 as part of the system's risk analytics capabilities; and the ability to format and deliver customized reports and dashboards 351, perform generalized, ad hoc data analytics on demand 352, continuously monitor, process and explore incoming data for subtle changes or diffuse informational threads 353 and generate cyber-physical systems graphing 354 as part of the business operating system's common capabilities. Output 317 can be used to configure network gateway security appliances 361, to assist in preventing network intrusion through predictive change to infrastructure recommendations 362, to alert an enterprise of ongoing cyberattack early in the attack cycle, possibly thwarting it but at least mitigating the damage 368, to record compliance to standardized guidelines or SLA requirements 363, to continuously probe existing network infrastructure and issue alerts to any changes which may make a breach more likely 364, suggest solutions to any domain controller ticketing weaknesses detected 365, detect presence of malware 366, and perform one time or continuous vulnerability scanning depending on client directives 367. These examples are, of course, only a subset of the possible uses of the system, they are exemplary in nature and do not reflect any boundaries in the capabilities of the invention.
FIG. 5 is a process flow diagram of a method for segmenting cyberattack information to appropriate corporation parties 400. As previously disclosed 200, 351, one of the strengths of the advanced cyber-decision platform is the ability to finely customize reports and dashboards to specific audiences, concurrently is appropriate. This customization is possible due to the devotion of a portion of the business operating system's programming specifically to outcome presentation by modules which include the observation and state estimation service 140 with its game engine 140 a and script interpreter 140 b. In the setting of cybersecurity, issuance of specialized alerts, updates and reports may significantly assist in getting the correct mitigating actions done in the most timely fashion while keeping all participants informed at predesignated, appropriate granularity. Upon the detection of a cyberattack by the system 401 all available information about the ongoing attack and existing cybersecurity knowledge are analyzed, including through predictive simulation in near real time 402 to develop both the most accurate appraisal of current events and actionable recommendations concerning where the attack may progress and how it may be mitigated. The information generated in totality is often more than any one group needs to perform their mitigation tasks. At this point, during a cyberattack, providing a single expansive and all inclusive alert, dashboard image, or report may make identification and action upon the crucial information by each participant more difficult, therefore the cybersecurity focused arrangement may create multiple targeted information streams each concurrently designed to produce most rapid and efficacious action throughout the enterprise during the attack and issue follow-up reports with and recommendations or information that may lead to long term changes afterward 403. Examples of groups that may receive specialized information streams include but may not be limited to front line responders during the attack 404, incident forensics support both during and after the attack 405, chief information security officer 406 and chief risk officer 407 the information sent to the latter two focused to appraise overall damage and to implement both mitigating strategy and preventive changes after the attack. Front line responders may use the cyber-decision platform's analyzed, transformed and correlated information specifically sent to them 404 a to probe the extent of the attack, isolate such things as: the predictive attacker's entry point onto the enterprise's network, the systems involved or the predictive ultimate targets of the attack and may use the simulation capabilities of the system to investigate alternate methods of successfully ending the attack and repelling the attackers in the most efficient manner, although many other queries known to those skilled in the art are also answerable by the invention. Simulations run may also include the predictive effects of any attack mitigating actions on normal and critical operation of the enterprise's IT systems and corporate users. Similarly, a chief information security officer may use the cyber-decision platform to predictively analyze 406 a what corporate information has already been compromised, predictively simulate the ultimate information targets of the attack that may or may not have been compromised and the total impact of the attack what can be done now and in the near future to safeguard that information. Further, during retrospective forensic inspection of the attack, the forensic responder may use the cyber-decision platform 405 a to clearly and completely map the extent of network infrastructure through predictive simulation and large volume data analysis. The forensic analyst may also use the platform's capabilities to perform a time series and infrastructural spatial analysis of the attack's progression with methods used to infiltrate the enterprise's subnets and servers. Again, the chief risk officer would perform analyses of what information 407 a was stolen and predictive simulations on what the theft means to the enterprise as time progresses. Additionally, the system's predictive capabilities may be employed to assist in creation of a plan for changes of the IT infrastructural that should be made that are optimal for remediation of cybersecurity risk under possibly limited enterprise budgetary constraints in place at the company so as to maximize financial outcome.
FIG. 6 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph 500, according to one aspect. According to the aspect, a DCG 500 may comprise a pipeline orchestrator 501 that may be used to perform a variety of data transformation functions on data within a processing pipeline, and may be used with a messaging system 510 that enables communication with any number of various services and protocols, relaying messages and translating them as needed into protocol-specific API system calls for interoperability with external systems (rather than requiring a particular protocol or service to be integrated into a DCG 500).
Pipeline orchestrator 501 may spawn a plurality of child pipeline clusters 502 a-b, which may be used as dedicated workers for streamlining parallel processing. In some arrangements, an entire data processing pipeline may be passed to a child cluster 502 a for handling, rather than individual processing tasks, enabling each child cluster 502 a-b to handle an entire data pipeline in a dedicated fashion to maintain isolated processing of different pipelines using different cluster nodes 502 a-b. Pipeline orchestrator 501 may provide a software API for starting, stopping, submitting, or saving pipelines. When a pipeline is started, pipeline orchestrator 501 may send the pipeline information to an available worker node 502 a-b, for example using AKKA™ clustering. For each pipeline initialized by pipeline orchestrator 501, a reporting object with status information may be maintained. Streaming activities may report the last time an event was processed, and the number of events processed. Batch activities may report status messages as they occur. Pipeline orchestrator 501 may perform batch caching using, for example, an IGFS™ caching filesystem. This allows activities 512 a-d within a pipeline 502 a-b to pass data contexts to one another, with any necessary parameter configurations.
A pipeline manager 511 a-b may be spawned for every new running pipeline, and may be used to send activity, status, lifecycle, and event count information to the pipeline orchestrator 501. Within a particular pipeline, a plurality of activity actors 512 a-d may be created by a pipeline manager 511 a-b to handle individual tasks, and provide output to data services 522 a-d. Data models used in a given pipeline may be determined by the specific pipeline and activities, as directed by a pipeline manager 511 a-b. Each pipeline manager 511 a-b controls and directs the operation of any activity actors 512 a-d spawned by it. A pipeline process may need to coordinate streaming data between tasks. For this, a pipeline manager 511 a-b may spawn service connectors to dynamically create TCP connections between activity instances 512 a-d. Data contexts may be maintained for each individual activity 512 a-d, and may be cached for provision to other activities 512 a-d as needed. A data context defines how an activity accesses information, and an activity 512 a-d may process data or simply forward it to a next step. Forwarding data between pipeline steps may route data through a streaming context or batch context.
A client service cluster 530 may operate a plurality of service actors 521 a-d to serve the requests of activity actors 512 a-d, ideally maintaining enough service actors 521 a-d to support each activity per the service type. These may also be arranged within service clusters 520 a-d, in a manner similar to the logical organization of activity actors 512 a-d within clusters 502 a-b in a data pipeline. A logging service 530 may be used to log and sample DCG requests and messages during operation while notification service 540 may be used to receive alerts and other notifications during operation (for example to alert on errors, which may then be diagnosed by reviewing records from logging service 530), and by being connected externally to messaging system 510, logging and notification services can be added, removed, or modified during operation without impacting DCG 500. A plurality of DCG protocols 550 a-b may be used to provide structured messaging between a DCG 500 and messaging system 510, or to enable messaging system 510 to distribute DCG messages across service clusters 520 a-d as shown. A service protocol 560 may be used to define service interactions so that a DCG 500 may be modified without impacting service implementations. In this manner it can be appreciated that the overall structure of a system using an actor-driven DCG 500 operates in a modular fashion, enabling modification and substitution of various components without impacting other operations or requiring additional reconfiguration.
FIG. 7 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph 500, according to one aspect. According to the aspect, a variant messaging arrangement may utilize messaging system 510 as a messaging broker using a streaming protocol 610, transmitting and receiving messages immediately using messaging system 510 as a message broker to bridge communication between service actors 521 a-b as needed. Alternately, individual services 522 a-b may communicate directly in a batch context 620, using a data context service 630 as a broker to batch-process and relay messages between services 522 a-b.
FIG. 8 is a diagram of an exemplary architecture for a system for rapid predictive analysis of very large data sets using an actor-driven distributed computational graph 500, according to one aspect. According to the aspect, a variant messaging arrangement may utilize a service connector 710 as a central message broker between a plurality of service actors 521 a-b, bridging messages in a streaming context 610 while a data context service 630 continues to provide direct peer-to-peer messaging between individual services 522 a-b in a batch context 620.
It should be appreciated that various combinations and arrangements of the system variants described above (referring to FIGS. 1A-8 ) may be possible, for example using one particular messaging arrangement for one data pipeline directed by a pipeline manager 511 a-b, while another pipeline may utilize a different messaging arrangement (or may not utilize messaging at all). In this manner, a single DCG 500 and pipeline orchestrator 501 may operate individual pipelines in the manner that is most suited to their particular needs, with dynamic arrangements being made possible through design modularity as described above in FIG. 6 .
Another way to detect cyberthreats may be through the continuous monitoring and analysis of user and device behavioral patterns. This method may be particularly useful when there is little info available on an exploit, for example, a newly developed malware. FIG. 9 is a diagram of an exemplary architecture 800 for a user and entity behavioral analysis system, according to one aspect. Architecture 800 may comprise a plurality of users 805 a-n, which may be individuals or connected devices, connecting to a user and entity behavioral analysis system 810. System 810 may comprise a grouping engine 813, a behavioral analysis engine 819, a monitoring service 822, and a multidimensional time series data store 120 for storing gathered and processed data. Grouping engine 813 may be configured to gather and identify user interactions and related metrics, which may include volume of interaction, frequency of interaction, and the like. Grouping engine 813 may use graph stack service 145 and DCG module 155 to convert and analyze the data in graph format. The interaction data may then be used to split users 805 a-n into a plurality of groups 816 a-n. Groupings may be based on department, project teams, interaction frequency, and other metrics which may be user-defined. Groupings may not be permanent, and may be adjusted and changed in real-time as group dynamics change. This may be automated by system 810, or an administrative user may manually change the groupings.
Behavioral analysis engine 819 may batch process and aggregate overall usage logs, access logs, KERBEROS session data, or data collected through the use of other network monitoring tools commonly used in the art such as BRO or SURICATA. The aggregated data may then be used to generate a behavioral baseline for each group established by grouping engine 813. Behavioral analysis engine 819 may use graph stack service 145 and DCG module 155 to convert and analyze the data in graph format using various machine learning models, and may also process the data using parallel computing to quickly process large amounts of data. Models may be easily added to the system. Behavioral analysis engine 819 may also be configured to process internal communications, such as email, using natural language processing. This may provide additional insight into current group dynamics so that a more accurate baseline may be established, or may provide an insight into health and mood of users.
Monitoring service 822 may actively monitor groups for anomalous behavior, as based the established baseline. For example, monitoring service 822 may use the data pipelines of ACDP system 100 or multidimensional time series data store 120 to conduct real-time monitoring of various network resource sensors. Aspects that may be monitored may include, but is not limited to, anomalous web browsing, for example, the number of distinct domains visited exceeding a predefined threshold; anomalous data exfiltration, for example, the amount of outgoing data exceeding a predefined threshold; unusual domain access, for example, a subgroup consisting a few members within an established group demonstrating unusual browsing behavior by accessing an unusual domain a predetermined number of times within a certain timeframe; anomalous login times, for example, a user logging into a workstation during off-hours; unlikely login locations, for example, a user logging in using an account from two distinct locations that may be physically impossible within a certain timeframe; anomalous service access, for example, unusual application access or usage pattern; and new machines, for example, a user logging into a machine or server not typically accessed.
Detailed Description of Exemplary Aspects
FIG. 31 is a flow diagram illustrating a method for detecting “golden ticket” attacks within a domain, according to an aspect of the invention. In a golden ticket attack, a malicious actor forges a TGT using compromised information (such as information dumped from memory on a client device connected to the domain, regardless of the authentication tickets actually issued to that client device), and then uses this falsified TGT to grant themselves domain administrator access. According to the method, a DC 3020 configured with a passive listener (as described above, with reference to FIG. 30 ) receives a request for a service ticket from a client (also known as a “principal” according to the Kerberos authentication protocol) 3101, the request including a TGT. The listener calculates a hash for the included TGT 3102, and sends the hash to ACDP 100. ACDP 100 then checks 3103 for a stored hash for the requesting client, which would indicate that the TGT is valid and was previously issued to this client for use in requesting service tickets for resource access. If no existing hash is found, or an existing hash does not match the one provided, this indicates that the TGT has been forged or altered and there is a high risk that the service ticket request is part of a golden ticket attack being used to obtain illicit access to domain resources 3104. If an existing hash is found that does match the one provided, this indicates that the TGT is valid for the requesting client, and the service ticket requests may be authorized and authentication proceeds as normal 3105.
FIG. 32 is a flow diagram illustrating a method for detecting “silver ticket” attacks within a domain, according to an aspect of the invention. A silver ticket attack involves a malicious actor forging a service ticket, rather than the TGT involved in a golden ticket attack. According to the method, a resource configured with a passive listener (as described above, with reference to FIG. 30 ) receives a service ticket from a client (also known as a “principal” according to the Kerberos authentication protocol) 3201. The listener calculates a hash for the service ticket 3202, and sends the hash to ACDP 100. ACDP 100 then checks 3203 for a stored hash for the client, which would indicate that the service ticket is valid and was previously issued to this client for use in accessing the respective resource. If no existing hash is found, or an existing hash does not match the one provided, this indicates that the service ticket has been forged or altered and there is a high risk that the service ticket is part of a silver ticket attack being used to obtain illicit access to domain resources 3204. If an existing hash is found that does match the one provided, this indicates that the service ticket is valid for the client and resource, and the client may be authorized to access the resource as normal 3205.
Golden and silver ticket attacks may be detected using this hash-based approach, as forged tickets generated by malicious software contain formatting anomalies such as empty fields that would be populated if the TGT was properly-issued and valid. These anomalies result in a different hash being created than the one created for a valid TGT issued by the DC, thereby making the forged ticket obvious upon inspection. Once such an attack has been detected, care must be taken not to alert the malicious actor that they have been discovered, as they may abandon the attack prematurely and prevent the collection of important information such as from where the attack originated or what access paths were used, what was accessed using the forged ticket, or what the intent of the attack may have been. Therefore, when a golden or silver ticket attack is discovered, a domain administrator may identify compromised accounts involved in the attack and choose to disable all but a selection of low-risk accounts; this may prevent the attacker from accessing sensitive information or causing damage to internal resources, while still allowing them some degree of activity to conceal their discovery while the administrator continues to analyze the attack.
FIG. 33 is a flow diagram illustrating a method for detecting “skeleton key” attacks within a domain, according to an aspect of the invention. In a skeleton key attack, a malicious actor modifies stored keys on a DC to grant themselves the ability to change the master password, enabling additional attacks as they can take control of the DC and perform such actions as granting tickets or creating new accounts with full privileges within the domain. According to the method, a listener operating on a client device may inspect the client's advertised encryption types within a ticket request to determine if AES is supported 3301. A listener operating on a DC may similarly inspect the DC's advertised encryption types for AES support 3302, as well as inspecting the encryption that appears in a DC response 3303 to the ticket request to determine whether AES encryption is used 3304. If AES is used in the response, operation continues as normal 3305. However, if AES is supported by both the client and DC yet does not appear in the response, this indicates that the keys stored by the DC have been tampered with 3306, potentially as part of a skeleton key attack wherein an attacker manipulates stored keys to implant a modified key that allows use of a new master password to grant them access.
FIG. 34 is a flow diagram illustrating a method for detecting compromised credentials within a domain, according to an aspect of the invention. In an attack using compromised credentials, a malicious actor takes control of a domain account and uses that account to access resources and perform actions while masquerading as the accountholder. According to the method, a listener operating on a DC may collect metadata on received requests 3401, such as (for example, including but not limited to) username, timestamp, location, device ID, or success/failure of each request. This information may then be stored in a multidimensional time-series database (MDTSDB) 3402 with associated timestamp information. This stored time-series data may then be analyzed using a directed computational graph (DCG) 3403 to identify regular patterns of user behavior 3404 and establish a baseline of “safe” behavior 3405. When DCG analysis indicates activity outside the normal parameters, this may indicate a compromised user account 3406, such as when a malicious actor connects using stolen credentials and behaves in a manner inconsistent with the actual accountholder.
FIG. 35 is a flow diagram illustrating a method for detecting attacks within a domain using a ticket ledger, according to an aspect of the invention. These attacks may include exploits known as “DCSync”, “DCShadow”, and “Kerberoasting”. In a DCSync attack, a malicious actor that has already obtained administrator privileges (such as through a golden ticket attack) mimics a valid domain admin account in order to request additional information from the DC, such as user passwords and account information. In a DCShadow attack, a malicious actor that has already obtained administrator privileges (such as through a golden ticket attack) mimics a domain controller to inject new data into the domain records while bypassing the normal security protocols that would prevent a nonprivileged account from modifying records. Both of these attack types require administrator access and can be identified using a ticket ledger collected over time using listeners within a domain. In a Kerberoasting attack, a malicious actor does not require a compromised account or any obtained privileges (unlike with DCSync and DCShadow). A malicious actor also does not need to send any packets to a DC or client in order to effect the compromise; information may be collected in memory by simply connecting a device to a domain, and then it may be dumped from memory and compromised offline. The actor may then reconnect and use obtained information such as account credentials, to obtain access within the domain and potentially continue with additional attacks (for example, escalating to a silver or golden ticket attack to obtain administrator access).
According to the method, a listener operating on a DC may collect traffic information within the domain 3501, allowing an ACDP to compile the traffic data and build a ledger of issued tickets within the domain 3502. This ledger may be analyzed by the ACDP to identify trust relationships between domain controllers and clients 3503. Any unusual activity, such as a DC admin account request from an account that is ordinarily unused or has no involvement with the clients for which is requesting data, may be identified as falling outside the known relationships 3504. This unusual activity may then indicate that an administrator account is acting unusually (such as requesting information for users with which it has no established trust relationship), or new information may suddenly appear that may indicate that records have been modified as part of a DCShadow attack. Spikes in activity levels may be used as an indicator of a Kerberoasting attack, indicating an account requesting or being issued more tickets than normal, which may serve as an indicator of a compromised account that may have had its credentials cracked in a Kerberoasting exploit.
FIG. 10 is a flow diagram of an exemplary method 1000 for cybersecurity behavioral analytics, according to one aspect. According to the aspect, behavior analytics may utilize passive information feeds from a plurality of existing endpoints (for example, including but not limited to user activity on a network, network performance, or device behavior) to generate security solutions. In an initial step 1001, a web crawler 115 may passively collect activity information, which may then be processed 1002 using a DCG 155 to analyze behavior patterns. Based on this initial analysis, anomalous behavior may be recognized 1003 (for example, based on a threshold of variance from an established pattern or trend) such as high-risk users or malicious software operators such as bots. These anomalous behaviors may then be used 1004 to analyze potential angles of attack and then produce 1005 security suggestions based on this second-level analysis and predictions generated by an action outcome simulation module 125 to determine the likely effects of the change. The suggested behaviors may then be automatically implemented 1006 as needed. Passive monitoring 1001 then continues, collecting information after new security solutions are implemented 1006, enabling machine learning to improve operation over time as the relationship between security changes and observed behaviors and threats are observed and analyzed.
This method 1000 for behavioral analytics enables proactive and high-speed reactive defense capabilities against a variety of cyberattack threats, including anomalous human behaviors as well as nonhuman “bad actors” such as automated software bots that may probe for, and then exploit, existing vulnerabilities. Using automated behavioral learning in this manner provides a much more responsive solution than manual intervention, enabling rapid response to threats to mitigate any potential impact. Utilizing machine learning behavior further enhances this approach, providing additional proactive behavior that is not possible in simple automated approaches that merely react to threats as they occur.
FIG. 11 is a flow diagram of an exemplary method 1100 for measuring the effects of cybersecurity attacks, according to one aspect. According to the aspect, impact assessment of an attack may be measured using a DCG 155 to analyze a user account and identify its access capabilities 1101 (for example, what files, directories, devices or domains an account may have access to). This may then be used to generate 1102 an impact assessment score for the account, representing the potential risk should that account be compromised. In the event of an incident, the impact assessment score for any compromised accounts may be used to produce a “blast radius” calculation 1103, identifying exactly what resources are at risk as a result of the intrusion and where security personnel should focus their attention. To provide proactive security recommendations through a simulation module 125, simulated intrusions may be run 1104 to identify potential blast radius calculations for a variety of attacks and to determine 1105 high risk accounts or resources so that security may be improved in those key areas rather than focusing on reactive solutions.
FIG. 12 is a flow diagram of an exemplary method 1200 for continuous cybersecurity monitoring and exploration, according to one aspect. According to the aspect, a state observation service 140 may receive data from a variety of connected systems 1201 such as (for example, including but not limited to) servers, domains, databases, or user directories. This information may be received continuously, passively collecting events and monitoring activity over time while feeding 1202 collected information into a graphing service 145 for use in producing time-series graphs 1203 of states and changes over time. This collated time-series data may then be used to produce a visualization 1204 of changes over time, quantifying collected data into a meaningful and understandable format. As new events are recorded, such as changing user roles or permissions, modifying servers or data structures, or other changes within a security infrastructure, these events are automatically incorporated into the time-series data and visualizations are updated accordingly, providing live monitoring of a wealth of information in a way that highlights meaningful data without losing detail due to the quantity of data points under examination.
FIG. 13 is a flow diagram of an exemplary method 1300 for mapping a cyber-physical system graph (CPG), according to one aspect. According to the aspect, a cyber-physical system graph may comprise a visualization of hierarchies and relationships between devices and resources in a security infrastructure, contextualizing security information with physical device relationships that are easily understandable for security personnel and users. In an initial step 1301, behavior analytics information (as described previously, referring to FIG. 10 ) may be received at a graphing service 145 for inclusion in a CPG. In a next step 1302, impact assessment scores (as described previously, referring to FIG. 11 ) may be received and incorporated in the CPG information, adding risk assessment context to the behavior information. In a next step 1303, time-series information (as described previously, referring to FIG. 12 ) may be received and incorporated, updating CPG information as changes occur and events are logged. This information may then be used to produce 1304 a graph visualization of users, servers, devices, and other resources correlating physical relationships (such as a user's personal computer or smartphone, or physical connections between servers) with logical relationships (such as access privileges or database connections), to produce a meaningful and contextualized visualization of a security infrastructure that reflects the current state of the internal relationships present in the infrastructure.
FIG. 14 is a flow diagram of an exemplary method 1400 for continuous network resilience scoring, according to one aspect. According to the aspect, a baseline score can be used to measure an overall level of risk for a network infrastructure, and may be compiled by first collecting 1401 information on publicly-disclosed vulnerabilities, such as (for example) using the Internet or common vulnerabilities and exploits (CVE) process. This information may then 1402 be incorporated into a CPG as described previously in FIG. 13 , and the combined data of the CPG and the known vulnerabilities may then be analyzed 1403 to identify the relationships between known vulnerabilities and risks exposed by components of the infrastructure. This produces a combined CPG 1404 that incorporates both the internal risk level of network resources, user accounts, and devices as well as the actual risk level based on the analysis of known vulnerabilities and security risks.
FIG. 15 is a flow diagram of an exemplary method 1500 for cybersecurity privilege oversight, according to one aspect. According to the aspect, time-series data (as described above, referring to FIG. 12 ) may be collected 1501 for user accounts, credentials, directories, and other user-based privilege and access information. This data may then 1502 be analyzed to identify changes over time that may affect security, such as modifying user access privileges or adding new users. The results of analysis may be checked 1503 against a CPG (as described previously in FIG. 13 ), to compare and correlate user directory changes with the actual infrastructure state. This comparison may be used to perform accurate and context-enhanced user directory audits 1504 that identify not only current user credentials and other user-specific information, but changes to this information over time and how the user information relates to the actual infrastructure (for example, credentials that grant access to devices and may therefore implicitly grant additional access due to device relationships that were not immediately apparent from the user directory alone).
FIG. 16 is a flow diagram of an exemplary method 1600 for cybersecurity risk management, according to one aspect. According to the aspect, multiple methods described previously may be combined to provide live assessment of attacks as they occur, by first receiving 1601 time-series data for an infrastructure (as described previously, in FIG. 12 ) to provide live monitoring of network events. This data is then enhanced 1602 with a CPG (as described above in FIG. 13 ) to correlate events with actual infrastructure elements, such as servers or accounts. When an event (for example, an attempted attack against a vulnerable system or resource) occurs 1603, the event is logged in the time-series data 1604, and compared against the CPG 1605 to determine the impact. This is enhanced with the inclusion of impact assessment information 1606 for any affected resources, and the attack is then checked against a baseline score 1607 to determine the full extent of the impact of the attack and any necessary modifications to the infrastructure or policies.
FIG. 17 is a flow diagram of an exemplary method 1700 for mitigating compromised credential threats, according to one aspect. According to the aspect, impact assessment scores (as described previously, referring to FIG. 11 ) may be collected 1701 for user accounts in a directory, so that the potential impact of any given credential attack is known in advance of an actual attack event. This information may be combined with a CPG 1702 as described previously in FIG. 13 , to contextualize impact assessment scores within the infrastructure (for example, so that it may be predicted what systems or resources might be at risk for any given credential attack). A simulated attack may then be performed 1703 to use machine learning to improve security without waiting for actual attacks to trigger a reactive response. A blast radius assessment (as described above in FIG. 11 ) may be used in response 1704 to determine the effects of the simulated attack and identify points of weakness, and produce a recommendation report 1705 for improving and hardening the infrastructure against future attacks.
FIG. 18 is a flow diagram of an exemplary method 1800 for dynamic network and rogue device discovery, according to one aspect. According to the aspect, an advanced cyber decision platform may continuously monitor a network in real-time 1801, detecting any changes as they occur. When a new connection is detected 1802, a CPG may be updated 1803 with the new connection information, which may then be compared against the network's resiliency score 1804 to examine for potential risk. The blast radius metric for any other devices involved in the connection may also be checked 1805, to examine the context of the connection for risk potential (for example, an unknown connection to an internal data server with sensitive information may be considered a much higher risk than an unknown connection to an externally-facing web server). If the connection is a risk, an alert may be sent to an administrator 1806 with the contextual information for the connection to provide a concise notification of relevant details for quick handling.
FIG. 19 is a flow diagram of an exemplary method 1900 for Kerberos “golden ticket” attack detection, according to one aspect. To detect these forms of attack, behavioral analytics may be employed to detect erroneously-issued authentication tickets or forged AO's, whether from incorrect configuration or from an attack. According to the aspect, an advanced cyber decision platform may continuously monitor a network 1901, informing a CPG in real-time of all traffic associated with people, places, devices, or services 1902. Machine learning algorithms detect behavioral anomalies as they occur in real-time 1903, notifying administrators with an assessment of the anomalous event 1904 as well as a blast radius score for the particular event and a network resiliency score to advise of the overall health of the network. By automatically detecting unusual behavior and informing an administrator of the anomaly along with contextual information for the event and network, a compromised ticket is immediately detected when a new authentication connection is made.
FIG. 20 is a flow diagram of an exemplary method 2000 for risk-based vulnerability and patch management, according to one aspect. According to the aspect, an advanced cyber decision platform may monitor all information about a network 2001, including (but not limited to) device telemetry data, log files, connections and network events, deployed software versions, or contextual user activity information. This information is incorporated into a CPG 2002 to maintain an up-to-date model of the network in real-time. When a new vulnerability is discovered, a blast radius score may be assessed 2003 and the network's resiliency score may be updated 2004 as needed. A security alert may then be produced 2005 to notify an administrator of the vulnerability and its impact, and a proposed patch may be presented 2006 along with the predicted effects of the patch on the vulnerability's blast radius and the overall network resiliency score. This determines both the total impact risk of any particular vulnerability, as well as the overall effect of each vulnerability on the network as a whole. This continuous network assessment may be used to collect information about new vulnerabilities and exploits to provide proactive solutions with clear result predictions, before attacks occur.
FIG. 21 is a flow diagram of an exemplary method 2100 for establishing groups of users according to one aspect. At an initial step 2103, data pertaining to network interaction between users and devices are gathered by a grouping engine. At step 2106, the grouping engine may then process the gathered information by converting it to a graph format and using DCG module to establish groupings for users. A system administrator may provide additional input, and fine-tune the groupings if required. At step 2109, a behavioral baseline is established for each group that may be based on the interaction information, network logs, connected devices, and the like. At step 2112, groups are continuous monitored for anomalous behavior.
FIG. 22 is a flow diagram of an exemplary method 2200 for monitoring groups for anomalous behavior, according to one aspect. At an initial step 2203, a system, as described above in FIG. 8 , gathers network-related data. This data may comprise usage logs, Kerberos session data, computers and other devices connected to the network, active users, software installed, and the like. At step 2206, a behavioral analysis engine may process the data. Parallel computing may be used to speed up the processing of the data. The data may then be sorted by, and associated to, previously established groupings. At step 2209, a behavioral baseline score is generated for each group based on the results of the data processing. At step 2212, the data is stored into a time-series graph database. The process repeats periodically to create snapshots of various moments in time, and stored into the database. This may allow the system to retrain the baseline to take into considering non-anomalous baseline variances that may occur over time, as well as forecast changes in group dynamics using predictive analysis functions of ACDP system 100.
FIG. 23 is a flow diagram for an exemplary method 2300 for handing a detection of anomalous behavior, according to one aspect. At an initial step 2303, the system detects anomalous user behavior from a group. This may be based on comparison to established baselines, or a high priority incident caught during routine monitoring, for example a device accessing a blacklisted domain. At step 2306, the system investigates the group in which the anomalous behavior originated. This may include a more thorough analysis of usage and access logs. If applicable, users or devices with higher access privileges may be investigated before those with lower access privileges. At step 2309, the source or sources of the anomalous behavior is identified, and some corrective measures may be taken. For example, the offending device or user account may be automatically locked out of the network until a solution has been implemented. At step 2312, group members and system administrators may be notified. The system may utilize the various techniques discussed above to recommend a corrective action, or the system may take action automatically.
FIG. 24 is a flow diagram illustrating an exemplary method 2400 for processing a new user connection, according to one aspect. At an initial step 2403, system 910 detects a user connecting to a monitored service provider. At step 2406, if the user is connecting with an existing AO, the process leads to the method discussed in FIG. 25 at step 2409.
If the user doesn't have an existing AO, the service provider forwards the user to an identity provider at step 2412. At step 2415, the identity provider prompts the user for identifying information, such as a username and password. At step 2418, after successful verification, the IdP generates a unique AO for the user. At step 2421, system 910 retrieves the AO and uses a hashing engine to calculate a cryptographic hash for the newly generated AO, and stores the hash in a data store.
FIG. 25 is a flow diagram illustrating an exemplary method 2500 for verifying the authenticity of an authentication object, according to one aspect. At an initial step 2503, a user with an AO connects to a monitored service provider. At step 2506, system 910 detects the connection request, retrieves the AO, and generates a cryptographic hash for the AO. System 910 may now compare the newly generated hashes with previous generated hashes stored in memory. At step 2509, if the AO is found to be authentic, the connect proceeds as normal and method 2500 ends at step 2512 as no further action for this session is required. If the AO is determined to be forged, method 2500 goes to step 2515 where ECA rules may be triggered to perform their preset functions, and perform “circuit breaker” checks within a user-configurable time period. At step 2518, a network administrator at step may be notified, and sent any relevant information, such as blast radius, access logs for the forged AO connection, and the like.
Hardware Architecture
Generally, the techniques disclosed herein may be implemented on hardware or a combination of software and hardware. For example, they may be implemented in an operating system kernel, in a separate user process, in a library package bound into network applications, on a specially constructed machine, on an application-specific integrated circuit (ASIC), or on a network interface card.
Software/hardware hybrid implementations of at least some of the aspects disclosed herein may be implemented on a programmable network-resident machine (which should be understood to include intermittently connected network-aware machines) selectively activated or reconfigured by a computer program stored in memory. Such network devices may have multiple network interfaces that may be configured or designed to utilize different types of network communication protocols. A general architecture for some of these machines may be described herein in order to illustrate one or more exemplary means by which a given unit of functionality may be implemented. According to specific aspects, at least some of the features or functionalities of the various aspects disclosed herein may be implemented on one or more general-purpose computers associated with one or more networks, such as for example an end-user computer system, a client computer, a network server or other server system, a mobile computing device (e.g., tablet computing device, mobile phone, smartphone, laptop, or other appropriate computing device), a consumer electronic device, a music player, or any other suitable electronic device, router, switch, or other suitable device, or any combination thereof. In at least some aspects, at least some of the features or functionalities of the various aspects disclosed herein may be implemented in one or more virtualized computing environments (e.g., network computing clouds, virtual machines hosted on one or more physical computing machines, or other appropriate virtual environments).
Referring now to FIG. 26 , there is shown a block diagram depicting an exemplary computing device 10 suitable for implementing at least a portion of the features or functionalities disclosed herein. Computing device 10 may be, for example, any one of the computing machines listed in the previous paragraph, or indeed any other electronic device capable of executing software- or hardware-based instructions according to one or more programs stored in memory. Computing device 10 may be configured to communicate with a plurality of other computing devices, such as clients or servers, over communications networks such as a wide area network a metropolitan area network, a local area network, a wireless network, the Internet, or any other network, using known protocols for such communication, whether wireless or wired.
In one aspect, computing device 10 includes one or more central processing units (CPU) 12, one or more interfaces 15, and one or more busses 14 (such as a peripheral component interconnect (PCI) bus). When acting under the control of appropriate software or firmware, CPU 12 may be responsible for implementing specific functions associated with the functions of a specifically configured computing device or machine. For example, in at least one aspect, a computing device 10 may be configured or designed to function as a server system utilizing CPU 12, local memory 11 and/or remote memory 16, and interface(s) 15. In at least one aspect, CPU 12 may be caused to perform one or more of the different types of functions and/or operations under the control of software modules or components, which for example, may include an operating system and any appropriate applications software, drivers, and the like.
CPU 12 may include one or more processors 13 such as, for example, a processor from one of the Intel, ARM, Qualcomm, and AMD families of microprocessors. In some aspects, processors 13 may include specially designed hardware such as application-specific integrated circuits (ASICs), electrically erasable programmable read-only memories (EEPROMs), field-programmable gate arrays (FPGAs), and so forth, for controlling operations of computing device 10. In a particular aspect, a local memory 11 (such as non-volatile random access memory (RAM) and/or read-only memory (ROM), including for example one or more levels of cached memory) may also form part of CPU 12. However, there are many different ways in which memory may be coupled to system 10. Memory 11 may be used for a variety of purposes such as, for example, caching and/or storing data, programming instructions, and the like. It should be further appreciated that CPU 12 may be one of a variety of system-on-a-chip (SOC) type hardware that may include additional hardware such as memory or graphics processing chips, such as a QUALCOMM SNAPDRAGON™ or SAMSUNG EXYNOS™ CPU as are becoming increasingly common in the art, such as for use in mobile devices or integrated devices.
As used herein, the term “processor” is not limited merely to those integrated circuits referred to in the art as a processor, a mobile processor, or a microprocessor, but broadly refers to a microcontroller, a microcomputer, a programmable logic controller, an application-specific integrated circuit, and any other programmable circuit.
In one aspect, interfaces 15 are provided as network interface cards (NICs). Generally, NICs control the sending and receiving of data packets over a computer network; other types of interfaces 15 may for example support other peripherals used with computing device 10. Among the interfaces that may be provided are Ethernet interfaces, frame relay interfaces, cable interfaces, DSL interfaces, token ring interfaces, graphics interfaces, and the like. In addition, various types of interfaces may be provided such as, for example, universal serial bus (USB), Serial, Ethernet, FIREWIRE™, THUNDERBOLT™, PCI, parallel, radio frequency (RF), BLUETOOTH™, near-field communications (e.g., using near-field magnetics), 802.11 (WiFi), frame relay, TCP/IP, ISDN, fast Ethernet interfaces, Gigabit Ethernet interfaces, Serial ATA (SATA) or external SATA (ESATA) interfaces, high-definition multimedia interface (HDMI), digital visual interface (DVI), analog or digital audio interfaces, asynchronous transfer mode (ATM) interfaces, high-speed serial interface (HSSI) interfaces, Point of Sale (POS) interfaces, fiber data distributed interfaces (FDDIs), and the like. Generally, such interfaces 15 may include physical ports appropriate for communication with appropriate media. In some cases, they may also include an independent processor (such as a dedicated audio or video processor, as is common in the art for high-fidelity AN hardware interfaces) and, in some instances, volatile and/or non-volatile memory (e.g., RAM).
Although the system shown in FIG. 26 illustrates one specific architecture for a computing device 10 for implementing one or more of the aspects described herein, it is by no means the only device architecture on which at least a portion of the features and techniques described herein may be implemented. For example, architectures having one or any number of processors 13 may be used, and such processors 13 may be present in a single device or distributed among any number of devices. In one aspect, a single processor 13 handles communications as well as routing computations, while in other aspects a separate dedicated communications processor may be provided. In various aspects, different types of features or functionalities may be implemented in a system according to the aspect that includes a client device (such as a tablet device or smartphone running client software) and server systems (such as a server system described in more detail below).
Regardless of network device configuration, the system of an aspect may employ one or more memories or memory modules (such as, for example, remote memory block 16 and local memory 11) configured to store data, program instructions for the general-purpose network operations, or other information relating to the functionality of the aspects described herein (or any combinations of the above). Program instructions may control execution of or comprise an operating system and/or one or more applications, for example. Memory 16 or memories 11, 16 may also be configured to store data structures, configuration data, encryption data, historical system operations information, or any other specific or generic non-program information described herein.
Because such information and program instructions may be employed to implement one or more systems or methods described herein, at least some network device aspects may include nontransitory machine-readable storage media, which, for example, may be configured or designed to store program instructions, state information, and the like for performing various operations described herein. Examples of such nontransitory machine-readable storage media include, but are not limited to, magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as optical disks, and hardware devices that are specially configured to store and perform program instructions, such as read-only memory devices (ROM), flash memory (as is common in mobile devices and integrated systems), solid state drives (SSD) and “hybrid SSD” storage drives that may combine physical components of solid state and hard disk drives in a single hardware device (as are becoming increasingly common in the art with regard to personal computers), memristor memory, random access memory (RAM), and the like. It should be appreciated that such storage means may be integral and non-removable (such as RAM hardware modules that may be soldered onto a motherboard or otherwise integrated into an electronic device), or they may be removable such as swappable flash memory modules (such as “thumb drives” or other removable media designed for rapidly exchanging physical storage devices), “hot-swappable” hard disk drives or solid state drives, removable optical storage discs, or other such removable media, and that such integral and removable storage media may be utilized interchangeably. Examples of program instructions include both object code, such as may be produced by a compiler, machine code, such as may be produced by an assembler or a linker, byte code, such as may be generated by for example a JAVA™ compiler and may be executed using a Java virtual machine or equivalent, or files containing higher level code that may be executed by the computer using an interpreter (for example, scripts written in Python, Perl, Ruby, Groovy, or any other scripting language).
In some aspects, systems may be implemented on a standalone computing system. Referring now to FIG. 27 , there is shown a block diagram depicting a typical exemplary architecture of one or more aspects or components thereof on a standalone computing system. Computing device 20 includes processors 21 that may run software that carry out one or more functions or applications of aspects, such as for example a client application 24. Processors 21 may carry out computing instructions under control of an operating system 22 such as, for example, a version of MICROSOFT WINDOWS™ operating system, APPLE macOS™ or iOS™ operating systems, some variety of the Linux operating system, ANDROID™ operating system, or the like. In many cases, one or more shared services 23 may be operable in system 20, and may be useful for providing common services to client applications 24. Services 23 may for example be WINDOWS™ services, user-space common services in a Linux environment, or any other type of common service architecture used with operating system 21. Input devices 28 may be of any type suitable for receiving user input, including for example a keyboard, touchscreen, microphone (for example, for voice input), mouse, touchpad, trackball, or any combination thereof. Output devices 27 may be of any type suitable for providing output to one or more users, whether remote or local to system 20, and may include for example one or more screens for visual output, speakers, printers, or any combination thereof. Memory 25 may be random-access memory having any structure and architecture known in the art, for use by processors 21, for example to run software. Storage devices 26 may be any magnetic, optical, mechanical, memristor, or electrical storage device for storage of data in digital form (such as those described above, referring to FIG. 26 ). Examples of storage devices 26 include flash memory, magnetic hard drive, CD-ROM, and/or the like.
In some aspects, systems may be implemented on a distributed computing network, such as one having any number of clients and/or servers. Referring now to FIG. 28 , there is shown a block diagram depicting an exemplary architecture 30 for implementing at least a portion of a system according to one aspect on a distributed computing network. According to the aspect, any number of clients 33 may be provided. Each client 33 may run software for implementing client-side portions of a system; clients may comprise a system 20 such as that illustrated in FIG. 27 . In addition, any number of servers 32 may be provided for handling requests received from one or more clients 33. Clients 33 and servers 32 may communicate with one another via one or more electronic networks 31, which may be in various aspects any of the Internet, a wide area network, a mobile telephony network (such as CDMA or GSM cellular networks), a wireless network (such as WiFi, WiMAX, LTE, and so forth), or a local area network (or indeed any network topology known in the art; the aspect does not prefer any one network topology over any other). Networks 31 may be implemented using any known network protocols, including for example wired and/or wireless protocols.
In addition, in some aspects, servers 32 may call external services 37 when needed to obtain additional information, or to refer to additional data concerning a particular call. Communications with external services 37 may take place, for example, via one or more networks 31. In various aspects, external services 37 may comprise web-enabled services or functionality related to or installed on the hardware device itself. For example, in one aspect where client applications 24 are implemented on a smartphone or other electronic device, client applications 24 may obtain information stored in a server system 32 in the cloud or on an external service 37 deployed on one or more of a particular enterprise's or user's premises.
In some aspects, clients 33 or servers 32 (or both) may make use of one or more specialized services or appliances that may be deployed locally or remotely across one or more networks 31. For example, one or more databases 34 may be used or referred to by one or more aspects. It should be understood by one having ordinary skill in the art that databases 34 may be arranged in a wide variety of architectures and using a wide variety of data access and manipulation means. For example, in various aspects one or more databases 34 may comprise a relational database system using a structured query language (SQL), while others may comprise an alternative data storage technology such as those referred to in the art as “NoSQL” (for example, HADOOP CASSANDRA™, GOOGLE BIGTABLE™, and so forth). In some aspects, variant database architectures such as column-oriented databases, in-memory databases, clustered databases, distributed databases, or even flat file data repositories may be used according to the aspect. It will be appreciated by one having ordinary skill in the art that any combination of known or future database technologies may be used as appropriate, unless a specific database technology or a specific arrangement of components is specified for a particular aspect described herein. Moreover, it should be appreciated that the term “database” as used herein may refer to a physical database machine, a cluster of machines acting as a single database system, or a logical database within an overall database management system. Unless a specific meaning is specified for a given use of the term “database”, it should be construed to mean any of these senses of the word, all of which are understood as a plain meaning of the term “database” by those having ordinary skill in the art.
Similarly, some aspects may make use of one or more security systems 36 and configuration systems 35. Security and configuration management are common information technology (IT) and web functions, and some amount of each are generally associated with any IT or web systems. It should be understood by one having ordinary skill in the art that any configuration or security subsystems known in the art now or in the future may be used in conjunction with aspects without limitation, unless a specific security 36 or configuration system 35 or approach is specifically required by the description of any specific aspect.
FIG. 29 shows an exemplary overview of a computer system 40 as may be used in any of the various locations throughout the system. It is exemplary of any computer that may execute code to process data. Various modifications and changes may be made to computer system 40 without departing from the broader scope of the system and method disclosed herein. Central processor unit (CPU) 41 is connected to bus 42, to which bus is also connected memory 43, nonvolatile memory 44, display 47, input/output (I/O) unit 48, and network interface card (NIC) 53. I/O unit 48 may, typically, be connected to keyboard 49, pointing device 50, hard disk 52, and real-time clock 51. NIC 53 connects to network 54, which may be the Internet or a local network, which local network may or may not have connections to the Internet. Also shown as part of system 40 is power supply unit 45 connected, in this example, to a main alternating current (AC) supply 46. Not shown are batteries that could be present, and many other devices and modifications that are well known but are not applicable to the specific novel functions of the current system and method disclosed herein.
It should be appreciated that some or all components illustrated may be combined, such as in various integrated applications, for example Qualcomm or Samsung system-on-a-chip (SOC) devices, or whenever it may be appropriate to combine multiple capabilities or functions into a single hardware device (for instance, in mobile devices such as smartphones, video game consoles, in-vehicle computer systems such as navigation or multimedia systems in automobiles, or other integrated hardware devices).
In various aspects, functionality for implementing systems or methods of various aspects may be distributed among any number of client and/or server components. For example, various software modules may be implemented for performing various functions in connection with the system of any particular aspect, and such modules may be variously implemented to run on server and/or client components.
The skilled person will be aware of a range of possible modifications of the various aspects described above. Accordingly, the present invention is defined by the claims and their equivalents.

Claims (6)

What is claimed is:
1. A system for detecting and mitigating attacks using forged authentication objects within a domain, comprising:
a computing device comprising a memory and a processor;
an authentication object inspector comprising a first plurality of programming instructions stored in the memory which, when operating on the processor, causes the computing device to:
receive network traffic comprising a plurality of network packets, the plurality of network packets comprising a plurality of first authentication objects known to be generated by an identity provider associated with an authentication domain;
store a record of each received first authentication object, with attached metadata comprising a timestamp of when each first authentication object was received, in a time-series database;
calculate a cryptographic hash of each first authentication object using a hashing engine;
store the cryptographic hash of each first authentication object in a database of hashes for the identity provider;
receive a request for access to a network resource associated with the authentication domain accompanied by a second authentication object;
calculate a cryptographic hash of the second authentication object using the hashing engine;
compare the cryptographic hash of the second authentication object with the cryptographic hashes of the first authentication objects stored in the database of hashes to determine whether the cryptographic hash of the second authentication object already exists in the database of hashes;
where the cryptographic hash of the second authentication object does not exist in the database of hashes, generate a notification that the identity provider may be compromised; and
the hashing engine comprising a second plurality of programming instructions stored in the memory which, when operating on the processor, causes the computing device to:
receive authentication objects from the authentication object inspector;
calculate cryptographic hashes for authentication objects received by performing a plurality of calculations and transformations on each authentication object received; and
return the cryptographic hashes of authentication objects received to the authentication object inspector.
2. The system of claim 1, wherein the authentication object inspector is operated by the identity provider.
3. The system of claim 1, wherein the authentication object inspector is operated by a client device communicating with the identity provider over a network.
4. A method for detecting and mitigating attacks using forged authentication objects within a domain, comprising the steps of:
using an authentication object inspector operating on a computing device comprising a memory and a processor to:
receive network traffic comprising a plurality of network packets, the plurality of network packets comprising at least a plurality of first authentication objects known to be generated by an identity provider associated with an authentication domain;
store a record of each received authentication object, with attached metadata comprising at least a timestamp of when the authentication object was received, in a time-series database;
calculate a cryptographic hash of each first authentication object using a hashing engine;
store the cryptographic hashes of the first authentication objects in a database of hashes for the identity provider;
receive a request for access to a network resource associated with the authentication domain accompanied by a second authentication object;
calculate a cryptographic hash of the second authentication object using the hashing engine;
compare the cryptographic hash of the second authentication object with the cryptographic hashes of the first authentication objects stored in the database of hashes to determine whether the cryptographic hash of the second authentication object already exists in the database;
where the cryptographic hash of the second authentication object does not exist in the database, generate a notification that the identity provider may be compromised; and
using the hashing engine operating on the computing device to:
receive authentication objects from the authentication object inspector;
calculate cryptographic hashes on authentication objects received by performing a plurality of calculations and transformations on each authentication object received; and
return the calculated cryptographic hashes to the authentication object inspector.
5. The method of claim 4, wherein the authentication object inspector is operated by the identity provider.
6. The method of claim 4, wherein the authentication object inspector is operated by a client device communicating with the identity provider over a network.
US17/169,924 2015-10-28 2021-02-08 Detecting and mitigating attacks using forged authentication objects within a domain Active 2036-04-11 US11570209B2 (en)

Priority Applications (20)

Application Number Priority Date Filing Date Title
US17/170,288 US11570204B2 (en) 2015-10-28 2021-02-08 Detecting and mitigating golden ticket attacks within a domain
US17/169,924 US11570209B2 (en) 2015-10-28 2021-02-08 Detecting and mitigating attacks using forged authentication objects within a domain
US17/567,060 US20220201042A1 (en) 2015-10-28 2021-12-31 Ai-driven defensive penetration test analysis and recommendation system
US17/960,081 US20230113332A1 (en) 2015-10-28 2022-10-04 Advanced detection of identity-based attacks to assure identity fidelity in information technology environments
US17/973,520 US11799900B2 (en) 2015-10-28 2022-10-25 Detecting and mitigating golden ticket attacks within a domain
US17/974,257 US11818169B2 (en) 2015-10-28 2022-10-26 Detecting and mitigating attacks using forged authentication objects within a domain
US17/986,850 US20230171292A1 (en) 2015-10-28 2022-11-14 Holistic external network cybersecurity evaluation and scoring
US18/184,548 US20230308459A1 (en) 2015-10-28 2023-03-15 Authentication attack detection and mitigation with embedded authentication and delegation
US18/333,414 US20230362141A1 (en) 2015-10-28 2023-06-12 Network authentication toxicity assessment
US18/339,214 US20230362200A1 (en) 2015-10-28 2023-06-21 Dynamic cybersecurity scoring and operational risk reduction assessment
US18/339,191 US20240163261A1 (en) 2015-10-28 2023-06-21 Dynamic authentication attack detection and enforcement at network, application, and host level
US18/361,825 US20240022546A1 (en) 2015-10-28 2023-07-29 Master ledger and local host log extension detection and mitigation of forged authentication attacks
US18/489,003 US11968227B2 (en) 2015-10-28 2023-10-18 Detecting KERBEROS ticket attacks within a domain
US18/501,977 US12003534B2 (en) 2015-10-28 2023-11-03 Detecting and mitigating forged authentication attacks within a domain
US18/402,662 US12224992B2 (en) 2015-10-28 2024-01-02 AI-driven defensive cybersecurity strategy analysis and recommendation system
US18/582,519 US20240195833A1 (en) 2015-10-28 2024-02-20 System for automated capture and analysis of business information for security and client-facing infrastructure reliability
US18/619,162 US20240244068A1 (en) 2015-10-28 2024-03-28 System and methods for detecting authentication object forgery or manipulation attacks
US18/639,954 US20240267402A1 (en) 2015-10-28 2024-04-18 Detecting kerberos ticket attacks within a domain
US18/672,024 US20240314162A1 (en) 2015-10-28 2024-05-23 Detecting and mitigating forged authentication attacks within a domain
US18/779,064 US12155693B1 (en) 2015-10-28 2024-07-21 Rapid predictive analysis of very large data sets using the distributed computational graph

Applications Claiming Priority (15)

Application Number Priority Date Filing Date Title
US14/925,974 US20170124464A1 (en) 2015-10-28 2015-10-28 Rapid predictive analysis of very large data sets using the distributed computational graph
US14/986,536 US10210255B2 (en) 2015-12-31 2015-12-31 Distributed system for large volume deep web data extraction
US15/091,563 US10204147B2 (en) 2016-04-05 2016-04-05 System for capture, analysis and storage of time series data from sensors with heterogeneous report interval profiles
US15/141,752 US10860962B2 (en) 2015-10-28 2016-04-28 System for fully integrated capture, and analysis of business information resulting in predictive decision making and simulation
US15/166,158 US20170124501A1 (en) 2015-10-28 2016-05-26 System for automated capture and analysis of business information for security and client-facing infrastructure reliability
US15/186,453 US20170124497A1 (en) 2015-10-28 2016-06-18 System for automated capture and analysis of business information for reliable business venture outcome prediction
US15/206,195 US20170124492A1 (en) 2015-10-28 2016-07-08 System for automated capture and analysis of business information for reliable business venture outcome prediction
US15/237,625 US10248910B2 (en) 2015-10-28 2016-08-15 Detection mitigation and remediation of cyberattacks employing an advanced cyber-decision platform
US15/616,427 US20170371726A1 (en) 2015-10-28 2017-06-07 Rapid predictive analysis of very large data sets using an actor-driven distributed computational graph
US15/655,113 US10735456B2 (en) 2015-10-28 2017-07-20 Advanced cybersecurity threat mitigation using behavioral and deep analytics
US15/725,274 US10609079B2 (en) 2015-10-28 2017-10-04 Application of advanced cybersecurity threat mitigation to rogue devices, privilege escalation, and risk-based vulnerability and patch management
US15/825,350 US10594714B2 (en) 2015-10-28 2017-11-29 User and entity behavioral analysis using an advanced cyber decision platform
US201762596105P 2017-12-07 2017-12-07
US15/837,845 US11005824B2 (en) 2015-10-28 2017-12-11 Detecting and mitigating forged authentication object attacks using an advanced cyber decision platform
US17/169,924 US11570209B2 (en) 2015-10-28 2021-02-08 Detecting and mitigating attacks using forged authentication objects within a domain

Related Parent Applications (2)

Application Number Title Priority Date Filing Date
US15/837,845 Continuation-In-Part US11005824B2 (en) 2015-10-28 2017-12-11 Detecting and mitigating forged authentication object attacks using an advanced cyber decision platform
US17/170,288 Continuation US11570204B2 (en) 2015-10-28 2021-02-08 Detecting and mitigating golden ticket attacks within a domain

Related Child Applications (3)

Application Number Title Priority Date Filing Date
US17/170,288 Continuation-In-Part US11570204B2 (en) 2015-10-28 2021-02-08 Detecting and mitigating golden ticket attacks within a domain
US17/973,520 Continuation-In-Part US11799900B2 (en) 2015-10-28 2022-10-25 Detecting and mitigating golden ticket attacks within a domain
US17/974,257 Continuation US11818169B2 (en) 2015-10-28 2022-10-26 Detecting and mitigating attacks using forged authentication objects within a domain

Publications (2)

Publication Number Publication Date
US20210297447A1 US20210297447A1 (en) 2021-09-23
US11570209B2 true US11570209B2 (en) 2023-01-31

Family

ID=77748484

Family Applications (6)

Application Number Title Priority Date Filing Date
US17/169,924 Active 2036-04-11 US11570209B2 (en) 2015-10-28 2021-02-08 Detecting and mitigating attacks using forged authentication objects within a domain
US17/974,257 Active US11818169B2 (en) 2015-10-28 2022-10-26 Detecting and mitigating attacks using forged authentication objects within a domain
US18/501,977 Active US12003534B2 (en) 2015-10-28 2023-11-03 Detecting and mitigating forged authentication attacks within a domain
US18/582,519 Pending US20240195833A1 (en) 2015-10-28 2024-02-20 System for automated capture and analysis of business information for security and client-facing infrastructure reliability
US18/672,024 Pending US20240314162A1 (en) 2015-10-28 2024-05-23 Detecting and mitigating forged authentication attacks within a domain
US18/779,064 Active US12155693B1 (en) 2015-10-28 2024-07-21 Rapid predictive analysis of very large data sets using the distributed computational graph

Family Applications After (5)

Application Number Title Priority Date Filing Date
US17/974,257 Active US11818169B2 (en) 2015-10-28 2022-10-26 Detecting and mitigating attacks using forged authentication objects within a domain
US18/501,977 Active US12003534B2 (en) 2015-10-28 2023-11-03 Detecting and mitigating forged authentication attacks within a domain
US18/582,519 Pending US20240195833A1 (en) 2015-10-28 2024-02-20 System for automated capture and analysis of business information for security and client-facing infrastructure reliability
US18/672,024 Pending US20240314162A1 (en) 2015-10-28 2024-05-23 Detecting and mitigating forged authentication attacks within a domain
US18/779,064 Active US12155693B1 (en) 2015-10-28 2024-07-21 Rapid predictive analysis of very large data sets using the distributed computational graph

Country Status (1)

Country Link
US (6) US11570209B2 (en)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220060453A1 (en) * 2015-10-28 2022-02-24 Qomplx, Inc. Detecting and mitigating forged authentication object attacks in multi - cloud environments
US20220166792A1 (en) * 2018-10-31 2022-05-26 SpyCloud, Inc. Detecting use of compromised security credentials in private enterprise networks
US20230118388A1 (en) * 2015-10-28 2023-04-20 Qomplx, Inc. Detecting and mitigating golden ticket attacks within a domain
US20230308459A1 (en) * 2015-10-28 2023-09-28 Qomplx, Inc. Authentication attack detection and mitigation with embedded authentication and delegation
US20230319019A1 (en) * 2015-10-28 2023-10-05 Qomplx, Inc. Detecting and mitigating forged authentication attacks using an advanced cyber decision platform
US11838300B1 (en) * 2019-12-24 2023-12-05 Musarubra Us Llc Run-time configurable cybersecurity system
US12199995B2 (en) * 2022-09-23 2025-01-14 Zhejiang Gongshang University System and method for authentication code generation based on adversarial machine learning

Families Citing this family (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10671750B2 (en) * 2018-08-17 2020-06-02 Mentis Inc. System and method for data classification centric sensitive data discovery
US11777979B2 (en) * 2020-05-11 2023-10-03 Firecompass Technologies Pvt Ltd System and method to perform automated red teaming in an organizational network
US11770377B1 (en) * 2020-06-29 2023-09-26 Cyral Inc. Non-in line data monitoring and security services
US20220159029A1 (en) * 2020-11-13 2022-05-19 Cyberark Software Ltd. Detection of security risks based on secretless connection data
US11888835B2 (en) * 2021-06-01 2024-01-30 Pure Storage, Inc. Authentication of a node added to a cluster of a container system
US11831688B2 (en) * 2021-06-18 2023-11-28 Capital One Services, Llc Systems and methods for network security
US12010125B2 (en) * 2021-06-29 2024-06-11 Microsoft Technology Licensing, Llc Anomaly detection in an application with delegate authorization
US20230376586A1 (en) 2022-05-23 2023-11-23 Wiz, Inc. Techniques for improved virtual instance inspection utilizing disk cloning
US12278819B1 (en) 2021-07-16 2025-04-15 Wiz, Inc. Cybersecurity threat detection utilizing unified identity mapping and permission detection
US11924190B2 (en) * 2021-08-17 2024-03-05 Cisco Technology, Inc. Service assurance via federation-based network during roaming
US12155640B2 (en) * 2021-10-21 2024-11-26 Jpmorgan Chase Bank, N.A. Systems and methods for cloud federated token just in time authorization
US12072976B1 (en) * 2021-10-26 2024-08-27 Gen Digital Inc. Systems and methods for utilizing telemetry data to customize threat protection actions against potential malware threats
CN114157490A (en) * 2021-12-03 2022-03-08 武汉极意网络科技有限公司 User request event analysis method based on clustering algorithm
US11936785B1 (en) 2021-12-27 2024-03-19 Wiz, Inc. System and method for encrypted disk inspection utilizing disk cloning techniques
US11841945B1 (en) 2022-01-31 2023-12-12 Wiz, Inc. System and method for cybersecurity threat detection utilizing static and runtime data
US11936693B2 (en) 2022-04-13 2024-03-19 Wiz, Inc. System and method for applying a policy on a network path
CN114826760B (en) * 2022-05-12 2023-08-15 深圳铸泰科技有限公司 Network security analysis method based on boundary theory
US12287899B2 (en) 2022-05-23 2025-04-29 Wiz, Inc. Techniques for detecting sensitive data in cloud computing environments utilizing cloning
CN115632859A (en) * 2022-10-21 2023-01-20 杭州安恒信息技术股份有限公司 Bill authenticity identification method, device, equipment and medium
US20240223577A1 (en) * 2022-12-29 2024-07-04 Varonis Systems, Inc. Indicators of compromise of access
US11763006B1 (en) * 2023-01-19 2023-09-19 Citibank, N.A. Comparative real-time end-to-end security vulnerabilities determination and visualization
US11748491B1 (en) 2023-01-19 2023-09-05 Citibank, N.A. Determining platform-specific end-to-end security vulnerabilities for a software application via a graphical user interface (GUI) systems and methods
US12299140B2 (en) 2023-01-19 2025-05-13 Citibank, N.A. Dynamic multi-model monitoring and validation for artificial intelligence models
US12282565B2 (en) 2023-01-19 2025-04-22 Citibank, N.A. Generative cybersecurity exploit synthesis and mitigation
US12271491B2 (en) 2023-01-19 2025-04-08 Citibank, N.A. Detection and mitigation of machine learning model adversarial attacks
US12223063B2 (en) 2023-01-19 2025-02-11 Citibank, N.A. End-to-end measurement, grading and evaluation of pretrained artificial intelligence models via a graphical user interface (GUI) systems and methods
US11874934B1 (en) * 2023-01-19 2024-01-16 Citibank, N.A. Providing user-induced variable identification of end-to-end computing system security impact information systems and methods
US20250039233A1 (en) * 2023-07-28 2025-01-30 Qomplx Llc Host - level ticket forgery detection and extension to network endpoints
US12003529B1 (en) * 2024-02-22 2024-06-04 Wiz, Inc. Techniques for detecting artificial intelligence model cybersecurity risk in a computing environment
US12154019B1 (en) 2024-06-07 2024-11-26 Citibank, N.A. System and method for constructing a layered artificial intelligence model

Citations (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6256544B1 (en) 1996-08-13 2001-07-03 Duerr Systems Gmbh Apparatus and method for controlling functional units in a manufacturing installation
US20030041254A1 (en) * 2001-08-24 2003-02-27 International Business Machines Corporation Securing sensitive configuration data remotely
US20030145225A1 (en) 2002-01-28 2003-07-31 International Business Machines Corporation Intrusion event filtering and generic attack signatures
US20070036314A1 (en) * 2005-07-20 2007-02-15 Kloberdans Michael J Telephony extension attack detection, recording, and intelligent prevention
US20070136821A1 (en) * 2005-12-13 2007-06-14 Interdigital Technology Corporation Method and system for protecting user data in a node
US20070150744A1 (en) * 2005-12-22 2007-06-28 Cheng Siu L Dual authentications utilizing secure token chains
US20080021866A1 (en) 2006-07-20 2008-01-24 Heather M Hinton Method and system for implementing a floating identity provider model across data centers
US20090182672A1 (en) * 2008-01-11 2009-07-16 Doyle Paul F System and Method for Financial Transaction Validation
US7702821B2 (en) 2005-09-15 2010-04-20 Eye-Fi, Inc. Content-aware digital media storage device and methods of using the same
US20110087888A1 (en) 2009-10-13 2011-04-14 Google Inc. Authentication using a weak hash of user credentials
US20130117831A1 (en) 2010-04-30 2013-05-09 Lock Box Pty Ltd Method and system for enabling computer access
US8601554B2 (en) 2011-11-09 2013-12-03 Microsoft Corporation Home realm discovery in mixed-mode federated realms
WO2014159150A1 (en) 2013-03-14 2014-10-02 Microsoft Corporation Software release workflow management
US20150128258A1 (en) 2012-04-11 2015-05-07 Utc Fire & Security Corporation Authentication mode reporting
US20150281225A1 (en) * 2014-03-27 2015-10-01 Microsoft Corporation Techniques to operate a service with machine generated authentication tokens
US20150317481A1 (en) * 2014-05-05 2015-11-05 Sypris Electronics, Llc System and device for verifying the integrity of a system from its subcomponents
US9253643B2 (en) 2009-03-05 2016-02-02 Interdigital Patent Holdings, Inc. Method and apparatus for H(e)NB integrity verification and validation
US20160072845A1 (en) 2003-12-30 2016-03-10 Entrust, Inc. Method and apparatus for providing authentication using policy-controlled authentication articles and techniques
US20160275123A1 (en) 2015-03-18 2016-09-22 Hitachi, Ltd. Pipeline execution of multiple map-reduce jobs
US9602530B2 (en) 2014-03-28 2017-03-21 Zitovault, Inc. System and method for predicting impending cyber security events using multi channel behavioral analysis in a distributed computing environment
WO2017075543A1 (en) 2015-10-28 2017-05-04 Fractal Industries, Inc. Rapid predictive analysis of very large data sets using the distributed computational graph
US10038559B2 (en) 2015-10-02 2018-07-31 Google Llc Signatures of updates exchanged in a binary data synchronization protocol
US10061635B2 (en) 2015-11-13 2018-08-28 Kriwan Industrie-Elektronik Gmbh Cyber physical system
US10248910B2 (en) 2015-10-28 2019-04-02 Fractal Industries, Inc. Detection mitigation and remediation of cyberattacks employing an advanced cyber-decision platform
US10367829B2 (en) 2015-11-19 2019-07-30 Anomali Incorporated Protecting threat indicators from third party abuse
US10628578B2 (en) 2013-03-15 2020-04-21 Imagine Communications Corp. Systems and methods for determining trust levels for computing components using blockchain
US11005824B2 (en) * 2015-10-28 2021-05-11 Qomplx, Inc. Detecting and mitigating forged authentication object attacks using an advanced cyber decision platform
US20210297443A1 (en) * 2015-10-28 2021-09-23 Qomplx, Inc. Detecting and mitigating golden ticket attacks within a domain

Family Cites Families (383)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US3370192A (en) 1966-10-07 1968-02-20 Nat Video Corp Color television tube construction including means for minimizing temperature differential between shadow mask frame and tube envelope
US5410681A (en) 1991-11-20 1995-04-25 Apple Computer, Inc. Interpreter for performing remote testing of computer systems
JPH0876955A (en) 1994-09-01 1996-03-22 Fujitsu Ltd System and method for displaying selection substance
US7435249B2 (en) 1997-11-12 2008-10-14 Covidien Ag Electrosurgical instruments which reduces collateral damage to adjacent tissue
PT1080415T (en) 1998-05-21 2017-05-02 Equifax Inc System and method for authentication of network users
US6477572B1 (en) 1998-12-17 2002-11-05 International Business Machines Corporation Method for displaying a network topology for a task deployment service
US7072863B1 (en) 1999-09-08 2006-07-04 C4Cast.Com, Inc. Forecasting using interpolation modeling
JP3499810B2 (en) 2000-03-06 2004-02-23 株式会社東芝 ENCRYPTION DEVICE, ENCRYPTION METHOD, COMPUTER-READABLE RECORDING MEDIUM CONTAINING PROGRAM FOR FUNCTIONING COMPUTER AS ENCRYPTION DEVICE, AND COMPUTER READING RECORDING PROGRAM FOR FUNCTIONING COMPUTER AS DECRYPTION DEVICE, DECRYPTION METHOD, AND DECRYPTION DEVICE Possible recording media
US6643661B2 (en) 2000-04-27 2003-11-04 Brio Software, Inc. Method and apparatus for implementing search and channel features in an enterprise-wide computer system
WO2002021318A2 (en) 2000-09-07 2002-03-14 Petrovantage, Inc. Computer method and apparatus for vessel selection and optimization
US7139747B1 (en) 2000-11-03 2006-11-21 Hewlett-Packard Development Company, L.P. System and method for distributed web crawling
JP2002169808A (en) * 2000-11-30 2002-06-14 Hitachi Ltd Secure multi-database system
US6906709B1 (en) 2001-02-27 2005-06-14 Applied Visions, Inc. Visualizing security incidents in a computer network
US7818224B2 (en) 2001-03-22 2010-10-19 Boerner Sean T Method and system to identify discrete trends in time series
US7603709B2 (en) 2001-05-03 2009-10-13 Computer Associates Think, Inc. Method and apparatus for predicting and preventing attacks in communications networks
JP2002342037A (en) 2001-05-22 2002-11-29 Fujitsu Ltd Disk unit
DE60316543T2 (en) 2002-03-29 2008-07-03 Global Dataguard, Inc., Dallas ADAPTIVE BEHAVIOR-RELATED IMPACT DETECTION
US7546333B2 (en) 2002-10-23 2009-06-09 Netapp, Inc. Methods and systems for predictive change management for access paths in networks
US20040138934A1 (en) * 2003-01-09 2004-07-15 General Electric Company Controlling a business using a business information and decisioning control system
US20040255167A1 (en) 2003-04-28 2004-12-16 Knight James Michael Method and system for remote network security management
US7437718B2 (en) 2003-09-05 2008-10-14 Microsoft Corporation Reviewing the security of trusted software components
US7685296B2 (en) 2003-09-25 2010-03-23 Microsoft Corporation Systems and methods for client-based web crawling
US20050071223A1 (en) 2003-09-30 2005-03-31 Vivek Jain Method, system and computer program product for dynamic marketing strategy development
US7933926B2 (en) 2004-01-09 2011-04-26 Sap Aktiengesellschaft User feedback system
US20050165822A1 (en) 2004-01-22 2005-07-28 Logic Sight, Inc. Systems and methods for business process automation, analysis, and optimization
WO2005077118A2 (en) 2004-02-11 2005-08-25 Spi Dynamics, Inc. System and method for testing web applications with recursive discovery and analysis
US7310632B2 (en) 2004-02-12 2007-12-18 Microsoft Corporation Decision-theoretic web-crawling and predicting web-page change
US7373524B2 (en) 2004-02-24 2008-05-13 Covelight Systems, Inc. Methods, systems and computer program products for monitoring user behavior for a server application
US20050198099A1 (en) 2004-02-24 2005-09-08 Covelight Systems, Inc. Methods, systems and computer program products for monitoring protocol responses for a server application
US7603714B2 (en) 2004-03-08 2009-10-13 International Business Machines Corporation Method, system and computer program product for computer system vulnerability analysis and fortification
US7493593B2 (en) 2004-03-18 2009-02-17 International Business Machines Corporation Method for generating a business process execution language for web services executable workflow code from an unstructured cyclic business process model
US7546207B2 (en) 2004-05-21 2009-06-09 Gm Global Technology Operations, Inc. Turn-by-turn navigation system with enhanced turn icon
US7480940B1 (en) 2004-06-10 2009-01-20 Symantec Corporation Structures and methods for a low and slow network reconnaissance detector
US20050289072A1 (en) 2004-06-29 2005-12-29 Vinay Sabharwal System for automatic, secure and large scale software license management over any computer network
US20060002556A1 (en) * 2004-06-30 2006-01-05 Microsoft Corporation Secure certificate enrollment of device over a cellular network
US20070168370A1 (en) 2004-11-16 2007-07-19 Hardy Mark D System and methods for provisioning geospatial data
US7546637B1 (en) 2004-11-22 2009-06-09 Symantec Corproation Structures and methods for using geo-location in security detectors
US20060149575A1 (en) 2005-01-04 2006-07-06 Srinivas Varadarajan Software engineering process monitoring
US8156029B2 (en) 2005-02-24 2012-04-10 Michael Gregory Szydlo Process for verifiably communicating risk characteristics of an investment portfolio
US9384345B2 (en) 2005-05-03 2016-07-05 Mcafee, Inc. Providing alternative web content based on website reputation assessment
US7743421B2 (en) 2005-05-18 2010-06-22 Alcatel Lucent Communication network security risk exposure management systems and methods
WO2006135756A1 (en) 2005-06-09 2006-12-21 Intepoint, Llc Multi-infrastructure modeling system
US7739653B2 (en) 2005-07-05 2010-06-15 Microsoft Corporation Representing software development item relationships via a graph
US20070055558A1 (en) 2005-08-19 2007-03-08 Shanahan James G Method and apparatus for probabilistic workflow mining
US7698213B2 (en) 2005-08-19 2010-04-13 The Hartford Steam Boiler Inspection And Insurance Co. Method of risk modeling by estimating frequencies of loss and loss distributions for individual risks in a portfolio
US7831582B1 (en) 2005-08-23 2010-11-09 Amazon Technologies, Inc. Method and system for associating keywords with online content sources
US7818417B2 (en) 2006-01-10 2010-10-19 International Business Machines Corporation Method for predicting performance of distributed stream processing systems
US7979460B2 (en) * 2006-02-15 2011-07-12 Sony Computer Entainment America Inc. Systems and methods for server management
WO2007103292A2 (en) 2006-03-01 2007-09-13 Townsend Analytics, Ltd. Methods and systems for risk management
US7530105B2 (en) 2006-03-21 2009-05-05 21St Century Technologies, Inc. Tactical and strategic attack detection and prediction
US20070276714A1 (en) 2006-05-15 2007-11-29 Sap Ag Business process map management
WO2007143226A2 (en) 2006-06-09 2007-12-13 Massachusetts Institute Of Technology Generating a multiple-prerequisite attack graph
US7890869B1 (en) 2006-06-12 2011-02-15 Redseal Systems, Inc. Network security visualization methods, apparatus and graphical user interfaces
US7660815B1 (en) 2006-06-30 2010-02-09 Amazon Technologies, Inc. Method and system for occurrence frequency-based scaling of navigation path weights among online content sources
US8615800B2 (en) 2006-07-10 2013-12-24 Websense, Inc. System and method for analyzing web content
JP5042315B2 (en) 2006-10-19 2012-10-03 チェックマークス リミテッド Detect security vulnerabilities in source code
US8346753B2 (en) 2006-11-14 2013-01-01 Paul V Hayes System and method for searching for internet-accessible content
US9654495B2 (en) 2006-12-01 2017-05-16 Websense, Llc System and method of analyzing web addresses
US8468244B2 (en) 2007-01-05 2013-06-18 Digital Doors, Inc. Digital information infrastructure and method for security designated data and with granular data stores
US8788306B2 (en) 2007-03-05 2014-07-22 International Business Machines Corporation Updating a forecast model
US8725597B2 (en) 2007-04-25 2014-05-13 Google Inc. Merchant scoring system and transactional database
US20080270203A1 (en) 2007-04-27 2008-10-30 Corporation Service Company Assessment of Risk to Domain Names, Brand Names and the Like
WO2008134708A1 (en) 2007-04-30 2008-11-06 Etelemetry, Inc. Method and system for activity monitoring and forecasting
US8006303B1 (en) 2007-06-07 2011-08-23 International Business Machines Corporation System, method and program product for intrusion protection of a network
US8607197B2 (en) 2007-08-28 2013-12-10 International Business Machines Corporation Displaying HTTP session entry and exit points
US8548777B2 (en) 2007-09-28 2013-10-01 Rockwell Automation Technologies, Inc. Automated recommendations from simulation
US20090094372A1 (en) * 2007-10-05 2009-04-09 Nyang Daehun Secret user session managing method and system under web environment, recording medium recorded program executing it
KR100935861B1 (en) 2007-11-12 2010-01-07 한국전자통신연구원 Method and apparatus for predicting network security risk
US8069190B2 (en) 2007-12-27 2011-11-29 Cloudscale, Inc. System and methodology for parallel stream processing
US20090199002A1 (en) 2008-02-05 2009-08-06 Icontrol, Inc. Methods and Systems for Shortened Hash Authentication and Implicit Session Key Agreement
US8583639B2 (en) 2008-02-19 2013-11-12 International Business Machines Corporation Method and system using machine learning to automatically discover home pages on the internet
US7840677B2 (en) 2008-03-11 2010-11-23 International Business Machines Corporation Systems, methods and computer program products for improving placement performance of message transforms by exploiting guided replication
JP5233505B2 (en) 2008-03-17 2013-07-10 株式会社リコー Joint work support device, joint work support system, joint work support method, program, and recording medium
EP2107715B1 (en) 2008-03-31 2019-12-25 Synopsys, Inc. Method, device arrangement and computer program product for creating identity graphs analyzing communication network
US9609015B2 (en) 2008-05-28 2017-03-28 Zscaler, Inc. Systems and methods for dynamic cloud-based malware behavior analysis
US8751629B2 (en) 2008-06-18 2014-06-10 Camber Defense Security And Systems Solutions, Inc. Systems and methods for automated building of a simulated network environment
US8370192B2 (en) 2008-09-23 2013-02-05 At&T Intellectual Property I, Lp Method and system for dynamic project management and capacity management
US8504504B2 (en) 2008-09-26 2013-08-06 Oracle America, Inc. System and method for distributed denial of service identification and prevention
US8116450B2 (en) 2008-10-01 2012-02-14 International Business Machines Corporation System and method for utility sampling for trust metrics in pki
US20100115276A1 (en) 2008-10-31 2010-05-06 Apple Inc. System and method for derivating deterministic binary values
US8677473B2 (en) 2008-11-18 2014-03-18 International Business Machines Corporation Network intrusion protection
US8352347B2 (en) 2008-12-29 2013-01-08 Athenainvest, Inc. Investment classification and tracking system using diamond ratings
US8108406B2 (en) 2008-12-30 2012-01-31 Expanse Networks, Inc. Pangenetic web user behavior prediction system
US8386519B2 (en) 2008-12-30 2013-02-26 Expanse Networks, Inc. Pangenetic web item recommendation system
US8793758B2 (en) 2009-01-28 2014-07-29 Headwater Partners I Llc Security, fraud detection, and fraud mitigation in device-assisted services systems
US9166990B2 (en) 2009-02-09 2015-10-20 Hewlett-Packard Development Company, L.P. Distributed denial-of-service signature transmission
US9110706B2 (en) 2009-02-09 2015-08-18 Microsoft Technology Licensing, Llc General purpose distributed data parallel computing using a high level language
US20140324521A1 (en) * 2009-02-11 2014-10-30 Johnathan Mun Qualitative and quantitative analytical modeling of sales performance and sales goals
US8352412B2 (en) 2009-02-27 2013-01-08 International Business Machines Corporation System for monitoring global online opinions via semantic extraction
US8516594B2 (en) 2009-04-24 2013-08-20 Jeff Bennett Enterprise information security management software for prediction modeling with interactive graphs
US20100275183A1 (en) 2009-04-28 2010-10-28 Panicker Vinod R Source code auditor with a customized rules builder
US8914878B2 (en) 2009-04-29 2014-12-16 Juniper Networks, Inc. Detecting malicious network software agents
US20100299651A1 (en) 2009-05-19 2010-11-25 Nec Laboratories America, Inc. Robust testing for discrete-time and continuous-time system models
US8949772B1 (en) 2009-06-01 2015-02-03 Amazon Technologies, Inc. Dynamic model based software application development
US8417656B2 (en) 2009-06-16 2013-04-09 Oracle International Corporation Techniques for building an aggregate model for performing diagnostics
US20100325685A1 (en) 2009-06-17 2010-12-23 Jamie Sanbower Security Integration System and Device
US8065257B2 (en) 2009-07-27 2011-11-22 Saab Sensis Corporation System and method for correlating past activities, determining hidden relationships and predicting future activities
US8412796B2 (en) * 2009-07-31 2013-04-02 University College Dublin—National University of Ireland, Dublin Real time information feed processing
US8601587B1 (en) 2009-09-04 2013-12-03 Raytheon Company System, method, and software for cyber threat analysis
US8380843B2 (en) 2009-09-10 2013-02-19 Oracle America, Inc. System and method for determining affinity groups and co-locating the affinity groups in a distributing network
US8245302B2 (en) 2009-09-15 2012-08-14 Lockheed Martin Corporation Network attack visualization and response through intelligent icons
US8898442B2 (en) 2009-09-29 2014-11-25 Sap Se Scenario-based process modeling for business processes including exception flow to handle an error in a task of the series of tasks
US8495521B2 (en) 2009-09-29 2013-07-23 International Business Machines Corporation Relationship map generator
US10027711B2 (en) 2009-11-20 2018-07-17 Alert Enterprise, Inc. Situational intelligence
US8407800B2 (en) 2009-11-24 2013-03-26 Honeywell International Inc. Method for software vulnerability flow analysis, generation of vulnerability-covering code, and multi-generation of functionally-equivalent code
US20120296845A1 (en) 2009-12-01 2012-11-22 Andrews Sarah L Methods and systems for generating composite index using social media sourced data and sentiment analysis
US9619291B2 (en) 2009-12-20 2017-04-11 Yahoo! Inc. System and method for a task management library to execute map-reduce applications in a map-reduce framework
US8516596B2 (en) 2010-01-26 2013-08-20 Raytheon Company Cyber attack analysis
US8781990B1 (en) 2010-02-25 2014-07-15 Google Inc. Crowdsensus: deriving consensus information from statements made by a crowd of users
US20110225287A1 (en) 2010-03-12 2011-09-15 Webtrends Inc. Method and system for distributed processing of web traffic analytics data
US8782080B2 (en) 2010-04-19 2014-07-15 Facebook, Inc. Detecting social graph elements for structured search queries
WO2011139195A1 (en) 2010-05-07 2011-11-10 Telefonaktiebolaget L M Ericsson (Publ) Method and arrangement for control of web resources
US8712596B2 (en) 2010-05-20 2014-04-29 Accenture Global Services Limited Malicious attack detection and analysis
WO2011155961A2 (en) 2010-06-10 2011-12-15 Siemens Corporation Method for quantitative resilience estimation of industrial control systems
US20110307467A1 (en) 2010-06-10 2011-12-15 Stephen Severance Distributed web crawler architecture
US9137024B2 (en) * 2010-06-23 2015-09-15 Apple System and method for incorporating an originating site into a security protocol for a downloaded program object
CA2803241C (en) 2010-07-01 2016-08-09 Mariano Nunez Di Croce Automated security assessment of business-critical systems and applications
US9152727B1 (en) 2010-08-23 2015-10-06 Experian Marketing Solutions, Inc. Systems and methods for processing consumer information for targeted marketing applications
US8707275B2 (en) 2010-09-14 2014-04-22 Microsoft Corporation Simulation environment for distributed programs
US8595240B1 (en) 2010-09-24 2013-11-26 Google Inc. Labeling objects by propagating scores in a graph
US9400962B2 (en) 2010-10-29 2016-07-26 Fujitsu Limited Architecture for distributed, parallel crawling of interactive client-server applications
US9515826B2 (en) 2010-11-18 2016-12-06 The Boeing Company Network topology aided by smart agent download
US9749197B2 (en) * 2010-12-02 2017-08-29 Verizon Patent And Licensing Inc. Mobile user data collection
AU2011343699B2 (en) 2010-12-15 2014-02-27 Shadow Networks, Inc. Network stimulation engine
US20180365302A1 (en) * 2011-01-20 2018-12-20 Peter Yurevich TABUN System for interactively searching for and displaying information on a webpage
US9171079B2 (en) 2011-01-28 2015-10-27 Cisco Technology, Inc. Searching sensor data
US20120215575A1 (en) 2011-02-22 2012-08-23 Bank Of America Corporation Risk Assessment And Prioritization Framework
US20160004858A1 (en) 2011-03-16 2016-01-07 J. Bradley Chen Security-Enhanced Web Application Module Translation
US8897900B2 (en) 2011-03-18 2014-11-25 Rockwell Automation Technologies, Inc. Graphical language for optimization and use
US8997233B2 (en) 2011-04-13 2015-03-31 Microsoft Technology Licensing, Llc Detecting script-based malware using emulation and heuristics
US8826426B1 (en) 2011-05-05 2014-09-02 Symantec Corporation Systems and methods for generating reputation-based ratings for uniform resource locators
US8209274B1 (en) 2011-05-09 2012-06-26 Google Inc. Predictive model importation
US8457996B2 (en) 2011-05-27 2013-06-04 Sap Ag Model-based business continuity management
US9438616B2 (en) 2011-06-01 2016-09-06 Hewlett Packard Enterprise Development Lp Network asset information management
US8813234B1 (en) 2011-06-29 2014-08-19 Emc Corporation Graph-based approach to deterring persistent security threats
US9015708B2 (en) 2011-07-28 2015-04-21 International Business Machines Corporation System for improving the performance of high performance computing applications on cloud using integrated load balancing
US20130036108A1 (en) * 2011-08-02 2013-02-07 Maxime Corbeau Method and system for assisting users with operating network devices
US9069725B2 (en) 2011-08-19 2015-06-30 Hartford Steam Boiler Inspection & Insurance Company Dynamic outlier bias reduction system and method
US20130060583A1 (en) 2011-09-02 2013-03-07 The Travelers Indemnity Company Systems and methods for insurance product pricing and safety program management
JP5761354B2 (en) 2011-09-08 2015-08-12 富士電機株式会社 Semiconductor device and manufacturing method of semiconductor device
EP2568395A1 (en) 2011-09-08 2013-03-13 Axel Springer Digital TV Guide GmbH Method and apparatus for automatic generation of recommendations
US9672355B2 (en) 2011-09-16 2017-06-06 Veracode, Inc. Automated behavioral and static analysis using an instrumented sandbox and machine learning classification for mobile security
AU2012338372A1 (en) 2011-09-19 2014-03-27 Tata Consultancy Services Limited A computing platform for development and deployment of sensor data based applications and services
US9256735B2 (en) 2011-10-10 2016-02-09 Masergy Communications, Inc. Detecting emergent behavior in communications networks
US8751867B2 (en) 2011-10-12 2014-06-10 Vmware, Inc. Method and apparatus for root cause and critical pattern prediction using virtual directed graphs
US8856936B2 (en) 2011-10-14 2014-10-07 Albeado Inc. Pervasive, domain and situational-aware, adaptive, automated, and coordinated analysis and control of enterprise-wide computers, networks, and applications for mitigation of business and operational risks and enhancement of cyber security
US9466041B2 (en) 2011-10-15 2016-10-11 Hewlett Packard Enterprise Development Lp User selected flow graph modification
US9686293B2 (en) 2011-11-03 2017-06-20 Cyphort Inc. Systems and methods for malware detection and mitigation
US20130159219A1 (en) 2011-12-14 2013-06-20 Microsoft Corporation Predicting the Likelihood of Digital Communication Responses
US9349103B2 (en) 2012-01-09 2016-05-24 DecisionQ Corporation Application of machine learned Bayesian networks to detection of anomalies in complex systems
US9129108B2 (en) 2012-01-31 2015-09-08 International Business Machines Corporation Systems, methods and computer programs providing impact mitigation of cyber-security failures
EP2812843A1 (en) 2012-02-09 2014-12-17 AOL Inc. Systems and methods for testing online systems and content
US8959494B2 (en) 2012-03-20 2015-02-17 Massively Parallel Technologies Inc. Parallelism from functional decomposition
AU2013272211B2 (en) 2012-03-22 2016-11-24 Los Alamos National Security, Llc Path scanning for the detection of anomalous subgraphs, anomaly/change detection and network situational awareness
US9639575B2 (en) 2012-03-30 2017-05-02 Khalifa University Of Science, Technology And Research Method and system for processing data queries
US9049207B2 (en) 2012-04-11 2015-06-02 Mcafee, Inc. Asset detection system
US8990392B1 (en) 2012-04-11 2015-03-24 NCC Group Inc. Assessing a computing resource for compliance with a computing resource policy regime specification
US9264395B1 (en) 2012-04-11 2016-02-16 Artemis Internet Inc. Discovery engine
US9286103B2 (en) 2012-04-21 2016-03-15 International Business Machines Corporation Method and apparatus for providing a test network as an IP accessible cloud service
US8726393B2 (en) 2012-04-23 2014-05-13 Abb Technology Ag Cyber security analyzer
US9338061B2 (en) 2012-04-26 2016-05-10 Hewlett Packard Enterprise Development Lp Open station as a stream analysis operator container
US8850588B2 (en) 2012-05-01 2014-09-30 Taasera, Inc. Systems and methods for providing mobile security based on dynamic attestation
US20170010589A1 (en) 2012-05-02 2017-01-12 Ether Dynamics Corporation Pseudo-genetic meta-knowledge artificial intelligence systems and methods
US9130971B2 (en) 2012-05-15 2015-09-08 Splunk, Inc. Site-based search affinity
US9672283B2 (en) 2012-06-06 2017-06-06 Data Record Science Structured and social data aggregator
US8819772B2 (en) 2012-06-25 2014-08-26 Appthority, Inc. In-line filtering of insecure or unwanted mobile device software components or communications
US9774616B2 (en) 2012-06-26 2017-09-26 Oppleo Security, Inc. Threat evaluation system and method
WO2014026220A1 (en) 2012-08-13 2014-02-20 Mts Consulting Pty Limited Analysis of time series data
US9461876B2 (en) 2012-08-29 2016-10-04 Loci System and method for fuzzy concept mapping, voting ontology crowd sourcing, and technology prediction
US9047181B2 (en) 2012-09-07 2015-06-02 Splunk Inc. Visualization of data from clusters
KR101402057B1 (en) 2012-09-19 2014-06-03 주식회사 이스트시큐리티 Analyzing system of repackage application through calculation of risk and method thereof
US9202040B2 (en) * 2012-10-10 2015-12-01 Globalfoundries Inc. Chip authentication using multi-domain intrinsic identifiers
US9235731B2 (en) 2012-10-16 2016-01-12 Truedata Systems, Inc. Trusted data relay
US9954884B2 (en) 2012-10-23 2018-04-24 Raytheon Company Method and device for simulating network resiliance against attacks
US20140149186A1 (en) 2012-11-29 2014-05-29 David Bernard Flaxer Method and system of using artifacts to identify elements of a component business model
CN104956373A (en) 2012-12-04 2015-09-30 惠普发展公司，有限责任合伙企业 Determining suspected root causes of anomalous network behavior
GB2511027A (en) 2012-12-04 2014-08-27 Anite Telecoms Ltd Apparatus and method for testing
US9734220B2 (en) 2012-12-04 2017-08-15 Planet Os Inc. Spatio-temporal data processing systems and methods
US9355385B2 (en) * 2012-12-06 2016-05-31 Microsoft Technology Licensing Location services in email and calendaring web services
US10074052B2 (en) 2013-01-16 2018-09-11 Tata Consultancy Services Limited System and method for smart public alerts and notifications
US9541982B2 (en) 2013-01-25 2017-01-10 Wisconsin Alumni Research Foundation Reconfigurable event driven hardware using reservoir computing for monitoring an electronic sensor and waking a processor
US20140279770A1 (en) 2013-03-15 2014-09-18 REMTCS Inc. Artificial neural network interface and methods of training the same for various use cases
US9674211B2 (en) 2013-01-30 2017-06-06 Skyhigh Networks, Inc. Cloud service usage risk assessment using darknet intelligence
US9185124B2 (en) 2013-02-27 2015-11-10 Sayan Chakraborty Cyber defense systems and methods
US20140244612A1 (en) 2013-02-28 2014-08-28 Linkedln Corporation Techniques for quantifying the intent and interests of members of a social networking service
US9558220B2 (en) 2013-03-04 2017-01-31 Fisher-Rosemount Systems, Inc. Big data in process control systems
US9674249B1 (en) 2013-03-11 2017-06-06 DataTorrent, Inc. Distributed streaming platform for real-time applications
US9262906B2 (en) 2013-03-14 2016-02-16 Comcast Cable Communications, Llc Processing sensor data
US10109014B1 (en) 2013-03-15 2018-10-23 Allstate Insurance Company Pre-calculated insurance premiums with wildcarding
US10275545B2 (en) 2013-03-15 2019-04-30 Ventana Systems, Inc. Modeling and simulation
US9721086B2 (en) 2013-03-15 2017-08-01 Advanced Elemental Technologies, Inc. Methods and systems for secure and reliable identity-based computing
US8949960B2 (en) 2013-03-15 2015-02-03 Google Inc. Privacy preserving knowledge and factor possession tests for persistent authentication
US9596141B2 (en) 2013-03-15 2017-03-14 Cisco Technology, Inc. Representing software defined networks using a programmable graph model
US10740358B2 (en) 2013-04-11 2020-08-11 Oracle International Corporation Knowledge-intensive data processing system
US9600792B2 (en) 2013-04-11 2017-03-21 Siemens Aktiengesellschaft Method and apparatus for generating an engineering workflow
GB201310007D0 (en) 2013-06-04 2013-07-17 Lyst Ltd Merchant system
US20150081363A1 (en) 2013-06-07 2015-03-19 TechCrowd Services, Inc. Group-Oriented Software Development
US9203827B2 (en) 2013-06-24 2015-12-01 Infosys Limited Methods for determining authentication requirements of information centric network based services and devices thereof
CN105519123B (en) 2013-06-28 2019-03-26 英特尔公司 The Media Stream of live crowdsourcing
US20160006629A1 (en) 2013-07-07 2016-01-07 George Ianakiev Appliance clearinghouse with orchestrated logic fusion and data fabric - architecture, system and method
US20150161738A1 (en) 2013-12-10 2015-06-11 Advanced Insurance Products & Services, Inc. Method of determining a risk score or insurance cost using risk-related decision-making processes and decision outcomes
US10284570B2 (en) 2013-07-24 2019-05-07 Wells Fargo Bank, National Association System and method to detect threats to computer based devices and systems
US8752178B2 (en) 2013-07-31 2014-06-10 Splunk Inc. Blacklisting and whitelisting of security-related events
US9300682B2 (en) 2013-08-09 2016-03-29 Lockheed Martin Corporation Composite analysis of executable content across enterprise network
US9276951B2 (en) 2013-08-23 2016-03-01 The Boeing Company System and method for discovering optimal network attack paths
US8806361B1 (en) 2013-09-16 2014-08-12 Splunk Inc. Multi-lane time-synched visualizations of machine data events
US9390376B2 (en) 2013-10-15 2016-07-12 Lockheed Martin Corporation Distributed machine learning intelligence development systems
US9262787B2 (en) 2013-10-18 2016-02-16 State Farm Mutual Automobile Insurance Company Assessing risk using vehicle environment information
US9374294B1 (en) 2013-11-05 2016-06-21 Cisco Technology, Inc. On-demand learning in overlay networks
WO2015070232A1 (en) 2013-11-11 2015-05-14 Amazon Technologies, Inc. Data stream ingestion and persistence techniques
US9858322B2 (en) 2013-11-11 2018-01-02 Amazon Technologies, Inc. Data stream ingestion and persistence techniques
US9231962B1 (en) 2013-11-12 2016-01-05 Emc Corporation Identifying suspicious user logins in enterprise networks
US10152676B1 (en) 2013-11-22 2018-12-11 Amazon Technologies, Inc. Distributed training of models using stochastic gradient descent
GB2520987B (en) 2013-12-06 2016-06-01 Cyberlytic Ltd Using fuzzy logic to assign a risk level profile to a potential cyber threat
US9753796B2 (en) 2013-12-06 2017-09-05 Lookout, Inc. Distributed monitoring, evaluation, and response for multiple devices
US9652538B2 (en) 2013-12-11 2017-05-16 Ebay Inc. Web crawler optimization system
US9369482B2 (en) 2013-12-12 2016-06-14 Tinfoil Security, Inc. Site independent system for deriving contextually tailored security vulnerability corrections for hardening solution stacks
US9134966B2 (en) 2013-12-12 2015-09-15 International Business Machines Corporation Management of mixed programming languages for a simulation environment
WO2015087333A1 (en) 2013-12-13 2015-06-18 Comilion Mobile Ltd. Collaborative system for cyber security analysis
US20150170053A1 (en) 2013-12-13 2015-06-18 Microsoft Corporation Personalized machine learning models
US10719562B2 (en) 2013-12-13 2020-07-21 BloomReach Inc. Distributed and fast data storage layer for large scale web data services
US9467461B2 (en) 2013-12-21 2016-10-11 Akamai Technologies Inc. Countering security threats with the domain name system
US10515366B1 (en) 2013-12-24 2019-12-24 EMC IP Holding Company LLC Network neighborhood topology as a predictor for fraud and anomaly detection
US9774522B2 (en) 2014-01-06 2017-09-26 Cisco Technology, Inc. Triggering reroutes using early learning machine-based prediction of failures
IN2014CH00466A (en) 2014-02-03 2015-08-07 Inmobi Pte Ltd
US20160012235A1 (en) 2014-02-10 2016-01-14 Vivo Security Inc. Analysis and display of cybersecurity risks for enterprise data
US9602513B2 (en) 2014-02-28 2017-03-21 Microsoft Technology Licensing, Llc Access control of edges in graph index applications
US9652604B1 (en) 2014-03-25 2017-05-16 Amazon Technologies, Inc. Authentication objects with delegation
WO2015145626A1 (en) 2014-03-26 2015-10-01 株式会社日立製作所 Time series data management method and time series data management system
US9602529B2 (en) 2014-04-02 2017-03-21 The Boeing Company Threat modeling and analysis
US9749344B2 (en) 2014-04-03 2017-08-29 Fireeye, Inc. System and method of cyber threat intensity determination and application to cyber threat mitigation
US9749343B2 (en) 2014-04-03 2017-08-29 Fireeye, Inc. System and method of cyber threat structure mapping and application to cyber threat mitigation
WO2015160830A1 (en) 2014-04-15 2015-10-22 Chemisense, Inc. Crowdsourced wearable sensor system
US20150295775A1 (en) 2014-04-15 2015-10-15 Splunk Inc. Graphical configuration of event streams for network data capture and processing
US9762443B2 (en) 2014-04-15 2017-09-12 Splunk Inc. Transformation of network data at remote capture agents
US10789367B2 (en) 2014-04-18 2020-09-29 Micro Focus Llc Pre-cognitive security information and event management
WO2015168203A1 (en) 2014-04-29 2015-11-05 PEGRight, Inc. Characterizing user behavior via intelligent identity analytics
US9911088B2 (en) 2014-05-01 2018-03-06 Microsoft Technology Licensing, Llc Optimizing task recommendations in context-aware mobile crowdsourcing
IL232528A0 (en) 2014-05-08 2014-08-31 Rami Puzis Social network honeypot
US11334831B2 (en) 2014-05-21 2022-05-17 X-Act Science, Inc. Predictive risk assessment in system modeling
US9503467B2 (en) 2014-05-22 2016-11-22 Accenture Global Services Limited Network anomaly detection
US20150347414A1 (en) 2014-05-30 2015-12-03 Linkedln Corporation New heuristic for optimizing non-convex function for learning to rank
WO2015184467A1 (en) 2014-05-30 2015-12-03 Reylabs Inc. Systems and methods involving mobile linear asset efficiency exploration, monitoring and/or display aspects
WO2015187768A1 (en) 2014-06-03 2015-12-10 The Security Oracle, Inc Defense and denial method
US9319430B2 (en) 2014-06-17 2016-04-19 International Business Machines Corporation Managing software deployment
US10212176B2 (en) 2014-06-23 2019-02-19 Hewlett Packard Enterprise Development Lp Entity group behavior profiling
US10469514B2 (en) * 2014-06-23 2019-11-05 Hewlett Packard Enterprise Development Lp Collaborative and adaptive threat intelligence for computer security
US20150379111A1 (en) 2014-06-26 2015-12-31 Vivint, Inc. Crowdsourcing automation sensor data
US10318882B2 (en) 2014-09-11 2019-06-11 Amazon Technologies, Inc. Optimized training of linear machine learning models
US10102480B2 (en) 2014-06-30 2018-10-16 Amazon Technologies, Inc. Machine learning service
US9565204B2 (en) 2014-07-18 2017-02-07 Empow Cyber Security Ltd. Cyber-security system and methods thereof
DE112015003406B4 (en) 2014-07-24 2022-05-25 Ab Initio Technology Llc Lineage Summation
US9930058B2 (en) 2014-08-13 2018-03-27 Honeywell International Inc. Analyzing cyber-security risks in an industrial control environment
US20160057159A1 (en) 2014-08-22 2016-02-25 Syracuse University Semantics-aware android malware classification
US9729538B2 (en) 2014-09-01 2017-08-08 Microsoft Israel Research And Development (2002) Ltd System, method and process for detecting advanced and targeted attacks with the recoupling of kerberos authentication and authorization
US10162969B2 (en) 2014-09-10 2018-12-25 Honeywell International Inc. Dynamic quantification of cyber-security risks in a control system
US9965627B2 (en) 2014-09-14 2018-05-08 Sophos Limited Labeling objects on an endpoint for encryption management
US10965711B2 (en) 2014-09-14 2021-03-30 Sophos Limited Data behavioral tracking
US9967282B2 (en) 2014-09-14 2018-05-08 Sophos Limited Labeling computing objects for improved threat detection
US9992228B2 (en) 2014-09-14 2018-06-05 Sophos Limited Using indications of compromise for reputation based network security
US9967283B2 (en) 2014-09-14 2018-05-08 Sophos Limited Normalized indications of compromise
US10122687B2 (en) 2014-09-14 2018-11-06 Sophos Limited Firewall techniques for colored objects on endpoints
US9967264B2 (en) 2014-09-14 2018-05-08 Sophos Limited Threat detection using a time-based cache of reputation information on an enterprise endpoint
US9591006B2 (en) 2014-09-18 2017-03-07 Microsoft Technology Licensing, Llc Lateral movement detection
US10120907B2 (en) 2014-09-24 2018-11-06 Oracle International Corporation Scaling event processing using distributed flows and map-reduce operations
US10210246B2 (en) 2014-09-26 2019-02-19 Oracle International Corporation Techniques for similarity analysis and data enrichment using knowledge sources
US9882929B1 (en) 2014-09-30 2018-01-30 Palo Alto Networks, Inc. Dynamic selection and generation of a virtual clone for detonation of suspicious content within a honey network
US9860208B1 (en) 2014-09-30 2018-01-02 Palo Alto Networks, Inc. Bridging a virtual clone of a target device in a honey network to a suspicious device in an enterprise network
US10044675B1 (en) 2014-09-30 2018-08-07 Palo Alto Networks, Inc. Integrating a honey network with a target network to counter IP and peer-checking evasion techniques
US9495188B1 (en) 2014-09-30 2016-11-15 Palo Alto Networks, Inc. Synchronizing a honey network configuration to reflect a target network environment
US9781144B1 (en) * 2014-09-30 2017-10-03 Fireeye, Inc. Determining duplicate objects for malware analysis using environmental/context information
US20160099960A1 (en) 2014-10-01 2016-04-07 Infocyte, Inc. System and method for scanning hosts using an autonomous, self-destructing payload
US10168691B2 (en) 2014-10-06 2019-01-01 Fisher-Rosemount Systems, Inc. Data pipeline for process control system analytics
US9952899B2 (en) 2014-10-09 2018-04-24 Google Llc Automatically generating execution sequences for workflows
US9736173B2 (en) 2014-10-10 2017-08-15 Nec Corporation Differential dependency tracking for attack forensics
US20160119365A1 (en) 2014-10-28 2016-04-28 Comsec Consulting Ltd. System and method for a cyber intelligence hub
CA2966408C (en) 2014-10-31 2019-11-05 Cyber Crucible Inc. A system and method for network intrusion detection of covert channels based on off-line network traffic
US9887933B2 (en) 2014-10-31 2018-02-06 The Nielsen Company (Us), Llc Method and apparatus to throttle media access by web crawlers
US10050985B2 (en) 2014-11-03 2018-08-14 Vectra Networks, Inc. System for implementing threat detection using threat and risk assessment of asset-actor interactions
US10055473B2 (en) 2014-11-07 2018-08-21 Core-Apps, Llc Systems for allowing annotation in real time
US9571517B2 (en) 2014-11-11 2017-02-14 Goldman, Sachs & Co. Synthetic cyber-risk model for vulnerability determination
US10078664B2 (en) 2014-12-05 2018-09-18 General Electric Company Searching for and finding data across industrial time series data
US9210185B1 (en) 2014-12-05 2015-12-08 Lookingglass Cyber Solutions, Inc. Cyber threat monitor and control apparatuses, methods and systems
US20160171415A1 (en) 2014-12-13 2016-06-16 Security Scorecard Cybersecurity risk assessment on an industry basis
US20160180240A1 (en) 2014-12-16 2016-06-23 Kyndi, Inc. Apparatus and method for high performance data analysis
US9100430B1 (en) 2014-12-29 2015-08-04 Palantir Technologies Inc. Systems for network risk assessment including processing of user access rights associated with a network of devices
US9292699B1 (en) 2014-12-30 2016-03-22 Airwatch Llc Encrypted file storage
US10291653B2 (en) 2015-01-16 2019-05-14 Sri International Visually intuitive interactive network management
US20160219066A1 (en) 2015-01-26 2016-07-28 Cisco Technology, Inc. Event correlation in a network merging local graph models from distributed nodes
US20180268264A1 (en) 2015-01-28 2018-09-20 Hewlett Packard Enterprise Development Lp Detecting anomalous sensor data
WO2016122638A1 (en) 2015-01-30 2016-08-04 Hewlett Packard Enterprise Development Lp Collaborative security lists
US9336481B1 (en) 2015-02-02 2016-05-10 James Albert Ionson Organically instinct-driven simulation system and method
US9535527B2 (en) 2015-02-18 2017-01-03 Blackberry Limited Portable electronic device including touch-sensitive display and method of controlling selection of information
US10511498B1 (en) 2015-02-25 2019-12-17 Infoblox Inc. Monitoring and analysis of interactions between network endpoints
US9729421B2 (en) 2015-03-25 2017-08-08 International Business Machines Corporation Outcome-based software-defined infrastructure
US9712553B2 (en) 2015-03-27 2017-07-18 The Boeing Company System and method for developing a cyber-attack scenario
US9667600B2 (en) 2015-04-06 2017-05-30 At&T Intellectual Property I, L.P. Decentralized and distributed secure home subscriber server device
US10546001B1 (en) * 2015-04-15 2020-01-28 Arimo, LLC Natural language queries based on user defined attributes
US10289841B2 (en) 2015-04-16 2019-05-14 Nec Corporation Graph-based attack chain discovery in enterprise security systems
US10298607B2 (en) 2015-04-16 2019-05-21 Nec Corporation Constructing graph models of event correlation in enterprise security systems
CN106156578B (en) * 2015-04-22 2020-02-14 深圳市腾讯计算机系统有限公司 Identity verification method and device
EP3258374B1 (en) 2015-05-07 2019-10-09 CyberArk Software Ltd. Systems and methods for detecting and reacting to malicious activity in computer networks
US10154049B2 (en) 2015-05-13 2018-12-11 Preempt Security, Inc. System and method for providing an in-line sniffer mode network based identity centric firewall
US10452664B2 (en) 2015-05-21 2019-10-22 Oracle International Corporation Declarative MapReduce using regular expressions
WO2016190868A1 (en) 2015-05-28 2016-12-01 Hewlett Packard Enterprise Development Lp Processing network data using a graph data structure
US10083236B2 (en) 2015-05-29 2018-09-25 Salesforce.Com, Inc. Database searching using a graph of nodes and edges formed using log node pairs
US10643144B2 (en) 2015-06-05 2020-05-05 Facebook, Inc. Machine learning system flow authoring tool
CA3128629A1 (en) 2015-06-05 2016-07-28 C3.Ai, Inc. Systems and methods for data processing and enterprise ai applications
AU2016276475A1 (en) 2015-06-09 2017-11-30 Satori Worldwide, Llc Distributed scalable workload testing
US10108907B2 (en) 2015-07-17 2018-10-23 Knoema Corporation Method and system to provide related data
US9756067B2 (en) 2015-08-10 2017-09-05 Accenture Global Services Limited Network security
US10185832B2 (en) 2015-08-12 2019-01-22 The United States Of America As Represented By The Secretary Of The Army Methods and systems for defending cyber attack in real-time
US9699205B2 (en) 2015-08-31 2017-07-04 Splunk Inc. Network security system
US10148679B2 (en) 2015-12-09 2018-12-04 Accenture Global Solutions Limited Connected security system
US9772934B2 (en) * 2015-09-14 2017-09-26 Palantir Technologies Inc. Pluggable fault detection tests for data pipelines
US10191768B2 (en) 2015-09-16 2019-01-29 Salesforce.Com, Inc. Providing strong ordering in multi-stage streaming processing
US10324773B2 (en) 2015-09-17 2019-06-18 Salesforce.Com, Inc. Processing events generated by internet of things (IoT)
US9842000B2 (en) 2015-09-18 2017-12-12 Salesforce.Com, Inc. Managing processing of long tail task sequences in a stream processing framework
US10146592B2 (en) 2015-09-18 2018-12-04 Salesforce.Com, Inc. Managing resource allocation in a stream processing framework
US10440054B2 (en) 2015-09-25 2019-10-08 Perspecta Labs Inc. Customized information networks for deception and attack mitigation
WO2017059014A1 (en) 2015-09-29 2017-04-06 Skytree, Inc. Interoperability of transforms under a unified platform and extensible transformation library of those interoperable transforms
US9967265B1 (en) 2015-09-29 2018-05-08 EMC IP Holding Company LLC Detecting malicious online activities using event stream processing over a graph database
US10320828B1 (en) 2015-09-30 2019-06-11 EMC IP Holding Company LLC Evaluation of security in a cyber simulator
US9771225B2 (en) 2015-10-08 2017-09-26 Rite-Hite Holding Corporation Methods and apparatus for monitoring a loading dock
US11539663B2 (en) 2015-10-28 2022-12-27 Qomplx, Inc. System and method for midserver facilitation of long-haul transport of telemetry for cloud-based services
US10380140B2 (en) 2015-11-30 2019-08-13 Tableau Software, Inc. Systems and methods for implementing a virtual machine for interactive visual analysis
US10410113B2 (en) 2016-01-14 2019-09-10 Preferred Networks, Inc. Time series data adaptation and sensor fusion systems, methods, and apparatus
US10318739B2 (en) 2016-01-19 2019-06-11 Sap Se Computing optimal fix locations for security vulnerabilities in computer-readable code
US20170241791A1 (en) 2016-02-24 2017-08-24 Allstate Insurance Company Risk Maps
US10764321B2 (en) 2016-03-24 2020-09-01 Lenovo Enterprise Solutions (Singapore) Pte. Ltd Identifying and remediating at-risk resources in a computing environment
US9928366B2 (en) 2016-04-15 2018-03-27 Sophos Limited Endpoint malware detection using an event graph
US9807104B1 (en) 2016-04-29 2017-10-31 STEALTHbits Technologies, Inc. Systems and methods for detecting and blocking malicious network activity
WO2017193140A1 (en) 2016-05-06 2017-11-09 Enterpriseweb Llc Systems and methods for domain-driven design and execution of modular and dynamic services, applications and processes
US10985997B2 (en) 2016-05-06 2021-04-20 Enterpriseweb Llc Systems and methods for domain-driven design and execution of metamodels
US10515062B2 (en) 2016-05-09 2019-12-24 Sumo Logic, Inc. Searchable investigation history for event data store
US10783535B2 (en) 2016-05-16 2020-09-22 Cerebri AI Inc. Business artificial intelligence management engine
US10958667B1 (en) 2016-06-03 2021-03-23 Mcafee Llc Determining computing system incidents using node graphs
KR101680525B1 (en) * 2016-07-12 2016-12-06 김주한 app forgery detection, 2-channel certification agency system and method thereof
WO2018013244A1 (en) 2016-07-14 2018-01-18 IronNet Cybersecurity, Inc. Simulation and virtual reality based cyber behavioral systems
US10540624B2 (en) 2016-07-20 2020-01-21 International Business Machines Corporation System and method to automate provenance-aware application execution
US10650141B2 (en) 2016-08-03 2020-05-12 Sophos Limited Mitigation of return-oriented programming attacks
EP3282668B1 (en) 2016-08-12 2020-10-21 Tata Consultancy Services Limited Comprehensive risk assessment in a heterogeneous dynamic network
EP3291120B1 (en) 2016-09-06 2021-04-21 Accenture Global Solutions Limited Graph database analysis for network anomaly detection systems
US10776847B1 (en) 2016-09-20 2020-09-15 Amazon Technologies, Inc. Modeling user intent
US10673880B1 (en) 2016-09-26 2020-06-02 Splunk Inc. Anomaly detection to identify security threats
WO2018064765A1 (en) 2016-10-03 2018-04-12 Bioconnect Inc. Biometric identification platform
US10212184B2 (en) 2016-10-27 2019-02-19 Opaq Networks, Inc. Method for the continuous calculation of a cyber security risk index
US10645100B1 (en) 2016-11-21 2020-05-05 Alert Logic, Inc. Systems and methods for attacker temporal behavior fingerprinting and grouping with spectrum interpretation and deep learning
US11392875B2 (en) 2016-12-06 2022-07-19 Refinitiv Us Organization Llc Risk identification engine and supply chain graph generator
US10261763B2 (en) 2016-12-13 2019-04-16 Palantir Technologies Inc. Extensible data transformation authoring and validation system
US10977551B2 (en) 2016-12-14 2021-04-13 Microsoft Technology Licensing, Llc Hybrid reward architecture for reinforcement learning
US10277629B1 (en) 2016-12-20 2019-04-30 Symantec Corporation Systems and methods for creating a deception computing system
US10645086B1 (en) 2016-12-30 2020-05-05 Charles Schwab & Co., Inc. System and method for handling user requests for web services
US10205735B2 (en) 2017-01-30 2019-02-12 Splunk Inc. Graph-based network security threat detection across time and entities
CA3053531A1 (en) 2017-02-17 2018-08-23 Kyndi, Inc. Method and apparatus of machine learning using a network with software agents at the network nodes and then ranking network nodes
US10791136B2 (en) 2017-03-20 2020-09-29 Fair Isaac Corporation System and method for empirical organizational cybersecurity risk assessment using externally-visible data
US11138514B2 (en) 2017-03-23 2021-10-05 Futurewei Technologies, Inc. Review machine learning system
US10862916B2 (en) 2017-04-03 2020-12-08 Netskope, Inc. Simulation and visualization of malware spread in a cloud-based collaboration environment
US10290141B2 (en) 2017-04-17 2019-05-14 Intel Corporation Cloud based distributed single game calculation of shared computational work for multiple cloud gaming client devices
US10122764B1 (en) 2017-04-25 2018-11-06 T-Mobile Usa, Inc. Multi-factor and context sensitive biometric authentication system
US11032307B2 (en) 2017-04-30 2021-06-08 Splunk Inc. User interface for defining custom threat rules in a network security system
EP3407288A1 (en) 2017-05-22 2018-11-28 Fujitsu Limited Apparatus and method for generation of a financial event database
US10992698B2 (en) 2017-06-05 2021-04-27 Meditechsafe, Inc. Device vulnerability management
US11030520B2 (en) 2017-06-06 2021-06-08 Ca, Inc. Distributed secure training of neural network model
US10505954B2 (en) 2017-06-14 2019-12-10 Microsoft Technology Licensing, Llc Detecting malicious lateral movement across a computer network
US9978067B1 (en) 2017-07-17 2018-05-22 Sift Science, Inc. System and methods for dynamic digital threat mitigation
US10321278B2 (en) 2017-09-12 2019-06-11 Motorola Solutions, Inc. Method and device for responding to a query
EP3457274A1 (en) 2017-09-16 2019-03-20 Tata Consultancy Services Limited System and method for creating domain specific language
US10579691B2 (en) 2017-09-27 2020-03-03 Salesforce.Com, Inc. Application programming interface representation of multi-tenant non-relational platform objects
US10338913B2 (en) 2017-12-05 2019-07-02 Archemy, Inc. Active adaptation of networked compute devices using vetted reusable software components
US11068991B2 (en) 2017-12-18 2021-07-20 Hartford Fire Insurance Company Closed-loop system incorporating risk analytic algorithm
GB201804904D0 (en) 2018-03-27 2018-05-09 Palantir Technologies Inc Code correction
EP3867722A4 (en) 2018-10-17 2022-08-03 Cognata Ltd. System and method for generating realistic simulation data for training an autonomous driver
US11277432B2 (en) 2018-12-03 2022-03-15 Accenture Global Solutions Limited Generating attack graphs in agile security platforms
US11113667B1 (en) 2018-12-18 2021-09-07 Asana, Inc. Systems and methods for providing a dashboard for a collaboration work management platform
US10438001B1 (en) 2018-12-31 2019-10-08 Arceo Labs Inc. Identification, prediction, and assessment of cyber security risk
US10462112B1 (en) 2019-01-09 2019-10-29 Cyberark Software Ltd. Secure distributed authentication data
US11736299B2 (en) 2019-01-18 2023-08-22 Prometheus8 Data access control for edge devices using a cryptographic hash
US11438361B2 (en) 2019-03-22 2022-09-06 Hitachi, Ltd. Method and system for predicting an attack path in a computer network
US20200364346A1 (en) 2019-05-08 2020-11-19 Battelle Memorial Institute Secure design and development: intertwined management and technological security assessment framework
US11397805B2 (en) 2019-05-09 2022-07-26 Microsoft Technology Licensing, Llc Lateral movement path detector
TWI717831B (en) 2019-09-11 2021-02-01 財團法人資訊工業策進會 Attack path detection method, attack path detection system and non-transitory computer-readable medium
US11477641B2 (en) 2019-09-30 2022-10-18 Microsoft Technology Licensing, Llc System and method for authentication session transfer using application download links

Patent Citations (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6256544B1 (en) 1996-08-13 2001-07-03 Duerr Systems Gmbh Apparatus and method for controlling functional units in a manufacturing installation
US20030041254A1 (en) * 2001-08-24 2003-02-27 International Business Machines Corporation Securing sensitive configuration data remotely
US7281125B2 (en) 2001-08-24 2007-10-09 Lenovo (Singapore) Pte. Ltd. Securing sensitive configuration data remotely
US20030145225A1 (en) 2002-01-28 2003-07-31 International Business Machines Corporation Intrusion event filtering and generic attack signatures
US20160072845A1 (en) 2003-12-30 2016-03-10 Entrust, Inc. Method and apparatus for providing authentication using policy-controlled authentication articles and techniques
US20070036314A1 (en) * 2005-07-20 2007-02-15 Kloberdans Michael J Telephony extension attack detection, recording, and intelligent prevention
US7702821B2 (en) 2005-09-15 2010-04-20 Eye-Fi, Inc. Content-aware digital media storage device and methods of using the same
US20070136821A1 (en) * 2005-12-13 2007-06-14 Interdigital Technology Corporation Method and system for protecting user data in a node
US20070150744A1 (en) * 2005-12-22 2007-06-28 Cheng Siu L Dual authentications utilizing secure token chains
US20080021866A1 (en) 2006-07-20 2008-01-24 Heather M Hinton Method and system for implementing a floating identity provider model across data centers
US20090182672A1 (en) * 2008-01-11 2009-07-16 Doyle Paul F System and Method for Financial Transaction Validation
US10410214B2 (en) 2008-01-11 2019-09-10 Deluxe Small Business Sales, Inc. System and method for financial transaction validation
US9253643B2 (en) 2009-03-05 2016-02-02 Interdigital Patent Holdings, Inc. Method and apparatus for H(e)NB integrity verification and validation
US20110087888A1 (en) 2009-10-13 2011-04-14 Google Inc. Authentication using a weak hash of user credentials
US20130117831A1 (en) 2010-04-30 2013-05-09 Lock Box Pty Ltd Method and system for enabling computer access
US8601554B2 (en) 2011-11-09 2013-12-03 Microsoft Corporation Home realm discovery in mixed-mode federated realms
US20150128258A1 (en) 2012-04-11 2015-05-07 Utc Fire & Security Corporation Authentication mode reporting
WO2014159150A1 (en) 2013-03-14 2014-10-02 Microsoft Corporation Software release workflow management
US10628578B2 (en) 2013-03-15 2020-04-21 Imagine Communications Corp. Systems and methods for determining trust levels for computing components using blockchain
US20150281225A1 (en) * 2014-03-27 2015-10-01 Microsoft Corporation Techniques to operate a service with machine generated authentication tokens
US9602530B2 (en) 2014-03-28 2017-03-21 Zitovault, Inc. System and method for predicting impending cyber security events using multi channel behavioral analysis in a distributed computing environment
US9292692B2 (en) 2014-05-05 2016-03-22 Sypris Electronics, Llc System and device for verifying the integrity of a system from its subcomponents
US20150317481A1 (en) * 2014-05-05 2015-11-05 Sypris Electronics, Llc System and device for verifying the integrity of a system from its subcomponents
US20160275123A1 (en) 2015-03-18 2016-09-22 Hitachi, Ltd. Pipeline execution of multiple map-reduce jobs
US10038559B2 (en) 2015-10-02 2018-07-31 Google Llc Signatures of updates exchanged in a binary data synchronization protocol
US10248910B2 (en) 2015-10-28 2019-04-02 Fractal Industries, Inc. Detection mitigation and remediation of cyberattacks employing an advanced cyber-decision platform
WO2017075543A1 (en) 2015-10-28 2017-05-04 Fractal Industries, Inc. Rapid predictive analysis of very large data sets using the distributed computational graph
US11005824B2 (en) * 2015-10-28 2021-05-11 Qomplx, Inc. Detecting and mitigating forged authentication object attacks using an advanced cyber decision platform
US20210297443A1 (en) * 2015-10-28 2021-09-23 Qomplx, Inc. Detecting and mitigating golden ticket attacks within a domain
US10061635B2 (en) 2015-11-13 2018-08-28 Kriwan Industrie-Elektronik Gmbh Cyber physical system
US10367829B2 (en) 2015-11-19 2019-07-30 Anomali Incorporated Protecting threat indicators from third party abuse

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20240048586A1 (en) * 2015-10-28 2024-02-08 Qomplx Llc Detecting kerberos ticket attacks within a domain
US20230118388A1 (en) * 2015-10-28 2023-04-20 Qomplx, Inc. Detecting and mitigating golden ticket attacks within a domain
US11757849B2 (en) * 2015-10-28 2023-09-12 Qomplx, Inc. Detecting and mitigating forged authentication object attacks in multi-cloud environments
US20230308459A1 (en) * 2015-10-28 2023-09-28 Qomplx, Inc. Authentication attack detection and mitigation with embedded authentication and delegation
US20230319019A1 (en) * 2015-10-28 2023-10-05 Qomplx, Inc. Detecting and mitigating forged authentication attacks using an advanced cyber decision platform
US11799900B2 (en) * 2015-10-28 2023-10-24 Qomplx, Inc. Detecting and mitigating golden ticket attacks within a domain
US20220060453A1 (en) * 2015-10-28 2022-02-24 Qomplx, Inc. Detecting and mitigating forged authentication object attacks in multi - cloud environments
US11968227B2 (en) * 2015-10-28 2024-04-23 Qomplx Llc Detecting KERBEROS ticket attacks within a domain
US20220166792A1 (en) * 2018-10-31 2022-05-26 SpyCloud, Inc. Detecting use of compromised security credentials in private enterprise networks
US11750645B2 (en) * 2018-10-31 2023-09-05 SpyCloud, Inc. Detecting use of compromised security credentials in private enterprise networks
US12166794B2 (en) * 2018-10-31 2024-12-10 SpyCloud, Inc. Detecting use of compromised security credentials in private enterprise networks
US11838300B1 (en) * 2019-12-24 2023-12-05 Musarubra Us Llc Run-time configurable cybersecurity system
US12199995B2 (en) * 2022-09-23 2025-01-14 Zhejiang Gongshang University System and method for authentication code generation based on adversarial machine learning

Also Published As

Publication number Publication date
US20240080338A1 (en) 2024-03-07
US11818169B2 (en) 2023-11-14
US20240195833A1 (en) 2024-06-13
US20210297447A1 (en) 2021-09-23
US20230123314A1 (en) 2023-04-20
US20240314162A1 (en) 2024-09-19
US20240396936A1 (en) 2024-11-28
US12155693B1 (en) 2024-11-26
US12003534B2 (en) 2024-06-04

Similar Documents

Publication Publication Date Title
US11818169B2 (en) Detecting and mitigating attacks using forged authentication objects within a domain
US11968227B2 (en) Detecting KERBEROS ticket attacks within a domain
US11582207B2 (en) Detecting and mitigating forged authentication object attacks using an advanced cyber decision platform
US12225042B2 (en) System and method for user and entity behavioral analysis using network topology information
US11818150B2 (en) System and methods for detecting and mitigating golden SAML attacks against federated services
US11757920B2 (en) User and entity behavioral analysis with network topology enhancements
US11757849B2 (en) Detecting and mitigating forged authentication object attacks in multi-cloud environments
US11323471B2 (en) Advanced cybersecurity threat mitigation using cyberphysical graphs with state changes
US10594714B2 (en) User and entity behavioral analysis using an advanced cyber decision platform
US10609079B2 (en) Application of advanced cybersecurity threat mitigation to rogue devices, privilege escalation, and risk-based vulnerability and patch management
US10432660B2 (en) Advanced cybersecurity threat mitigation for inter-bank financial transactions
US20230388278A1 (en) Detecting and mitigating forged authentication object attacks in multi - cloud environments with attestation
US20230319019A1 (en) Detecting and mitigating forged authentication attacks using an advanced cyber decision platform
US20230308459A1 (en) Authentication attack detection and mitigation with embedded authentication and delegation
US20240244068A1 (en) System and methods for detecting authentication object forgery or manipulation attacks
WO2019113492A1 (en) Detecting and mitigating forged authentication object attacks using an advanced cyber decision platform

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

AS Assignment

Owner name: QOMPLX, INC., VIRGINIA

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:SELLERS, ANDREW;CRABTREE, JASON;REEL/FRAME:055241/0339

Effective date: 20210211

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: SMAL); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: DOCKETED NEW CASE - READY FOR EXAMINATION

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STPP Information on status: patent application and granting procedure in general

Free format text: PUBLICATIONS -- ISSUE FEE PAYMENT VERIFIED

STCF Information on status: patent grant

Free format text: PATENTED CASE

AS Assignment

Owner name: QPX, LLC., NEW YORK

Free format text: PATENT ASSIGNMENT AGREEMENT TO ASSET PURCHASE AGREEMENT;ASSIGNOR:QOMPLX, INC.;REEL/FRAME:064674/0407

Effective date: 20230810

AS Assignment

Owner name: QPX LLC, NEW YORK

Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE RECEIVING PARTY PREVIOUSLY RECORDED AT REEL: 064674 FRAME: 0408. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:QOMPLX, INC.;REEL/FRAME:064966/0863

Effective date: 20230810

AS Assignment

Owner name: QOMPLX LLC, NEW YORK

Free format text: CHANGE OF NAME;ASSIGNOR:QPX LLC;REEL/FRAME:065036/0449

Effective date: 20230824

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

AS Assignment

Owner name: QOMPLX LLC, VIRGINIA

Free format text: CHANGE OF ADDRESS;ASSIGNOR:QOMPLX LLC;REEL/FRAME:069083/0279

Effective date: 20241001