Implementing Hardware Security Key Authentication
Overview
Cybersecurity skill for implementing hardware security key authentication. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"implementing hardware security key authentication"
"Implements FIDO2/WebAuthn hardware security key authentication including registr"
Deploying phishing-resistant multi-factor authentication (MFA) using FIDO2 hardware security keys for high-value accounts (administrators, developers, privileged users)
Building a WebAuthn relying party server that supports both roaming authenticators (USB/NFC security keys) and platform authenticators (Windows Hello, Touch ID, Android biometrics)
Migrating an existing password-based authentication system to support passkeys (discoverable credentials) as a primary or secondary authentication factor
Enrolling YubiKey devices for an organization's workforce, including PIN setup, credential registration, and backup key provisioning
Implementing passwordless authentication flows that comply with NIST SP 800-63B AAL3 (authenticator assurance level 3) requirements
Do not use without HTTPS in production (WebAuthn requires a secure origin), for systems where users cannot physically access a USB/NFC port, or as the sole authentication factor without a recovery mechanism for lost keys.
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Python 3.10+ with
fido2 (python-fido2 >= 2.0.0), flask, and cryptography libraries installed
- HTTPS-enabled web server (WebAuthn API requires secure context; localhost is exempt for development)
- FIDO2-compatible hardware security key (YubiKey 5 Series, SoloKeys, Titan Security Key) or platform authenticator
- Modern web browser supporting the WebAuthn API (Chrome 67+, Firefox 60+, Safari 14+, Edge 79+)
- Understanding of public key cryptography, challenge-response protocols, and HTTP session management
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Assess Requirements — Evaluate current environment and define hardware security key authentication implementation requirements.
- Design Architecture — Plan the hardware security key authentication architecture, including components, integrations, and data flows.
- Configure Components — Set up and configure each hardware security key authentication component according to best practices.
- Test Integration — Validate that all components work together. Run functional and security tests.
- Deploy to Production — Roll out the implementation with monitoring and rollback capabilities.
- Validate and Document — Verify the implementation meets requirements. Document configuration and runbooks.
Tools
- Configuration Management — Infrastructure as code and automation
- Monitoring Stack — Observability and alerting
- Documentation Platform — Runbooks and architecture docs
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: implementing-hardware-security-key-authentication3description: Use when implements FIDO2/WebAuthn hardware security key authentication4 including registration ceremonies, authentication flows, YubiKey enrollment, and5 passkey migration strategies. Builds a complete relying party server using the python-fido26 library that supports cross-platform authenticators, resident key (discoverable7 credential) workflows, and user verification policies. Use when working with implementing8 hardware security key authentication.9domain: cybersecurity10tags:11- FIDO212- WebAuthn13- hardware-security-key14- YubiKey15- passkeys16- passwordless-authentication17- CTAP218subdomain: identity-and-access-management19version: 1.0.020author: oyi7721license: Apache-2.022atlas_techniques:23- AML.T005124- AML.T005425- AML.T005626nist_ai_rmf:27- MEASURE-2.728- MEASURE-2.529- GOVERN-6.130- MAP-5.131nist_csf:32- PR.AA-0133- PR.AA-0234- PR.AA-0535category: cybersecurity36metadata:37 source: https://skillmd.com/skills/oyi77/implementing-hardware-security-key-authentication38---3940# Implementing Hardware Security Key Authentication4142## Overview4344Cybersecurity skill for implementing hardware security key authentication. Follows industry best practices and security standards.4546## When to Use47**Trigger phrases:**48- "implementing hardware security key authentication"49- "Implements FIDO2/WebAuthn hardware security key authentication including registr"505152- Deploying phishing-resistant multi-factor authentication (MFA) using FIDO2 hardware security keys for high-value accounts (administrators, developers, privileged users)53- Building a WebAuthn relying party server that supports both roaming authenticators (USB/NFC security keys) and platform authenticators (Windows Hello, Touch ID, Android biometrics)54- Migrating an existing password-based authentication system to support passkeys (discoverable credentials) as a primary or secondary authentication factor55- Enrolling YubiKey devices for an organization's workforce, including PIN setup, credential registration, and backup key provisioning56- Implementing passwordless authentication flows that comply with NIST SP 800-63B AAL3 (authenticator assurance level 3) requirements5758**Do not use** without HTTPS in production (WebAuthn requires a secure origin), for systems where users cannot physically access a USB/NFC port, or as the sole authentication factor without a recovery mechanism for lost keys.596061## When NOT to Use6263- When you lack proper authorization for testing64- For production systems without change management65- When the task requires legal or compliance expertise beyond technical scope666768## Prerequisites6970- Python 3.10+ with `fido2` (python-fido2 >= 2.0.0), `flask`, and `cryptography` libraries installed71- HTTPS-enabled web server (WebAuthn API requires secure context; localhost is exempt for development)72- FIDO2-compatible hardware security key (YubiKey 5 Series, SoloKeys, Titan Security Key) or platform authenticator73- Modern web browser supporting the WebAuthn API (Chrome 67+, Firefox 60+, Safari 14+, Edge 79+)74- Understanding of public key cryptography, challenge-response protocols, and HTTP session management7576## Workflow7778```python79# Example: IOC detection80import re8182IOC_PATTERNS = {83 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",84 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",85 "hash_md5": r"\b[a-f0-9]{32}\b",86 "hash_sha256": r"\b[a-f0-9]{64}\b",87}8889def extract_iocs(text: str) -> dict:90 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}91```92931. **Assess Requirements** — Evaluate current environment and define hardware security key authentication implementation requirements.942. **Design Architecture** — Plan the hardware security key authentication architecture, including components, integrations, and data flows.953. **Configure Components** — Set up and configure each hardware security key authentication component according to best practices.964. **Test Integration** — Validate that all components work together. Run functional and security tests.975. **Deploy to Production** — Roll out the implementation with monitoring and rollback capabilities.986. **Validate and Document** — Verify the implementation meets requirements. Document configuration and runbooks.99100## Tools101102- **Configuration Management** — Infrastructure as code and automation103- **Monitoring Stack** — Observability and alerting104- **Documentation Platform** — Runbooks and architecture docs105106107## Process1081091. **Reconnaissance** — Gather target information, identify attack surface, enumerate services1101. **Analysis/Exploitation** — Execute the technique, analyze results, document findings1111. **Reporting** — Document IOCs, write findings, provide remediation recommendations112113## Verification114115- [ ] All hardware security key authentication procedures executed completely and documented116- [ ] Findings validated against multiple data sources117- [ ] False positives identified and filtered118- [ ] Results documented with evidence and timestamps119- [ ] Recommendations provided with risk-based prioritization120121## Anti-Rationalization Table122123| Rationalization | Reality |124|---|---|125| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |126| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |127| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |