Free tools Windows power users keep installed
One-click scans. No signup required.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Do not give an AI agent the private signing key. Keep the key in a hardware security module (HSM), managed key service, or dedicated signer, and let the agent request only a narrowly authorized signing operation. The signer—not the model’s instructions—must verify the caller, permitted key, operation, and request scope each time.
Why an agent should not hold a signing key
An agent’s tools and delegated permissions are part of its attack surface. Prompt injection, a compromised integration, or an ordinary workflow bug can cause an agent with excessive authority to take actions its operator did not intend. The Canadian Centre for Cyber Security and partner agencies recommend aligning agentic AI risks and mitigations with an organization’s existing security model and risk posture (Canadian Centre for Cyber Security guidance).
A private signing key can authorize messages, transactions, software, or other actions that relying systems trust. If the agent can read or export that key, a compromise of the agent process can become a compromise of every workflow that accepts signatures from it. Keeping key material outside the model context and ordinary agent process narrows that path, but it does not by itself make signing safe: an agent can still misuse an authorized signing endpoint unless the endpoint checks each request.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use a separate signing boundary
Separate the agent from the component that holds or uses the key. The agent submits a proposed signing task; a signer service or key-management boundary authenticates the agent, checks authorization, performs the operation, and returns only the result needed for the workflow. The private key should not appear in prompts, model memory, general-purpose agent-readable files, or ordinary environment variables.
#1 Best Overall
- POWERFUL SECURITY KEY: The Security Key C NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key C NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key C NFC via USB-C and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
- Identify the caller. Give each agent a distinct identity tied to an owner and workflow. Do not treat a shared credential as sufficient proof of which agent requested an operation.
- Check authority for every request. Validate the identity, allowed key, algorithm, operation, request scope, and any required human approval at runtime. Do not rely on the agent following an instruction such as “sign only safe requests.”
- Constrain the result. Return the signature or other cryptographic result the workflow requires, not key material or broader credentials.
- Verify before acting. The receiving system should verify the signature and apply its own policy before accepting the message or executing a downstream action.
For asynchronous messages, transport protections alone may not preserve integrity after a message enters a queue or event bus. AWS documents a pattern in which a sender signs with an asymmetric AWS KMS key and the receiver verifies before acting; it recommends separate keys for distinct trust zones and monitoring unexpected signing operations or volume spikes (AWS guidance on agent-to-agent communication).
Grant the least authority the workflow needs
Start by determining which workflows genuinely need signatures. Some may need only read access or a non-signing action. For signing workflows, scope permissions to the specific identity, task, key, algorithm, and operation. Require short-lived or just-in-time authority for high-impact operations where practical, and perform authorization checks at request time. NIST’s guidance on tokens and assertions is written for federal agencies and cloud service providers, so adapt it to the workload and jurisdiction rather than treating it as a universal mandate (NIST IR 8587).
Rank #2
- POWERFUL SECURITY KEY: The YubiKey 5C NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5C NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5C NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
- Assign a distinct identity and responsible owner to each agent.
- Deny unreviewed tools and integrations by default, then add only task-required access.
- Require a separate approval for irreversible or high-impact signing actions when the workflow warrants it.
- Use different keys across materially different trust zones so compromise in one zone does not automatically authorize actions in another.
- Review effective permissions regularly, including permissions inherited through tools, services, and delegated credentials.
Choose a key boundary that fits the workload
An HSM, managed key service, or dedicated signer can keep key material out of the agent process, but each has different operational and authorization characteristics. Compare options against the actual workflow rather than assuming that a particular device or cloud service provides safe authorization by itself.
| Decision point | What to establish |
|---|---|
| Key custody and export | Where keys are held, whether they can be exported, and who controls backup and recovery. |
| Request authorization | Which identities may request signing, and how finely permissions can restrict keys, algorithms, operations, and request scope. |
| Compatibility | Whether the required APIs, cryptographic algorithms, libraries, and workflow integrations are supported. |
| Audit and alerting | Whether requests, outcomes, identities, and unusual activity can be logged and monitored. |
| Operations | Who owns deployment, availability, rotation, recovery, and response to suspected misuse. |
| Trust boundaries and demand | Whether keys can be separated by zone and whether the service meets the workflow’s expected volume and latency needs. |
For a local or server-side hardware boundary, Yubico describes YubiHSM 2 as a USB-A HSM for key management and signing, with access controls, audit logging, and PKCS#11/SDK integration (YubiHSM 2 product information; YubiHSM 2 documentation). It is an implementation option for organizations able to operate and integrate the device, not a default fit for every deployment. A USB authentication key should not be treated as interchangeable with a general-purpose HSM.
Rank #3
- POWERFUL SECURITY KEY: The YubiKey 5 NFC is the most versatile physical passkey, protecting your digital life from phishing attacks. It ensures only you can access your accounts
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 NFC secures 100+ of your favorite accounts, including email, password managers, and more
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 NFC via USB and tap it, or tap it against your phone (NFC), to authenticate. No batteries, no internet connection, and no extra fees required
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it
- PRIMARY & SPARE KEYS: Just like having a spare house key, we recommend buying two YubiKeys - one for daily use and one as a spare. That way you’ll never get locked out of your accounts
Log activity and make revocation testable
Record enough context to reconstruct who requested a signature and what happened. Useful fields include the agent identity, effective scope, requested operation, key or resource, result, and correlation context linking the request to its workflow. Alert on signing operations that are unexpected for that identity, key, time, or volume. Logging is useful only if someone can review alerts and act on them.
Plan and test how to cut off authority during an incident. Microsoft’s agent security guidance emphasizes dedicated identities, reviewed permissions, logging, and tested revocation (Microsoft agent security guidance). Verify that operators can disable the agent, rotate its credentials, invalidate relevant tokens, and remove stale permissions—and confirm that the signer rejects requests afterward.
Rank #4
- POWERFUL SECURITY KEY: The Security Key NFC is the essential physical passkey for protecting your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with Google, Microsoft, and Apple. A single Security Key NFC secures 100 of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your Security Key NFC via USB-A and tap it, or tap it against your phone (NFC) to authenticate. No batteries, no internet connection, and no extra fees required.
- TRUSTED PASSKEY TECHNOLOGY: Uses the latest passkey standards (FIDO2/WebAuthn & FIDO U2F) but does not support One-Time Passwords. For complex needs, check out the YubiKey 5 Series.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
Implementation checklist
- Inventory workflows and identify which truly require signatures.
- Assign each signing agent a distinct identity and owner; remove unreviewed tools and integrations.
- Keep private keys out of prompts, model memory, ordinary environment variables, and general-purpose agent-readable files.
- Place signing behind an HSM, managed key service, or dedicated signer; restrict keys, algorithms, operations, and request scope.
- Authenticate and authorize every signing request, with additional approval for actions whose impact justifies it.
- Verify signatures before accepting instructions or taking downstream action.
- Separate keys across materially different trust zones and define rotation and recovery procedures.
- Log request identity, effective scope, operation, resource, result, and workflow correlation context; alert on unexpected operations or unusual volume.
- Test disabling the agent, rotating credentials, invalidating tokens, and removing permissions.
There is no established quantitative statistic in the cited material for AI-agent signing-key theft, agent compromise rates, or comparative HSM effectiveness. NIST and CISA reported nearly 250 individual comments from more than 20 contributors on NIST IR 8587; that is a feedback count, not an incident or effectiveness measure (NIST and CISA announcement).
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsQuick Recap
Best Value
- POWERFUL SECURITY KEY: The YubiKey 5 is a versatile physical passkey that protects your digital life from phishing attacks. It ensures only you can access your accounts.
- WORKS WITH 1000+ ACCOUNTS: Compatible with popular accounts like Google, Microsoft, and Apple. A single YubiKey 5 secures 100+ of your favorite accounts, including email, password managers, and more.
- FAST & CONVENIENT LOGIN: Plug in your YubiKey 5 via USB and tap it to authenticate. No batteries, no internet connection, and no extra fees required.
- MOST SECURE PASSKEY: Supports FIDO2/WebAuthn, FIDO U2F, Yubico OTP, OATH-TOTP/HOTP, Smart card (PIV), and OpenPGP. That means it’s versatile, working almost anywhere you need it.
- BUILT TO LAST: Made from tough, waterproof, and crush-resistant materials. Manufactured in Sweden and programmed in the USA with the highest security standards.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
