End node problem
The end node problem arises when individual computers are used for sensitive work and/or temporarily become part of a trusted, well-managed network/cloud and then are used for more risky activities and/or join untrusted networks. (Individual computers on the periphery of networks/clouds are called end nodes.) End nodes often are not managed to the trusted network‘s high computer security standards.[1] End nodes often have weak/outdated software, weak security tools, excessive permissions, mis-configurations, questionable content and apps, and covert exploitations.[2] Cross contamination and unauthorized release of data from within a computer system becomes the problem.
Within the vast cyber-ecosystem, these end nodes often attach transiently to one or more clouds/networks, some trustworthy and others not. A few examples: a corporate desktop browsing the Internet, a corporate laptop checking company webmail via a coffee shop's open Wi-Fi access point, a personal computer used to telecommute during the day and gaming at night, or app within a smartphone/tablet (or any of the previous use/device combinations). Even if fully updated and tightly locked down, these nodes may ferry malware from one network (e.g. a corrupted webpage or an infected email message) into another, sensitive network. Likewise, the end nodes may exfiltrate sensitive data (e.g. log keystrokes or screen-capture). Assuming the device is fully trustworthy, the end node must provide the means to properly authenticate the user. Other nodes may impersonate trusted computers, thus requiring device authentication. The device and user may be trusted but within an untrustworthy environment (as determined by inboard sensors' feedback). Collectively, these risks are called the end node problem. There are several remedies but all require instilling trust in the end node and conveying that trust to the network/cloud.
The cloud’s weakest link
[edit]Cloud computing provides scalable processing and storage resources on demand over the internet. Recent discussions have focused on cloud security.[3] Analysts suggest that security risks are often lower within the monitored, redundant environment of professional cloud hosts and higher at the unstandardized end nodes and devices that connect to these networks.[4][5] While many such cloud environments are FISMA-certified, the end nodes connecting to them rarely are configured to any standard.[6]
Ever growing risk
[edit]From 2005 to 2009, primary threats to personal and corporate data increasingly originated from exploits targeting users' personal computers. Organized cyber-criminals found it more profitable to exploit security vulnerabilities in standard personal and work computers rather than attempting to breach heavily fortified perimeters.[7] One common example of this is stealing small business's online banking account access.[8]
Solutions
[edit]To eliminate the end node problem, only allow authenticated users on trusted remote computers in safe environments to connect to your network/cloud. There are many ways to accomplish this with existing technology, each with different levels of trust.
Many companies issue typical laptops and only allow those specific computers to remotely connect. For example, the US Department of Defense only allows its remote computers to connect via VPN to its network (no direct Internet browsing) and uses two-factor authentication.[9] Some organizations use server-side tools to scan and/or validate the end node's computer[citation needed], such as communicating with the node's Trusted Platform Module (TPM).
A far higher level of trust can be obtained by issuing an immutable, tamper-resistant client[permanent dead link] with no local storage, allowing it to connect only after device and user authentication, remotely providing the OS and software (via PXE or Etherboot), and then only providing remote desktop or browser access to sensitive data.
A less expensive approach is to trust any hardware (corporate, government, personal, or public) but provide a known kernel and software and require strong authentication of the user. For example, the DoD’s Software Protection Initiative[10] offers Lightweight Portable Security, a LiveCD that boots only in RAM creating a pristine, non-persistent, end node while using Common Access Card software for authentication into DoD networks.
See also
[edit]References
[edit]- ↑ Tim Fisher (12 December 2018). "What Is a Node in a Computer Network: Your computer and printer are both network nodes". Retrieved 24 December 2018.
- ↑ Natalia Chrzanowska (23 March 2017). "Why to Use Node.js: Pros and Cons of Choosing Node.js for Back-end Development". Retrieved 24 December 2018.
- ↑ "How Secure Is Cloud Computing?".
- ↑ "Architecture from the top down". Archived from the original on 2021-08-13. Retrieved 2014-01-07.
- ↑ "VPN users: The weak link in network security?". Archived from the original on 2009-05-11. Retrieved 2010-02-06.
- ↑ Rose, Scott; Borchert, Oliver; Mitchell, Stu; Connelly, Sean (2020-08-11). Zero Trust Architecture (Report). National Institute of Standards and Technology.
- ↑ "Business Insights and Resources" (PDF).
- ↑ "Cyberthieves stealing from large percentage of small businesses". USA Today. 9 March 2010.
- ↑ "Fort Sill Virtual Private Network (VPN) Policy". Archived from the original on 2011-06-17. Retrieved 2010-02-06.
- ↑ DoD Software Protection Initiative Archived 2010-05-13 at the Wayback Machine