Grid Computing Web Services
Definition of a computer system Survivable
A computer system, which may be composed of multiple systems and components individual, designed to provide strategic services must be able to perform in a consistent and timely in terms operating. It must be able to achieve its goals and objectives if it is in a state of normal operation or in some sort of stress or a hostile environment. A discussion on information systems survivable can be very complex and far-reaching one. However, in this article we will discuss some of the basics.
Survivable computer security and computer systems
————————————————–
Survivable computer systems and computer security are linked in many ways but at a very low very different. For example, hardening of a particular system to withstand the attacks may be a smart component of a computer system survivable. It does not the ability of a computer system to fulfill its purpose when it is affected by an event as a deliberate attack, a natural disaster or accident, or a general failure. A computer system survivability must be adaptable discharge its principal core functions even in a hostile environment, even if various components of the computer system can not. In some cases, even if all "primary" has been destroyed.
For example, a system designed to provide real-time information critical analysis on the specialty drug stops working for several hours because of the loss of wide dissemination of the communication. However, it maintains the validity of data when communication is restored and the systems back online. This system could be considered as surviving under conditions beyond its control.
On the other hand, the same system fails to provide continuous access to information under normal circumstances or operating environment as a localized failure, may not be considered as having fulfilled its purpose or has reached his goal.
Fault tolerant and high availability systems
—————————-
Many computer systems are designed with components of fault tolerance so that they continue to operate when the key portions of the system will fail. For example, multiple power supplies, hard drives or redundant arrays, or multiple processors and motherboards that can continue to operate even if its peer component is destroyed or fails. The probability of all components to be dismissed if at some time in May be quite low. However, a malicious entity that knows how redundant components are configured may be able to engineer critical errors in all areas of the rendered ineffective fault tolerant components.
High availability also plays a role in a computer system survivable. However, the component design May not maintain the survivability system when certain events such as various forms of attack malicious. An example of this could be a critical web service that has been duplicated, for example, multiple computers, to enable a feature continues if one or more of the individual web servers were to fail. The problem is that many implementations of high availability using the same components and methodology on all the individual systems. If an attack or malicious intelligent event takes place and addresses a broad array specific vulnerability on one individual systems, it is reasonable to assume the remaining computer systems involved in high availability implementation are also susceptible to the same or similar vulnerabilities. A degree of variation must be made in the way which all systems participate in implementing highly available.
What's the difference between an attack, failure and accident?
How these differences impact A Survivable Computer System
————————————————– ——–
In many cases, when I speak safety systems with customers, the issue of business continuity and disaster recovery ride. Most companies that provide service they deem it important enough to know the system should be operational in a consistent manner. However, generally speaking little about the different events and scenarios surrounding this and this can lead to disappointment in the future with what customers thought was a "system of survival" does not meet their expectations. Some of the things I want to put in place during these conversations, is what their computer and Goal Systems objective is, what exactly does not work for them continues, and more precisely what constitutes an attack failure or accident can result in operating losses or failure to achieve the objectives.
A failure may be defined as a localized event that impacts the operation of a system and its ability to provide services or meet its objectives. An example could be the failure of one or more critical or non-core functions that the representation or the overall operation of the system. Say, failure of one module of code that causes a cascading event that prevents redundant modules to perform correctly. Or a hardware failure which makes them unable to locate the computer system.
An accident is usually an event that is outside the control of administrators system and a local / private. An example of this would be natural disaster like hurricanes, if you live in South Florida like me, or floods, loss or wide dissemination of power, because the provider of utilities cut power lines wrong during an upgrade to the grid. Two years ago, one of my clients, which provides web based services, records management could not deliver revenue generating services to their customers as a telecommunications engineer Cutting through a major phone trunk six blocks away from their desks. They lost their phone and data services for nearly a week.
A turn now to "attack". We all know accidents happen, we know that everything fails at one time or another, and in general we can speculate on how these things will happen. An attack, executed by an intelligent, experienced person or group can be very difficult to predict. There are many well known and documented forms of attacks. The problem is understanding and human Imagination continually enhance the form of malicious attacks and can seriously threaten even the most advanced computer systems designed for survival. An accident or failure has no capacity to think outside the box or make a high availability design is flawed because all participants use the same design. The probability that an attack might occur, and success may be quite low, but the impact may be devastating.
Conclusion
———————————————–
One of the reasons I wrote this article was to show that not everything is about prevention. Although prevention is an important element of the design of survivable computer system, a critical computer system must be able to achieve its objectives, even when working in hostile or stressful circumstances. Or if taking preventive measures ultimately prove insufficient. It may be impossible to think of all the various events that can affect system Computer criticism but it is possible to reasonably define the possibilities.
The subject of computer systems of survival is in fact a complex and evolving technology. This article has discussed only some of the fundamental aspects of the computer system of survival. I count on continuation of this article for further study of computer systems survivable.
About the Author
Did you find this article useful? For more useful tips and hints, points to ponder and keep in mind, techniques, and insights pertaining to Internet Business, do please browse for more information at our websites.
http://www.allhottips.com
http://www.bookstoretoday.com
Microsoft OS Cloud Windows Azure Data Center – Google and Amazon battle
