Establishing secure connection…Loading editor…Preparing document…

Legal CII CT Presence Agreement

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

LEGAL CII CT PRESENCE AGREEMENT

This CII CT Presence Agreement ("Agreement") is entered into as of by and between Client Name: , with principal address: (hereinafter "Client"), and Provider Name: , with principal address: (hereinafter "Provider").

Recitals

WHEREAS, Client operates or owns critical infrastructure systems and related information technology and control system assets that require specialized cybersecurity presence and control‑system expertise; and

WHEREAS, Provider maintains a Cyber Threat / Cybersecurity Team ("CII CT Team") experienced in on‑site and remote presence for monitoring, assessment, incident response and testing of critical infrastructure; and

WHEREAS, Client desires to permit Provider and the CII CT Team limited presence and access to specified systems and premises under the terms set forth in this Agreement and Provider agrees to provide such presence under the terms herein.

Now Therefore

NOW THEREFORE, in consideration of the mutual covenants and agreements contained herein and for other good and valuable consideration, the receipt and sufficiency of which are hereby acknowledged, the parties agree as follows.

1. Definitions

1.1 "Presence" means Provider personnel physical or virtual presence at Client premises, network access, privileged access to control systems, remote monitoring sessions, or any activity requiring elevated credentials to observe, test, or respond to cyber or operational events.

1.2 "Covered Systems" means the systems, networks, and assets specifically identified in Section 2 and in any Schedule A attached hereto that are subject to Provider presence or access.

2. Scope of Presence and Access

2.1 Provider is authorized to have Presence at the following Client locations and systems:

2.2 The Covered Systems to be included under this Agreement are described as follows:

2.3 The authorized modality for Presence (check all that apply):

3. Personnel, Credentials and Vetting

3.1 Provider shall ensure that all personnel assigned to perform Presence duties are appropriately qualified, hold required clearances, and have undergone background checks reasonably acceptable to Client. Provider shall provide names and credentials of assigned personnel upon request prior to initial access:

3.2 Provider shall ensure that all access credentials are uniquely assigned, logged, and revoked immediately upon termination of the individual's assignment or upon expiration or termination of this Agreement.

4. Security, Compliance and Operational Controls

4.1 Provider shall comply with Client's site security rules and technical security specifications, including but not limited to network segmentation, least privilege access, multi‑factor authentication where required, logging, and agreed change control procedures.

4.2 Provider shall not alter production control system configurations, introduce unapproved software or devices, or execute tests that may disrupt operations without prior written authorization from Client's designated authority.

5. Confidentiality and Data Handling

5.1 Provider acknowledges that all information obtained through Presence, whether technical, operational, or business in nature, is Confidential Information of Client. Provider shall hold such Confidential Information in strict confidence and use it solely for the purpose of performing Provider's obligations under this Agreement.

5.2 Provider shall implement and maintain administrative, physical and technical safeguards appropriate to the sensitivity of the Confidential Information, including encryption in transit and at rest where applicable, and shall not retain copies beyond the period necessary to perform Services without Client's written consent.

6. Incident Identification and Reporting

6.1 Provider shall report any suspected or confirmed security incidents, data breaches, or operational impacts discovered during Presence to Client's Incident Contact within the shorter of twenty‑four (24) hours of discovery or as otherwise required by applicable law.

7. Liability; Indemnification

7.1 Provider shall indemnify, defend and hold harmless Client and its officers, directors and employees from and against any third party claims, liabilities, losses, damages, costs and expenses (including reasonable attorneys' fees) arising out of Provider's gross negligence, willful misconduct or material breach of this Agreement, provided that Client provides prompt written notice of any claim and cooperates in the defense of the claim.

7.2 Except for liability arising from Provider's gross negligence, willful misconduct or breach of Section 5 (Confidentiality), neither party shall be liable to the other for consequential, incidental, special or punitive damages.

8. Insurance

8.1 Provider shall maintain at its expense commercial general liability insurance and professional liability / cyber liability insurance in amounts sufficient to cover its obligations under this Agreement. Minimum coverages required are set forth below and Provider shall furnish certificates of insurance upon Client request.

9. Term and Termination

9.1 Term. The initial term of this Agreement shall commence on and shall continue until unless earlier terminated in accordance with this Agreement.

9.2 Termination for Convenience. Either party may terminate this Agreement for convenience upon thirty (30) days' written notice to the other party.

9.3 Immediate Termination. Client may immediately suspend or terminate Provider's Presence if Provider's actions create an immediate risk to safety or continuity of Client operations, without prejudice to any rights or remedies available to Client.

10. Fees and Expenses

10.1 Fees. Client shall pay Provider the fees for Presence as set forth in Schedule B or as mutually agreed in writing. If fees are hourly, the hourly rate is:

10.2 Expenses. Client shall reimburse Provider for pre‑approved travel and out‑of‑pocket expenses incurred in connection with on‑site Presence upon submission of reasonable documentation.

11. Notices

All notices required or permitted under this Agreement shall be in writing and delivered to the addresses below by certified mail, courier, or email (with confirmation). Notices shall be effective upon receipt.

12. Amendments; Waiver; Counterparts

12.1 No amendment to this Agreement shall be effective unless in writing and signed by authorized representatives of both parties. No failure or delay in exercising any right shall operate as a waiver of that right.

12.2 This Agreement may be executed in counterparts, each of which shall be deemed an original and all of which together shall constitute one and the same instrument. Facsimile or electronic signatures shall be binding for all purposes.

13. Governing Law; Entire Agreement; Severability

13.1 Governing Law. This Agreement shall be governed by and construed in accordance with the laws of the State of , without regard to conflict of laws principles.

13.2 Entire Agreement. This Agreement, including any Schedules and attachments, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements and understandings, whether written or oral.

13.3 Severability. If any provision of this Agreement is determined to be invalid, illegal or unenforceable, the remainder of this Agreement shall remain in full force and effect and the parties shall negotiate in good faith a substitute provision that most nearly preserves the parties' original intent.

Schedule of Additional Terms (Optional)

Specify additional procedural or technical constraints, special hours of presence, or other agreed limitations below:

Client Printed Name:

By:

Date:

Provider Printed Name:

By:

Date:

Enter text✕

What the Legal CII CT Presence Agreement Is

The Legal CII CT Presence Agreement documents and governs an individual or organization’s authorized presence, access permissions, confidentiality obligations, and reporting requirements when interacting with facilities, systems, or information classified as CII (Critical Infrastructure Information) or CT (Controlled Technology). It sets out the parties, scope, permitted activities, time windows, data handling rules, and enforcement remedies, and is used to create a clear, auditable record of presence for compliance, security, and contractual purposes.

Why a Formal Presence Agreement Matters

A clear presence agreement reduces ambiguity about who may be on site, what they may access, and how sensitive information is handled. It supports regulatory compliance, preserves chain-of-custody and audit trails, and reduces operational and legal risk by documenting consent, limitations, and remedies.

Why a Formal Presence Agreement Matters

Who typically completes a Legal CII CT Presence Agreement

Organizations and respondents use these agreements when access to critical facilities, sensitive systems, or controlled technologies must be authorized, documented, and auditable.

  • Government agencies and regulators — document contractor access for oversight and public-safety compliance.
  • Infrastructure and utilities contractors — record site visits, maintenance windows, and equipment access controls.
  • Legal, compliance, and security teams — preserve audit trails and define incident reporting procedures.

The agreement is suitable for contracting parties, visiting technicians, vendors, and internal staff whose presence creates compliance obligations or security accountability.

Core parts of a professional Legal CII CT Presence Agreement

A complete agreement organizes identity, scope, timing, obligations, data protections, and enforcement into distinct sections so each party’s rights and duties are unambiguous and enforceable.

Parties

Clearly identify each signatory, legal entity names, and authorized representatives; include role and contact details for notices.

Scope of Presence

Specify the exact locations, systems, or datasets covered and any restricted sub-areas or excluded activities to prevent scope creep.

Access Window

List permitted start and end dates, daily access hours, escalation contacts, and procedures for extending or terminating presence.

Confidentiality

State classification levels, handling rules, encryption or storage requirements, and permitted disclosures consistent with applicable law.

Audit & Reporting

Define logging requirements, who receives audit copies, retention periods, and how anomalies or incidents must be reported.

Remedies

Outline sanctions for breaches, indemnities, insurance expectations, and the dispute-resolution forum or governing law.

Step-by-step: completing the agreement

Follow these steps in order to assemble, verify, sign, and deliver a legally robust presence agreement.

  • 01
    Prepare document: Populate parties, scope, dates, and obligations before sending.
  • 02
    Verify identity: Confirm signer identity using ID credential or approved authentication method.
  • 03
    Execute signatures: Collect signatures and dates; notarize if required by jurisdiction.
  • 04
    Distribute copies: Provide signed copies and retain one in an auditable repository.

Recommended digital workflow settings

Configure a consistent eSigning workflow to enforce authentication, retention, and notification rules across all agreements.

Field Configuration
Signer Authentication Email + SMS code or KBA for higher assurance
Retention Automate archival to secure storage with access logs
Notifications Auto-notify signers and compliance teams on completion
Template Reuse Lock core clauses and allow variable field editing

Typical digital signing flow for presence agreements

A standard electronic workflow produces an auditable record with identity, timestamps, and an immutable completion certificate.

  • Upload: Upload the agreement in PDF or DOCX format.
  • Place fields: Add signature, date, and initial fields where required.
  • Send to signer: Deliver via secure email link or enterprise SSO.
  • Complete and archive: Capture audit trail and store the final executed copy.

Platform and integration considerations

Choose a platform that supports required authentication, secure storage, and your integration needs to maintain an auditable chain of custody.

  • Integrations: Salesforce, NetSuite, Microsoft 365 supported
  • Formats: PDF, Word DOCX, Excel supported
  • Authentication: Email, SMS code, KBA, SSO options

Vendor pricing and feature comparison

Compare basic pricing and core feature availability to select a platform that matches compliance, volume, and cost requirements for presence agreements.

signNow DocuSign Adobe Sign PandaDoc HelloSign
Starting Price $8/user/mo $15/user/mo $14/user/mo $19/user/mo $15/user/mo
Free Plan Yes, 30-day trial No No Yes, limited Yes, limited
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

Security and compliance features to require

Transit Encryption: TLS 1.2/1.3
At-rest Encryption: AES-256
Certifications: SOC 2 Type II
Regulatory Support: HIPAA BAA available
FDA Compliance: 21 CFR Part 11 supported
International: GDPR and ISO 27001 compliance

Primary legal risks and potential penalties

1099 Filing Penalties: $60/$130/$330 per form
I-9 Violations: $281–$2,789 per violation
Intentional Disregard: $660+ per form
HIPAA Breach: Civil penalties and corrective action
Notarization Errors: May void acknowledgement
Improper Access: Contract damages and injunctive relief

Common mistakes to avoid when preparing the agreement

  • Using informal or ambiguous location descriptions that do not identify exact rooms, systems, or asset tags can create enforcement disputes and operational confusion.
  • Failing to verify signer identity or relying solely on generic email authentication for high-risk access increases exposure to unauthorized entry and repudiation claims.
  • Omitting retention and audit-log instructions leads to inconsistent recordkeeping and hinders incident response or regulatory audits.
  • Relying on handwritten initials without a clear signature block or explicit authorization for electronic execution can complicate enforceability in some contexts.

Frequently asked questions about Legal CII CT Presence Agreements

Answers to common legal and practical questions to help you determine whether the agreement fits your needs and how to implement it.


Need help? Contact support

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