Establishing secure connection…Loading editor…Preparing document…

Security Supplemental Form

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

Security Supplemental Form

This Security Supplemental Form ("Supplement") is entered into as of by and between Client Name: and Service Provider Name: .

WHEREAS

WHEREAS, Client and Service Provider are parties to a written agreement entitled Master Services Agreement dated (the "Master Agreement");

WHEREAS, the parties desire to supplement the Master Agreement to set forth specific security obligations, controls, incident response commitments, and payment adjustments associated with the provision of services that involve access to, processing of, or storage of Client data.

SCOPE OF WORK

SECURITY CONTROLS AND REQUIREMENTS

The Service Provider shall implement and maintain the following controls as applicable to the Services provided:

Network security controls (firewalls, segmentation, intrusion detection)

Encryption of Data at Rest and in Transit (specify algorithms and key management below)

Access controls and least-privilege administration

Incident response and notification procedures

Regular penetration testing and vulnerability scanning

Physical security for facilities (where applicable)

Employee background checks and security training

AUDIT, COMPLIANCE AND REPORTING

Service Provider shall permit Client or an independent assessor engaged by Client to conduct security audits or assessments no more than and upon prior written notice. All such audits shall be conducted during normal business hours and in a manner that does not unreasonably disrupt Service Provider operations.

INCIDENT NOTIFICATION AND RESPONSE

Service Provider shall notify Client of any confirmed or reasonably suspected security incident affecting Client data within hours of discovery and provide regular written updates until the incident is resolved. Notification shall include the nature of the incident, affected data categories, mitigation steps taken, and planned remediation.

PAYMENT TERMS

As consideration for the additional security services described in this Supplement, Client shall pay Service Provider the Security Fee in accordance with the terms below.

Invoices are payable within the period specified in Payment Schedule. Overdue amounts shall accrue interest as set forth in Late Payment above and Client shall be responsible for all reasonable collection costs and expenses incurred by Service Provider in enforcing payment.

TERM AND TERMINATION

This Supplement shall commence on and shall continue in effect until unless earlier terminated in accordance with this Supplement or the Master Agreement.

Either party may terminate this Supplement for material breach of the security obligations if the breaching party fails to cure the breach within days after receiving written notice. Termination of this Supplement shall not relieve any party of obligations accruing prior to termination, including payment obligations and obligations regarding the return or destruction of Client data.

CONFIDENTIALITY

The parties agree that any Client data, security assessments, vulnerability reports, and other information designated as confidential shall be treated as Confidential Information. Service Provider shall not use, disclose, or permit access to Confidential Information except as necessary to perform the Services. The obligations in this section shall not apply to information that: (a) is or becomes publicly known other than through a breach by the Service Provider; (b) is rightfully received from a third party without restriction; or (c) is independently developed by the Service Provider without reference to Client Confidential Information. The confidentiality obligations shall survive termination of this Supplement for a period of three (3) years or for as long as required by applicable law for certain categories of regulated data.

LIABILITY, INDEMNIFICATION AND REMEDIATION

Service Provider shall be liable for damages arising from Service Provider's willful misconduct or gross negligence in implementing the security controls required by this Supplement. Service Provider agrees to indemnify and hold Client harmless from third-party claims resulting from a failure to comply with the security obligations set forth herein, subject to any limitations or caps set forth in the Master Agreement. In the event of a data breach caused by Service Provider, Service Provider shall be responsible for reasonable remediation costs, including forensic investigation and required notifications as set out in Incident Notification and Response.

GOVERNING LAW

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

ENTIRE AGREEMENT

This Supplement, together with the Master Agreement, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, proposals, or representations, whether written or oral, relating to the same subject matter. Any amendment to this Supplement must be in writing and signed by authorized representatives of both parties.

GENERAL PROVISIONS

If any provision of this Supplement is held invalid or unenforceable, the remainder of the Supplement will remain in full force and effect. The parties agree that monetary damages may be an inadequate remedy for breach of certain obligations contained herein and that injunctive relief may be sought in appropriate circumstances.

Client:

By:

Date:

Service Provider:

By:

Date:

Enter text✕

What the Security Supplemental Form Is

The Security Supplemental Form collects additional security-related details that supplement a primary agreement or application, such as access controls, background-check authorizations, or system access levels. It documents who will have access to sensitive systems or data, the specific controls to be applied, and any conditions or approvals required before access is granted. Organizations use this form to standardize risk assessments, preserve an audit trail of security commitments, and ensure consistent onboarding or provisioning of personnel or vendors.

Why a Security Supplemental Form Matters

A clear supplemental form reduces ambiguity about access rights and control measures, supports compliance with federal standards like HIPAA when applicable, and creates a documented decision trail that can be reproduced for audits and incident response.

Why a Security Supplemental Form Matters

Who Typically Completes the Security Supplemental Form

Organizations use this form during onboarding, vendor setup, contracting, or project initiation to capture security-specific obligations separate from the base contract.

  • IT and Security Teams responsible for provisioning accounts and documenting technical controls
  • Human Resources or Facilities for physical access, background-check approvals, and badge issuance
  • Procurement and Legal for vendor security commitments and contractually required safeguards

Completion often requires coordination across stakeholders so that technical, legal, and business requirements align before granting access.

Step-by-Step: Completing the Security Supplemental Form

Follow these sequential steps to gather approvals, confirm identity, and record security controls before granting access or executing a contract.

  • 01
    Prepare: Collect base agreement, requester details, and system identifiers before starting the form.
  • 02
    Fill Fields: Complete required fields with exact formats and attach supporting documents such as IDs or authorizations.
  • 03
    Verify: Confirm identity and background-check status per policy, and validate access level requests with system owners.
  • 04
    Approve: Route for signatures, capture audit trail, and provision access only after final approval.

How Digital Submission and Approval Typically Works

An electronic workflow streamlines collection, authentication, and approval while preserving a time-stamped record of actions and attachments.

  • Upload: Sender uploads the form and attaches required documents such as background-check authorizations.
  • Place Fields: Assign signature, date, and conditional fields to the relevant signers or approvers.
  • Authenticate: Signers authenticate via email, SMS code, or stronger methods depending on risk.
  • Complete: Signed copies and an audit trail (IP, timestamp) are stored for retention and compliance.

Recommended Digital Workflow Settings

Configure your e-submission workflow to match organizational risk and compliance requirements before sending the form for signature.

Field Configuration
Authentication Method Email link | SMS code | KBA for high risk
Field Types Signature, Date, Checkbox, Conditional fields
Routing Order Sequential approvals with role-based signers
Retention Settings Enable secure storage and exportable audit trail

Technical and Integration Considerations

Ensure the chosen platform supports required authentication, secure storage, and the file formats you plan to use.

  • Integrations: Connectors for Salesforce, Microsoft 365, NetSuite, Google Workspace simplify routing and record linking
  • File Formats: Supports PDF, DOCX, and HTML for import and export
  • Authentication: Options for email, SMS, KBA, and SSO provide flexible identity assurance

Confirm that the platform can produce a tamper-evident audit trail and meets any industry-specific compliance requirements before deployment.

Key Components to Include in a Professional Security Supplemental Form

A complete form combines identification, scope, controls, approvals, and supporting evidence so decisions are consistent and defensible.

Parties

Clearly identify the requester, approver, and system owner with contact information

Scope

Define systems, assets, or data covered and any limitations on access

Access Controls

Specify role-based permissions, MFA requirements, and session limits

Background Checks

Document required checks, consent status, and retention of results

Signatures and Dates

Capture final approvals with signer identity, role, and date

Attachments

Include supporting documentation such as IDs, policies, or approvals

Security and Compliance Controls to Record

Encryption: TLS 1.2/1.3 in transit; AES-256 at rest
Access Controls: Role-based permissions and MFA required
Audit Trail: Time-stamped events with IP and signer attribution
HIPAA: BAA required for protected health information
SOC 2: SOC 2 Type II attestation available
21 CFR Part 11: Supports electronic records and signatures for FDA-regulated use

Practical Tips for Accurate and Efficient Completion

Apply consistent standards, validate identity early, and use conditional fields to reduce reviewer workload.

Verify Identity Early
Confirm government ID or corporate credentials before granting access; delaying verification increases risk and can require revocation and rework.
Use Conditional Fields
Display only relevant questions based on role or answer values to reduce errors and speed completion of the form.
Attach Proof Documents
Include signed authorizations, background-check results, or training records to avoid follow-up and to support audit requests.
Record Decisions
Keep a dated, signed approval trail with the rationale for any exception to standard access controls for future review.

Common Preparation Mistakes to Avoid

  • Entering nicknames or partial names that fail identity verification and delay provisioning
  • Using inconsistent date formats that create ambiguity in effective dates or retention calculations
  • Omitting required attachments such as signed consent forms or ID copies, which triggers rework
  • Applying overly broad access roles without documented justification, increasing security risk

Consequences of Incomplete or Incorrect Forms

Unauthorized Access: Increased breach risk and potential regulatory fines
Compliance Violations: HIPAA or sector breaches may lead to enforcement action
Operational Delay: Missing approvals block provisioning and project timelines
Legal Exposure: Contract disputes if obligations are unclear
Data Loss: Poor controls increase risk of exfiltration
Tax or Reporting Penalties: Late or missing filings can trigger statutory fines

Typical Timelines and Processing Expectations

Establish clear internal SLAs for form submission, review, and provisioning to avoid access gaps and compliance issues.

Submission Deadline:

Provide the form upon request or at hiring; submission should occur before access is granted

Review Period:

Security owner review within 3 business days is common for standard requests

Approval Window:

Final approval often required within 5 business days to support onboarding schedules

Provisioning Time:

Allow 1–2 business days after approval for technical provisioning

Retention Trigger:

Retention begins on effective date and follows industry or legal retention periods

Key Milestones From Request to Record

Track each milestone from initiation through provisioning and retention so stakeholders can monitor progress and compliance.

01

Request Initiated

Requester files the form and uploads supporting documents

02

Security Review

Security team evaluates risk and required controls

03

Final Approval

Authorized approver signs and documents exceptions

04

Provisioning & Archive

Access is provisioned and signed records stored securely

eSignature Pricing Overview for Preparing and Signing the Form

Pricing and feature availability vary by vendor and plan. The table highlights starting prices and common capability differences relevant to secure form workflows.

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

Frequently Asked Questions and Troubleshooting

Answers to common questions about validity, notarization, identity verification, and record retention for the Security Supplemental Form.


Need help? Contact support

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