Establishing secure connection…Loading editor…Preparing document…

Retainer Addendum for MFA

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

RETainer ADDENDUM FOR MFA

This Retainer Addendum for Multi-Factor Authentication and Related Security Services ("Addendum") is made effective as of by and between Firm Name: and Client Name: (each a "Party" and collectively the "Parties").

RECITALS

WHEREAS, the Parties entered into a written retainer or engagement agreement dated (the "Retainer Agreement"); and

WHEREAS, the Parties desire to augment the Retainer Agreement with specific terms governing the implementation, maintenance and responsibilities relating to Multi-Factor Authentication ("MFA") and related authentication controls for access to systems, communications, and confidential materials; and

WHEREAS, the Parties intend that the security measures described herein be incorporated into the Retainer Agreement by reference to ensure protection of Confidential Information and reasonable operational safeguards.

NOW, THEREFORE

NOW, THEREFORE, in consideration of the mutual promises set forth below and other good and valuable consideration, the receipt and sufficiency of which are acknowledged, the Parties agree as follows:

1. SCOPE OF ADDENDUM

1.1 Purpose. This Addendum governs the selection, implementation, operation and maintenance of MFA controls for access to systems, portals, communications channels, file repositories and other services provided under the Retainer Agreement. The MFA measures described herein supplement and do not replace any technical, administrative or contractual safeguards otherwise required by the Retainer Agreement.

1.2 Applicability. This Addendum applies to all users granted access to services covered by the Retainer Agreement, including but not limited to Client personnel, representatives, consultants and any third-party users for whom access is provisioned by either Party.

2. MFA IMPLEMENTATION

2.1 Methods. The Parties agree that acceptable MFA methods include at least one of the following selected methods: .

2.2 Deployment. Firm shall deploy or configure MFA on systems under its control in accordance with industry-standard practices and the specific methods checked above. Implementation Start Date: . Any change to selected methods shall require written notice to the other Party in accordance with the Notices provision.

3. RESPONSIBILITIES

3.1 Client Obligations. Client shall: (a) ensure authorized users maintain accurate contact information and registered authentication devices; (b) not share MFA credentials or devices; (c) promptly report lost, stolen or suspected compromised authenticators to Firm; and (d) comply with Firm's reasonable policies for enrollment and re-enrollment.

3.2 Firm Obligations. Firm shall: (a) enable and maintain MFA configurations consistent with the selected methods; (b) provide reasonable enrollment and support for Client users; (c) maintain administrative controls to revoke access in case of compromise; and (d) log administrative changes to MFA settings for a period of not less than days.

4. FEES AND COSTS

4.1 MFA Fees. Client agrees to reimburse Firm for reasonable, documented costs associated with MFA hardware, licensing or third-party services where applicable. Estimated Fee Amount: . Billing Frequency: .

4.2 Expense Approval. Any single expense over requires prior written approval from Client's authorized representative.

5. CONFIDENTIALITY AND DATA SECURITY

5.1 Protection of Credentials. The Parties acknowledge that authentication credentials and related metadata constitute Confidential Information under the Retainer Agreement. Each Party shall protect such information with at least the same degree of care it uses to protect its own confidential information, but no less than reasonable care.

5.2 Data Handling. Any personally identifiable information collected in the enrollment or operation of MFA shall be processed and stored only for purposes necessary to provide the MFA services and in compliance with applicable law. Firm shall segregate authentication data from other client data where technologically feasible.

6. INCIDENT RESPONSE AND NOTIFICATION

6.1 Notification. In the event of a suspected compromise of MFA credentials or an incident affecting access controls, the discovering Party shall notify the other Party without unreasonable delay and, in any event, within hours of discovery of the incident.

6.2 Response. The Parties shall cooperate to investigate the incident, mitigate harm, revoke or re-issue credentials, and implement remediation measures as reasonably required. Costs of remediation shall be allocated as set forth in the Retainer Agreement unless caused by the gross negligence or willful misconduct of the responsible Party.

7. LIMITATION OF LIABILITY; INDEMNIFICATION

7.1 Limitation of Liability. Except for willful misconduct or gross negligence, neither Party shall be liable for indirect, incidental, special, punitive or consequential damages arising out of or related to the implementation or operation of MFA services under this Addendum, even if advised of the possibility of such damages.

7.2 Indemnification. Each Party shall indemnify, defend and hold harmless the other Party from and against any third-party claims arising from that Party's breach of this Addendum, negligence, willful misconduct, or violation of applicable law in connection with MFA implementation. The indemnifying Party shall have the right to control the defense and settlement of any claim, provided that no settlement shall admit liability or impose obligations on the indemnified Party without its prior written consent.

8. TERM AND TERMINATION

8.1 Term. This Addendum commences on the Effective Date and continues for the term of the Retainer Agreement unless earlier terminated in accordance with this Section.

8.2 Termination for Convenience. Either Party may terminate this Addendum for convenience upon days' prior written notice to the other Party. Termination shall not relieve Client of obligations to pay for services performed or expenses incurred prior to termination.

9. NOTICES

10. AMENDMENTS; WAIVER; COUNTERPARTS

10.1 Amendments. Any amendment or modification of this Addendum must be in writing and signed by authorized representatives of both Parties.

10.2 Waiver. Failure or delay by either Party to exercise any right shall not constitute a waiver of that right. A waiver is effective only if in writing and signed by the waiving Party.

10.3 Counterparts. This Addendum may be executed in counterparts, each of which shall be deemed an original and all of which together shall constitute one instrument.

11. GOVERNING LAW; ENTIRE AGREEMENT; SEVERABILITY

11.1 Governing Law. This Addendum shall be governed by and construed in accordance with the laws of the State of without regard to its conflict of laws principles.

11.2 Entire Agreement. This Addendum, together with the Retainer Agreement, constitutes the entire agreement between the Parties with respect to MFA and supersedes all prior and contemporaneous agreements and understandings related to the subject matter hereof.

11.3 Severability. If any provision of this Addendum is held invalid or unenforceable, the remaining provisions shall remain in full force and effect and the Parties shall negotiate in good faith a substitute provision that effectuates the original intent to the greatest extent permitted by law.

SIGNATURES

The Parties have executed this Addendum as of the dates set forth below.

Client:

By:

Date:

Firm:

By:

Date:

Enter text✕

What a Retainer Addendum for MFA Covers

A Retainer Addendum for MFA is a supplemental agreement attached to a professional services retainer that documents multi-factor authentication responsibilities, required security controls, and any fee adjustments tied to authentication. It identifies which party provides MFA tools, assigns costs for setup or recurring services, and defines incident response and access rules. The addendum is used with the principal retainer to remove ambiguity about who must implement, fund, and support MFA and to establish the effective date for authentication obligations.

Why Add MFA Terms to a Retainer

Documenting MFA expectations in a retainer addendum reduces disputes over security responsibilities and cost allocation, clarifies breach and access procedures, and creates contractual authority to enforce authentication requirements during the engagement.

Why Add MFA Terms to a Retainer

Who Typically Completes This Addendum

Service providers, outside vendors, and clients use this addendum to record MFA obligations, cost sharing, and operational rules under a retainer.

  • Law firms and legal service providers managing privileged access and client portals.
  • IT consultants and managed service providers responsible for implementing MFA controls.
  • Healthcare and financial vendors handling protected health or financial data under retainer.

When access to confidential systems or regulated data is involved, include stakeholders from legal, security, and billing to approve the addendum before execution.

Step-by-Step: How to Complete the Addendum

Follow these steps to complete and attach the Retainer Addendum for MFA to an existing retainer agreement.

  • 01
    Prepare Addendum: Use a clear template that references the primary retainer agreement.
  • 02
    Fill Fields: Complete required fields and verify names and dates against the retainer.
  • 03
    Obtain Signatures: Collect signatures and authentication evidence per ESIGN/UETA requirements.
  • 04
    Store Copies: Save executed copies and audit trails to secure records for retention.

Typical Routing After Execution

This routing overview shows common destinations and the documentation flow after completing the addendum promptly.

  • To Client: Provide executed copy to client and record delivery method in audit trail.
  • Internal Records: Save to secure document repository with access controls and retention tags.
  • Third-Party Vendor: Send to MFA vendor when contract names the provider for onboarding.
  • Compliance Officer: Notify compliance or security teams and attach the incident response section.

Configuring an Online Workflow for the Addendum

Configure online workflows to collect signatures, enforce authentication, and log audit data when completing the addendum.

Field Configuration
Authentication Method Select email, SMS OTP, or knowledge-based authentication.
Required Fields Full legal name, effective date, MFA provider, cost allocation.
Signature Settings Enable ESIGN/Ops consent and capture timestamp and IP.
Notifications Auto-email executed copies and notify security and billing teams.

Platform Capabilities to Verify Before e-Signing

Ensure your signing platform supports strong authentication, audit trails, and secure storage before collecting e-signatures for the addendum.

  • File Formats: PDF and Word DOCX supported.
  • Integrations: Connects with NetSuite and Salesforce.
  • Authentication: Supports SMS, email, and 2FA.

Key Dates to Record in the Addendum

Key dates associated with the Retainer Addendum for MFA include effective dates, implementation deadlines, and review or renewal windows.

Effective Date:

Date obligations begin; enter MM/DD/YYYY.

Implementation Deadline:

When MFA must be active; specify hours or business days.

Review Period:

Periodic security review cadence, e.g., annually.

Renewal Window:

Window to renegotiate MFA costs before expiration.

Notice Period:

Time required for changes or termination of MFA terms.

Milestones: From Drafting to Operational MFA

Follow this milestone sequence to implement and finalize MFA provisions within an active retainer promptly.

01

Draft Addendum

Prepare language that aligns with the primary retainer and security policy.

02

Internal Review

Legal and security teams review clauses and cost terms.

03

Signatures Collected

Execute signatures and capture authentication evidence in the audit trail.

04

Operationalize MFA

Onboard vendor, configure access, and confirm user enrollment.

Common Mistakes to Avoid

  • Failing to specify who pays for MFA setup and recurring fees, leading to billing disputes and delayed implementation.
  • Using vague scope language that omits systems or user roles, which creates enforcement gaps and operational confusion.
  • Relying on weak authentication methods without defined mitigation measures for credential compromise or lost devices.
  • Not aligning retention and audit trail requirements with HIPAA, IRS, or contractual obligations, risking noncompliance penalties.

Potential Consequences of an Incorrect Addendum

Contract Disputes: Ambiguity in duties
Billing Errors: Unrecoverable costs
Compliance Fines: HIPAA or IRS penalties
Operational Downtime: Access interruptions
Invalid Signatures: ESIGN challenges
Vendor Liability: Unclear indemnity

Vendor Pricing Snapshot for eSignature Plans

This vendor pricing snapshot highlights plan-level features and caps relevant to signing and storing Retainer Addenda for MFA.

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, no credit card required Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Real-World Examples of MFA Addenda in Use

Real-world examples show how teams attach MFA obligations to retainers to reduce friction and maintain compliance across provider relationships.

Optica Ventures

Optica used a Retainer Addendum to assign MFA responsibilities and streamline signature capture for onboarding external partners.

  • The interface is simple and easy-to-use for our team;
  • Optica reduced onboarding time by combining clear contractual MFA duties with electronic signatures and centralized storage, eliminating back-and-forth on authentication responsibilities and producing auditable records for compliance reviews and audits.

Fertility Centers

A healthcare provider attached an MFA addendum to their service retainer to protect patient portals and delegate vendor authentication responsibilities.

  • the API has been great and responsive
  • The provider established clear audit trail requirements, six-year HIPAA retention clauses, and vendor incident obligations in the addendum, which simplified audits and reduced legal uncertainty when reviewing access to sensitive patient records.

Security and Compliance Basics to Reference

Encryption: TLS 1.2/1.3 in transit, AES-256 at rest
Certifications: SOC 2 Type II, ISO 27001, PCI DSS
HIPAA: BAA available; HIPAA-compliant workflows
ESIGN/UETA: Compliant with ESIGN and UETA
Audit Trail: Detailed timestamps, IPs, and action logs
Authentication: Supports SMS, email, KBA, and 2FA

Practical Tips for Clear, Enforceable Addenda

Adopt these best practices to reduce risk, improve clarity, and streamline e-signature processing for MFA addenda.

Specify payment and cost responsibility
State exact dollar amounts or formulas for one-time setup, periodic subscription fees, and support costs. Include timing for invoicing, responsibility for failed payments, and whether costs are refundable when services are terminated or modified.
Tie MFA scope to specific systems and roles
List covered systems, data categories, and user roles. Define exceptions, emergency access procedures, and approved temporary bypass measures. Clear scope prevents enforcement disputes and reduces unnecessary user lockouts while focusing remediation on affected systems.
Require measurable audit trails and retention
Mandate preserved audit logs capturing signer identity, timestamps, IP addresses, and authentication method. Specify retention duration consistent with HIPAA or IRS requirements, and test log export and reproduction to ensure evidentiary quality in disputes or audits.
Review and update annually or after incidents
Schedule periodic reviews of the addendum to reflect technology changes, shifts in vendor responsibilities, or regulatory updates. After security incidents, perform a targeted amendment to clarify remediation actions, responsibilities, and any changes to cost allocation.

Frequently Asked Questions

Answers to frequent questions about completing and executing a Retainer Addendum for MFA, including signing, notarization, and retention guidance.


Need help? Contact support

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