AutoLit® User Guide
Examining Results in Synthesis
Administrative Tools
Support and FAQs
Best Nest Building Practices
SLR Basics: How to Perform Systematic Review
NMA Basics: How to Perform a Meta-Analysis
Best Practices for Writing a Publishable Manuscript
This is an old revision of the document!
This policy outlines our plan for authenticating users who connect remotely to Nested Knowledge IT systems.
Who is affected: This policy affects all employees of this Nested Knowledge and its subsidiaries, and all contractors, consultants, temporary employees and business partners.
Affected Systems: Server or VPN.
Nested Knowledge has no internal network for employees, therefore multi-factor application for remote access is not applicable. Should Nested Knowledge establish a network, access to the network through remote access will be managed by a Virtual Private Network (VPN). The VPN will request for username and password or some other form of advanced authentication. Remote access must conform at least minimally to all statutory requirements including but not limited to HCFA, HRS-323C, and HIPAA.
Should Nested Knowledge establish a network, access to the network through remote access will be managed by a Virtual Private Network (VPN). The VPN will request for username and password, and it may require dual-factor authentication.
The Nested Knowledge application is run in a VPC (for details, see Network Security Policy). This network is only accessible by release engineers who are granted SSH keys. These keys may be revoked or refreshed at any time, as necessitated by personnel changes or incidents.The VPC is only accessible through a single bastion host.
