Is notarization required for this form?

Generally no. The Access Security Duo Token Form is an internal authorization record and typically does not require notarization, but specific agencies or legal processes may request notarized acknowledgment for asset transfer or legal proof; follow organizational policy.

Can I complete and sign this form electronically?

Yes. Electronic signatures that meet the ESIGN Act (15 U.S.C. ch. 96) and state UETA requirements are acceptable where the organization permits them; ensure the chosen eSignature method captures intent, attribution, and retention.

How do I report a lost or stolen Duo token?

Immediately submit a completed form indicating loss or theft, notify IT or security, and decommission the token in Duo's management console to revoke access and document the incident for audit purposes.

Can tokens be reassigned between employees?

Reassignment is possible if approved and documented; record transfer details, approvals, and perform identity verification to maintain chain of custody and prevent unauthorized access.

How long should I keep completed forms?

Retain forms at least for operational needs and audits. Follow federal baselines—three years for many financial records (IRC §6501(a)) and six years if PHI applies (45 CFR §164.530(j)); consult records policy for longer state-specific periods.

Who to contact for approval or questions?

Contact your IT helpdesk or security administrator listed in the form's routing instructions; they can advise on identity verification, enrollment status in Duo, and required approvals for special cases.

Electronic Signature
Templates
Miscellaneous
Access Security Duo Token Form

Access Security Duo Token Form

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

ACCESS SECURITY DUO TOKEN FORM

WHEREAS

WHEREAS, Company Name: operates information systems that require multi-factor authentication to protect sensitive data and systems; and

WHEREAS, Recipient Name: requires an assigned Duo token (hardware or software) to access authorized systems in the performance of Recipient's duties;

NOW, THEREFORE, the parties agree to the terms below for issuance, use, maintenance, and return of the Duo authentication token.

REQUESTOR / RECIPIENT INFORMATION

Recipient Printed Name Employee / Contractor ID Department Job Title Business Email Work Phone

TOKEN DETAILS

Token Type: Hardware Token Software Token (mobile app)

Hardware Token Serial Number / Device ID Mobile Device Make / Model Mobile Phone Number Requested Activation Date

SCOPE OF WORK

Describe the specific access granted, systems covered, and permitted use of the Duo token. Include any limitations or special conditions.

ASSIGNMENT, USE, AND RESPONSIBILITIES

Recipient acknowledges receipt of the Duo token and accepts responsibility for safeguarding the token and any associated credentials. Disclosure of credentials to unauthorized persons is prohibited. Lost or compromised tokens must be reported immediately to Information Security.

Recipient Acceptance (check to acknowledge) I acknowledge receipt and accept responsibility for the issued token and for compliance with security policies.

PAYMENT TERMS

If a fee is assessed for issuance, replacement, or maintenance of a Duo token, the following payment provisions apply.

Payment Amount Payment Schedule / Method Late Fee

TERM AND TERMINATION

This Agreement commences on Start Date: and remains in effect until End Date: unless earlier terminated in accordance with this section.

Either party may terminate this Agreement for any reason upon providing written notice to the other party at least Notice Period (days):

Upon termination or separation of employment, Recipient must return any issued hardware token and ensure software tokens are removed from personal devices. Failure to return issued tokens may result in charges and revocation of access.

CONFIDENTIALITY

Recipient will treat authentication credentials, token serial numbers, and any incidental security configuration details as Confidential Information. Recipient will not disclose Confidential Information to third parties except as required for performance of job duties and only under conditions that protect confidentiality.

SECURITY, MONITORING, AND AUDIT

Recipient acknowledges that usage of corporate systems and authentication tokens may be monitored and audited for security and compliance. Recipient consents to such monitoring to the extent permitted by law.

INDEMNITY

Recipient agrees to indemnify and hold harmless Company from any loss or liability arising from Recipient's negligent or willful failure to safeguard the token or to comply with the terms of this Agreement.

GOVERNING LAW

This Agreement will be governed by and construed in accordance with the laws of the State of without regard to conflicts of law principles.

ENTIRE AGREEMENT

This document constitutes the entire agreement between the parties with respect to issuance and use of the Duo token and supersedes all prior agreements, understandings, and communications, whether written or oral, relating to the same subject matter.

APPROVALS / ADMINISTRATIVE USE

Request Reason Manager / Approver Printed Name Approver Signature Approver Date

Company Representative:

By:

Date:

Recipient:

By:

Date:

What the Access Security Duo Token Form Is

The Access Security Duo Token Form is a standardized request and authorization document used by organizations to issue, register, replace, or decommission Duo hardware tokens for multi-factor authentication. It records the requester identity, account or system affiliation, token serial number, issuance date, and approving administrator details. Completed forms provide an auditable chain of custody for tokens, support enrollment into Duo's MFA system, and serve as evidence for access reviews and internal security policy compliance across IT and security teams.

Why a Controlled Token Form Matters

Using a formal Access Security Duo Token Form centralizes approvals, documents custody, and records enrollment activity, which reduces unauthorized access risk and strengthens auditability for internal controls and regulatory reviews.

Who Completes and Keeps This Form

Organizations and individuals who request or manage Duo hardware tokens complete this form as part of access control workflows.

IT administrators managing MFA inventory, enrollments, token lifecycle records, and access revocation procedures across corporate systems.
HR or onboarding teams coordinating token issuance during new-hire setup, role changes, and exit processing with documented approvals.
Employees requesting replacements, reporting loss or theft, or authorizing token reassignment between company accounts or devices.

Typical users include enterprise IT teams, security administrators, HR or facilities staff, and employees requesting or returning MFA tokens.

Step-by-Step: From Request to Enrollment

Follow these steps to complete and process the Access Security Duo Token Form from request through enrollment and tracking.

01

Complete Request: Provide requester details, department, and reason for token.
02

Verify Identity: Confirm requester identity via corporate credentials or ID.
03

Assign Token: Record serial number, asset tag, and issuance date.
04

Enroll Token: Register the token in Duo and confirm successful authentication.

Typical Digital Workflow Configuration

Configure routing and authentication so requests flow cleanly from requester to approver and into enrollment systems.

Field	Configuration
Signer Authentication	Email link with optional SMS code verification
Approval Routing	Route to IT manager, then security lead for final approval
Token Tracking	Update central inventory record and asset management system
Retention Location	Store final PDF in secure document repository with restricted access

Where Completed Forms Go and Who Keeps Copies

After signing, distribute and retain copies according to role: IT retains originals for inventory, security keeps audit copies, and requester receives a confirmation.

IT Records: Central inventory copy retained for audits and reconciliation.
Security Team: Audit copy used for access reviews and incident response.
Requester: Recipient copy for personal records and verification.
HR or Employer: Onboarding/offboarding copy linked to personnel file.

Technical Requirements for Electronic Completion

Technical prerequisites for completing and storing the Access Security Duo Token Form electronically.

Supported Formats: PDF and DOCX accepted
Authentication Options: Email link, SMS code, or SSO
Common Integrations: Salesforce, Microsoft 365, NetSuite, Box

Typical eSignature Vendor Pricing and Features

Compare common plan and capability dimensions for eSignature platforms when you need digital signing and secure storage for token forms.

	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 by plan	Varies by plan	Varies by plan

Required Form Fields at a Glance

Requester Name: Full legal name required

Requester ID: Company or employee ID

Department: Business unit or system name

Token Serial: Exact hardware serial number

Issue Date: MM/DD/YYYY format

Approver: Approver name and date

Consequences of Incomplete or Incorrect Forms

Unauthorized Access: Increased breach risk

Access Disruption: User locked out of systems

Audit Findings: Negative compliance review

Legal Exposure: Regulatory or contractual liability

Inventory Loss: Asset reconciliation gaps

Operational Delay: Delayed onboarding or support

Common Preparation Errors to Avoid

Leaving the token serial blank or transposed, which breaks the link between the physical device and the inventory record and complicates incident response.
Using informal or abbreviated names that do not match HR or identity provider records, causing enrollment and directory mapping failures.
Routing approvals through an incorrect chain or failing to capture approver identity, which undermines accountability and auditability.
Storing signed forms in unsecured locations or on personal devices, increasing the risk of unauthorized access and data exposure.

Practical Tips for Accurate and Efficient Processing

Adopt consistent controls and periodic reviews to keep token inventories accurate and reduce processing time.

Standardize Form Fields

Use a single validated template with required fields and dropdowns to eliminate free-text variation; enforce MM/DD/YYYY dates and exact serial formats to reduce manual reconciliation and data-entry errors.

Digitize with Strong Authentication

Enable email plus SMS or SSO authentication for signers, retain an audit trail for attribution, and use encrypted storage to meet security and compliance expectations.

Centralize Inventory and Reconciliation

Link form completion to your asset management system so issuance, returns, and lost-item reports automatically update inventory and reduce orphaned tokens.

Schedule Regular Audits

Perform periodic reconciliations between HR, IAM, and token inventories and document findings to demonstrate control effectiveness to internal and external auditors.

Illustrative Examples from Practice

Real-world examples show how organizations use a controlled token form to speed onboarding and maintain compliance with audit requirements.

Optica Ventures

Optica standardized token issuance across distributed teams to reduce confusion and lost devices.

Streamlined enrollment and tracking.
"The interface is simple and easy-to-use for our team; more importantly, it is just as easy for our customers."

Martin Properties

A property management firm centralized token requests to ensure contractors received temporary access.

Reduced on-site delays.
"I can process and execute all of these documents online with 100% compliance and built-in security."

Frequently Asked Questions and Troubleshooting

Answers to common questions about execution, notarization, eSign use, lost tokens, and retention for the Access Security Duo Token Form.

Need help? Contact support

Is notarization required for this form?
Generally no. The Access Security Duo Token Form is an internal authorization record and typically does not require notarization, but specific agencies or legal processes may request notarized acknowledgment for asset transfer or legal proof; follow organizational policy.
Can I complete and sign this form electronically?
Yes. Electronic signatures that meet the ESIGN Act (15 U.S.C. ch. 96) and state UETA requirements are acceptable where the organization permits them; ensure the chosen eSignature method captures intent, attribution, and retention.
How do I report a lost or stolen Duo token?
Immediately submit a completed form indicating loss or theft, notify IT or security, and decommission the token in Duo's management console to revoke access and document the incident for audit purposes.
Can tokens be reassigned between employees?
Reassignment is possible if approved and documented; record transfer details, approvals, and perform identity verification to maintain chain of custody and prevent unauthorized access.
How long should I keep completed forms?
Retain forms at least for operational needs and audits. Follow federal baselines—three years for many financial records (IRC §6501(a)) and six years if PHI applies (45 CFR §164.530(j)); consult records policy for longer state-specific periods.
Who to contact for approval or questions?
Contact your IT helpdesk or security administrator listed in the form's routing instructions; they can advise on identity verification, enrollment status in Duo, and required approvals for special cases.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now