RFP_8100_JNH3000_ATT_8_v1.pdf
PDF 1 MB Posted
- Attached to
- Aviation Telephone System & Services
- Solicitation number
- RFP 8100 JNH3000
- Issued by
- Texas
About this file
This is an Airport VPN Request Form (Version 1.9, dated June 8, 2022) issued by the City of Austin Aviation Department for Austin Bergstrom International Airport (AUS) to manage third-party network connections for vendors, consultants, and partner companies. The form establishes procedures for granting remote access to City of Austin Aviation Department network resources through VPN connectivity, specifying that requestors must provide detailed information about the accessing party, justification for access, applications and protocols to be used, remote device security configurations, and the contract period during which access is required. The form requires completion of all sections, including requestor information, Aviation Department point of contact details, security questionnaires addressing password enforcement, anti-virus protection, firewall status, and operating system specifications, along with defined access start and end dates and the purpose of the connection.
The document includes a Third Party Connection Acceptable Use Policy that establishes binding obligations for partner companies utilizing the VPN connection. Key requirements include mandatory notification to the Aviation Department within one business day when employees with access leave the company or transfer positions, maintenance of at least 10 days of connection logs for auditing purposes, prohibition of VPN account sharing on shared systems with requirement for unique accounts per individual user, and notification of any changes to the user base with a two-week lead time except when directed otherwise by the City's IS Manager or Assistant Director. The policy stipulates that all network access will be monitored, non-compliance constitutes a security violation reportable to appropriate personnel, and violations may result in immediate termination of the partner agreement. Both the requestor and Aviation Department Division Manager must sign the form acknowledging understanding and compliance with the policy.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFP_8100_JNH3000_ATT_12_v1.pdf | ||
| RFP_8100_JNH3000_ATT_4_v1.pdf | ||
| RFP_8100_JNH3000_ATT_3_v1.pdf | ||
| RFP_8100_JNH3000_ATT_1_v1.pdf | ||
| RFP_8100_JNH3000_ATT_6_v1.pdf | ||
| RFP_8100_JNH3000_ATT_14_v1.pdf | ||
| RFP_8100_JNH3000_ADD_4_v1.pdf | ||
| RFP_8100_JNH3000_ADD_6_v1.pdf | ||
| RFP_8100_JNH3000_ADD_3_v1.pdf | ||
| RFP_8100_JNH3000_ADD_5_v1.pdf | ||
| RFP_8100_JNH3000_ATT_5_v1.pdf | ||
| RFP_8100_JNH3000_ATT_7_v1.pdf | ||
| RFP_8100_JNH3000_ATT_2_v1.pdf | ||
| RFP_8100_JNH3000_ATT_11_v1.xlsx | XLSX spreadsheet | |
| RFP_8100_JNH3000_ATT_13_v1.xlsx | XLSX spreadsheet | |
| RFP_8100_JNH3000_ATT_10_v1.xlsx | XLSX spreadsheet | |
| IFB_2200_CSH1061_ATT_10_v1.docx | DOCX document | |
| RFP_8100_JNH3000_ATT_9_v1.xlsx | XLSX spreadsheet | |
| RFP_8100_JNH3000_ADD_2_v1.pdf | ||
| RFP_8100_JNH3000_ATT_15_v1.pdf | ||
| RFP_8100_JNH3000_ADD_1_v1.pdf | ||
| RFP_8100_JNH3000_ATT_2_v2.pdf | ||
| RFP_8100_JNH3000_ATT_1_v7.pdf | ||
| RFP_8100_JNH3000_ATT_4_v2.pdf |
Show all 24
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Version 1.9 Date: 6/8/2022
Airport VPN Request Form (Third Party Connections: Vendors, Consultants …)
City of Austin – Aviation Department / Austin Bergstrom International Airport (AUS) Information System
Instructions
Please fill out this form completely. Incomplete forms will be returned and completion of the request will be delayed. Email signed form to servicedesk@flyaustin.com or fax to (512) 530-4576.
1. Requestor information
Requestor Requestor’s Manager
Name: Name:
Phone: Phone:
Mobile Phone: Mobile Phone:
E-mail: E-mail:
Office Location: Office Location:
Company: Project:
2. COA – Aviation Department Point of Contact information
Aviation Dept. Point of Contact Manager
Name: Name:
Division: Division
Phone: Phone:
E-mail: E-mail:
3. Justification for VPN access:
4. Applications / Protocols to be Accessed
Remote Desktop (RDP ☐ VNC ☐ Other Remote Control: _________________________________________________________
Server names or IP addresses to be accessed:
Other Applications or Protocols to be accessed:
TCP/UDP ports used:
5. Remote Device Security:
City of Austin – Aviation Department security policy sets minimum security criteria for all PCs that attach to City of Austin – Aviation
Department networks. Remote device must also meet the relevant security criteria. Please answer the following questions about remote device configuration and security management practices.
Are strong passwords enforced for your account capable of logging into the remote device? Yes ☐ No ☐
Is the sharing of passwords strictly prohibited? Yes ☐ No ☐
Are the operating system and applications kept up to date with service packs and security patches? Yes ☐ No ☐
Is the device protected by active anti-virus software that has up-to-date virus definition files? Enter the brand and version of current anti-virus software: ______________________________________________________________
Yes ☐ No ☐
Is the device protected by active firewalls or IP filters? What is brand name: Yes ☐ No ☐
Disconnect from VPN service when using my computer for personal use (such as surfing the web, etc.) Yes ☐ No ☐
Do not distribute the VPN client software or share VPN connection information. Yes ☐ No ☐
What operating system and service pack are installed on the remote computer?______________________________ Yes ☐ No ☐
Inf orm ati on al Use
O nly
Exhibit D mailto:servicedesk@austintexas.gov gamezt Cross-Out
Version 1.9 Date: 6/8/2022
6. Contract between partner company and Aviation Department is effective from: to:(date)
7. Access dates
Start Date: End Date:
Purpose:
Third Party Connection Acceptable Use Policy
To ensure that a secure method of connectivity is provided between City of Austin – Aviation Department and third party (partner) companies, and to provide guidelines for the use of network and computing resources associated with a Third Party Network as defined below.
Scope:
This policy applies to any person(s) and/or contractor(s) (hereinafter referred to as "users") whose access to or use of Internet, electronic mail and/or computer use is funded by the City or is available through equipment owned or leased by the City.
Definition:
A "Third Party Network Connection" is defined as connections that allow data sharing between the COA and a partner electronically. Allowable “Third Party Network Connections" are listed in Statement of the Policy.
Statement of the Policy:
Third Party Network Connections are to be used for business purposes only as outlined by the Information Requirements
Document for each connection. Third party connections must have an "Authorization for Third Party Connection" on file with the Security Officer .In the text below, "user" refers to employees/contractors of the partner company who use the resources associated with the partner network.
1) The information provided on the VPN Request Form is correct to the best of my knowledge.
2) The partner company shall notify the appropriate City of Austin – Aviation Department personnel when an employee, who has access on City of Austin – Aviation Department equipment per the partner connection, leaves the company or is transferred to another position which no longer requires access. The partner company will send termination notices within one business day of the employee's last physical day with the account and IP information to servicedesk@flyaustin.com
3) The partner company shall assume all responsibility for protection of their private network(s) which may be interconnected via the third party connection to City of Austin – Aviation Department.
4) Only employees of the partner company who have approved access shall use the resources associated with the partner connection.
5) No sharing of VPN accounts on shared systems will be permitted. Every account must have a unique person associated with it.
6) The point of contact at the partner company shall notify the City of Austin – Aviation Department via the servicedesk@flyaustin.com account whenever there is a change in the user base for the work performed over the partner network. Changes have a two week lead time except when directed by City of Austin – Aviation Department IS Manager or a
City of Austin – Aviation Department Assistant Director.
7) All access to City of Austin – Aviation Department network will be monitored. For auditing reasons, the partner company will be required to keep 10 days of logs for all IP's connecting to City of Austin – Aviation Department resources. This can be an intrusion detection system or simply a router with logging turned on and saved. Any noncompliance with these requirements will constitute a security violation and will be reported to the appropriate City of Austin – Aviation Department Personnel, and it may result in immediate termination of the partner agreement.
I have read and understand the Third Party Connection Acceptable Use Policy for use of a third party partner connection and agree to abide by it.
Requestor Signature Date
Aviation Dept. - Division Manager Signature Date
AUS Information System use only
AUS IT Approvals Cherwell Ticket #
Setup Staffs Start Access Date
VPN Account Cisco AnyConnect ☐ Global Protect ☐ End Access Date
Inf orm ati on al Use
O nly mailto:servicedesk@flyaustin.com mailto:servicedesk@flyaustin.com
| ManagerEmail: |
| Justification for VPN access: |
| Other Remote Control: |
| Server names or IP addresses to be accessed: |
| TCPUDP ports used 1: |
| TCPUDP ports used 2: |
| Is the sharing of passwords strictly prohibited: |
| version of current antivirus software: |
| Is the device protected by active firewalls or IP filters What is brand name: |
| What operating system and service pack are installed on the remote computer: |
| Contract between partner company and Aviation Department is effective from: |
| todate: |
| Start Date: |
| End Date: |
| Date: |
| Date_2: |
| Cherwell Ticket: |
| Setup Staffs: |
| Start Access Date: |
| End Access Date: |
| RequestorName: |
| RequestorPhone: |
| RequestorMobile Phone: |
| RequestorEmail: |
| RequestorOffice Location: |
| RequestorCompany: |
| Requestors ManagerName: |
| Requestors ManagerPhone: |
| Requestors ManagerMobile Phone: |
| Requestors ManagerEmail: |
| Requestors ManagerOffice Location: |
| Requestors ManagerProject: |
| Aviation Dept Point of ContactName: |
| Aviation Dept Point of ContactDivision: |
| Aviation Dept Point of ContactPhone: |
| Aviation Dept Point of ContactEmail: |
| ManagerName: |
| ManagerDivision: |
| Check Box7: Off |
| Check Box8: Off |
| Check Box9: Off |
| Check Box10: Off |
| Check Box11: Off |
| Check Box12: Off |
| Check Box13: Off |
| Check Box14: Off |
| Check Box15: Off |
| Check Box16: Off |
| Check Box17: Off |
| Check Box18: Off |
| Check Box19: Off |
| Check Box20: Off |
| Check Box21: Off |
| Check Box22: Off |
| Check Box23: Off |
| Check Box24: Off |
| Check Box25: Off |
| Check Box26: Off |
| ManagerPhone: |
File details come from the government source that posted it. Updated .