Corporate network exemption attestation
Request details
| Field | Customer response |
|---|---|
| Company legal name | |
| Yesoma workspace and request reference | |
| Company website | |
| Headquarters country, city and region | |
| Requester's full name and role | |
| Business email and verification contact | |
| Office or private corporate VPN | |
| Network provider | |
| Business purpose and requested period | |
| Assignment/control evidence reference |
List each static, public internet-facing address or the smallest necessary address range. An address range may be written as a CIDR block. Include IPv6 when used. Do not provide passwords, secret keys or private home addresses.
| Address or range | Office/VPN purpose | Assignment and control evidence |
|---|---|---|
Statement by the company representative
I, [full name], acting as [role] for [company legal name], confirm that I am authorised to submit this request on the company's behalf.
The public IP addresses and address ranges listed above are statically assigned to and controlled by our company for its office network or private corporate VPN. Where the addresses are supplied by an internet or hosting provider, we have provided evidence of assignment and company control.
These addresses are not shared public VPN exits, residential connections or dynamically assigned connections. We have described their business purpose and supplied the requested evidence.
Our company will manage access through these networks in accordance with Yesoma's terms and the conditions of any approved exception. We will promptly notify Yesoma Support of changes to their assignment, control, use or security.
We understand that approval applies only to the specified workspace, addresses, purpose and period. Approval may expire or be revoked. Normal authentication, two-factor authentication, workspace permissions and other security requirements remain applicable. A technical network exception does not establish legal eligibility for access.
The information provided is accurate and complete to the best of my knowledge.
| Signature field | Response |
|---|---|
| Full name | |
| Role and company | |
| Business email | |
| Signature | |
| Date |
An authorised CISO, IT/security lead, company director or business owner may sign. Yesoma verifies the representative's authority before approval.
Yesoma approval record
Staff complete this section after review. A signature or approval decision alone does not show that implementation and verification have finished.
| Field | Staff record |
|---|---|
| Verified customer and workspace | |
| Support Case and linked implementation task | |
| Approved addresses, purpose and conditions | |
| Review evidence and decision reason | |
| Approver and decision date | |
| Implementer and change reference | |
| Activation date and expiry date | |
| Verification evidence and verifier | |
| Renewal/revocation history |
Normal exceptions have a maximum 90-day period. Trial/proof-of-concept exceptions have a maximum 30-day period. Renewal requires fresh review. Replacement addresses require a new linked request. Restrict the signed document and review evidence to authorised participants under the applicable retention policy.