This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
wiki:policies:network [2021/11/15 21:44] katcow |
wiki:policies:network [2024/01/24 21:24] (current) katcow |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Wireless Connection Policy ====== | ====== Wireless Connection Policy ====== | ||
- | ===== I. Purpose | + | ==== I. Purpose ==== |
- | ===== II. Scope ===== | + | Though the networks used by remote workers are beyond our control, it is essential that we mitigate these possible external threats as much as we can through this policy. |
- | ==== | + | ==== II. Scope ==== |
- | ===== III. Wireless Connection Policy ===== | + | 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 guidance on procedures for safely using home networks, which includes practices such as using strong passwords, eliminating guest networks, securing IoT devices, and frequently updating devices. | ||
====== Network Security Policy ====== | ====== Network Security Policy ====== | ||
- | ===== I. Purpose ===== | + | ==== I. Purpose ==== |
+ | |||
+ | This policy provides guidance to safeguard networks 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. | ||
+ | |||
+ | ==== III. Network Security Policy ==== | ||
+ | |||
+ | Nested Knowledge, a fully remote company, does not maintain any internal networks for employees. | ||
+ | |||
+ | The Nested Knowledge cloud application, | ||
+ | |||
+ | ==== 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, communcations between all services and the database are encrypted via TSL. | ||
+ | |||
+ | ==== Network change management procedures | ||
- | ===== II. Scope ===== | + | When network architecture changes, a review by the technical lead, Karl Holub, must be processed. Additionally, |
- | ==== | + | ===== Revision History ===== |
- | ===== III. Network Security Policy ===== | + | ^Author^Date of Revision/ |
+ | |K. Cowie|01/ | ||
+ | |K. Holub|11/ | ||
- | Nested Knowledge, a fully remote company, does not maintain any networks. In a scenario where Nested Knowledge operates a network, we will update our secruity plan to include regular monitoring for malicious activity. | + | [[: |