What fields are mandatory?

Required fields typically include hostname, primary IP, owner contact, operating system, and backup schedule. Marking mandatory fields reduces incomplete submissions and supports automation into CMDBs.

Can the form be signed electronically?

Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted. For consumer-facing records, follow 15 U.S.C. §7001(c) disclosure requirements; internal inventory forms generally do not require a consumer disclosure.

Who can view submitted data?

Restrict access by role. Limit personal data to authorized staff, log access in an audit trail, and apply encryption in transit and at rest to meet regulatory obligations.

Is notarization ever required?

Server inventory forms rarely require notarization. Notarization applies when the form acts as or supports a legal filing that statute requires a notarial act.

How to correct errors after submission?

Submit a revision with changed fields highlighted, include approver signatures if required, and preserve the original for audit continuity. Track corrections in the audit log.

How long must I keep the form?

Retention depends on purpose: follow IRS rules for tax-related records (IRC §6501(a)), HIPAA six-year rule (45 CFR §164.530(j)) for healthcare, and your organization’s retention schedule.

Electronic Signature
Templates
Miscellaneous
Server Information Form

Server Information Form

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

SERVER INFORMATION FORM

Recitals

WHEREAS, Service Provider: and Client Name: (each a "Party" and together the "Parties") desire to set forth the terms under which Client will provide information about one or more computer servers and related infrastructure to Service Provider to enable delivery of hosting, management, monitoring, maintenance, backup, or other services.

WHEREAS, the Parties wish to record certain server-level technical details, administrative contacts, security credentials and operating parameters necessary to perform the services and to memorialize certain commercial and confidentiality terms applicable to the exchange of that information.

Server Identification

Server Reference / Tag Primary Hostname Primary IP Address Additional IPs (comma-separated)

Infrastructure Details

Physical or Virtual

Physical Virtual Cloud

Operating System / Version Hardware / Instance Size Physical Location / Data Center

Administrative Access & Credentials

Primary SSH User SSH Key Fingerprint or Public Key (if applicable) Administrative Accounts & Roles

Operational Configuration

Primary Services / Ports Maintenance Window Backup Schedule & Retention

Scope of Work

The Parties agree that Service Provider will perform services consistent with the technical details provided in this form and any attachments. Services may include monitoring, patching, configuration management, backups, incident response and other services mutually agreed in writing. Describe the specific scope and deliverables below.

Payment Terms

Client will pay Service Provider the fees set forth below in consideration for the services. Unless otherwise agreed in writing, fees are due in U.S. dollars and exclusive of taxes and third-party charges.

Payment Amount (per billing period or one-time) Payment Schedule / Due Dates

Late payments shall incur a late fee of on overdue balances, plus any reasonable collection costs and interest to the extent permitted by law.

Term and Termination

This Agreement commences on Start Date: and continues until End Date: unless earlier terminated as provided below.

Either Party may terminate for convenience with prior written notice of days. Either Party may terminate for material breach that is not cured within thirty (30) days after written notice specifying the breach.

Confidentiality

Each Party acknowledges that Server Information, credentials, configuration details, access logs, and any non-public business or technical information disclosed in connection with this Agreement constitute Confidential Information. Each Party shall (a) use Confidential Information only for the purposes of performing its obligations hereunder; (b) restrict disclosure to employees, contractors or agents with a need to know and who are bound by confidentiality obligations no less protective than those herein; and (c) implement reasonable administrative, physical and technical safeguards to protect Confidential Information. Confidential Information does not include information that is or becomes publicly available without breach of this Agreement, is rightfully received from a third party free of obligation of confidentiality, or is independently developed without use of the other's Confidential Information.

Warranties, Liability and Indemnity

Service Provider will perform services in a professional manner consistent with industry standards. Client warrants that it has authority to provide the server information and access described in this form and that use of such information will not violate third-party agreements. Except as expressly provided, neither Party makes any further warranties. To the maximum extent permitted by law, each Party's aggregate liability arising out of this Agreement shall be limited to the fees paid by Client to Service Provider in the twelve (12) months preceding the claim. Client agrees to indemnify and hold Service Provider harmless from claims arising from Client-supplied content, credentials or instructions.

Governing Law; Entire Agreement

This Agreement shall be governed by and construed in accordance with the laws of the jurisdiction selected by the Parties. This form, together with any exhibits or attachments expressly incorporated by reference, constitutes the entire agreement between the Parties with respect to the subject matter and supersedes all prior and contemporaneous agreements, proposals and communications, whether oral or written. No amendment shall be effective unless in writing and signed by both Parties.

Acknowledgment and Certification

By signing below, the undersigned certify that the information provided in this Server Information Form is true and complete to the best of their knowledge, that they have authority to provide the information and to bind their respective Party, and that they accept and agree to the terms set forth in this document.

Client certifies that any confidential credentials provided will be rotated or revoked in accordance with the Parties' agreed access control procedures when no longer required.

Acknowledgment Checkbox

I acknowledge and certify the accuracy of the information above and acceptance of the terms in this form.

Service Provider:

By:

Date:

Client:

By:

Date:

What the Server Information Form Is and When to Use It

A Server Information Form is a standardized record used to capture technical, administrative, and compliance details about a server asset. Typical fields include hostname, IP addresses, operating system, physical or cloud location, owner and support contacts, backup schedule, patch level, encryption status, and any regulatory classification. Organizations use the form for inventory, change control, incident response, audits, and third-party onboarding. The form can be maintained as a fillable PDF or within a configuration management database and may be executed electronically under U.S. e-signature law when signatures are required.

Why maintaining a Server Information Form matters

A complete Server Information Form centralizes asset data, reduces mean time to resolution during incidents, supports compliance audits, and documents custody and responsibilities for each server.

Typical users and stakeholders for this form

Teams and roles that complete or rely on the Server Information Form vary by organization but share accountability for asset management and security.

IT operations teams who maintain host configuration and patch schedules and perform routine inventory reconciliations.
Security or SOC teams that need asset classification, encryption status, and incident escalation contacts.
Compliance officers or auditors who require documented evidence of controls, ownership, and retention.

Clear role assignment on the form helps ensure updates, approvals, and periodic reviews occur on schedule.

Core sections to include in a professional Server Information Form

A well-structured form groups technical data, ownership, security posture, lifecycle details, maintenance schedules, and supporting evidence to simplify audits and operations.

Asset Details

Hostname, alias, asset tag, serial number, virtualization host, and identifying metadata to uniquely identify the server.

Network Information

Primary IP address, secondary addresses, subnet/CIDR, VLAN or network segment, gateway, and DNS entries for connectivity mapping.

Security & Compliance

Encryption status, encryption algorithms, authentication methods, regulatory classification (HIPAA, PCI, etc.), and audit log locations.

Maintenance & Backup

Backup schedule, retention policy, last successful backup date, recovery point objective (RPO), and maintenance windows.

Ownership & Contacts

Responsible owner, business unit, escalation contacts, and third-party vendor support details for rapid response.

Attachments & Evidence

Links or attachments for system diagrams, configuration files, support contracts, certificates, and recent vulnerability scan results.

Security and compliance fields to capture

Encryption: AES-256 at rest

Transport: TLS 1.2/1.3 in transit

Access Controls: Role-based accounts

Audit Trail: Timestamped logs

Regulatory Flag: HIPAA/PCI/GLBA

Incident Owner: Primary responder contact

Step-by-step: completing and approving the Server Information Form

Follow a consistent sequence to gather accurate details and obtain necessary approvals before storing the record.

01

Gather Data: Collect host, network, and security details from source systems.
02

Fill Form: Enter values carefully, using required formats and attachments.
03

Review: Manager and security review for accuracy and classification.
04

Store: Save in CMDB and archive signed copy per retention policy.

Where to send the completed form and how it is used

Routing depends on your organization: integration with CMDBs, ticketing tools, and security systems ensures the form is actionable.

Configuration DB: Import data to the CMDB for discovery and asset linkage.
Ticketing System: Attach to change or onboarding tickets for traceability.
Security Team: Provide classification, encryption details, and escalation contacts.
Third-Party Vendor: Share only approved fields under an NDA or BAA.

Typical online workflow settings for digitizing the form

Configure automated routing, field validation, and retention rules to reduce manual errors and speed approvals.

Field	Configuration
Authentication	SSO or email verification with optional MFA
Routing	Auto-route to manager then security reviewer
Validation	IP and date format checks enabled
Retention	Archive signed record per retention policy

Technical considerations for digital completion and signing

Confirm file formats, integrations, and signer authentication options before deploying the online form.

Supported Formats: PDF, DOCX, HTML
Integrations: CMDB, Service Desk, Google Workspace
Authentication: Email, SMS code, or SSO

Ensure the platform supports secure transport (TLS 1.2/1.3), at-rest encryption (AES-256), audit trails, and any necessary BAAs or compliance attestations.

Recommended timelines and update cadence

Establish explicit deadlines for initial entry, periodic review, and post-change updates to keep the inventory current and auditable.

Initial Inventory:

Complete within 30 days of asset deployment or discovery.

Post-Change Update:

Update form within 5 business days after configuration changes.

Quarterly Review:

Validate entries and ownership at least every 90 days.

Incident Update:

Document any security incident details immediately after containment.

Audit Snapshot:

Produce an audit-ready export annually or per regulatory schedule.

Common mistakes to avoid when preparing the form

Entering truncated hostnames or aliases that do not match DNS records, leading to misidentification during response.
Listing generic owner contacts instead of named, reachable personnel, which delays incident escalation.
Failing to include backup retention details or last successful backup date, hampering recovery decisions.
Omitting encryption or certificate status, exposing the organization to unexpected audit findings and risk.

Risks and potential consequences of incorrect or missing data

Compliance Fines: Regulatory penalties where protected data is mishandled.

Security Breach: Longer dwell time and larger impact from incidents.

Operational Downtime: Delayed recovery due to missing topology or ownership data.

Audit Failures: Evidence gaps during SOC, HIPAA, or PCI reviews.

Insurance Issues: Coverage disputes if controls are undocumented.

Third-Party Risk: Vendor access errors or misconfigurations from incomplete data.

Representative eSignature pricing and capability snapshot

Compare baseline pricing and key capabilities for common eSignature vendors. Values show starting price and common compliance or feature distinctions.

	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	Yes, 7-day free trial	Varies by plan	Varies by plan	Trial available	Trial available
Bulk Send	Yes (Premium)	Yes (paid tiers)	Yes (paid tiers)	Yes	Limited
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Frequently asked questions about the Server Information Form

Answers to common questions about required fields, signing options, access controls, and record corrections for the Server Information Form.

Need help? Contact support

What fields are mandatory?
Required fields typically include hostname, primary IP, owner contact, operating system, and backup schedule. Marking mandatory fields reduces incomplete submissions and supports automation into CMDBs.
Can the form be signed electronically?
Yes. Electronic signatures are valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted. For consumer-facing records, follow 15 U.S.C. §7001(c) disclosure requirements; internal inventory forms generally do not require a consumer disclosure.
Who can view submitted data?
Restrict access by role. Limit personal data to authorized staff, log access in an audit trail, and apply encryption in transit and at rest to meet regulatory obligations.
Is notarization ever required?
Server inventory forms rarely require notarization. Notarization applies when the form acts as or supports a legal filing that statute requires a notarial act.
How to correct errors after submission?
Submit a revision with changed fields highlighted, include approver signatures if required, and preserve the original for audit continuity. Track corrections in the audit log.
How long must I keep the form?
Retention depends on purpose: follow IRS rules for tax-related records (IRC §6501(a)), HIPAA six-year rule (45 CFR §164.530(j)) for healthcare, and your organization’s retention schedule.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now