Establishing secure connection…Loading editor…Preparing document…

Security Yubikey Form

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

Security YubiKey Agreement

Agreement Date:

Parties

Recitals (Whereas)

WHEREAS, Provider is a supplier of hardware authentication tokens commonly known as YubiKey devices and associated provisioning, management, and support services; and

WHEREAS, Client desires to obtain YubiKey devices from Provider for the purpose of strengthening account authentication and protecting Client systems, and Provider agrees to issue, manage, and support such devices subject to the terms of this Agreement.

NOW, THEREFORE, in consideration of the mutual covenants set forth herein, the parties agree as follows.

Scope of Work

Provider will supply, configure, and deliver physical YubiKey devices and perform associated provisioning and administrative services as described below. Provider's obligations include secure initial configuration, recording device serial numbers, and providing documentation of assignment. Client is responsible for user training and enforcing the Client security policy referenced in Section 6.

Payment Terms

Client shall pay Provider the fees for devices, configuration, and services as set forth below. All fees are exclusive of applicable taxes unless otherwise stated.

Term and Termination

This Agreement commences on the Start Date and continues until the End Date unless earlier terminated pursuant to this Section.

Start Date:     End Date:

Confidentiality

Each party shall keep confidential all non-public information disclosed by the other party that is designated confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure ("Confidential Information"). Provider's Confidential Information includes device cryptographic material, provisioning credentials, and device inventory records. Confidential Information shall not be disclosed except to employees, contractors, or agents with a need to know who are bound by confidentiality obligations at least as protective as this Agreement.

By checking this box, Client acknowledges receipt of and agrees to comply with the confidentiality obligations set forth in this Agreement.

Security, Loss, and Revocation

Client is responsible for secure physical custody of assigned YubiKey devices and must report lost, stolen, or compromised devices to Provider immediately. Provider will assist with revocation and re-provisioning pursuant to Provider's procedures. Client acknowledges that reissuance of devices may incur additional fees as set forth in Payment Terms.

Limitation of Liability and Indemnification

Except for willful misconduct or gross negligence, neither party will be liable to the other for consequential, incidental, special, or punitive damages. Client shall indemnify and hold Provider harmless from claims arising from Client's misuse of devices, failure to follow instructions, or failure to promptly report loss or compromise.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the state of without regard to its choice of law rules.

Entire Agreement

This Agreement, together with any appendices and purchase orders expressly incorporated herein, constitutes the entire agreement between the parties regarding the subject matter and supersedes all prior agreements and understandings, whether written or oral.

Miscellaneous

Any amendments to this Agreement must be in writing and signed by authorized representatives of both parties. If any provision is found invalid, the remainder will continue in full force and effect.

Provider - Printed Name:

By:

Date:

Client - Printed Name:

By:

Date:

Enter text✕

What the Security Yubikey Form Is and when it’s used

The Security Yubikey Form is an administrative record used to issue, assign, and track YubiKey hardware authenticators for multifactor authentication and FIDO2/WebAuthn access. Typical uses include initial device issuance, replacement or decommissioning, transfer between employees, and recording device serial numbers and public-key associations. Organizations use the form to record authorizing manager approvals, device model and serial, user identity, and lifecycle actions so IT and security teams retain an audit-ready trail of who received which physical token and when.

Why a formal Security Yubikey Form matters

A standardized form centralizes device records, reduces risk of orphaned credentials, and documents authorization for issuing high-assurance authenticators. It supports accountability, simplifies audits, and helps enforce least-privilege device distribution.

Why a formal Security Yubikey Form matters

Primary users and stakeholders

Clear role separation on the form reduces misuse, speeds provisioning, and preserves an auditable chain of custody

  • IT / Security teams: maintain inventory, configure device policies, and revoke lost tokens when necessary
  • HR / Onboarding: trigger device issuance for new hires and record assignment in personnel files
  • Managers / Approvers: authorize issuance or replacement based on role and access requirements

Who can sign or approve device issuance

Issuing Manager

An authorized manager or supervisor who confirms the employee’s role and approves the security token issuance. The Issuing Manager should include printed name, title, and department; their approval documents authorization and the business need for elevated authentication.

IT Security Officer

The security officer or IAM administrator records device serials, binds public keys to user accounts, and certifies installation steps completed. This signature confirms technical provisioning and that the token meets corporate policy.

Essential fields to capture on the form

User Name: Full legal name
Employee ID: Company ID or payroll number
Device Model: Example: YubiKey 5 Series
Serial Number: Device serial or UID
Issue Date: MM/DD/YYYY
Approver: Name and signature

Step-by-step: completing the Security Yubikey Form

Follow these sequential steps to ensure accurate assignment, traceability, and policy compliance when issuing or returning a YubiKey.

  • 01
    Verify Identity: Confirm user identity against company ID
  • 02
    Record Device: Enter model and serial number
  • 03
    Assign Account: Bind public key to user account
  • 04
    Authorize & Sign: Manager and IT approve and date

Typical lifecycle actions recorded on the form

Document lifecycle events so IT, HR, and security have a complete history of device state changes and approvals.

  • Issuance: Device issued to user with recorded serial
  • Activation: Token bound to user credentials
  • Loss/Theft: Report, disable, and replace token
  • Return/Retire: Deprovision and log disposition

How digital completion and eSubmission typically work

Ensure the chosen platform supports audit trails, export formats, and secure storage aligned with your compliance needs.

  • Formats: PDF, DOCX, or HTML
  • Integrations: Identity systems, HRIS, ticketing
  • Authentication: Email, SSO, or MFA

Typical fields and workflow settings for online forms

Configure the online form fields and routing so issuance triggers are consistent and auditable.

Field Configuration
User Full Name Required text field
Serial Number Required, unique validation
Approver Role-based signer
Deprovision Action Conditional checkbox triggers ticket creation

Key risks and potential penalties for incomplete or incorrect forms

Unauthorized Access: Account compromise risk
Failed Audit: Regulatory scrutiny
HIPAA Violations: Possible fines and enforcement
Operational Disruption: Loss of access for users
Evidence Gaps: Inadequate incident response
Contract Risk: Noncompliance with vendor terms

Common mistakes to avoid when preparing the form

  • Omitting serial numbers or entering them incorrectly, which breaks inventory reconciliation
  • Failing to collect approver identity and signature, leaving issuance unauthorized
  • Not linking the device to the correct user account, causing orphaned credentials
  • Neglecting to log device return or destruction, inflating active inventory counts

Practical tips for accurate and efficient completion

Adopt these practices to reduce errors, accelerate provisioning, and maintain compliance.

Use standardized templates
A single template reduces variability and speeds data entry across departments.
Enable validation
Use input masks for serials and required-field checks to prevent omissions.
Record approvals electronically
E-signatures and audit trails provide tamper-evidence and speed reviews.
Integrate with IAM
Automate binding and deprovisioning to reduce manual workload.

Real-world examples of Security Yubikey Form use

These short examples show how different organizations record issuance and lifecycle events.

Tech Company

A software firm issued YubiKeys at onboarding to reduce phishing risk

  • Issued keys were logged with serials and approver signatures
  • The IT team automated account binding, enabling immediate access while preserving a searchable audit trail for compliance reviews.

Healthcare Clinic

A clinic required BAA-covered processes for tokens used with EHR access

  • Each issuance recorded patient-data access justification
  • Retention tied to HIPAA rules ensured records were available for six years for audits and incident response.

Timing considerations and processing expectations

Processing times depend on whether issuance is handled in-person or remotely and on platform automation levels.

In-Person Issuance:

Same-day processing if approver present

Remote Provisioning:

1–3 business days with automated workflows

Replacement for Loss:

Immediate suspension, replacement within 1–5 days

Audit Retrieval:

Depends on archive system; 24–72 hours typical

Retention Start:

Date of issuance triggers retention clock

Key milestones in device issuance and lifecycle

Track these sequential stages to ensure each device moves through provisioning, activation, and retirement with controls.

01

Request and Approval

Manager requests device and provides business justification

02

Provisioning

IT records serial and binds to account

03

Activation Verification

User tests authentication and confirms functionality

04

Return or Revocation

Device returned or disabled and disposition logged

eSignature platform comparison for digital completion and signing

Compare common eSignature vendors and key plan features relevant to completing and storing the Security Yubikey Form electronically.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Trial 7-day free trial Varies by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No cap 100 envelopes/user/year Varies Varies Varies

FAQs and common troubleshooting for the Security Yubikey Form

Answers to frequently asked operational, legal, and technical questions about completing or storing the form.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users