Thin Client Operating System Security - Report Example

?THIN CLIENT OPERATING SYSTEM SECURITY Thin client is a term which is used to refer to a network computer or PCs which are used by businesses whose design makes them to be managed centrally and their configuration makes them to lack CD/DVD players or expansion slots. Therefore these devices contain only equipment which is essential for the business functions which they serve. Moreover, thin client refers to a set of technologies which are designed to reduce the total cost ownership (TCO) for businesses. The reduction in TCO results from the fact that thin clients are characterized by low costs in hardware, maintenance, support and bandwidth. In addition, thin clients have reduced downtime and significantly improved performance1. More importantly through is the fact that thin computers provide enhanced security as compared to desktop PCs. Thin client operating system describes a small size client OS which require much fewer resources as compared to fat clients which are much large and high resource dependent. This essay gives a critical analysis and discussion of the security implications which are related to systems such as Windows CE, Google Chromium and Linux which make use of the thin client operating system. Wide scale security threats and incidences are associated with machines or systems that are Windows based. It in this regard that thin clients have been described to be useful within networks of various organizations with a view of boosting their security. It is however important to note that thin client where originally developed with an aim of providing remote access to Windows which utilized them. Regardless of this original function, it is notable that the concepts and protocols associated with thin client operating systems have helped many companies or organizations to significantly improve the security of their Windows. Regardless of this, it is argued that thin clients cannot replace Windows PCs at wholesale level2. However the use of thin clients within Windows is essentially aimed at improving overall network security for specific functions and purposes. This security advantage with the use of thin clients is achieved with maintenance of desktop consistency. Operating systems which utilize thin clients such as Google Chromium, Linux and Windows CE allow the thin clients to access the central server of their networks for multiple or numerous user sessions. This is achieved through the capability of the thin operating system to utilize Windows Terminal Services. It is therefore notable that thin clients provide Windows which use them with multiple sessions which emanate from a central system3. This paradigm is similar to that of a mainframe computer. However the implication of thin client operating system on improved network security does not result from its ability to maintain an organization network which is composed of PCs that are Windows based. Instead, the role of thin operating system in network security is related or focused on the Windows servers which provide the main sessions for the network. It is important to consider though that there are drawbacks which are related to the application of thin clients to achieve remote desktops that are session based. The most significant of these drawbacks is network speed. It has been noted that even within a fast network, the application of remote access to desktops us significantly slower as compared to a PC. The reduction in speed is regardless of the security benefits which are associated with the remote access and as a result, organizations are mandated to make tradeoffs which allow them to decide on either the benefits associated with security or speed. The utilization of thin operating system by Google Chromium, Linux and Windows CE significantly reduces the overall costs associated with securing networks. Many organizations employ standardized and reproducible PCs with Windows within their system4. When thin clients are implemented in such systems and their networks, it leads to a situation where there are fewer computers which would require maintenance out of a security breach or drawback. It is in this sense that thin operating systems are argued to have a positive implication on the costs associated with security threats on networks. However it is notable that it is impractical to run an entire organizational network with only thin clients. Because of this, organizations must be able to make informed decisions on how and where thin clients should be installed and implemented within the network. It is recommended that decisions on implementing thin clients within an organizational computer network should be based on access control and security as the determining factors for management decisions. Windows based personal computers are currently used significantly to access web applications and the internet. The frequent use of PCs to access the internet makes them predisposed and vulnerable to the security threats which characterize communication and data exchange via the internet. In the light of this, many organizations have prioritized their agenda on deciding whether access to web application should be based on a fat operating system or a thin operating system such as thin clients. The attractiveness of the fat clients is related to their ability to stand alone which makes it desirable from the user point of view. However, the low operating costs and reduced security risks which are associated with thin clients makes them very desirable from the organizational point of view5. It is emphasized that organizations should weigh more on the security aspect of computer systems and network. This means that a thin client is likely to be favored due to the underlying positive implications on the security of organizational data during exchanges and communication over local and wide area networks. The use of thin operating system by Google Chromium, Linux and Windows CE leads to prevention of zombies and the resultant system sabotage. One of the greatest system damage which attackers can inflict on organizational systems is capturing its Windows PCs and consequently turning them onto zombies. This means that the attackers accesses an organizational PC, mostly via the internet and infects t with a Trojan. As a result, the hackers or system attackers have unfettered access to the zombie PC6. The system attacker then links the zombie PCs to form network called a botnet. The botnet is consequently used to attack other networks within the organization. This form of security breach is easily achieved by attackers because all that is required is a download of a malicious file by an unsuspecting PC operator. This often occurs regardless of the regulations and security standards which organizations set to prevent such download. This leads to the discussion of the role of thin operating system in prevention of zombies and the resultant sabotage to a system. Systems such as Google Chromium, Linux and Windows CE make use of thin operating system because thin clients have an inability of becoming zombie hosts. This means that system attackers are not able to turn them into zombies and sabotage the network. One of the major characteristics of thin clients is the fact that they are closed and therefore do not have disk drives. Because of this, it is apparent that thin clients lack a place where malicious code can be inserted through. This is because thin clients are dependent on the applications which are installed on servers. Because servers have relatively more secure and powerful computing capability and defenses against malicious applications, it is reflective that the closed characteristic of thin clients makes a system secure since there is no possibility of endpoint entry of malicious code. Furthermore, the servers upon whose applications thin clients depend upon have a higher operator attention and stable software configuration which makes them more secure. On the other hand, the use of PCs within a network predisposes it to entry of malicious code via its disk drives7. Systems such as Google Chromium, Linux and Windows CE benefit from the positive implication of thin clients in dodging theft. Organizations and departments have in many occasions reported theft of their laptops which are said to contain numerous confidential data, records or information. Theft leads to falling of private and confidential data into unauthorized hands. This is therefore s significant security concern and threat which causes great concern on the part of the organization and their clients. Even though many enterprises and organizations have designed policies which mandate their staff to encrypt data which is held in their laptop computers, it has been noted that this level of security and system protection is not sufficiently implemented. In addition, the implementation of encryption techniques is commonly compromised by the application of relatively weaker user passwords on the system cipher key. These security challenges are often mitigated through the implementation of thin clients within systems. Thin clients lack disk memory. This is because they depend on servers for the storage of their applications. It is therefore apparent that thin clients are useless to thieves in case of theft. Additionally, thin operating systems cannot be used elsewhere apart from within a protected and authorized server. In this sense therefore, the use of thin operating system presents a positive implication on their security. However, thin clients as compared to laptop computers lack mobility. Mobility and security tradeoff is therefore used to decide upon their implementation within systems. Systems which utilize thin operating system have more software control as compared to regular PCs. The IT management staff within organizations often demonstrates reluctance in allowing users to copy or install software applications which emanate from unknown publishers or sources. Organizational have such policies for license reasons but these measures are basically meant to secure systems. Applications which users download from the internet often contain malicious software such as Trojans and Rootkits. When these are installed to systems, they would sabotage or render them non-functional. Additionally, the malicious software would cause leaking of data into unauthorized sites. It is in light of this that thin client architecture allows IT management staff to have more control over installation of software. This is related to the fact that users are not able to install applications via thin clients because they depend on servers which have high application monitoring capability8. Systems which employ thin operating system have higher limitations on personal use of the system as compared to PCs. Employees within organizations often use company system resources and PCs for their personal purposes such as travel planning, online shopping and social networking. It becomes less feasible to limit the use of organizational system resources in Windows architecture. In addition, employees often find ways through they would circumvent any limitations on the use of company PCs for activities which are not related to work activities. The thin client architecture on the other hand allows IT management to have greater control on the use of company system resources9. This includes the control of applications and internet sites which employees are able to access. It is however notable that thin client operating systems are not ideal for the needs of every organization and users because of diversity of needs and functionalities. Regardless of this argument, organizations which have a large number of non-power and stationery users achieve effectiveness in management and higher level of security when a thin client operating system is used within their networks. In the light of the above discussion, demonstration and illustrations, it is conclusive that thin client operating system is advantageous over Window based PCs in terms of securing systems and organizational networks. This is attributed to the fact that systems such as Google Chromium, Linux and Windows CE which utilize thin clients benefit from prevention of system sabotage and theft. This reflects a positive implication of thin clients in safeguarding the privacy and confidentiality of data within organization systems. In addition, thin client architecture allows increased software control by IT management10. This prevents installation of malicious software that is downloaded from the internet such as Trojans and Rootkits by system users. More importantly, thin client operating systems allows organizations to limit the personal use of organizational system resources. Regardless of the aforementioned positive benefits of thin client operating systems, it is notable that it is not practical that it would replace Windows based PCs. Bibliography Brodkin, J 2009, 'HP upgrades mobile, desktop thin clients', Network World, 26, 20, p. 31 Edwards, C 2009, 'Will 'Thin Clients' Replace Office PCs?' Business week, 4142, pp. 63-64 Harrast, S, & Bean, L 2008, '“Thin Client” Technology: Should You Bet Your Company's Future on It?', Journal of Corporate Accounting & Finance (Wiley), 12, 5, pp. 45-52 Hocking, M 2011, 'Thin client security in the cloud', Network Security, 2011, 6, pp. 17-19 Strassmann, PA 2009, '5 Secure Reasons for Thin Clients', Baseline, 80, p. 27 Sturdevant, C 2011, 'PC versus Thin Clients', Eweek, 28, 18, p. 8 Vlissidis, P, & Hickey, M 2010, 'Thin clients: slim security?', Network Security, 2010, 4, pp. 16-19 Read More