How should I choose between TCP and UDP?

Select TCP for connection-oriented services (HTTP, SSH) and UDP for connectionless protocols (DNS, SNMP). If unsure, consult the application documentation and test in a staging environment before changing production rules. Incorrect protocol selection can block traffic or allow unintended packets.

Can I use 'any' as an allowed source?

Avoid using 'any' except when there is documented business need and an approved exception. Restricting sources by CIDR, VPN, or security group reduces exposure and supports auditability. Exceptions should include compensating controls and periodic review.

Do I need signatures for port changes?

Formal approvals should be captured for changes that affect production or sensitive systems. Use an eSignature workflow to record approver identity and timestamp. For consumer-facing or regulated data changes, ensure the platform meets applicable compliance requirements like HIPAA with a BAA.

How long must I retain these records?

Keep records while services are active plus at least three years; retain longer if tied to tax, contractual, or regulated activities. HIPAA requires six years for certain health records (45 CFR §164.530(j)). Follow your retention policy for final disposition.

What if an entry has an incorrect port number?

Correct the entry immediately and document the correction with who made the change, why, and the effective date. If the incorrect entry caused an outage or incident, include it in the post-incident report and adjust controls to prevent recurrence.

Is an electronic approval legally valid?

Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and most states under UETA, provided intent, consent, attribution, and retention requirements are met. Certain exceptions may apply to specific document types.

Electronic Signature
Templates
Miscellaneous
Network Configuration Port Numbers

Network Configuration Port Numbers

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

NETWORK CONFIGURATION PORT NUMBERS

This Network Configuration Port Numbers Agreement (the "Agreement") is entered into as of between:

Client Name: Service Provider Name:

RECITALS

WHEREAS, Client operates networked systems and requires explicit configuration and documentation of port numbers, protocols, and associated firewall and NAT rules to ensure secure and auditable connectivity; and

WHEREAS, Service Provider has the expertise to define, document and implement network configuration for specific port numbers and to coordinate related change controls, testing, and acceptance; and

NOW, THEREFORE, in consideration of the mutual covenants and promises contained herein, the parties agree as follows.

SCOPE OF WORK

Service Provider will prepare, validate, and deliver a port configuration inventory and implement agreed configuration changes on Client network equipment. The services include documentation of port numbers, protocol designation, source/destination ranges, NAT/firewall rules, testing, and change-log entries. Service Provider will coordinate scheduled maintenance windows with Client and perform rollback if required.

Detailed Scope Description (list actions, deliverables, and acceptance criteria):

PORT CONFIGURATION INVENTORY

The parties agree that each port configuration entry will include the fields set forth below. Service Provider will populate entries and deliver the completed inventory as a deliverable under this Agreement.

Entry 1 — Port Number

Protocol (check all that apply): TCP UDP Other

Service Description: Direction: Inbound Outbound Both Source IP or Range: Destination IP or Range: NAT Required: Yes No Firewall / ACL Notes:

Entry 2 — Port Number

Protocol (check all that apply): TCP UDP Other

Service Description: Direction / Source / Destination: Firewall / ACL Notes:

Entry 3 — Port Number

Protocol (check all that apply): TCP UDP Other

Service Description: Firewall / ACL Notes:

Entry 4 — Port Number

Protocol (check all that apply): TCP UDP Other

Service Description: Firewall / ACL Notes:

PAYMENT TERMS

Client shall pay Service Provider for the services described in this Agreement in accordance with the following terms.

Total Fee (USD): Payment Schedule (milestones, percentages, or dates): Invoice Due (days from invoice): Late Fee:

TERM AND TERMINATION

This Agreement commences on and continues until unless earlier terminated as set forth herein.

Either party may terminate this Agreement for material breach by the other party if the breaching party fails to cure such breach within days after written notice. Either party may terminate for convenience upon days' prior written notice.

CONFIDENTIALITY

For purposes of this Agreement, "Confidential Information" means non-public business, technical or security information disclosed by one party to the other, including but not limited to port inventories, firewall configurations, credentials, topology diagrams, and vulnerability findings. Receiving party shall (i) use Confidential Information only to perform its obligations under this Agreement; (ii) restrict disclosure to personnel with a need to know and under obligation of confidentiality; and (iii) implement reasonable administrative, technical and physical safeguards to protect Confidential Information from unauthorized access or disclosure.

Confidential Information does not include information that is or becomes publicly known through no breach of this Agreement, was rightfully known to receiving party prior to disclosure, or is independently developed without use of confidential materials.

Confidentiality Acknowledgement: Party acknowledges and agrees to the confidentiality obligations set forth above.

COMPLIANCE, RISK ALLOCATION & WARRANTIES

Service Provider represents that services will be performed in a professional manner consistent with industry standards. Client acknowledges that changes to port configurations involve risk to availability and security; Client is responsible for verifying and accepting changes in accordance with acceptance criteria set forth in the Scope of Work. Except as expressly stated, Service Provider disclaims all other warranties, and liability shall be limited to direct damages not to exceed the total fees paid under this Agreement for the relevant services.

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.

ENTIRE AGREEMENT

This Agreement, including all attachments and the port configuration inventory delivered hereunder, constitutes the entire agreement between the parties with respect to its subject matter and supersedes all prior and contemporaneous agreements, proposals, and communications, whether written or oral. Any amendment must be in writing and signed by authorized representatives of both parties.

SERVICE PROVIDER ACKNOWLEDGMENT OF SECURITY PRACTICES

Service Provider certifies that it will follow reasonable security practices, including the use of current encryption for credential transmission, least-privilege access for personnel performing changes, logging of configuration changes and maintenance of a rollback plan for each change implemented under this Agreement.

Service Provider Security Contact:

Client Printed Name:

By:

Date:

Service Provider Printed Name:

By:

Date:

What Network Configuration Port Numbers Are and why they matter

Network Configuration Port Numbers is a structured record that lists TCP/UDP port assignments, service mappings, and access rules used to configure firewalls, routers, and hosts across a network. The document centralizes numeric port values, protocol types, intended services, and brief justification for each mapping so administrators and auditors can confirm consistency with security policy. It also helps change control by documenting owner, effective date, and rollback instructions for each port change. Maintaining a clear port registry reduces operational errors and supports incident response and compliance workflows.

Why keeping an authoritative port-number record improves security and uptime

A documented map of port numbers ensures consistent firewall rules, reduces accidental exposure of services, and speeds troubleshooting across teams.

Teams and roles that typically manage port-number records

IT operations, security engineers, network architects, and managed service providers commonly create and maintain port-number registries to coordinate changes and enforce allowable service traffic.

IT Operations — Maintains live device configurations and schedules change windows; verifies rule application across environments.
Security Team — Reviews port assignments for compliance with internal security policy and external standards.
Application Owners — Request specific ports and provide justification tied to application architecture.

Essential components of a professional port-number registry

A comprehensive template combines technical fields with governance metadata so entries are actionable and auditable across teams.

Port entry

Numeric port (e.g., 80), protocol (TCP/UDP), and optional port range to identify the exact network endpoint.

Service name

Common service or application name (HTTP, SSH, custom app) and internal service ID if used by CMDB.

Allowed sources

IP addresses, subnets, or security groups permitted to initiate connections to the port.

Purpose / justification

Short business or technical reason for opening the port and references to design docs or tickets.

Owner

Team or person accountable for the service, along with a contact email or ticketing queue.

Change metadata

Effective date, approving authority, rollback steps, and audit-trail reference.

Step-by-step: adding a new port assignment to the registry

Follow this sequence to request, approve, and deploy a new port mapping while preserving auditability.

01

1. Request: Submit a ticket with port, protocol, purpose, and owner information.
02

2. Review: Security and network teams validate necessity and exposure risk.
03

3. Approve: Authorized approver documents consent and sets effective date.
04

4. Deploy: Operations implements rule and records configuration change with audit reference.

Configuring an electronic workflow for port-number approvals

Set up an eSignature and routing workflow to capture approvals, timestamps, and audit trails for each change.

Field	Configuration
Requester	Auto-fill from ticketing system; email required for notifications
Approver	Role-based approver group; require single or multiple sign-offs
Evidence	Attach change request, test plan, and rollback steps
Retention	Store signed records in secure archive for required retention period

Digital signing and submission requirements for configuration records

Use an eSignature platform that captures signer identity, timestamps, and an immutable audit trail when approvals are required.

Authentication: Email link, SMS code, or stronger multi-factor methods
File formats: PDF or DOCX preserved with audit trail
Integrations: Connectors for ticketing, CMDB, and cloud provider APIs

Where records are filed and how they move through your systems

A consistent routing model reduces search time and links approvals to device configurations and audit logs.

Ticketing system: Initiates request and stores change history
eSignature platform: Collects approvals, timestamps, and audit trail
CMDB: Maps port to service and owner
Configuration repo: Holds device-level config committed after deployment

Critical data fields to include for compliance and traceability

Port: Numeric port or range

Protocol: TCP/UDP/BOTH

Service: Service or application name

Sources: CIDR or security group

Owner: Team or person

Approval: Approver and date

Common mistakes that cause security gaps or outages

Using 'any' as the source without documented exception and approval
Not mapping ports to a ticket or change request for traceability
Mismatched protocol selection (e.g., TCP vs UDP) leading to blocked services
Failing to record rollback steps before deployment

Operational and compliance risks of incorrect port documentation

Service outage: Unplanned downtime and business impact

Security incident: Open ports increase attack surface

Regulatory exposure: HIPAA or PCI noncompliance risks

Audit failure: Missing evidence of approvals

Incident response delay: Slower containment and recovery

Financial loss: Remediation and potential fines

Timing expectations for requests, approvals, and deployments

Set clear SLAs for each stage to avoid unnecessary delays and ensure reviewers have time to assess security impact.

Request submission:

Submit at least 3 business days before planned change

Security review SLA:

2 business days for standard requests

Operational approval:

1 business day after security sign-off

Deployment window:

Scheduled during maintenance window

Post-change verification:

Verify within 24 hours of deployment

Key milestones in the port-change lifecycle

Track these sequential milestones from request through verification to ensure control and visibility.

01

Request Filed

Ticket opened with details and attachments

02

Security Assessment

Threat and exposure analysis completed

03

Approval Granted

Authorized approver documents consent

04

Deployment & Verify

Change applied and functionality confirmed

Real-world scenarios for Network Configuration Port Numbers

These concise examples illustrate typical workflows and outcomes when a port registry is used correctly.

Mid-size enterprise IT

A dev team requests port 8443 for a staging service to support testing

Security approves after CIDR restriction
Post-deployment the operations team documents the rule, links the ticket, and reduces mean time to remediate by reducing ambiguity during incidents.

Managed service provider

An MSP centralizes port mappings across 30 clients to avoid conflicts

The provider enforces role-based approvals
Standardized records cut onboarding time for new clients and simplify cross-tenant audits.

Sample eSignature pricing comparison for managing approvals and audit trails

Compare common vendor starting prices and feature availability relevant to electronic approvals and compliance; signNow is listed first per platform data.

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

Frequently asked questions about Network Configuration Port Numbers

Answers to common technical and process questions that help avoid misconfiguration and maintain compliance.

Need help? Contact support

How should I choose between TCP and UDP?
Select TCP for connection-oriented services (HTTP, SSH) and UDP for connectionless protocols (DNS, SNMP). If unsure, consult the application documentation and test in a staging environment before changing production rules. Incorrect protocol selection can block traffic or allow unintended packets.
Can I use 'any' as an allowed source?
Avoid using 'any' except when there is documented business need and an approved exception. Restricting sources by CIDR, VPN, or security group reduces exposure and supports auditability. Exceptions should include compensating controls and periodic review.
Do I need signatures for port changes?
Formal approvals should be captured for changes that affect production or sensitive systems. Use an eSignature workflow to record approver identity and timestamp. For consumer-facing or regulated data changes, ensure the platform meets applicable compliance requirements like HIPAA with a BAA.
How long must I retain these records?
Keep records while services are active plus at least three years; retain longer if tied to tax, contractual, or regulated activities. HIPAA requires six years for certain health records (45 CFR §164.530(j)). Follow your retention policy for final disposition.
What if an entry has an incorrect port number?
Correct the entry immediately and document the correction with who made the change, why, and the effective date. If the incorrect entry caused an outage or incident, include it in the post-incident report and adjust controls to prevent recurrence.
Is an electronic approval legally valid?
Yes. Electronic signatures are legally enforceable under the federal ESIGN Act (15 U.S.C. ch. 96) and most states under UETA, provided intent, consent, attribution, and retention requirements are met. Certain exceptions may apply to specific document types.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now