Patent Description:
To implement defense in depth, cybersecurity professionals consider the different kinds of attacks that could be made. They select defenses based on criteria such as: which attacks are most likely to occur, which attacks are most likely to succeed, which attacks are most harmful if successful, which defenses are in place, which defenses could be put in place, and the costs and procedural changes and training involved in putting a particular defense in place.

In particular, installing tools and techniques for detecting and limiting identity attacks is one of the many possibilities to consider when implementing defense in depth. Some examples of identity attacks include "password spray" attacks in which an attacker tests a given password against multiple accounts. If none of the accounts accept the first password tried, then a second password may be sprayed or stuffed, i.e., tested against multiple accounts. In a "credential stuffing" identity attack, an attacker tries to access a website B using credentials from a breached website A. In general, an identity attack continues until it is detected and shut down, or until the attacker succeeds in gaining illicit access to one or more desired accounts and moves on to the next phase of the attack, such as installing malware, exfiltrating data, or encrypting data to hold it for ransom. <CIT> relates to a system for identifying a brute force attack on an account. During a log in attempt, a username and the corresponding password are obtained and it is determined whether the password satisfies a preset password strength range. If the acquired password does not pass the password strength check, it is determined whether the number of consecutive failed password strength checks reaches a preset value during the process of determining that the terminal requesting to log in to the current system uses the acquired username to log in to the current system. If the preset value is reached, it is determined that the terminal requesting to log in to the system is a brute force cracking terminal. After it is determined that the terminal is a brute force cracking terminal, if the terminal requests to log in to the current system again, a password strength check is not required, and the login failure prompt information is directly returned. <CIT> discloses a detection method aiming at brute force cracking, which comprises the following steps: acquiring a log of each account in a client; determining historical trial passwords of all accounts according to the login logs; respectively matching and searching the historical trial passwords of each account in a blasting dictionary; historical trial passwords which are tried to log in different account numbers and are all failed to log in are recorded in the blasting dictionary; judging whether the historical trial password of the account meets a preset condition or not according to the matching search result, wherein the preset condition comprises that the ratio of the historical trial password of the account matched and searched in the blasting dictionary exceeds a preset ratio upper limit; and if so, judging that the account is attacked by brute force cracking.

The object of the invention is to enhance identity attack detection.

Some embodiments described in this document provide improved technology for detecting the likely presence of attacker activity in a monitored computer network. In particular, some embodiments detect identity attacks based on the use of compromised or otherwise weak passphrases in failed sign-in attempts. These embodiments look beyond the mere number of failed sign-ins by automatically noting what kind of passwords, usernames, and other credentials were used in the failed sign-in attempts. A relatively high percentage of weak credentials in failed sign-ins is treated as an indicator of an identity attack.

Some embodiments use or provide an attack detection hardware and software combination which is configured for automatic detection of an identity attack and for initiating an automatic defense against the identity attack.

Other technical activities and characteristics pertinent to teachings herein will also become apparent to those of skill in the art. The examples given are merely illustrative. Rather, this Summary is provided to introduce - in a simplified form - some technical concepts that are further described below in the Detailed Description. The innovation is defined with claims as properly understood, and to the extent this Summary conflicts with the claims, the claims should prevail.

A more particular description will be given with reference to the attached drawings. These drawings only illustrate selected aspects and thus do not fully determine coverage or scope.

Innovations may expand beyond their origins, but understanding an innovation's origins can help one more fully appreciate the innovation. In the present case, some teachings described herein were motivated by technical challenges faced by Microsoft innovators who were working to improve the usability of Microsoft cybersecurity offerings.

In particular, a technical challenge was to how to automatically and efficiently detect identity attacks against accounts in a cloud or other computer network. Even more particularly, the innovators faced the technical challenge of detecting identity attacks which take a "low and slow" approach that avoids triggering less innovative mechanisms. Such mechanisms may perform account lockout after a specified number of login failures, or they may block an IP address from which a specified number of login failures originated, or they may do both.

Some embodiments taught herein go beyond an approach which relies merely on the number of failed sign-ins to trigger account lockout or IP blocking. Instead, these embodiments automatically note the weakness or strength of passwords, usernames, and other credentials that were used in the failed sign-in attempts. When a relatively high percentage (e.g., a majority, or another specified threshold) of simple passwords, compromised passwords, wrong usernames, expired authentication tokens or certificates, or other weak credentials are being used in failed sign-ins, the embodiment initiates or even imposes defensive measures against an identity attack.

Defensive measures may include locking an account even before the published lockout level of failed sign-ins has been reached, or blocking an IP address from further communication with accounts even before an established IP blocking level of failed sign-ins has been reached, for example. Other defensive measures may require additional authentication for account access, e.g., require multifactor authentication, or notify administrators, or otherwise restrict access. Multiple defensive measures may also be initiated or imposed.

Other aspects of these embodiments, and other identity attack detection enhancement embodiments, are also described herein.

With reference to <FIG>, an operating environment <NUM> for an embodiment includes at least one computer system <NUM>. The computer system <NUM> may be a multiprocessor computer system, or not. An operating environment may include one or more machines in a given computer system, which may be clustered, client-server networked, and/or peer-to-peer networked within a cloud. An individual machine is a computer system, and a network or other group of cooperating machines is also a computer system. A given computer system <NUM> may be configured for end-users, e.g., with applications, for administrators, as a server, as a distributed processing node, and/or in other ways.

Human users <NUM> may interact with the computer system <NUM> by using displays, keyboards, and other peripherals <NUM>, via typed text, touch, voice, movement, computer vision, gestures, and/or other forms of I/O. A screen <NUM> may be a removable peripheral <NUM> or may be an integral part of the system <NUM>. A user interface may support interaction between an embodiment and one or more human users. A user interface may include a command line interface, a graphical user interface (GUI), natural user interface (NUI), voice command interface, and/or other user interface (UI) presentations, which may be presented as distinct options or may be integrated.

System administrators, network administrators, cloud administrators, security analysts and other security personnel, operations personnel, developers, testers, engineers, auditors, and end-users are each a particular type of user <NUM>. Automated agents, scripts, playback software, devices, and the like acting on behalf of one or more people may also be users <NUM>, e.g., to facilitate testing a system <NUM>. Storage devices and/or networking devices may be considered peripheral equipment in some embodiments and part of a system <NUM> in other embodiments, depending on their detachability from the processor <NUM>. Other computer systems not shown in <FIG> may interact in technological ways with the computer system <NUM> or with another system embodiment using one or more connections to a network <NUM> via network interface equipment, for example.

Each computer system <NUM> includes at least one processor <NUM>. The computer system <NUM>, like other suitable systems, also includes one or more computer-readable storage media <NUM>. Storage media <NUM> may be of different physical types. The storage media <NUM> may be volatile memory, non-volatile memory, fixed in place media, removable media, magnetic media, optical media, solid-state media, and/or of other types of physical durable storage media (as opposed to merely a propagated signal or mere energy). In particular, a configured storage medium <NUM> such as a portable (i.e., external) hard drive, CD, DVD, memory stick, or other removable non-volatile memory medium may become functionally a technological part of the computer system when inserted or otherwise installed, making its content accessible for interaction with and use by processor <NUM>. The removable configured storage medium <NUM> is an example of a computer-readable storage medium <NUM>. Some other examples of computer-readable storage media <NUM> include built-in RAM, ROM, hard disks, and other memory storage devices which are not readily removable by users <NUM>.

The storage medium <NUM> is configured with binary instructions <NUM> that are executable by a processor <NUM>; "executable" is used in a broad sense herein to include machine code, interpretable code, bytecode, and/or code that runs on a virtual machine, for example. The storage medium <NUM> is also configured with data <NUM> which is created, modified, referenced, and/or otherwise used for technical effect by execution of the instructions <NUM>. The instructions <NUM> and the data <NUM> configure the memory or other storage medium <NUM> in which they reside; when that memory or other computer readable storage medium is a functional part of a given computer system, the instructions <NUM> and data <NUM> also configure that computer system. In some embodiments, a portion of the data <NUM> is representative of real-world items such as product characteristics, inventories, physical measurements, settings, images, readings, targets, volumes, and so forth. Such data is also transformed by backup, restore, commits, aborts, reformatting, and/or other technical operations.

Although an embodiment may be described as being implemented as software instructions executed by one or more processors in a computing device (e.g., general purpose computer, server, or cluster), such description is not meant to exhaust all possible embodiments. One of skill will understand that the same or similar functionality can also often be implemented, in whole or in part, directly in hardware logic, to provide the same or similar technical effects. Alternatively, or in addition to software implementation, the technical functionality described herein can be performed, at least in part, by one or more hardware logic components. For example, and without excluding other implementations, an embodiment may include hardware logic components <NUM>, <NUM> such as Field-Programmable Gate Arrays (FPGAs), Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Products (ASSPs), System-on-a-Chip components (SOCs), Complex Programmable Logic Devices (CPLDs), and similar components. Components of an embodiment may be grouped into interacting functional modules based on their inputs, outputs, and/or their technical effects, for example.

In addition to processors <NUM> (e.g., CPUs, ALUs, FPUs, TPUs and/or GPUs), memory / storage media <NUM>, and displays <NUM>, an operating environment may also include other hardware <NUM>, such as batteries, buses, power supplies, wired and wireless network interface cards, for instance. The nouns "screen" and "display" are used interchangeably herein. A display <NUM> may include one or more touch screens, screens responsive to input from a pen or tablet, or screens which operate solely for output. In some embodiments peripherals <NUM> such as human user I/O devices (screen, keyboard, mouse, tablet, microphone, speaker, motion sensor, etc.) will be present in operable communication with one or more processors <NUM> and memory.

In some embodiments, the system includes multiple computers connected by a wired and/or wireless network <NUM>. Networking interface equipment <NUM> can provide access to networks <NUM>, using network components such as a packet-switched network interface card, a wireless transceiver, or a telephone network interface, for example, which may be present in a given computer system. Virtualizations of networking interface equipment and other network components such as switches or routers or firewalls may also be present, e.g., in a software-defined network or a sandboxed or other secure cloud computing environment. In some embodiments, one or more computers are partially or fully "air gapped" by reason of being disconnected or only intermittently connected to another networked device or remote cloud. In particular, identity attack detection functionality could be installed on an air gapped network and then be updated periodically or on occasion using removable media. A given embodiment may also communicate technical data and/or technical instructions through direct memory access, removable nonvolatile storage media, or other information storage-retrieval and/or transmission approaches.

One of skill will appreciate that the foregoing aspects and other aspects presented herein under "Operating Environments" may form part of a given embodiment. This document's headings are not intended to provide a strict classification of features into embodiment and non-embodiment feature sets.

One or more items are shown in outline form in the Figures, or listed inside parentheses, to emphasize that they are not necessarily part of the illustrated operating environment or all embodiments, but may interoperate with items in the operating environment or some embodiments as discussed herein. It does not follow that items not in outline or parenthetical form are necessarily required, in any Figure or any embodiment. In particular, <FIG> is provided for convenience; inclusion of an item in <FIG> does not imply that the item, or the described use of the item, was known prior to the current innovations.

<FIG> illustrates an environment having a monitored network <NUM>, <NUM>. The monitored network includes monitored computers <NUM>, <NUM> that send or receive communications <NUM> over network <NUM> connections. Monitoring produces logs <NUM> that describe events <NUM>, such as login attempts, data transfers, and other network activity. "Data transfer" may refer to the act of transferring data to computer or may refer to a memorialization of that act in a log; "transfer" does not imply removal of an original, but rather is used interchangeably with "transmit" or "send a copy".

An enhanced identity attack detection system <NUM> receives the events and analyzes them as taught herein using identity attack detection functionality <NUM> such as specialized software configured to operate as taught herein, e.g., by considering failed sign-in credential strength. An identity attack detection system <NUM> system may go beyond merely detecting an identity attack <NUM>, by initiating or imposing defensive measures designed to restrict access to the monitored computer(s) <NUM>. A system <NUM> "initiates" a defensive measure by requesting that another system perform the defensive measure, while a system <NUM> "imposes" a defensive measure by itself performing the defensive measure.

Such defensive measures may be referred to expressly for emphasis, e.g., as parts or behaviors of a "detection and defense system" <NUM>. But unless defensive measures are explicitly excluded, it is understood herein that identity attack detection systems and methods not only include functionality to detect identity attacks but also include functionality to initiate or impose defensive measures against detected attacks. Defensive measures generally are referred to herein using reference numeral <NUM>.

An identity attack <NUM> may be caused or instigated by one or more attackers <NUM>. In the illustrated environment of <FIG>, the attackers <NUM> reside outside a network boundary <NUM> that is defined, e.g., by firewalls. But teachings herein may also be advantageously applied to detect identity attacks perpetrated by insider attackers.

Moreover, in the illustrated environment, the identity attack detection system <NUM> resides outside the monitored network <NUM>, but in other environments an identity attack detection system <NUM> resides inside the monitored network <NUM>. Similarly, the illustrated environment shows the identity attack detection system <NUM> communicating with a separately located cybersecurity center <NUM>, but in other environments an identity attack detection system <NUM> resides inside the cybersecurity center <NUM>, and in others the identity attack detection system <NUM> operates without any cybersecurity center <NUM> per se.

<FIG> illustrates an enhanced system <NUM> which is configured to detect identity attacks and to initiate or impose defensive measures <NUM> against such attacks. The system <NUM> may be networked through an interface <NUM>. The illustrated system <NUM> includes identity attack detection software <NUM> to perform computations that detect identity attacks by tracking specific measures <NUM> of weak credential <NUM> usage in failed sign-ins <NUM>. For example, the identity attack detection software <NUM> may perform a method <NUM> illustrated in <FIG> and may track one or more of the weak credential usage measures <NUM> shown in <FIG>. The software <NUM> may compare measure <NUM> values against access restriction conditions <NUM>, and when an access restriction condition <NUM> is met, the software <NUM> may initiate or impose access restrictions <NUM> as defensive measures <NUM> against an apparent identity attack <NUM>. An apparent attack, which is also referred to as an "attack candidate" <NUM>, is not necessarily an actual attack but aa a precaution is treated as an actual attack. The restrictions <NUM> may restrict access to one or more target accounts <NUM>, restrict access from one or more source locations <NUM>, or do both.

For clarity, note that herein "measure" may refer to a defensive measure <NUM> which is an act of cyber defense, or "measure" may refer to a weak credential usage measure <NUM> which is a count or other statistic reflecting weak credential <NUM> usage in failed sign-ins <NUM>. Context will indicate which meaning is intended.

A sign-in attempt may fail for any of a variety of reasons. In some cases, which are distinguished herein, sign-in failure is due to use of an incorrect password that is also a weak password (e.g., too short or too simple). In some, the failure is due to use of an incorrect password that is also a compromised password (compromised passwords are often short and simple, but not always). In some cases, which are also distinguished herein, sign-in failure is due to use of an incorrect username.

Sign-in failure may also be due to use of an incorrect password that is nonetheless strong, e.g., sufficiently long and complex to pass a strength test that makes it suitable in theory for use within the monitored network. This may occur, e.g., when a user mistypes the correct password, e.g., by leaving caps lock on or by transposing two characters or omitting a single character. Some accounts are configured to allow sign-ins only during certain hours, or only from certain locations, so sign-in attempts outside those hours or from other non-approved locations will fail, regardless of whether the password submitted is strong and regardless of whether the correct username is used in the attempt. Attempts to login to a locked account will also fail, even when the correct complex password and correct username are used, unless the attempt includes or follows unlocking the account. Errors in data transmission may also cause sign-in failures.

<FIG> illustrates various aspects <NUM> of at least one identity attack detection system <NUM>. These aspects are discussed at various points herein, and additional details regarding them are provided in the discussion of a List of Reference Numerals later in this disclosure document.

<FIG> shows some examples of weak credential failed sign-in measures <NUM>. These measures <NUM> are discussed at various points herein, and additional details regarding them are provided in the discussion of a List of Reference Numerals later in this disclosure document.

Some embodiments use or provide a functionality-enhanced system, such as system <NUM> or another system <NUM> that is enhanced as taught herein. In some embodiments, an attack detection system which is configured for automatic detection of an identity attack and for initiating an automatic defense against the identity attack includes a digital memory <NUM>, and also includes a processor <NUM> in operable communication with the memory. The processor <NUM> is configured to perform steps for detecting an identity attack in or against a monitored network <NUM>. The steps include (a) determining that a credential <NUM> used in a failed sign-in <NUM> to a target account <NUM> from a source location <NUM> is a weak credential <NUM>, (b) in response to the determining, updating a measure <NUM> of weak credential failed sign-ins, (c) ascertaining that the updated measure <NUM> satisfies an access restriction condition <NUM>, and (d) in response to at least the ascertaining, initiating an access restriction <NUM> on at least one of the target account and the source location, whereby the system <NUM> enhances cybersecurity by detecting behavior which indicates an identity attack <NUM> and by initiating an access restriction <NUM> in response to the behavior, and wherein said detecting is based on at least both noting sign-in failure <NUM> and determining credential weakness <NUM>.

With regard to measure <NUM>, an embodiment may count failed sign-ins to an account <NUM> without also counting failed sign-ins from an IP address <NUM>, <NUM>. Another embodiment may count failed sign-ins from an IP address <NUM>, <NUM> without counting failed sign-ins to an account <NUM>. Other embodiments may track both failed sign-ins from an IP address and failed sign-ins to an account.

An embodiment may use one or more different kinds of measures <NUM> that can indicate an attack <NUM>, e.g., measures based on a targeted account counter, measures based on a general source location counter, measures based on a familiar source location counter, measures based on a count of failed sign-ins to a set <NUM> of accounts (an attack <NUM> may spray multiple accounts), and measures based on a count of failed sign-ins from a set <NUM> of locations (an attacker may rotate through multiple IP addresses <NUM>).

In some embodiments, the measure <NUM> of weak credential failed sign-ins includes at least one of the following situations wherein the weak credential of interest is a weak passphrase <NUM>: a measure <NUM> based on a count <NUM> of weak passphrase failed sign-ins directed to the target account, a measure <NUM> based on a count <NUM> of weak passphrase failed sign-ins directed from the source location, a measure <NUM> based on a count <NUM> of weak passphrase failed sign-ins directed from the source location when the source location is familiar in that the source location has been previously associated with an authorized user of the target account, a measure <NUM> based on a count <NUM> of weak passphrase failed sign-ins directed from the source location when the source location is unfamiliar in that the source location has not been previously associated with an authorized user of the target account, a measure <NUM> based on a count <NUM> of weak passphrase failed sign-ins directed to any of a predefined set of accounts that includes the target account, or a measure <NUM> based on a count <NUM> of weak passphrase failed sign-ins directed from any of a predefined set of locations that includes the source location.

As a result of distinguishing familiar locations from unfamiliar locations and giving them different respective counts an possibly also different respective restriction thresholds <NUM>, an embodiment may block traffic from unfamiliar locations <NUM> (per a lower threshold <NUM> or higher failed sign-in count <NUM> or both) while still allowing traffic from familiar locations <NUM> (per a higher threshold <NUM> or lower failed sign-in count <NUM> or both).

In some embodiments, the measure <NUM> of weak credential failed sign-ins includes at least one of the following situations wherein the weak credential of interest is a wrong username <NUM>: a measure <NUM> based on a count <NUM> of wrong username failed sign-ins directed to the target account, a measure <NUM> based on a count <NUM> of wrong username failed sign-ins directed from the source location, a measure <NUM> based on a count <NUM> of wrong username failed sign-ins directed from the source location when the source location is familiar in that the source location has been previously associated with an authorized user of the target account, a measure <NUM> based on a count <NUM> of wrong username failed sign-ins directed from the source location when the source location is unfamiliar in that the source location has not been previously associated with an authorized user of the target account, a measure <NUM> based on a count <NUM> of wrong username failed sign-ins directed to any of a predefined set of accounts that includes the target account, or a measure <NUM> based on a count <NUM> of wrong username failed sign-ins directed from any of a predefined set of locations that includes the source location.

An embodiment may leverage existing password strength testing code <NUM> by using it as part of identity attack detection instead of (or in addition to) using that strength testing code <NUM> to enforce good password hygiene when accounts <NUM> are created and passwords are initially set, or when users <NUM> change their passwords. Some embodiments include a passphrase strength testing code <NUM> which upon execution tests passphrase <NUM> strength and which is configured to test proposed passphrases <NUM> submitted by authorized users of accounts in the monitored network <NUM>. In these embodiments, determining that a passphrase used in a failed sign-in to a target account from a source location is a weak passphrase <NUM> includes executing the passphrase strength testing code.

Some embodiments include a list <NUM> of compromised passphrases. In these embodiments, determining <NUM> that a passphrase used in a failed sign-in to a target account from a source location is a weak passphrase includes searching <NUM> the list of compromised passphrases.

In some embodiments, the attack detection system <NUM> resides <NUM> in the monitored network. That is, the attack detection system may be part of the network that it monitors. In some other embodiments, it straddles the network boundary <NUM>, and in some the attack detection system <NUM> resides <NUM> outside the monitored network.

Other system embodiments are also described herein, either directly or derivable as system versions of described processes or configured media, duly informed by the extensive discussion herein of computing hardware.

Although specific architectural examples are shown in the Figures, an embodiment may depart from those examples. For instance, items shown in different Figures may be included together in an embodiment, items shown in a Figure may be omitted, functionality shown in different items may be combined into fewer items or into a single item, items may be renamed, or items may be connected differently to one another.

Examples are provided in this disclosure to help illustrate aspects of the technology, but the examples given within this document do not describe all of the possible embodiments. A given embodiment may include additional or different technical features, mechanisms, sequences, data structures, or functionalities for instance, and may otherwise depart from the examples provided herein.

<FIG> illustrates a family of methods <NUM> that may be performed or assisted by an enhanced system, such as system <NUM> or another functionality <NUM> enhanced system as taught herein. <FIG> further illustrates identity attack detection methods (which may also be referred to as "processes" in the legal sense of that word) that are suitable for use during operation of a system which has innovative functionality taught herein. <FIG> includes some refinements, supplements, or contextual actions for steps shown in <FIG>. <FIG> also incorporates steps shown in <FIG>.

Technical processes shown in the Figures or otherwise disclosed will be performed automatically, e.g., by an enhanced SIEM tool <NUM>, <NUM>, unless otherwise indicated. Processes may also be performed in part automatically and in part manually to the extent action by a human administrator or other human person is implicated, e.g., in some embodiments a human administrator may specify respective values for one or more of the restriction thresholds <NUM>, <NUM>. No process contemplated as innovative herein is entirely manual.

In a given embodiment zero or more illustrated steps of a process may be repeated, perhaps with different parameters or data to operate on. Steps in an embodiment may also be done in a different order than the top-to-bottom order that is laid out in <FIG> and <FIG>. Steps may be performed serially, in a partially overlapping manner, or fully in parallel. In particular, the order in which flowchart <NUM> action items or flowchart <NUM> action items are traversed to indicate the steps performed during a process may vary from one performance of the process to another performance of the process. The flowchart traversal order may also vary from one process embodiment to another process embodiment. Steps may also be omitted, combined, renamed, regrouped, be performed on one or more machines, or otherwise depart from the illustrated flow, provided that the process performed is operable and conforms to at least one claim.

The present disclosure distinguishes between "initiating" an access restriction or other defense and "imposing" one. Initiating <NUM> includes making a request for access restriction but does not require that the access restriction actually happen, whereas imposing <NUM> does require that the access restriction actually happen. In particular, initiating <NUM> may involve alerting an administrator so that the administrator can decide whether to put the access restriction in place, whereas imposing <NUM> automatically puts the access restriction in place.

Some embodiments use or provide an attack detection method for enhancing cybersecurity, including the following automatic steps: determining <NUM> that a passphrase used in a failed sign-in to a target account from a source location is a weak credential; in response to the determining, updating <NUM> a measure of weak credential failed sign-ins; ascertaining <NUM> that the updated measure satisfies an access restriction condition; and in response to at least the ascertaining, imposing <NUM> an access restriction on at least one of the target account and the source location. This method enhances cybersecurity by detecting <NUM> behavior which indicates an identity attack <NUM> and by imposing <NUM> an access restriction in response to the behavior. Notably, the detecting <NUM> is based on at least both noting <NUM> sign-in failure and determining <NUM> credential weakness.

One advantage of embodiments taught herein is that they may detect identity attacks sooner than mechanisms that rely entirely on counting failed sign-ins without distinguishing between the failures based on credential weakness. For example, access to an account may be restricted before the account would have been locked under a conventional approach. In some embodiments, the method imposes <NUM> an access restriction <NUM> on access to the target account before an account lockout threshold <NUM> number of failed sign-ins has been directed to the target account. As another example, access to an IP address may be restricted before the IP address would have been blocked under a conventional approach. In some embodiments, the method imposes <NUM> an access restriction on access from the source location <NUM> before a source location blocking threshold <NUM> number of failed sign-ins has been directed from the source location.

In some embodiments, passphrase complexity <NUM> may be based on an extent of different kinds of characters (e.g., alphabetic, numeric, symbols, upper/lower case), character repetition, or patterns. In particular, a points-based approach such as one used by some passphrase strength testing code <NUM> may be employed to calculate complexity <NUM>. Patterns can be evident as repeated weak strings or substrings such as "passwordpassword" or "<NUM>", or evident as keyboard patterns such as "asdf" or "1qaz", or as repeated characters such as "aaaaaaaa" or " <NUM>", or as combinations thereof, for example.

In some embodiments, the credential used in a failed sign-in includes a passphrase and determining that the credential is a weak credential includes at least one of the following: testing <NUM> strength of the passphrase based on at least passphrase length <NUM>, testing <NUM> strength of the passphrase based on at least passphrase complexity <NUM>, or searching <NUM> a list <NUM> of compromised passphrases.

Embodiments may use or include various kinds of access restrictions <NUM>, including for example additional authentication <NUM>. The additional authentication <NUM> that is required <NUM> in some cases could be any kind of authentication in addition to the weak passphrase, e.g., a code texted to a phone, an approval from an administrator, a physical token, a biometric factor, or even a second and different passphrase that is associated with the target account.

In some embodiments, imposing <NUM> the access restriction <NUM> includes at least one of the following: locking <NUM> the target account, requiring <NUM> an additional authentication <NUM> for access to the target account, or blocking <NUM> an IP address at the source location.

In some embodiments, identity attack indicators include a high volume of failed sign-ins coming from an IP address with a majority of the failed sign-ins using weak passwords. This may include situations where the failed sign-ins coming from the source location are measured within a specified time period, or situations where all failed sign-ins coming from the source location are measured.

In some embodiments, identity attack indicators include a high volume of failed sign-ins towards an account with a majority of the failed sign-ins using weak passwords. This may include situations where the failed sign-ins toward the account are measured within a specified time period, or situations where all failed sign-ins toward the account are measured.

In some embodiments, a "high volume" of failed sign-ins (toward an account or from a location or both) occurs when the number of failed sign-ins crosses any value defined as a location restriction threshold <NUM> or any value defined as an account restriction threshold <NUM>. In particular, in some embodiments a majority approach is used, e.g., the restriction condition <NUM> calls for X failed attempts using weak passwords across Y sign-ins total where X/Y > <NUM>%. In some embodiments, the larger the number of failed sign-in attempts, the more strongly the indicator signals an actual identity attack has probably been detected.

In some embodiments, ascertaining <NUM> that the updated <NUM> measure <NUM> satisfies an access restriction condition <NUM> includes ascertaining <NUM>, <NUM> that a majority <NUM> of the failed sign-ins <NUM> coming from the source location <NUM> used <NUM> one or more weak passphrases <NUM>.

In some embodiments, ascertaining <NUM> that the updated <NUM> measure <NUM> satisfies an access restriction condition <NUM> includes ascertaining <NUM>, <NUM> that a majority <NUM> of the failed sign-ins <NUM> towards the target account <NUM> used <NUM> one or more weak passphrases <NUM>.

Some embodiments track sign-in attempts using wrong (e.g., unknown) usernames <NUM>. That is, instead of (or in addition to) tracking wrong passwords some embodiments track wrong usernames. This may be part of tracking failed sign-ins from an IP address <NUM>. Tracking wrong usernames may track <NUM> usernames that don't exist in the monitored account, or that don't exist in the monitored network <NUM> as a whole. Tracking wrong usernames from a location <NUM> may provide an alternative or additional indicator of an attempted attack <NUM> and could be useful to help stop <NUM> traffic from that source location.

Some embodiments consider a passphrase weak when the passphrase is found in a list <NUM> of compromised passphrases. Such a list <NUM> may be generated anywhere from solely to substantially (i.e., from <NUM>% to at least <NUM>%) from attempts to login to the monitored network <NUM>. In some embodiments, the list <NUM> is generated anywhere from solely to substantially from sign-in attempts to any network, e.g., a list <NUM> such as one that is publicly available from the haveibeenpwned website may be used, in whole or in part, possibly with entries from other compromised passphrase sources.

In some embodiments, determining <NUM>, <NUM> that the credential used in a failed sign-in is a weak credential includes at least one of the following: searching <NUM> a list <NUM> of compromised passphrases in which at least three-quarters of the listed passphrases were harvested <NUM> from attempts to sign-in to the monitored network, or searching <NUM> a list <NUM> of compromised passphrases in which at least half of the listed passphrases were harvested <NUM> from attempts to sign-in to one or more networks other than the monitored network or from attempts to sign-in to an unspecified network (some sources of compromised passphrases do not specify which network <NUM> their entries are harvested from).

It is expected, but not required, that many if not most identity attacks <NUM> will come from outside the monitored network <NUM>. But teachings herein may also be applied to defend against an insider attack. In some embodiments, imposing <NUM> an access restriction includes restricting <NUM> access attempts that come from inside the monitored network <NUM>.

Some embodiments distinguish between the locations that are sources of failed logins according to whether they were previously associated with an owner of the account the failed login was aimed at. In particular, in some embodiments a set of familiar locations <NUM>, <NUM> and a set of unfamiliar locations <NUM>, <NUM> have separate counters. In some embodiments, updating <NUM> a measure <NUM> of weak passphrase failed sign-ins over time includes updating <NUM> a familiar location attempt count <NUM> of weak passphrase failed sign-ins to the target account which came from one or more familiar locations <NUM>, and also includes updating <NUM> an unfamiliar location attempt count <NUM> of weak passphrase failed sign-ins to the target account which came from one or more unfamiliar locations <NUM>. A location <NUM> is deemed familiar when the location has been previously associated with an authorized user of the target account, and otherwise the location is deemed unfamiliar.

Some embodiments include a configured computer-readable storage medium <NUM>. Storage medium <NUM> may include disks (magnetic, optical, or otherwise), RAM, EEPROMS or other ROMs, and/or other configurable memory, including in particular computer-readable storage media (which are not mere propagated signals). The storage medium which is configured may be in particular a removable storage medium <NUM> such as a CD, DVD, or flash memory. A general-purpose memory, which may be removable or not, and may be volatile or not, can be configured into an embodiment using items such as identity attack detection software <NUM>, WCFSI measures <NUM>, access restriction conditions <NUM>, compromised passphrase lists <NUM>, passphrase strength testing code <NUM>, and restriction thresholds <NUM>, <NUM>, in the form of data <NUM> and instructions <NUM>, read from a removable storage medium <NUM> and/or another source such as a network connection, to form a configured storage medium. The configured storage medium <NUM> is capable of causing a computer system <NUM> to perform technical process steps for identity cyberattack detection and defense, as disclosed herein. The Figures thus help illustrate configured storage media embodiments and process (a. method) embodiments, as well as system and process embodiments. In particular, any of the process steps illustrated in <FIG> or <FIG>, or otherwise taught herein, may be used to help configure a storage medium to form a configured storage medium embodiment.

Some embodiments use or provide a computer-readable storage medium <NUM>, <NUM> configured with data <NUM> and instructions <NUM> which upon execution by at least one processor <NUM> cause a computing system to perform an attack detection method for enhancing cloud cybersecurity. This method includes: determining <NUM> that a credential <NUM> used in a failed sign-in to a target account in a cloud computing environment from a source location is a weak credential <NUM>; in response to the determining <NUM>, updating <NUM> a measure <NUM> of weak credential failed sign-ins; ascertaining <NUM> that the updated measure satisfies an access restriction condition <NUM>; and in response to at least the ascertaining <NUM>, initiating <NUM> an access restriction <NUM> on at least one of the target account and the source location. Thus, the system enhances cybersecurity by detecting <NUM> behavior which indicates an identity attack and by initiating <NUM>, <NUM> an access restriction in response to the behavior. The detecting <NUM> is based on at least both noting <NUM> sign-in failure and determining <NUM> credential weakness, unlike approaches that rely on sign-in failure counts without considering credential weakness.

In some embodiments, the credential <NUM> submitted during a sign-in attempt includes a username and the method includes: determining <NUM>, <NUM> that the username used in a failed sign-in to a target account in a cloud computing environment from a source location is a wrong username <NUM>; in response to the determining, updating <NUM> a measure of wrong username failed sign-ins. In some of these embodiments, initiating <NUM> or imposing <NUM> an access restriction is at least partially in response to the measure <NUM> of wrong username failed sign-ins.

In some embodiments, the credential <NUM> used in a sign-in attempt includes a passphrase, and determining <NUM> that the credential is a weak credential <NUM> includes finding <NUM> at least one of the following in the passphrase: repetition <NUM> of a character, or repetition <NUM> of a string.

In some embodiments, updating <NUM> the measure includes updating (e.g., incrementing) account counters <NUM> which track the number of failed sign-ins with weak passphrases for each of a plurality <NUM> of respective accounts, and updating IP address counters <NUM> which track the number of failed sign-ins with weak passphrases for each of a plurality <NUM> of IP addresses.

In some embodiments, ascertaining <NUM> that the updated measure satisfies an access restriction condition includes at least one of the following: ascertaining that a count of failed sign-ins directed to the target account has reached an account restriction threshold <NUM>, when the account restriction threshold is no greater than seventy percent of an account lockout threshold <NUM> that is not based on any passphrase weakness determination; or ascertaining that a count of failed sign-ins directed from the source location has reached a source location restriction threshold <NUM>, when the source location restriction threshold is no greater than sixty percent of a source location blocking threshold <NUM> that is not based on any passphrase weakness determination. Thus, the embodiment may detect identity attacks faster than other mechanisms that fail to consider credential strength.

One of skill will recognize that not every part of this disclosure, or any particular details therein, are necessarily required to satisfy legal criteria such as enablement, written description, or best mode. Any apparent conflict with any other patent disclosure, even from the owner of the present innovations, has no role in interpreting the claims presented in this patent disclosure. With this understanding, which pertains to all parts of the present disclosure, some additional examples and observations are offered.

Some embodiments implement or otherwise use teachings herein for detecting and blocking password-centric identity attacks by identifying a series of known weak passwords in failed sign-in attempts. By way of context, password spray attacks are one of the most common forms of identity-related attacks, and the frequency of these attacks is believed to be increasing at the time of this disclosure's writing. Bad actors (attackers) choose a set of passwords they believe will be commonly used amongst a set of accounts and then attempt to sign-in. A goal is that one of these sign-in attempts will be successful and the bad actor will then have access to a user's account.

IP blocking <NUM> and account lockout <NUM> (sometimes called "smart lockout") are possible defenses against password-centric identity attacks. As to IP blocking, if there are multiple failed sign-ins coming from a single IP address <NUM>, all sign-in attempts coming from this IP will be blocked. Blocking will take place once the IP address has hit a set threshold <NUM> for failed sign-in attempts. As to account lockout, if there are a set threshold number <NUM> of failed sign-ins for a specific account, that account will be locked.

Particular attention is directed herein to weak passwords. As part of eliminating weak passwords, a service such as a Microsoft Azure® Active Directory® (AAD) service may utilize some form of proposed password screening as a kind of password protection (marks of Microsoft Corporation). In particular, AAD Password Protection software <NUM> uses a points-based algorithm to assess a password (typically one proposed for use) to check whether it is weak and easily guessable. The password is checked against a list of ~<NUM> known weak or popular words and possible character substitutions and variations. If the user's password contains one of these ~<NUM> words and phrases, the password receives fewer points and likely will not pass an acceptance threshold. This password strength testing algorithm detects millions of common passwords used today and many if not all of their variations. Of course, the number of listed passwords checked may vary among different software <NUM> implementations, as may the points that are awarded or deducted for aspects of length or complexity, and also whether a points-based approach is implemented.

When attackers <NUM> perform password-centric attacks <NUM>, they tend to use easy-to-configure and easy-to-guess passwords. Since many people have multiple online accounts that require a username + password pair, people tend to use passwords that lack complexity so they are easy to remember and easy to enter. Bad actors are aware of this tendency and take advantage of it when performing an attack. Many password spray attacks employ a set of commonly used easy-to-guess passwords. Most of not all of these common passwords don't pass the acceptance points threshold set by the AAD Password Protection points-based algorithm.

Password spray and other password-centric attacks are identified when there is an increase in failed sign-in attempts. This increase indicates that a bad actor is attempting to guess a user's password and the failed attempts means the bad actors hasn't been able to guess passwords. Failed attempts can sometimes mean the genuine user has forgotten their own password and they are trying to guess it, but these failed sign-ins are normally evident only as a few attempts at a time.

In some networks <NUM>, the presence of hundreds to thousands of failed attempts are indicators of an attack <NUM>. More generally, an increase measure <NUM> may be absolute, e.g., based at least in part on noting <NUM> one hundred more failed attempts <NUM> than yesterday in a given network <NUM>, or noting <NUM> a thousand more failed attempts <NUM> than in last week's average. Or an increase measure <NUM> may be relative, e.g., based at least in part on noting <NUM> at least <NUM>% more failed attempts <NUM> than yesterday, or noting an increase of at least <NUM>% in failed attempts <NUM> over a period of sixty minutes. These specific numbers are examples; a given embodiment may use other values for absolute increase thresholds, relative increase thresholds, and durations over which an increase is measured.

In some environments, before a bad actor's IP address is blocked due to IP blocking or before a user's account is locked, the bad actor must hit a threshold <NUM> or <NUM>. Under one Microsoft AAD approach, for example, IP blocking depends on a pre-set threshold <NUM> defined by Microsoft, which is typically in the range of one hundred to thousands of failed attempts, and account lockout depends on a threshold <NUM> set by a cloud tenant's administrator, with a default threshold <NUM> of ten failed attempts. Similar thresholds <NUM> and <NUM> are used by some Microsoft Account (MSA) security enforcement mechanisms. Thus, the location blocking threshold <NUM> may allow thousands of failed sign-in attempts before the bad actor's IP is blocked from all authentication requests.

Some bad actors have picked up on the threshold patterns and have adjusted their attacking strategy and frequency of attacks to deliberately stay below the threshold(s) <NUM> or <NUM> or both. This is sometimes called a "low and slow" attack. Some bad actors <NUM> change their IP addresses so that IP blocking mechanisms never flag them. This allows the bad actors to continuously perform attacks without ever getting blocked.

Recognizing that bad actors use common passwords in their attacks and that these common passwords can be filtered out by the AAD Password Protection points-based algorithm or other strength testing code <NUM>, some embodiments employ the passwords used in these attacks (or the characteristics of such passwords such as shortness and simplicity) to identify attackers faster and to proactively block them before they hit the more granular thresholds <NUM>, <NUM>.

In some embodiments, existing cybersecurity mechanisms for IP blocking and account lockout logic are enhanced to help block bad actors sooner, before they even hit less focused thresholds <NUM>, <NUM>. Those broader thresholds were defined by a software vendor, a cloud service provider, or an enterprise, for example. More finely tuned restriction thresholds <NUM>, <NUM> may be defined by the same entities, but operate differently as discussed herein.

In some embodiments, whenever a failed sign-in is detected, the enhanced cybersecurity mechanism will flag whether the failed password was a weak password or known bad password. Weak passwords will be classified as such by using AAD Password Protection's points-based algorithm or other password strength testing code <NUM>. If the failed password has the points needed to pass the AAD Password Protection threshold or other applicable acceptance threshold, the password will be considered a strong password. Otherwise, the password will be deemed a known bad password (and hence be deemed a weak passphrase <NUM>). A counter <NUM> for the number of failed sign-ins with known bad passwords will be kept for each account, and a counter <NUM> for the number of failed sign-ins with known bad passwords will be kept for each IP address.

If such an embodiment notes a high volume of failed sign-ins coming from an IP address and a majority of those failed sign-ins are using weak passwords, the IP will be blocked <NUM> immediately. This blocking will be done before the IP address hits the overall IP blocking threshold <NUM>. Similarly, if the embodiment notes a high volume of failed sign-in attempts towards an account and a majority of those failed sign-ins are using weak passwords, the account will be locked <NUM> immediately, before the account hits the defined Smart Lockout threshold or similar lockout threshold <NUM>.

In this example, this data <NUM>, <NUM> will be obtained for any non-repeated bad password request that comes in from unfamiliar locations <NUM>, as opposed to requests from a familiar location <NUM> such as a familiar IP address or device or browser used previously by the account's owner. This distinction between unfamiliar and familiar locations may be made because identity attacks are often performed from outside of the user's location and using devices that are not owned by the account's genuine user. Making a location familiarity distinction avoids inconveniencing users on the basis of genuine user traffic, which normally comes from the account's familiar locations, devices, and IP addresses.

Such improvements may block bad actors before large thresholds <NUM>, <NUM> for wide scale attacks are met. Bad actors that change their IP address to dodge IP blocking may now be caught because detection won't focus only on the actual IP address, but will also consider the passwords attackers are spraying during the attack.

Additional support for the discussion above is provided below. For convenience, this additional support material appears under various headings. Nonetheless, it is all intended to be understood as an integrated and integral part of the present disclosure's discussion of the contemplated embodiments.

The technical character of embodiments described herein will be apparent to one of ordinary skill in the art, and will also be apparent in several ways to a wide range of attentive readers. Some embodiments address technical activities such as password spray attack detection, automatically counting failed sign-in attempts in a cloud, differentiating between strong and weak passwords using points-based or other testing code <NUM> that checks hundreds of variations in real time, maintaining failed login counters for hundreds or even thousands of user accounts <NUM>, and maintaining failed login counters for thousands or even tens of thousands of IP addresses <NUM>, which are each activities deeply rooted in computing technology. Some of the technical mechanisms discussed include, e.g., password strength testing code <NUM>, logs <NUM> that track weak credentials <NUM> and failed sign-ins <NUM>, digital access restriction conditions <NUM> and access restrictions <NUM>, restriction thresholds <NUM>, <NUM>, and compromised password lists <NUM> with thousands or more entries. Some of the technical effects discussed include, e.g., faster identity attack detection based on WCFSI measures <NUM> than is provided when detection does not consider credential strength, and attack <NUM> detection despite an attacker's use of rotating IP addresses <NUM>. Thus, purely mental processes are clearly excluded. Other advantages based on the technical characteristics of the teachings will also be apparent to one of skill from the description provided.

Some embodiments described herein may be viewed by some people in a broader context. For instance, concepts such as authentication, failure, identity, security, and strength may be deemed relevant to a particular embodiment. However, it does not follow from the availability of a broad context that exclusive rights are being sought herein for abstract ideas; they are not. Rather, the present disclosure is focused on providing appropriately specific embodiments whose technical effects fully or partially solve particular technical problems, such as how to automatically and effectively assess the likelihood that certain accounts and IP addresses are part of a cyberattack. Other configured storage media, systems, and processes involving authentication, failure, identity, security, or strength are outside the present scope. Accordingly, vagueness, mere abstractness, lack of technical character, and accompanying proof problems are also avoided under a proper understanding of the present disclosure.

Any of these combinations of code, data structures, logic, components, communications, and/or their functional equivalents may also be combined with any of the systems and their variations described above. A process may include any steps described herein in any subset or combination or sequence which is operable. Each variant may occur alone, or in combination with any one or more of the other variants. Each variant may occur with any of the processes and each process may be combined with any one or more of the other processes. Each process or combination of processes, including variants, may be combined with any of the configured storage medium combinations and variants described above.

More generally, one of skill will recognize that not every part of this disclosure, or any particular details therein, are necessarily required to satisfy legal criteria such as enablement, written description, or best mode. Also, embodiments are not limited to the particular motivating examples, password strength testing algorithms, operating system environments, feature examples, software processes, development tools, identifiers, data structures, data organizations, notations, control flows, pseudocode, naming conventions, or other implementation choices described herein. Any apparent conflict with any other patent disclosure, even from the owner of the present innovations, has no role in interpreting the claims presented in this patent disclosure.

Some acronyms, abbreviations, names, and symbols are defined below. Others are defined elsewhere herein, or do not require definition here in order to be understood by one of skill.

Reference is made herein to exemplary embodiments such as those illustrated in the drawings, and specific language is used herein to describe the same.

The meaning of terms is clarified in this disclosure, so the claims should be read with careful attention to these clarifications. Specific examples are given, but those of skill in the relevant art(s) will understand that other examples may also fall within the meaning of the terms used, and within the scope of one or more claims. Terms do not necessarily have the same meaning here that they have in general usage (particularly in non-technical usage), or in the usage of a particular industry, or in a particular dictionary or set of dictionaries. Reference numerals may be used with various phrasings, to help show the breadth of a term. Omission of a reference numeral from a given piece of text does not necessarily mean that the content of a Figure is not being discussed by the text. The inventors assert and exercise the right to specific and chosen lexicography. Quoted terms are being defined explicitly, but a term may also be defined implicitly without using quotation marks. Terms may be defined, either explicitly or implicitly, here in the Detailed Description and/or elsewhere in the application file.

As used herein, a "computer system" (a. "computing system") may include, for example, one or more servers, motherboards, processing nodes, laptops, tablets, personal computers (portable or not), personal digital assistants, smartphones, smartwatches, smartbands, cell or mobile phones, other mobile devices having at least a processor and a memory, video game systems, augmented reality systems, holographic projection systems, televisions, wearable computing systems, and/or other device(s) providing one or more processors controlled at least in part by instructions. The instructions may be in the form of firmware or other software in memory and/or specialized circuitry.

An "administrator" is any user that has legitimate access (directly or indirectly) to multiple accounts of other users by using their own account's credentials. Some examples of administrators include network administrators, system administrators, domain administrators, privileged users, service provider personnel, and infrastructure administrators.

A "multithreaded" computer system is a computer system which supports multiple execution threads. The term "thread" should be understood to include code capable of or subject to scheduling, and possibly to synchronization. A thread may also be known outside this disclosure by another name, such as "task," "process," or "coroutine," for example. However, a distinction is made herein between threads and processes, in that a thread defines an execution path inside a process. Also, threads of a process share a given address space, whereas different processes have different respective address spaces. The threads of a process may run in parallel, in sequence, or in a combination of parallel execution and sequential execution (e.g., time-sliced).

A "processor" is a thread-processing unit, such as a core in a simultaneous multithreading implementation. A processor includes hardware. A given chip may hold one or more processors. Processors may be general purpose, or they may be tailored for specific uses such as vector processing, graphics processing, signal processing, floating-point arithmetic processing, encryption, I/O processing, machine learning, and so on.

"Kernels" include operating systems, hypervisors, virtual machines, BIOS or UEFI code, and similar hardware interface software.

"Code" means processor instructions, data (which includes constants, variables, and data structures), or both instructions and data. "Code" and "software" are used interchangeably herein. Executable code, interpreted code, and firmware are some examples of code.

"Program" is used broadly herein, to include applications, kernels, drivers, interrupt handlers, firmware, state machines, libraries, and other code written by programmers (who are also referred to as developers) and/or automatically generated.

A "routine" is a callable piece of code which normally returns control to an instruction just after the point in a program execution at which the routine was called. Depending on the terminology used, a distinction is sometimes made elsewhere between a "function" and a "procedure": a function normally returns a value, while a procedure does not. As used herein, "routine" includes both functions and procedures. A routine may have code that returns a value (e.g., sin(x)) or it may simply return without also providing a value (e.g., void functions).

"Service" means a consumable program offering, in a cloud computing environment or other network or computing system environment, which provides resources to multiple programs or provides resource access to multiple programs, or does both.

"Cloud" means pooled resources for computing, storage, and networking which are elastically available for measured on-demand service. A cloud may be private, public, community, or a hybrid, and cloud services may be offered in the form of infrastructure as a service (IaaS), platform as a service (PaaS), software as a service (SaaS), or another service. Unless stated otherwise, any discussion of reading from a file or writing to a file includes reading/writing a local file or reading/writing over a network, which may be a cloud network or other network, or doing both (local and networked read/write).

"IoT" or "Internet of Things" means any networked collection of addressable embedded computing or data generation or actuator nodes. Such nodes may be examples of computer systems as defined herein, and may include or be referred to as a "smart" device, "endpoint", "chip", "label", or "tag", for example, and IoT may be referred to as a "cyber-physical system". IoT nodes and systems typically have at least two of the following characteristics: (a) no local human-readable display; (b) no local keyboard; (c) a primary source of input is sensors that track sources of non-linguistic data to be uploaded from the IoT device; (d) no local rotational disk storage - RAM chips or ROM chips provide the only local memory; (e) no CD or DVD drive; (f) embedment in a household appliance or household fixture; (g) embedment in an implanted or wearable medical device; (h) embedment in a vehicle; (i) embedment in a process automation control system; or (j) a design focused on one of the following: environmental monitoring, civic infrastructure monitoring, agriculture, industrial equipment monitoring, energy usage monitoring, human or animal health or fitness monitoring, physical security, physical transportation system monitoring, object tracking, inventory control, supply chain control, fleet management, or manufacturing. IoT communications may use protocols such as TCP/IP, Constrained Application Protocol (CoAP), Message Queuing Telemetry Transport (MQTT), Advanced Message Queuing Protocol (AMQP), HTTP, HTTPS, Transport Layer Security (TLS), UDP, or Simple Object Access Protocol (SOAP), for example, for wired or wireless (cellular or otherwise) communication. IoT storage or actuators or data output or control may be a target of unauthorized access, either via a cloud, via another network, or via direct local access attempts.

"Access" to a computational resource includes use of a permission or other capability to read, modify, write, execute, or otherwise utilize the resource. Attempted access may be explicitly distinguished from actual access, but "access" without the "attempted" qualifier includes both attempted access and access actually performed or provided.

As used herein, "include" allows additional elements (i.e., includes means comprises) unless otherwise stated.

"Optimize" means to improve, not necessarily to perfect. For example, it may be possible to make further improvements in a program or an algorithm which has been optimized.

"Process" is sometimes used herein as a term of the computing science arts, and in that technical sense encompasses computational resource users, which may also include or be referred to as coroutines, threads, tasks, interrupt handlers, application processes, kernel processes, procedures, or object methods, for example. As a practical matter, a "process" is the computational entity identified by system utilities such as Windows® Task Manager, Linux® ps, or similar utilities in other operating system environments (marks of Microsoft Corporation, Linus Torvalds, respectively). "Process" is also used herein as a patent law term of art, e.g., in describing a process claim as opposed to a system claim or an article of manufacture (configured storage medium) claim. Similarly, "method" is used herein at times as a technical term in the computing science arts (a kind of "routine") and also as a patent law term of art (a "process"). "Process" and "method" in the patent law sense are used interchangeably herein. Those of skill will understand which meaning is intended in a particular instance, and will also understand that a given claimed process or method (in the patent law sense) may sometimes be implemented using one or more processes or methods (in the computing science sense).

"Automatically" means by use of automation (e.g., general purpose computing hardware configured by software for specific operations and technical effects discussed herein), as opposed to without automation. In particular, steps performed "automatically" are not performed by hand on paper or in a person's mind, although they may be initiated by a human person or guided interactively by a human person. Automatic steps are performed with a machine in order to obtain one or more technical effects that would not be realized without the technical interactions thus provided. Steps performed automatically are presumed to include at least one operation performed proactively.

One of skill understands that technical effects are the presumptive purpose of a technical embodiment. The mere fact that calculation is involved in an embodiment, for example, and that some calculations can also be performed without technical components (e.g., by paper and pencil, or even as mental steps) does not remove the presence of the technical effects or alter the concrete and technical nature of the embodiment. Identity attack detection operations such as parsing logs <NUM> to extract sign-in attempt results for multiple accounts of multiple users <NUM>, testing <NUM> passphrase strength, identifying locations <NUM> and categorizing locations as to familiarity, updating <NUM> measures <NUM> in a cloud or other network <NUM> having dozens or more users <NUM>, triggering <NUM> defensive code, locking <NUM> accounts <NUM>, blocking <NUM> IP addresses <NUM>, and many other operations discussed herein, are understood to be inherently digital. A human mind cannot interface directly with a CPU or other processor, or with RAM or other digital storage, to read and write the necessary data to perform the identity attack detection <NUM> or defense <NUM> steps taught herein. This would all be well understood by persons of skill in the art in view of the present disclosure.

"Computationally" likewise means a computing device (processor plus memory, at least) is being used, and excludes obtaining a result by mere human thought or mere human action alone. For example, doing arithmetic with a paper and pencil is not doing arithmetic computationally as understood herein. Computational results are faster, broader, deeper, more accurate, more consistent, more comprehensive, and/or otherwise provide technical effects that are beyond the scope of human performance alone. "Computational steps" are steps performed computationally. Neither "automatically" nor "computationally" necessarily means "immediately". "Computationally" and "automatically" are used interchangeably herein.

"Proactively" means without a direct request from a user. Indeed, a user may not even realize that a proactive step by an embodiment was possible until a result of the step has been presented to the user. Except as otherwise stated, any computational and/or automatic step described herein may also be done proactively.

Throughout this document, use of the optional plural "(s)", "(es)", or "(ies)" means that one or more of the indicated features is present. For example, "processor(s)" means "one or more processors" or equivalently "at least one processor".

One of skill will recognize that this innovation disclosure discusses various data values and data structures, and recognize that such items reside in a memory (RAM, disk, etc.), thereby configuring the memory. One of skill will also recognize that this innovation disclosure discusses various algorithmic steps which are to be embodied in executable code in a given implementation, and that such code also resides in memory, and that it effectively configures any general purpose processor which executes it, thereby transforming it from a general purpose processor to a special-purpose processor which is functionally special-purpose hardware.

Accordingly, one of skill would not make the mistake of treating as nonoverlapping items (a) a memory recited in a claim, and (b) a data structure or data value or code recited in the claim. Data structures and data values and code are understood to reside in memory, even when a claim does not explicitly recite that residency for each and every data structure or data value or piece of code mentioned. Accordingly, explicit recitals of such residency are not required. However, they are also not prohibited, and one or two select recitals may be present for emphasis, without thereby excluding all the other data values and data structures and code from residency. Likewise, code functionality recited in a claim is understood to configure a processor, regardless of whether that configuring quality is explicitly recited in the claim.

Throughout this document, unless expressly stated otherwise any reference to a step in a process presumes that the step may be performed directly by a party of interest and/or performed indirectly by the party through intervening mechanisms and/or intervening entities, and still lie within the scope of the step. That is, direct performance of the step by the party of interest is not required unless direct performance is an expressly stated requirement. For example, a step involving action by a party of interest such as ascertaining, authenticating, blocking, counting, defending, detecting, determining, executing, finding, harvesting, imposing, initiating, locking, logging, measuring, monitoring, noting, reaching, reporting, residing, requiring, restricting, searching, tracking, triggering, updating (and ascertains, ascertained, authenticates, authenticated, etc.) with regard to a destination or other subject may involve intervening action such as the foregoing or forwarding, copying, uploading, downloading, encoding, decoding, compressing, decompressing, encrypting, decrypting, authenticating, invoking, and so on by some other party, including any action recited in this document, yet still be understood as being performed directly by the party of interest.

Whenever reference is made to data or instructions, it is understood that these items configure a computer-readable memory and/or computer-readable storage medium, thereby transforming it to a particular article, as opposed to simply existing on paper, in a person's mind, or as a mere signal being propagated on a wire, for example.

Moreover, notwithstanding anything apparently to the contrary elsewhere herein, a clear distinction is to be understood between (a) computer readable storage media and computer readable memory, on the one hand, and (b) transmission media, also referred to as signal media, on the other hand. A transmission medium is a propagating signal or a carrier wave computer readable medium. By contrast, computer readable storage media and computer readable memory are not propagating signal or carrier wave computer readable media. Unless expressly stated otherwise in the claim, "computer readable medium" means a computer readable storage medium, not a propagating signal per se and not mere energy.

An "embodiment" herein is an example. The term "embodiment" is not interchangeable with "the invention". Embodiments may freely share or borrow aspects to create other embodiments (provided the result is operable), even if a resulting combination of aspects is not explicitly described per se herein. Requiring each and every permitted combination to be explicitly and individually described is unnecessary for one of skill in the art, and would be contrary to policies which recognize that patent specifications are written for readers who are skilled in the art. Formal combinatorial calculations and informal common intuition regarding the number of possible combinations arising from even a small number of combinable features will also indicate that a large number of aspect combinations exist for the aspects described herein. Accordingly, requiring an explicit recitation of each and every combination would be contrary to policies calling for patent specifications to be concise and for readers to be knowledgeable in the technical fields concerned.

The following list is provided for convenience and in support of the drawing figures and as part of the text of the specification, which describe innovations by reference to multiple items. Items not listed here may nonetheless be part of a given embodiment. For better legibility of the text, a given reference number is recited near some, but not all, recitations of the referenced item in the text. The same reference number may be used with reference to different examples or different instances of a given item. The list of reference numerals is:.

In short, the teachings herein provide a variety of identity attack detection and defense functionalities which operate in enhanced systems <NUM>. Cybersecurity is enhanced, with particular attention to automated attacks which result in failed sign-ins using weak credentials. Some embodiments detect <NUM> identity attacks <NUM> by comparing usage <NUM> of compromised passphrases <NUM> and variations thereof or other weak credentials <NUM> in failed sign-in attempts <NUM> to access restriction conditions <NUM>. A restriction threshold (<NUM> or <NUM> or both) amount <NUM> of weak credential failed sign-ins (WCFSI) or a WCFSI measure <NUM> increase indicates <NUM> an identity attack <NUM>, such as a password spray attack <NUM>. Going beyond noting <NUM> merely the number of failed sign-ins <NUM> by also considering (e.g., <NUM> or <NUM>) credential strength (the alternative to weakness <NUM>) allows embodiments to detect <NUM> attacks <NUM> sooner than other approaches.

An embodiment may also initiate <NUM> or impose <NUM> defenses, e.g., by locking <NUM> accounts <NUM>, by blocking <NUM> IP addresses <NUM>, or by requiring <NUM> additional authentication <NUM> before access to an account is allowed. Weak credentials <NUM> may include short passwords (e.g., length <NUM> under ten characters), simple passwords (e.g., lacking complexity <NUM> in the form of diverse character groups), compromised passwords <NUM>, or wrong usernames <NUM>, for instance. Password strength testing <NUM> may be used for attack <NUM> detection <NUM> in addition to the preventive hygiene use on passwords that are proposed by authorized users <NUM> when accounts <NUM> are created. Familiar locations <NUM> and unfamiliar locations <NUM> which are sources <NUM> of traffic <NUM> may be tracked (e.g., measured <NUM>), as sets <NUM> or individually. Other aspects of embodiments are also described herein.

Embodiments are understood to also themselves include or benefit from tested and appropriate security controls and privacy controls such as the General Data Protection Regulation (GDPR), e.g., it is understood that appropriate measures should be taken to help prevent misuse of computing systems through the injection or activation of malware into SIEM software. Use of the tools and techniques taught herein is compatible with use of such controls.

Although Microsoft technology is used in some motivating examples, the teachings herein are not limited to use in technology supplied or administered by Microsoft. Under a suitable license, for example, the present teachings could be embodied in software or services provided by other cloud service providers.

Although particular embodiments are expressly illustrated and described herein as processes, as configured storage media, or as systems, it will be appreciated that discussion of one type of embodiment also generally extends to other embodiment types. For instance, the descriptions of processes in connection with <FIG> and <FIG> also help describe configured storage media, and help describe the technical effects and operation of systems and manufactures like those discussed in connection with other Figures. It does not follow that limitations from one embodiment are necessarily read into another. In particular, processes are not necessarily limited to the data structures and arrangements presented while discussing systems or manufactures such as configured memories.

Those of skill will understand that implementation details may pertain to specific code, such as specific thresholds, comparisons, specific kinds of runtimes or programming languages or architectures, specific scripts or other tasks, and specific computing environments, and thus need not appear in every embodiment. Those of skill will also understand that program identifiers and some other terminology used in discussing details are implementation-specific and thus need not pertain to every embodiment. Nonetheless, although they are not necessarily required to be present here, such details may help some readers by providing context and/or may illustrate a few of the many possible implementations of the technology discussed herein.

With due attention to the items provided herein, including technical processes, technical effects, technical mechanisms, and technical details which are illustrative but not comprehensive of all claimed or claimable embodiments, one of skill will understand that the present disclosure and the embodiments described herein are not directed to subject matter outside the technical arts, or to any idea of itself such as a principal or original cause or motive, or to a mere result per se, or to a mental process or mental steps, or to a business method or prevalent economic practice, or to a mere method of organizing human activities, or to a law of nature per se, or to a naturally occurring thing or process, or to a living thing or part of a living thing, or to a mathematical formula per se, or to isolated software per se, or to a merely conventional computer, or to anything wholly imperceptible or any abstract idea per se, or to insignificant post-solution activities, or to any method implemented entirely on an unspecified apparatus, or to any method that fails to produce results that are useful and concrete, or to any preemption of all fields of usage, or to any other subject matter which is ineligible for patent protection under the laws of the jurisdiction in which such protection is sought or is being licensed or enforced.

Reference herein to an embodiment having some feature X and reference elsewhere herein to an embodiment having some feature Y does not exclude from this disclosure embodiments which have both feature X and feature Y, unless such exclusion is expressly stated herein. All possible negative claim limitations are within the scope of this disclosure, in the sense that any feature which is stated to be part of an embodiment may also be expressly removed from inclusion in another embodiment, even if that specific exclusion is not given in any example herein. The term "embodiment" is merely used herein as a more convenient form of "process, system, article of manufacture, configured computer readable storage medium, and/or other example of the teachings herein as applied in a manner consistent with applicable law. " Accordingly, a given "embodiment" may include any combination of features disclosed herein, provided the embodiment is consistent with at least one claim.

Not every item shown in the Figures need be present in every embodiment. Conversely, an embodiment may contain item(s) not shown expressly in the Figures. Although some possibilities are illustrated here in text and drawings by specific examples, embodiments may depart from these examples. For instance, specific technical effects or technical features of an example may be omitted, renamed, grouped differently, repeated, instantiated in hardware and/or software differently, or be a mix of effects or features appearing in two or more of the examples. Functionality shown at one location may also be provided at a different location in some embodiments; one of skill recognizes that functionality modules can be defined in various ways in a given implementation without necessarily omitting desired technical effects from the collection of interacting modules viewed as a whole. Distinct steps may be shown together in a single box in the Figures, due to space limitations or for convenience, but nonetheless be separately performable, e.g., one may be performed without the other in a given performance of a method.

Reference has been made to the figures throughout by reference numerals. Any apparent inconsistencies in the phrasing associated with a given reference numeral, in the figures or in the text, should be understood as simply broadening the scope of what is referenced by that numeral. Different instances of a given reference numeral may refer to different embodiments, even though the same reference numeral is used. Similarly, a given reference numeral may be used to refer to a verb, a noun, and/or to corresponding instances of each, e.g., a processor <NUM> may process <NUM> instructions by executing them.

As used herein, terms such as "a", "an", and "the" are inclusive of one or more of the indicated item or step. In particular, in the claims a reference to an item generally means at least one such item is present and a reference to a step means at least one instance of the step is performed. Similarly, "is" and other singular verb forms should be understood to encompass the possibility of "are" and other plural forms, when context permits, to avoid grammatical errors or misunderstandings.

Headings are for convenience only; information on a given topic may be found outside the section whose heading indicates that topic.

All claims and the abstract, as filed, are part of the specification.

To the extent any term used herein implicates or otherwise refers to an industry standard, and to the extent that applicable law requires identification of a particular version of such as standard, this disclosure shall be understood to refer to the most recent version of that standard which has been published in at least draft form (final form takes precedence if more recent) as of the earliest priority date of the present disclosure under applicable patent law.

Claim 1:
An attack detection system, which is configured for automatic detection of an identity attack (<NUM>) and for initiating an automatic defense against the identity attack, the system comprising:
a digital memory (<NUM>);
a processor (<NUM>) in operable communication with the memory, the processor configured to perform steps for detecting behavior which indicates an identity attack in or against a monitored network and for initiating an access restriction in response to the behavior, the steps including (a) determining (<NUM>) that a credential (<NUM>) used in a failed sign-in to a target account (<NUM>) from a source location (<NUM>) is a weak credential, (b) in response to the determining, updating (<NUM>) a measure (<NUM>) of weak credential failed sign-ins, (c) ascertaining (<NUM>) that the updated measure satisfies an access restriction condition (<NUM>), and (d) in response to at least the ascertaining, initiating (<NUM>) an access restriction on at least one of the target account and the source location, wherein the detecting the behavior is based on at least both noting sign-in failure and determining credential weakness,
wherein determining that a credential used in a failed sign-in to a target account from a source account is a weak credential includes identifying a sign-in attempt, identifying the success or failure of the sign-in attempt, identifying the credential used in the sign-in attempt and then testing the credential's strength.