> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/policies/policies/internal-policies/wireless-connection-policy.md). # Wireless Connection Policy ## Wireless Connection Policy #### I. Purpose The networks used by remote workers (primarily from home or shared offices) are a subtle threat vector, and it is essential that we mitigate threat models presented by this mode of access. #### II. Scope This policy applies to all employees and contractors who work with Nested Knowledge and access internal or confidential Nested Knowledge data. #### III. Wireless Connection Policy Wireless network acceptable practices are based on the data classification system. Public data may be accessed on any network. Internal Nested Knowledge data, confidential data, and restricted data may only be accessed on secure networks. All personnel accessing non-public data must avoid the use of public, high-risk networks. **Home Network Procedures** All employees and contractors are provided with training and compliance checks on procedures for safely using home networks, which includes practices such as using strong passwords, eliminating guest networks, securing IoT devices, limiting reach of routers, and frequently updating devices. ## Network Security Policy #### I. Purpose This policy provides guidance to safeguard networks maintained by Nested Knowledge from harm. #### II. Scope This policy applies to all employees and contractors who work with Nested Knowledge and access internal or confidential Nested Knowledge data. Due to the nature of our networks, the policy primarily applies to IT staff / developers who may be accessing production networks. #### III. Network Security Policy Nested Knowledge, a fully remote company, does not maintain an internal network for employees, opting instead for cloud applications available over the internet. The Nested Knowledge cloud application and marketing site run in an isolated, private network (AWS Virtual Private Cloud, “VPC”). Only front-end servers are exposed to the internet via gateway; backend services and databases are unreachable outside the VPC. Access to the VPC is provided by a bastion host via SSH key authentication. All access attempts to the VPC are logged with IP address, port/protocol, and time of access and periodically reviewed for unexpected or malicious activity and retained for a period of 1 year. #### Security Protocols For The Transmission Of Data Across The Network All communications from the VPC are encrypted by SSH (developers) or HTTPS (users of the application). Within the VPC, communications between all services and the database are encrypted via TSL. #### Network Change Management Procedures When network architecture changes, review by a technical lead must be performed. Additionally, the technical lead will perform annual review of this policy and ongoing compliance. *Reviewed 2025-12-12 by Karl Holub.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nested-knowledge.com/policies/policies/internal-policies/wireless-connection-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.