China
Africa
Explore chapters and articles related to this topic
Network Security for EIS and ECS Systems
Published in Barney L. Capehart, Timothy Middelkoop, Paul J. Allen, David C. Green, Handbook of Web Based Energy Information and Control Systems, 2020
As mentioned earlier, malicious software such as Trojans, worms, and viruses represents a significant threat to system integrity. The best method for managing this risk involves both technology and human stewardship. Many anti-virus tools, such as McAfee VirusScan and Norton Anti-Virus, are available for both workstations and servers. These programs use sophisticated algorithms to recognize code patterns that are characteristic of malicious software. Anti-virus programs use a database of known malicious software and code patterns and the database must be updated frequently as new malicious software threats emerge literally every day. All levels of the organization should be involved in protecting the IT system from viruses and malicious software scanning on a regular basis. Users must therefore be trained to understand how malicious software works and how the available tools can be used to prevent damaging attacks. Administrators should actively discourage users from receiving, much less running, executable files received through email and should disallow such privileges if at all possible.
Foundation and Application of Expert System Verification and Validation
Published in Jay Liebowitz, The Handbook of Applied Expert Systems, 2019
Of particular concern from the point of view of V&V is the system complexity. The complexity of the system is defined by several characteristics which make the system harder to develop and analyze. Generally, the higher the complexity, the greater the opportunity for errors and the greater the need for V&V. However, there is another factor that needs to be considered in determining the extent of estimated V&V required: system integrity. System integrity refers to the joint capability of a system to operate for long periods without failures, to fail gracefully with reasonable warnings, to be able to recover rapidly without much difficulty, and to avoid causing expensive damage to property or harm to people or the environment. How much integrity is required of a system will be a function of several factors. Thus, a highly complex system with a low degree of required integrity should probably not need as much V&V as a highly complex system with a very high degree of required system integrity.
The Bioprocessing Industry—An Introduction
Published in Sarfaraz K. Niazi, Disposable Bioprocessing Systems, 2016
Although disposable technologies have delivered success in development laboratories and GMP production suites, challenges and improvement opportunities yet remain. For example, concerns with extractables and leachables have not been fully resolved even though they have been addressed in detail. System integrity issues could lead to contaminations or loss of product. Product quality consistency and lot-to-lot variability present additional challenges to wider acceptance of disposable systems. The ongoing cost of disposables is always a problem to consider especially as the capital cost of hard-walled systems is fully amortized; however, the general consensus is that despite this accounting system, the disposable systems are preferred, one reason being that newer developments and improvements in disposable components will allow the manufacturer to always be using state-of-the-art technology rather than be stuck with a decades-old system.
Cyber Diversity Index for Sustainable Self-Control of Machines
Published in Cybernetics and Systems, 2022
“An operating system is said to have system integrity when it is designed, implemented and maintained to protect itself against unauthorized access, and does so to the extent that security controls specified for that system cannot be compromised. A multilevel- secure trusted computing base ensures system integrity. The trusted computing base has the ability to protect itself against unauthorized user access” (IBM-Integrity 2020). Integrity of software and operating systems appears to be subjective, because integrity is assumed until a vulnerability is discovered. The system has no or has partial integrity until patched. The system than has integrity until another vulnerability is discovered. If the vulnerability was never discovered, but still there, the system never had true integrity in the first place. System integrity, perhaps is not about protecting one self or system that cannot be compromised, system that can self-patch or self-heal but is about system that has self-control of its own core purpose. Application Integrity Diversification (AID) is introduced in the experiments as a measurement of an application's integrity or core purpose. Any unknown change to this measurement would signal a deviation of the applications' integrity or its own normal cybernetic behavioral profile.