Back to catalog
Static reviewDevelopment

Skill dossier

detecting-anomalous-authentication-patterns

Source declaration

Detects anomalous authentication patterns using UEBA analytics, statistical baselines, and machine learning models to identify impossible travel, credential stuffing, brute force, password spraying, and compromised account behaviors across authentication logs. Activates for requests involving authentication anomaly detection, login behavior analysis, UEBA implementation, or suspicious sign-in investigation.

The author's original description, preserved in English. It describes intent, not verified performance.

Detects anomalous authentication patterns using UEBA analytics, statistical baselines, and machine learning models to identify impossible travel, credential stuffing, brute force, password spraying, and compromised account behaviors across authentication logs. Activates for requests involving authentication anomaly detection, login behavior analysis, UEBA implementation, or suspicious sign-in investigation.

developmentreferencesscripts

Research summary

Machine-generated analysis; pending human review

These observations come from deterministic source parsing, not a human security review or controlled task evaluation.

Detects anomalous authentication patterns using UEBA analytics, statistical baselines, and machine learning models to identify impossible travel, credential stuffing, brute force, password spraying, and compromised account behaviors across authentication logs. Activates for requests involving authentication anomaly detection, login behavior analysis, UEBA implementation, or suspicious sign-in investigation. This bilingual summary is generated deterministically from collected source text and file structure; it is pending human editorial review.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Workflow [Source statement; provisional, not tested. Evidence: skills/detecting-anomalous-authentication-patterns/SKILL.md:L89]
  • Step 1: Collect and Normalize Authentication Logs [Source statement; provisional, not tested. Evidence: skills/detecting-anomalous-authentication-patterns/SKILL.md:L91]
  • Step 2: Detect Impossible Travel Anomalies [Source statement; provisional, not tested. Evidence: skills/detecting-anomalous-authentication-patterns/SKILL.md:L186]
  • Step 3: Detect Brute Force and Password Spraying [Source statement; provisional, not tested. Evidence: skills/detecting-anomalous-authentication-patterns/SKILL.md:L277]
  • Step 4: Build Behavioral Baselines and Detect Deviations [Source statement; provisional, not tested. Evidence: skills/detecting-anomalous-authentication-patterns/SKILL.md:L384]
  • Step 5: Implement SIEM Detection Rules [Source statement; provisional, not tested. Evidence: skills/detecting-anomalous-authentication-patterns/SKILL.md:L523]
  • Step 6: Correlate and Score Authentication Anomalies [Source statement; provisional, not tested. Evidence: skills/detecting-anomalous-authentication-patterns/SKILL.md:L594]

Limitations & scope

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Relevant for

  • Practitioners evaluating whether to inspect and install the source skill; this audience is inferred from the product context, not measured usage. [Evidence: skills/detecting-anomalous-authentication-patterns/SKILL.md:L1-L66]

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
4
Markdown files
2
scripts
1
references
1
Size
51.3 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/detecting-anomalous-authentication-patterns/LICENSEOther11 KB
skills/detecting-anomalous-authentication-patterns/references/api-reference.mdReference2.3 KB
skills/detecting-anomalous-authentication-patterns/scripts/agent.pyScript8.6 KB
skills/detecting-anomalous-authentication-patterns/SKILL.mdInstruction29.4 KB

SKILL.md frontmatter

{
  "name": "detecting-anomalous-authentication-patterns",
  "description": "Detects anomalous authentication patterns using UEBA analytics, statistical baselines, and machine learning models to identify impossible travel, credential stuffing, brute force, password spraying, and compromised account behaviors across authentication logs. Activates for requests involving authentication anomaly detection, login behavior analysis, UEBA implementation, or suspicious sign-in investigation.\n",
  "domain": "cybersecurity",
  "subdomain": "identity-access-management",
  "tags": [
    "UEBA",
    "authentication-anomaly",
    "impossible-travel",
    "brute-force",
    "credential-stuffing",
    "behavioral-analytics"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "atlas_techniques": [
    "AML.T0043",
    "AML.T0018"
  ],
  "nist_ai_rmf": [
    "MEASURE-2.7",
    "MEASURE-2.5",
    "MAP-5.1"
  ],
  "nist_csf": [
    "PR.AA-01",
    "PR.AA-02",
    "PR.AA-05",
    "PR.AA-06"
  ],
  "mitre_attack": [
    "T1110",
    "T1110.003",
    "T1110.004",
    "T1078",
    "T1021"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "initial-access",
      "positioning"
    ],
    "techniques": [
      {
        "id": "T1110.004",
        "name": "Brute Force:  Credential Stuffing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1110.003",
        "name": "Brute Force: Password Spraying",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1006",
        "name": "Account Takeover",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1006.002",
        "name": "Account Takeover: Exposed Login Credential",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "T1539",
        "name": "Steal Web Session Cookie",
        "tactic": "positioning",
        "source": "attack"
      }
    ]
  }
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Decision

    When to Use

    Source-described decision candidate under “When to Use”; not verified execution.

  2. 02
    Action

    Workflow

    Source-described action candidate under “Workflow”; not verified execution.

  3. 03
    Action

    Step 1: Collect and Normalize Authentication Logs

    Source-described action candidate under “Step 1: Collect and Normalize Authentication Logs”; not verified execution.

  4. 04
    Action

    Step 2: Detect Impossible Travel Anomalies

    Source-described action candidate under “Step 2: Detect Impossible Travel Anomalies”; not verified execution.

  5. 05
    Action

    Step 3: Detect Brute Force and Password Spraying

    Source-described action candidate under “Step 3: Detect Brute Force and Password Spraying”; not verified execution.

  6. 06
    Action

    Step 4: Build Behavioral Baselines and Detect Deviations

    Source-described action candidate under “Step 4: Build Behavioral Baselines and Detect Deviations”; not verified execution.

Inspect all extracted workflow candidates (20 candidate steps)
  1. 07
    Action

    Create user behavioral profiles and flag statistical anomalies:

    Source-described action candidate under “Step 4: Build Behavioral Baselines and Detect Deviations”; not verified execution.

  2. 08
    Action

    Step 5: Implement SIEM Detection Rules

    Source-described action candidate under “Step 5: Implement SIEM Detection Rules”; not verified execution.

  3. 09
    Action

    Step 6: Correlate and Score Authentication Anomalies

    Source-described action candidate under “Step 6: Correlate and Score Authentication Anomalies”; not verified execution.

  4. 10
    Action

    Key Concepts

    Source-described action candidate under “Key Concepts”; not verified execution.

  5. 11
    Action

    Tools & Systems

    Source-described action candidate under “Tools & Systems”; not verified execution.

  6. 12
    Action

    Common Scenarios

    Source-described action candidate under “Common Scenarios”; not verified execution.

  7. 13
    Action

    Run password spray detection across the timeframe to identify all targeted accounts

    Source-described action candidate under “Scenario: Detecting Compromised Executive Account After Password Spray”; not verified execution.

  8. 14
    Action

    Cross-reference targeted accounts with subsequent successful logins from related IP ranges

    Source-described action candidate under “Scenario: Detecting Compromised Executive Account After Password Spray”; not verified execution.

  9. 15
    Action

    Build behavioral baseline for the executive account and flag all deviations

    Source-described action candidate under “Scenario: Detecting Compromised Executive Account After Password Spray”; not verified execution.

  10. 16
    Action

    Check for impossible travel between the executive's last legitimate login and the attacker's session

    Source-described action candidate under “Scenario: Detecting Compromised Executive Account After Password Spray”; not verified execution.

  11. 17
    Action

    Identify post-compromise activity: mailbox rules, file downloads, delegated access changes

    Source-described action candidate under “Scenario: Detecting Compromised Executive Account After Password Spray”; not verified execution.

  12. 18
    Action

    Calculate composite risk score combining password spray, new IP, off-hours login, and new device signals

    Source-described action candidate under “Scenario: Detecting Compromised Executive Account After Password Spray”; not verified execution.

  13. 19
    Action

    Trigger automated response: force session termination, disable account, notify manager

    Source-described action candidate under “Scenario: Detecting Compromised Executive Account After Password Spray”; not verified execution.

  14. 20
    Output

    Output Format

    Source-described output candidate under “Output Format”; not verified execution.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

Attention recommended

59 deterministic lexical finding(s) require review across the collected text. Findings can occur in documentation and do not prove execution or exploitability; binary-only files were not scanned.

Network accessObserved
File writesObserved
Credential useNot observed
Medium

Network access is mentioned

6 occurrences

A URL or network client appears in this source line. Review destinations, data sent, and trust boundaries; static text cannot establish actual network activity. This rule matched 6 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Note

File modification is described or implemented

51 occurrences

This line contains a possible file-write or redirection operation. Check destination paths and overwrite behavior; the static review did not write any file. This rule matched 51 location(s) in the collected text; 3 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

High

Dynamic command execution is referenced

2 occurrences

A shell, dynamic evaluation, or process execution primitive appears here. Inspect arguments and input control. Presence in source does not prove a command ran. This rule matched 2 location(s) in the collected text; 2 representative location(s) are cited. Matching text may be documentation, and the analyzer did not execute it.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
Inspect the pinned source at https://github.com/mukul975/Anthropic-Cybersecurity-Skills/blob/54a798831d2266a3ca61ce68a7acb80b81160d57/skills/detecting-anomalous-authentication-patterns/SKILL.md and follow the source repository's installation instructions. No installation was performed or verified by this static analyzer. Source license: Apache-2.0.

Prerequisites

  • Static analysis cannot assess runtime behavior, command success, network reachability, or model output quality.
  • No commands, scripts, network requests, model calls, or controlled skill executions were performed.
  • Category, tags, capabilities, workflows, and bilingual editorial summaries are deterministic candidates pending human review, not verified outcomes.
  • Exact token counts are unavailable until a later pipeline performs and records an official model-specific count.

Example prompts

Not provided

A decision, with its limits attached

Strengths

  • The snapshot contains 4 collected file(s), 2 Markdown file(s), and 1 script file(s), enabling source-level inspection. [Evidence: skills/detecting-anomalous-authentication-patterns/SKILL.md:L1]

Considerations

  • No functional, security, or model-quality result has been established. Human review must inspect source context and all cited findings before installation or publication.
Research conclusion

Provisional deterministic static inventory only; pending human editorial review and, separately, controlled evaluation. No install recommendation, security assurance, or effectiveness claim is made.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

mukul975Anthropic-Cybersecurity-Skillsskills/detecting-anomalous-authentication-patterns
Source type
Community
Commit
54a798831d2266a3ca61ce68a7acb80b81160d57
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
Apache-2.0
Repository stars
36,446
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.