Back to catalog
Static reviewDevelopment

Skill dossier

configuring-multi-factor-authentication-with-duo

Source declaration

Deploys Cisco Duo multi-factor authentication across enterprise applications, VPN, RDP, and SSH access points, covering Duo Authentication Proxy setup, adaptive authentication policies, device trust assessment, and phishing-resistant WebAuthn/FIDO2 deployment aligned with NIST 800-63B AAL2/AAL3. Use when adding or hardening MFA for remote access, VPN, or privileged logins with Duo.

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

Deploys Cisco Duo multi-factor authentication across enterprise applications, VPN, RDP, and SSH access points, covering Duo Authentication Proxy setup, adaptive authentication policies, device trust assessment, and phishing-resistant WebAuthn/FIDO2 deployment aligned with NIST 800-63B AAL2/AAL3. Use when adding or hardening MFA for remote access, VPN, or privileged logins with Duo.

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.

Deploys Cisco Duo multi-factor authentication across enterprise applications, VPN, RDP, and SSH access points, covering Duo Authentication Proxy setup, adaptive authentication policies, device trust assessment, and phishing-resistant WebAuthn/FIDO2 deployment aligned with NIST 800-63B AAL2/AAL3. Use when adding or hardening MFA for remote access, VPN, or privileged logins with Duo. 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/configuring-multi-factor-authentication-with-duo/SKILL.md:L84]
  • Step 1: Duo Authentication Proxy Setup [Source statement; provisional, not tested. Evidence: skills/configuring-multi-factor-authentication-with-duo/SKILL.md:L86]
  • Step 2: VPN MFA Integration [Source statement; provisional, not tested. Evidence: skills/configuring-multi-factor-authentication-with-duo/SKILL.md:L93]
  • Step 3: RDP/Windows Logon MFA [Source statement; provisional, not tested. Evidence: skills/configuring-multi-factor-authentication-with-duo/SKILL.md:L100]
  • Step 4: Adaptive Policy Configuration [Source statement; provisional, not tested. Evidence: skills/configuring-multi-factor-authentication-with-duo/SKILL.md:L107]
  • Step 5: Phishing-Resistant MFA Deployment [Source statement; provisional, not tested. Evidence: skills/configuring-multi-factor-authentication-with-duo/SKILL.md:L119]
  • Step 6: Monitoring and Response [Source statement; provisional, not tested. Evidence: skills/configuring-multi-factor-authentication-with-duo/SKILL.md:L126]

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/configuring-multi-factor-authentication-with-duo/SKILL.md:L1-L32]

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
8
Markdown files
5
scripts
2
references
4
Size
39 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/configuring-multi-factor-authentication-with-duo/assets/template.mdReference1.4 KB
skills/configuring-multi-factor-authentication-with-duo/LICENSEOther11 KB
skills/configuring-multi-factor-authentication-with-duo/references/api-reference.mdReference1.5 KB
skills/configuring-multi-factor-authentication-with-duo/references/standards.mdReference1.2 KB
skills/configuring-multi-factor-authentication-with-duo/references/workflows.mdReference1.6 KB
skills/configuring-multi-factor-authentication-with-duo/scripts/agent.pyScript4.7 KB
skills/configuring-multi-factor-authentication-with-duo/scripts/process.pyScript11.4 KB
skills/configuring-multi-factor-authentication-with-duo/SKILL.mdInstruction6.3 KB

SKILL.md frontmatter

{
  "name": "configuring-multi-factor-authentication-with-duo",
  "description": "Deploys Cisco Duo multi-factor authentication across enterprise applications, VPN, RDP, and SSH access points, covering Duo Authentication Proxy setup, adaptive authentication policies, device trust assessment, and phishing-resistant WebAuthn/FIDO2 deployment aligned with NIST 800-63B AAL2/AAL3. Use when adding or hardening MFA for remote access, VPN, or privileged logins with Duo.",
  "domain": "cybersecurity",
  "subdomain": "identity-access-management",
  "tags": [
    "iam",
    "identity",
    "access-control",
    "authentication",
    "mfa",
    "duo",
    "multi-factor"
  ],
  "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": [
    "T1621",
    "T1110.004",
    "T1110.003",
    "T1078",
    "T1556.006"
  ]
}

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
    Action

    Overview

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

  2. 02
    Decision

    When to Use

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

  3. 03
    Action

    Objectives

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

  4. 04
    Action

    Key Concepts

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

  5. 05
    Action

    Security Keys (WebAuthn/FIDO2): Phishing-resistant, AAL3 capable

    Source-described action candidate under “Duo Authentication Methods (by security strength)”; not verified execution.

  6. 06
    Action

    Duo Verified Push: Requires code entry, resistant to MFA fatigue attacks

    Source-described action candidate under “Duo Authentication Methods (by security strength)”; not verified execution.

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

    Duo Push: Push notification to Duo Mobile app

    Source-described action candidate under “Duo Authentication Methods (by security strength)”; not verified execution.

  2. 08
    Action

    TOTP (Duo Mobile Passcode): Time-based one-time password

    Source-described action candidate under “Duo Authentication Methods (by security strength)”; not verified execution.

  3. 09
    Action

    Hardware Tokens: OTP from physical token

    Source-described action candidate under “Duo Authentication Methods (by security strength)”; not verified execution.

  4. 10
    Action

    SMS/Phone Call: Least secure, use only as fallback

    Source-described action candidate under “Duo Authentication Methods (by security strength)”; not verified execution.

  5. 11
    Action

    Workflow

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

  6. 12
    Action

    Step 1: Duo Authentication Proxy Setup

    Source-described action candidate under “Step 1: Duo Authentication Proxy Setup”; not verified execution.

  7. 13
    Action

    Deploy Duo Authentication Proxy on Windows/Linux server

    Source-described action candidate under “Step 1: Duo Authentication Proxy Setup”; not verified execution.

  8. 14
    Action

    Configure primary authentication (AD/LDAP or RADIUS)

    Source-described action candidate under “Step 1: Duo Authentication Proxy Setup”; not verified execution.

  9. 15
    Action

    Configure Duo API credentials (Integration Key, Secret Key, API Hostname)

    Source-described action candidate under “Step 1: Duo Authentication Proxy Setup”; not verified execution.

  10. 16
    Decision

    Set failmode (safe=deny if Duo unreachable, secure=allow)

    Source-described decision candidate under “Step 1: Duo Authentication Proxy Setup”; not verified execution.

  11. 17
    Action

    Test proxy connectivity to Duo cloud and AD

    Source-described action candidate under “Step 1: Duo Authentication Proxy Setup”; not verified execution.

  12. 18
    Action

    Step 2: VPN MFA Integration

    Source-described action candidate under “Step 2: VPN MFA Integration”; not verified execution.

  13. 19
    Action

    Configure VPN concentrator for RADIUS authentication

    Source-described action candidate under “Step 2: VPN MFA Integration”; not verified execution.

  14. 20
    Action

    Point RADIUS to Duo Authentication Proxy

    Source-described action candidate under “Step 2: VPN MFA Integration”; not verified execution.

  15. 21
    Action

    Configure Duo proxy with [radiusserverauto] section

    Source-described action candidate under “Step 2: VPN MFA Integration”; not verified execution.

  16. 22
    Action

    Test VPN login with Duo Push

    Source-described action candidate under “Step 2: VPN MFA Integration”; not verified execution.

  17. 23
    Action

    Deploy to all VPN users with enrollment period

    Source-described action candidate under “Step 2: VPN MFA Integration”; not verified execution.

  18. 24
    Action

    Step 3: RDP/Windows Logon MFA

    Source-described action candidate under “Step 3: RDP/Windows Logon MFA”; not verified execution.

  19. 25
    Action

    Install Duo Authentication for Windows Logon on target servers

    Source-described action candidate under “Step 3: RDP/Windows Logon MFA”; not verified execution.

  20. 26
    Action

    Configure Duo application in Admin Panel

    Source-described action candidate under “Step 3: RDP/Windows Logon MFA”; not verified execution.

  21. 27
    Action

    Set offline access options (allow N offline logins)

    Source-described action candidate under “Step 3: RDP/Windows Logon MFA”; not verified execution.

  22. 28
    Action

    Configure bypass for service accounts

    Source-described action candidate under “Step 3: RDP/Windows Logon MFA”; not verified execution.

  23. 29
    Action

    Test RDP login with Duo MFA

    Source-described action candidate under “Step 3: RDP/Windows Logon MFA”; not verified execution.

  24. 30
    Action

    Step 4: Adaptive Policy Configuration

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  25. 31
    Action

    Create user groups (Standard, Privileged, Contractors)

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  26. 32
    Action

    Configure per-group authentication policies:

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  27. 33
    Action

    Standard: Duo Push allowed, remembered device 7 days

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  28. 34
    Action

    Privileged: Verified Push required, no remembered device

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  29. 35
    Action

    Contractors: WebAuthn required, no remembered device

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  30. 36
    Action

    Configure device health policies:

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  31. 37
    Action

    Require encrypted disk

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  32. 38
    Action

    Block outdated OS versions

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  33. 39
    Action

    Require firewall enabled

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  34. 40
    Action

    Set trusted network exceptions for corporate IPs

    Source-described action candidate under “Step 4: Adaptive Policy Configuration”; not verified execution.

  35. 41
    Action

    Step 5: Phishing-Resistant MFA Deployment

    Source-described action candidate under “Step 5: Phishing-Resistant MFA Deployment”; not verified execution.

  36. 42
    Action

    Enable Verified Push (requires entering 3-digit code from login screen)

    Source-described action candidate under “Step 5: Phishing-Resistant MFA Deployment”; not verified execution.

  37. 43
    Action

    Register WebAuthn/FIDO2 security keys for privileged users

    Source-described action candidate under “Step 5: Phishing-Resistant MFA Deployment”; not verified execution.

  38. 44
    Action

    Disable SMS and phone call for high-risk groups

    Source-described action candidate under “Step 5: Phishing-Resistant MFA Deployment”; not verified execution.

  39. 45
    Action

    Configure Duo Risk-Based Factor Selection

    Source-described action candidate under “Step 5: Phishing-Resistant MFA Deployment”; not verified execution.

  40. 46
    Action

    Monitor for MFA fatigue attack patterns

    Source-described action candidate under “Step 5: Phishing-Resistant MFA Deployment”; not verified execution.

  41. 47
    Action

    Step 6: Monitoring and Response

    Source-described action candidate under “Step 6: Monitoring and Response”; not verified execution.

  42. 48
    Action

    Configure Duo Admin Panel alerts

    Source-described action candidate under “Step 6: Monitoring and Response”; not verified execution.

  43. 49
    Action

    Set up authentication log forwarding to SIEM

    Source-described action candidate under “Step 6: Monitoring and Response”; not verified execution.

  44. 50
    Action

    Monitor for: MFA denial patterns, bypass usage, new device enrollments

    Source-described action candidate under “Step 6: Monitoring and Response”; not verified execution.

  45. 51
    Action

    Create incident response playbook for MFA compromise

    Source-described action candidate under “Step 6: Monitoring and Response”; not verified execution.

  46. 52
    Action

    Regular review of bypass and exception policies

    Source-described action candidate under “Step 6: Monitoring and Response”; not verified execution.

  47. 53
    Action

    Security Controls

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

  48. 54
    Action

    Common Pitfalls

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

  49. 55
    Action

    Verification

    Source-described action candidate under “Verification”; 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

21 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

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

9 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 9 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/configuring-multi-factor-authentication-with-duo/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 8 collected file(s), 5 Markdown file(s), and 2 script file(s), enabling source-level inspection. [Evidence: skills/configuring-multi-factor-authentication-with-duo/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/configuring-multi-factor-authentication-with-duo
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.