Chapter 8. Trusting Other Computers

   


Few systems are islands any more. The question is how much each system should trust the other systems that it communicates with. A SysAdmin must answer this question while walking a tightrope anchored by sound technical data on one end and politics on the other. Insist on too much security, and your users will try to get you fired for obstructing their work or will look for ways around security as a challenge. Allow security to get too lax and suffer break-ins, and the same users will try to get you fired for not providing security and protecting their work. You will need to decide how much the systems under your control will trust other systems.

This trust will translate into what services will be allowed and to which systems. Citing "authorities" might help convince management. So might talking about known incidents and vulnerabilities of various types of systems. These are discussed at great length in the various security resources mentioned in Appendix A.

The topics covered in this chapter include:

  • "Secure Systems and Insecure Systems" on page 355

  • "Trust No One The Highest Security" on page 356

  • "Linux and UNIX Systems Within Your Control" on page 358

  • "Mainframes Within Your Control" on page 359

  • "A Window Is Worth a Thousand Cannons" on page 359

  • "Firewall Vulnerabilities" on page 361

  • "Virtual Private Networks" on page 364

  • "Viruses and Linux" on page 365


   
Top


Real World Linux Security Prentice Hall Ptr Open Source Technology Series
Real World Linux Security Prentice Hall Ptr Open Source Technology Series
ISBN: N/A
EAN: N/A
Year: 2002
Pages: 260

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net