Using Find/Redirect Commands to Troubleshoot

UNIX architecture is a PC interface architecture which represents the UNIX theory. It might subscribe to specifications such as the Single UNIX standards (SUS) or similar POSIX IEEE specification (Tanenbaum, 1995). Not a single available specification explains all about the UNIX interface PC system. By and large, this has been a heritage of the UNIX feuds. However, there are many systems that are UNIX-like in their development, like GNU/Linux distributions (Kai Hwang, 1993). UNIX and Unix-like structures have been at the core of heated legal wars, and the holders of the UNIX brand. UNIX kernel for instance, has main elements of the operating system, which comprises of many kernel subsystems such as process control, memory control, file control, device control and network control. The UNIX substructures include features like; Concurrency. Virtual memory, Paging and Real-time data system. UNIX history stretch way back in 1965, when Bell Labs in cooperation with MIT and General Electric assembled their best brains together to code a new computer interface, known as Multics, which offers a multi-user, multiprocessor and hierarchical data system, in a continuum of its many features (ISO/IEC, 1996). This then formed an architecture that was seen and independent and opens to the end user. UNIX was first used as a text processing system for the copyright domain at Bell Laboratories, an aspect that justified additional research and development by the coding faction (Butenhof, 1997). In terms of comparisons, both UNIX and Windows systems employ real time screening. Unlike Windows PC system, which is highly susceptible to espionage attacks hence rendering the interface a security threat, UNIX is completely the opposite, because it’s built on a 64 bit an architecture that’s rather rigorous for most hackers to penetrate. When it comes to aesthetic, windows looks more appealing and user friendly, while UNIX is quite is the opposite (Bacon, 1993).

Even though there may be sporadic setting up that runs on applications that requires minimal interaction with the core interface, most of the management interfaces, irrespective if their category will have customized systems supporting the control structures domain or programs that are kept on the modern interface. In its simplest appearance, this interface would be Windows, UNIX and if not some version of the UNIX platform. When it comes to forensic assessment, working with these interfaces is rather uncomplicated. Harvesting the main data files, gathering the needed evidence relevant transactions as well as audit, or latest operations that are somewhat modern, it would be easier to retrieve the current state data as associated to processes and integrations. Nevertheless, when the control structures solution is created to reside on top of the core interface and important variations have been created to the file system, some intricacies can arise with regards to information assessments, PCSF (2008).

In most case, these intricacies are linked to the security and approval of functionalities. Modern entry point to these structures is normally function-bases, permitting a company to present some important granularity as it connects to having control of how operators, developers and engineers gain entry to the system constituents. It is not strange to have a solution that approves for the creation of entry protocols that only allow specific functions to execute certain roles CSPLCS (2008). Even though, most of the modern solutions take advantage of underlying approval tools, the manner in which the solution ties that approval into the real control of the interface might put in place new logging systems or at the very least, a secondary transaction log that might be unknown to the evaluator. UNIX supports a lockout method that ensures that illegal users don’t have access to the system whereas giving full rights to end-users to activities associated to their functions. Besides the standard access management tools for data resource in the functional sphere, it is rather probable that the remedy employs security measures are created to how terminals and appliances traits is controlled, PCSF (2008). It now commonplace that dealers are able to create technologies that stretch beyond the native interfaces approval functionalities into environs of repository, alarms or engineering activities, all of which have the ability to influence the trait of the system. Typical example include, replacing conventional boot-up executable in Windows-based interfaces with other custom made executable files that meet the demands of the mechanized process. It is however, common for operators to employ such technologies in a way that the approval as well as authorization related with gaining access to the system differs from the approval related with making any modifications, PCIS (2008).

References

Andrew S. Tanenbaum (1995). Distributed Operating Systems. Prentice Hall.

David R. Butenhof (1997). Programming with POSIX Threads. Addison Wesley Longman, Inc.

ISO/IEC (1996). Information Technology-Portable Operating System Interface (POSIX): System Application Program Interface (API) (C Language). ANSI/IEEE Std. 1003.1. Edition. 9945-1: IEEE Standards Office.

Jean Bacon (1993). Concurrent Systems: An Integrated Approach to Operating Systems, Database, and Distributed Systems. Addison-Wesley,

Kai Hwang. (1993). Advanced Computer Architecture: Parallelism, Scalability, Programmability. McGraw-Hill.

Partnership for Critical Infrastructure Security (PCIS) (2008): http://www.pcis.org/, Web site accessed 10/12/2013.