Back to catalog
Static reviewDevelopment

Skill dossier

implementing-hardware-security-key-authentication

Source declaration

Builds a FIDO2/WebAuthn relying party server with the python-fido2 library, covering registration and authentication ceremonies, YubiKey enrollment, resident key (discoverable credential/passkey) workflows, and user verification policies. Use when implementing phishing-resistant MFA with hardware security keys, building a WebAuthn relying party, enrolling YubiKeys for a workforce, or migrating password-based authentication to passkeys.

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

Builds a FIDO2/WebAuthn relying party server with the python-fido2 library, covering registration and authentication ceremonies, YubiKey enrollment, resident key (discoverable credential/passkey) workflows, and user verification policies. Use when implementing phishing-resistant MFA with hardware security keys, building a WebAuthn relying party, enrolling YubiKeys for a workforce, or migrating password-based authentication to passkeys.

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.

Builds a FIDO2/WebAuthn relying party server with the python-fido2 library, covering registration and authentication ceremonies, YubiKey enrollment, resident key (discoverable credential/passkey) workflows, and user verification policies. Use when implementing phishing-resistant MFA with hardware security keys, building a WebAuthn relying party, enrolling YubiKeys for a workforce, or migrating password-based authentication to passkeys. 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-hardware-security-key-authentication/SKILL.md:L64]
  • Step 1: Relying Party Server Configuration [Source statement; provisional, not tested. Evidence: skills/implementing-hardware-security-key-authentication/SKILL.md:L66]
  • Step 2: Registration Ceremony (Credential Creation) [Source statement; provisional, not tested. Evidence: skills/implementing-hardware-security-key-authentication/SKILL.md:L80]
  • Step 3: Authentication Ceremony (Assertion) [Source statement; provisional, not tested. Evidence: skills/implementing-hardware-security-key-authentication/SKILL.md:L95]
  • Step 4: YubiKey Enrollment and Management [Source statement; provisional, not tested. Evidence: skills/implementing-hardware-security-key-authentication/SKILL.md:L105]
  • Step 5: Passkey Migration Strategy [Source statement; provisional, not tested. Evidence: skills/implementing-hardware-security-key-authentication/SKILL.md:L115]

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-hardware-security-key-authentication/SKILL.md:L1-L43]

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

File inventory

PathTypeBytes
skills/implementing-hardware-security-key-authentication/LICENSEOther11 KB
skills/implementing-hardware-security-key-authentication/references/api-reference.mdReference6.3 KB
skills/implementing-hardware-security-key-authentication/scripts/agent.pyScript37.9 KB
skills/implementing-hardware-security-key-authentication/SKILL.mdInstruction17.5 KB

SKILL.md frontmatter

{
  "name": "implementing-hardware-security-key-authentication",
  "description": "Builds a FIDO2/WebAuthn relying party server with the python-fido2 library, covering registration and authentication ceremonies, YubiKey enrollment, resident key (discoverable credential/passkey) workflows, and user verification policies. Use when implementing phishing-resistant MFA with hardware security keys, building a WebAuthn relying party, enrolling YubiKeys for a workforce, or migrating password-based authentication to passkeys.\n",
  "domain": "cybersecurity",
  "subdomain": "identity-and-access-management",
  "tags": [
    "FIDO2",
    "WebAuthn",
    "hardware-security-key",
    "YubiKey",
    "passkeys",
    "passwordless-authentication",
    "CTAP2"
  ],
  "version": "1.0.0",
  "author": "mukul975",
  "license": "Apache-2.0",
  "atlas_techniques": [
    "AML.T0051",
    "AML.T0054",
    "AML.T0056"
  ],
  "nist_ai_rmf": [
    "MEASURE-2.7",
    "MEASURE-2.5",
    "GOVERN-6.1",
    "MAP-5.1"
  ],
  "nist_csf": [
    "PR.AA-01",
    "PR.AA-02",
    "PR.AA-05"
  ],
  "mitre_attack": [
    "T1078",
    "T1190",
    "T1059",
    "T1003",
    "T1110"
  ]
}

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: Relying Party Server Configuration

    Source-described action candidate under “Step 1: Relying Party Server Configuration”; not verified execution.

  4. 04
    Output

    Define RP identity: Create a `PublicKeyCredentialRpEntity` with the relying party name (display name shown to users) and RP ID (the effective domain of the application). The RP ID must be a registrable domain suffix of the origin -- for example, `example.com` is valid for `https://auth.example.com` but `other.com` is not.

    Source-described output candidate under “Step 1: Relying Party Server Configuration”; not verified execution.

  5. 05
    Action

    Initialize Fido2Server: Instantiate the `Fido2Server` class from the python-fido2 library with the RP entity. The server handles challenge generation, attestation verification, and assertion validation.

    Source-described action candidate under “Step 1: Relying Party Server Configuration”; not verified execution.

  6. 06
    Decision

    Configure attestation preference: Set the attestation conveyance preference to control whether the server requests proof of the authenticator's identity:

    Source-described decision candidate under “Step 1: Relying Party Server Configuration”; not verified execution.

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

    `none`: No attestation requested (simplest, recommended for most deployments)

    Source-described action candidate under “Step 1: Relying Party Server Configuration”; not verified execution.

  2. 08
    Input

    `indirect`: Attestation may be provided but CA may anonymize it

    Source-described input candidate under “Step 1: Relying Party Server Configuration”; not verified execution.

  3. 09
    Action

    `direct`: Full attestation chain from the authenticator's manufacturer

    Source-described action candidate under “Step 1: Relying Party Server Configuration”; not verified execution.

  4. 10
    Action

    `enterprise`: Device-identifying attestation for managed environments

    Source-described action candidate under “Step 1: Relying Party Server Configuration”; not verified execution.

  5. 11
    Action

    Session management: Configure server-side sessions to store WebAuthn state between the begin and complete phases of registration/authentication ceremonies. Use secure, httponly cookies with SameSite=Strict.

    Source-described action candidate under “Step 1: Relying Party Server Configuration”; not verified execution.

  6. 12
    Action

    Credential storage: Design the database schema to store credential records: `credentialid` (binary), `publickey` (COSE key), `signcount` (uint32 for clone detection), `userid`, `createdat`, `lastused`, `displayname`, and `transports` (USB, NFC, BLE, internal).

    Source-described action candidate under “Step 1: Relying Party Server Configuration”; not verified execution.

  7. 13
    Action

    Step 2: Registration Ceremony (Credential Creation)

    Source-described action candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  8. 14
    Output

    Begin registration: Call `server.registerbegin()` with the user entity (`PublicKeyCredentialUserEntity` containing user ID, username, and display name), the list of existing credentials for the user (to prevent duplicate registration), and options for `userverification` and `authenticatorattachment`.

    Source-described output candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  9. 15
    Action

    Authenticator selection criteria:

    Source-described action candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  10. 16
    Action

    `authenticatorattachment: cross-platform` restricts to roaming authenticators (USB/NFC keys)

    Source-described action candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  11. 17
    Action

    `authenticatorattachment: platform` restricts to built-in authenticators (Touch ID, Windows Hello)

    Source-described action candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  12. 18
    Action

    Omitting this field allows both types

    Source-described action candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  13. 19
    Action

    `residentkey: required` forces creation of a discoverable credential (passkey) stored on the authenticator

    Source-described action candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  14. 20
    Action

    `userverification: required` enforces PIN or biometric verification on the authenticator

    Source-described action candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  15. 21
    Action

    Client-side ceremony: The browser calls `navigator.credentials.create()` with the options from the server. The authenticator generates a new key pair, stores the private key in its secure element, and returns the public key, credential ID, attestation object, and client data JSON.

    Source-described action candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  16. 22
    Action

    Complete registration: Call `server.registercomplete()` with the saved state and the client response. The server verifies the attestation signature, extracts the credential public key and ID, and returns `AuthenticatorData` containing the credential data to store.

    Source-described action candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  17. 23
    Action

    Store credential: Persist the `credentialdata` (contains `credentialid`, `publickey` as COSE key, and `signcount`) to the database associated with the user account.

    Source-described action candidate under “Step 2: Registration Ceremony (Credential Creation)”; not verified execution.

  18. 24
    Action

    Step 3: Authentication Ceremony (Assertion)

    Source-described action candidate under “Step 3: Authentication Ceremony (Assertion)”; not verified execution.

  19. 25
    Action

    Begin authentication: Call `server.authenticatebegin()` with the list of registered credentials for the user (or omit for discoverable credential flows where the authenticator identifies the user). Set `userverification` based on the assurance level required.

    Source-described action candidate under “Step 3: Authentication Ceremony (Assertion)”; not verified execution.

  20. 26
    Decision

    Client-side assertion: The browser calls `navigator.credentials.get()` with the server options. The authenticator locates the matching credential, performs user verification if required, increments the signature counter, and signs the challenge with the private key.

    Source-described decision candidate under “Step 3: Authentication Ceremony (Assertion)”; not verified execution.

  21. 27
    Action

    Complete authentication: Call `server.authenticatecomplete()` with the saved state, registered credentials, and the client response. The server verifies the assertion signature against the stored public key and validates the signature counter has incremented (clone detection).

    Source-described action candidate under “Step 3: Authentication Ceremony (Assertion)”; not verified execution.

  22. 28
    Decision

    Update sign count: After successful authentication, update the stored `signcount` for the credential. If the new sign count is not greater than the stored value, the key may have been cloned -- flag this as a security event.

    Source-described decision candidate under “Step 3: Authentication Ceremony (Assertion)”; not verified execution.

  23. 29
    Action

    Discoverable credential flow: For passwordless authentication, the user does not need to enter a username first. The authenticator presents all discoverable credentials for the RP ID, and the selected credential's `userHandle` identifies the user.

    Source-described action candidate under “Step 3: Authentication Ceremony (Assertion)”; not verified execution.

  24. 30
    Action

    Step 4: YubiKey Enrollment and Management

    Source-described action candidate under “Step 4: YubiKey Enrollment and Management”; not verified execution.

  25. 31
    Action

    PIN initialization: Before first use, a YubiKey requires a FIDO2 PIN (minimum 4 characters, 8 retries before lockout). Guide users through PIN setup using the Yubico Authenticator application or programmatically via the CTAP2 `clientPin` command.

    Source-described action candidate under “Step 4: YubiKey Enrollment and Management”; not verified execution.

  26. 32
    Action

    Primary key enrollment: Register the user's primary YubiKey with their account. Store the credential with a user-friendly label (e.g., "USB-A YubiKey - Office") and the authenticator's AAGUID for device identification.

    Source-described action candidate under “Step 4: YubiKey Enrollment and Management”; not verified execution.

  27. 33
    Action

    Backup key enrollment: Require users to register at least two security keys. The backup key should be stored separately (home, safety deposit box). Both keys must be registered to the same account so either can authenticate.

    Source-described action candidate under “Step 4: YubiKey Enrollment and Management”; not verified execution.

  28. 34
    Action

    Key attestation verification: For enterprise deployments, verify the attestation certificate chain to confirm the key is a genuine YubiKey from Yubico. Compare the AAGUID against Yubico's published values to identify the exact model.

    Source-described action candidate under “Step 4: YubiKey Enrollment and Management”; not verified execution.

  29. 35
    Action

    Key lifecycle management: Implement administrative functions to list a user's registered keys, revoke compromised keys, force re-enrollment, and audit key usage patterns (last authentication time, total authentications).

    Source-described action candidate under “Step 4: YubiKey Enrollment and Management”; not verified execution.

  30. 36
    Action

    Step 5: Passkey Migration Strategy

    Source-described action candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  31. 37
    Action

    Phased rollout: Begin with voluntary passkey enrollment alongside existing password authentication. Track adoption metrics (percentage of users with passkeys, percentage of logins using passkeys vs. passwords).

    Source-described action candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  32. 38
    Output

    Credential upgrade flow: When a user authenticates with a password, prompt them to register a passkey. Present the WebAuthn registration dialog immediately after successful password login to minimize friction.

    Source-described output candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  33. 39
    Input

    Cross-device passkeys: Support synced passkeys (passkeys stored in platform credential managers like iCloud Keychain, Google Password Manager, or 1Password) for users who do not have hardware security keys. These provide phishing resistance without requiring dedicated hardware.

    Source-described input candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  34. 40
    Action

    Account recovery: Design recovery flows for users who lose all their security keys:

    Source-described action candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  35. 41
    Action

    Recovery codes generated at enrollment time (printed, stored in password manager)

    Source-described action candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  36. 42
    Action

    Supervised re-enrollment by an administrator after identity verification

    Source-described action candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  37. 43
    Action

    Temporary time-limited password login with mandatory key re-enrollment

    Source-described action candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  38. 44
    Action

    Never allow recovery via email or SMS alone, as these defeat the phishing resistance

    Source-described action candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  39. 45
    Action

    Password deprecation timeline: After passkey adoption exceeds the target threshold, enforce passkey-only authentication for high-privilege accounts first, then expand to all accounts. Maintain password as a fallback during the transition window.

    Source-described action candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  40. 46
    Action

    Monitoring and metrics: Track registration success rates, authentication failure rates (wrong key, timeout, cancelled), mean time to authenticate, and the ratio of passkey to password logins.

    Source-described action candidate under “Step 5: Passkey Migration Strategy”; not verified execution.

  41. 47
    Action

    Key Concepts

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

  42. 48
    Action

    Tools & Systems

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

  43. 49
    Action

    Common Scenarios

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

  44. 50
    Action

    Provision YubiKey 5 NFC keys (2 per developer: primary + backup) and distribute in tamper-evident packaging with initial PIN setup instructions

    Source-described action candidate under “Scenario: Deploying FIDO2 MFA for a Development Team”; not verified execution.

  45. 51
    Action

    Deploy the WebAuthn relying party server integrated with the company's SSO (OAuth 2.0 / OpenID Connect) provider, configured with `authenticatorattachment: cross-platform` and `userverification: required`

    Source-described action candidate under “Scenario: Deploying FIDO2 MFA for a Development Team”; not verified execution.

  46. 52
    Action

    Run enrollment sessions where each developer registers both keys to their account, with attestation verification confirming genuine YubiKey 5 NFC AAGUIDs

    Source-described action candidate under “Scenario: Deploying FIDO2 MFA for a Development Team”; not verified execution.

  47. 53
    Action

    Configure the SSO provider to require FIDO2 as the second factor for all developer accounts, with a 30-day grace period where TOTP remains available

    Source-described action candidate under “Scenario: Deploying FIDO2 MFA for a Development Team”; not verified execution.

  48. 54
    Output

    Implement a self-service portal for key management: view registered keys, register replacement keys, and report lost/stolen keys (which triggers immediate credential revocation and re-enrollment)

    Source-described output candidate under “Scenario: Deploying FIDO2 MFA for a Development Team”; not verified execution.

  49. 55
    Input

    After the grace period, disable TOTP for developer accounts. Monitor authentication logs for any fallback attempts and provide 1:1 support for remaining holdouts

    Source-described input candidate under “Scenario: Deploying FIDO2 MFA for a Development Team”; not verified execution.

  50. 56
    Action

    Achieve 100% FIDO2 adoption for the development team, reducing phishing risk to near-zero for production infrastructure access

    Source-described action candidate under “Scenario: Deploying FIDO2 MFA for a Development Team”; not verified execution.

  51. 57
    Action

    Implement WebAuthn with `residentkey: required` to create discoverable credentials that enable username-less login

    Source-described action candidate under “Scenario: Implementing Passwordless Login for a Customer-Facing Application”; not verified execution.

  52. 58
    Action

    Support both platform authenticators (Touch ID, Windows Hello, Android biometrics) and roaming authenticators (security keys) by omitting `authenticatorattachment`

    Source-described action candidate under “Scenario: Implementing Passwordless Login for a Customer-Facing Application”; not verified execution.

  53. 59
    Output

    Add a "Sign in with a passkey" button to the login page that triggers `navigator.credentials.get()` with an empty `allowCredentials` list, prompting the authenticator to present available passkeys

    Source-described output candidate under “Scenario: Implementing Passwordless Login for a Customer-Facing Application”; not verified execution.

  54. 60
    Action

    After successful passkey creation, prompt users to create a passkey on a second device for redundancy

    Source-described action candidate under “Scenario: Implementing Passwordless Login for a Customer-Facing Application”; not verified execution.

  55. 61
    Action

    Maintain password login as a fallback during the rollout period, with a persistent prompt encouraging passkey setup after each password login

    Source-described action candidate under “Scenario: Implementing Passwordless Login for a Customer-Facing Application”; not verified execution.

  56. 62
    Action

    Track metrics: passkey registration rate (target 30% in first quarter), passkey vs. password login ratio, authentication failure rates, and account takeover incidents

    Source-described action candidate under “Scenario: Implementing Passwordless Login for a Customer-Facing Application”; not verified execution.

  57. 63
    Action

    After 6 months, offer incentives (extended session duration, reduced CAPTCHA) for users who switch to passkey-only authentication

    Source-described action candidate under “Scenario: Implementing Passwordless Login for a Customer-Facing Application”; not verified execution.

  58. 64
    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

47 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

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

40 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 40 location(s) in the collected text; 3 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-hardware-security-key-authentication/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-hardware-security-key-authentication/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-hardware-security-key-authentication
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.