Back to catalog
Static reviewDevelopment

Skill dossier

implementing-passwordless-auth-with-microsoft-entra

Source declaration

Implements passwordless authentication using Microsoft Entra ID with FIDO2 security keys, Windows Hello for Business, Microsoft Authenticator passkeys, and certificate-based authentication to eliminate password-based attacks. Use when deploying passwordless sign-in, configuring FIDO2 passkeys, enforcing phishing-resistant MFA, or setting Microsoft Entra authentication method policies.

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

Implements passwordless authentication using Microsoft Entra ID with FIDO2 security keys, Windows Hello for Business, Microsoft Authenticator passkeys, and certificate-based authentication to eliminate password-based attacks. Use when deploying passwordless sign-in, configuring FIDO2 passkeys, enforcing phishing-resistant MFA, or setting Microsoft Entra authentication method policies.

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.

Implements passwordless authentication using Microsoft Entra ID with FIDO2 security keys, Windows Hello for Business, Microsoft Authenticator passkeys, and certificate-based authentication to eliminate password-based attacks. Use when deploying passwordless sign-in, configuring FIDO2 passkeys, enforcing phishing-resistant MFA, or setting Microsoft Entra authentication method policies. 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/implementing-passwordless-auth-with-microsoft-entra/SKILL.md:L86]
  • Step 1: Configure Authentication Methods Policy [Source statement; provisional, not tested. Evidence: skills/implementing-passwordless-auth-with-microsoft-entra/SKILL.md:L88]
  • Step 2: Configure Authentication Strength Conditional Access [Source statement; provisional, not tested. Evidence: skills/implementing-passwordless-auth-with-microsoft-entra/SKILL.md:L183]
  • Step 3: Deploy Windows Hello for Business via Intune [Source statement; provisional, not tested. Evidence: skills/implementing-passwordless-auth-with-microsoft-entra/SKILL.md:L262]
  • Step 4: Register FIDO2 Security Keys for Users [Source statement; provisional, not tested. Evidence: skills/implementing-passwordless-auth-with-microsoft-entra/SKILL.md:L324]
  • Step 5: Disable Legacy Authentication Methods [Source statement; provisional, not tested. Evidence: skills/implementing-passwordless-auth-with-microsoft-entra/SKILL.md:L403]
  • Step 6: Monitor Passwordless Adoption Metrics [Source statement; provisional, not tested. Evidence: skills/implementing-passwordless-auth-with-microsoft-entra/SKILL.md:L453]

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/implementing-passwordless-auth-with-microsoft-entra/SKILL.md:L1-L62]

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
42.9 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/implementing-passwordless-auth-with-microsoft-entra/LICENSEOther11 KB
skills/implementing-passwordless-auth-with-microsoft-entra/references/api-reference.mdReference2.4 KB
skills/implementing-passwordless-auth-with-microsoft-entra/scripts/agent.pyScript8.4 KB
skills/implementing-passwordless-auth-with-microsoft-entra/SKILL.mdInstruction21.1 KB

SKILL.md frontmatter

{
  "name": "implementing-passwordless-auth-with-microsoft-entra",
  "description": "Implements passwordless authentication using Microsoft Entra ID with FIDO2 security keys, Windows Hello for Business, Microsoft Authenticator passkeys, and certificate-based authentication to eliminate password-based attacks. Use when deploying passwordless sign-in, configuring FIDO2 passkeys, enforcing phishing-resistant MFA, or setting Microsoft Entra authentication method policies.\n",
  "domain": "cybersecurity",
  "subdomain": "identity-access-management",
  "tags": [
    "passwordless",
    "FIDO2",
    "passkeys",
    "Microsoft-Entra",
    "Windows-Hello",
    "phishing-resistant-MFA"
  ],
  "version": "1.0",
  "author": "mahipal",
  "license": "Apache-2.0",
  "nist_csf": [
    "PR.AA-01",
    "PR.AA-02",
    "PR.AA-05",
    "PR.AA-06"
  ],
  "mitre_attack": [
    "T1078",
    "T1110",
    "T1556",
    "T1098",
    "T1566"
  ],
  "mitre_f3": {
    "version": "1.1",
    "tactics": [
      "initial-access"
    ],
    "techniques": [
      {
        "id": "T1660",
        "name": "Phishing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1557",
        "name": "Adversary-in-the-Middle",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1110.004",
        "name": "Brute Force:  Credential Stuffing",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "T1111",
        "name": "Multi-Factor Authentication Interception",
        "tactic": "initial-access",
        "source": "attack"
      },
      {
        "id": "F1006",
        "name": "Account Takeover",
        "tactic": "initial-access",
        "source": "f3"
      },
      {
        "id": "F1004",
        "name": "Access with Stolen Session Cookie",
        "tactic": "initial-access",
        "source": "f3"
      }
    ]
  }
}

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: Configure Authentication Methods Policy

    Source-described action candidate under “Step 1: Configure Authentication Methods Policy”; not verified execution.

  4. 04
    Action

    Step 2: Configure Authentication Strength Conditional Access

    Source-described action candidate under “Step 2: Configure Authentication Strength Conditional Access”; not verified execution.

  5. 05
    Action

    Create Conditional Access policies requiring phishing-resistant authentication:

    Source-described action candidate under “Step 2: Configure Authentication Strength Conditional Access”; not verified execution.

  6. 06
    Action

    Step 3: Deploy Windows Hello for Business via Intune

    Source-described action candidate under “Step 3: Deploy Windows Hello for Business via Intune”; not verified execution.

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

    Step 4: Register FIDO2 Security Keys for Users

    Source-described action candidate under “Step 4: Register FIDO2 Security Keys for Users”; not verified execution.

  2. 08
    Action

    Step 5: Disable Legacy Authentication Methods

    Source-described action candidate under “Step 5: Disable Legacy Authentication Methods”; not verified execution.

  3. 09
    Action

    Step 6: Monitor Passwordless Adoption Metrics

    Source-described action candidate under “Step 6: Monitor Passwordless Adoption Metrics”; 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
    Output

    Phase 1 (Month 1-2): Enable FIDO2 and WHfB authentication methods in report-only Conditional Access

    Source-described output candidate under “Scenario: Enterprise-Wide Passwordless Migration”; not verified execution.

  8. 14
    Action

    Phase 2 (Month 2-3): Deploy WHfB to all managed Windows devices via Intune with Cloud Kerberos Trust

    Source-described action candidate under “Scenario: Enterprise-Wide Passwordless Migration”; not verified execution.

  9. 15
    Action

    Phase 3 (Month 3-5): Distribute FIDO2 security keys to executives, IT admins, and finance (highest-risk users first)

    Source-described action candidate under “Scenario: Enterprise-Wide Passwordless Migration”; not verified execution.

  10. 16
    Action

    Phase 4 (Month 5-8): Enable Authenticator passkeys for mobile-primary users and field workers

    Source-described action candidate under “Scenario: Enterprise-Wide Passwordless Migration”; not verified execution.

  11. 17
    Output

    Phase 5 (Month 8-10): Switch Conditional Access from report-only to enforced for phishing-resistant auth

    Source-described output candidate under “Scenario: Enterprise-Wide Passwordless Migration”; not verified execution.

  12. 18
    Action

    Phase 6 (Month 10-12): Disable SMS and voice call methods, block legacy authentication protocols

    Source-described action candidate under “Scenario: Enterprise-Wide Passwordless Migration”; not verified execution.

  13. 19
    Action

    Ongoing: Monitor adoption metrics, issue TAPs for stragglers, maintain break-glass accounts

    Source-described action candidate under “Scenario: Enterprise-Wide Passwordless Migration”; 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.

Items warrant review

15 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

14 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 14 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

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 1 location(s) in the collected text; 1 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/implementing-passwordless-auth-with-microsoft-entra/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/implementing-passwordless-auth-with-microsoft-entra/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/implementing-passwordless-auth-with-microsoft-entra
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.