P. 1
MIS Security Check

MIS Security Check

|Views: 13|Likes:
Published by Ali Muhammad

More info:

Published by: Ali Muhammad on May 08, 2012
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOCX, PDF, TXT or read online from Scribd
See more
See less






  • Chapter 1: Introduction
  • Chapter 2: Policies and Guidelines
  • Chapter 3: Users and Passwords
  • Chapter 4: Users, Groups, and the Superuser
  • Chapter 5: The UNIX Filesystem
  • Chapter 6 Cryptography
  • Chapter 7: Backups
  • Chapter 8: Defending Your Accounts
  • Chapter 9.. Integrity Management
  • Chapter 10: Auditing and Logging
  • Chapter 11: Protecting Against Programmed Threats
  • Chapter 12: Physical Security
  • Chapter 13: Personnel Security
  • Chapter 14: Thlephone Security
  • Chapter 15. UUCP
  • Chapter 16. TCP/IP Networks
  • Chapter 17: TCP/IP Services
  • Chapter 18: WWW Security
  • Chapter 19: RPC, NIS, NIS+, and Kerberos
  • Chapter 20: NFS
  • Chapter 21: Firewalls
  • Chapter 22: Wrappers and Proxies
  • Chapter 23: Writing Secure SUID and Network Programs
  • Chapter 24: Discovering a Break-in
  • Chapter 25: Denial of Service Attacks and Solutions
  • Chapter 26: Computer Security and US. Law
  • Chapter 27: "Who Do You Trust?

Be extremely careful about installing new software. Never install binaries obtained
from untrustworthy sources (like the Usenet).
When installing new software, install it first on a noncritical system on which you can
test it and observe any misbehavior or bugs.
Run integrity checks on your system on a regular basis (see Chapter 9).
Don't include nonstandard directories in your execution path.
Don't leave any bin or library directories writable by untrustworthy accounts.
Set permissions on commands to prevent unauthorized alteration.
Scan your system for any user home directories or dot files that are world writ-able or
group writable.

If you suspect a network-based worm attack or a virus in widely circulated software,
call a FIRST response team or the vendor to confirm the instance before spreading
any alarm.
Never write or use SUID or SGID shell scripts unless you are a hoary UNIX wizard.
Disable terminal answer-back, if possible.
Never have "." (the current directory) in your search path. Never have writ-able
directories in your search path.
When running as the superuser, get in the habit of typing full pathnames for
Check the behavior of your xargs and find commands. Review the use of these
commands (and the shell) in all scripts executed by cron.
Watch for unauthorized modification to initialization files in any user or system
account, including editor start-up files, .forward files, etc.
Periodically review all system start-up and configuration files for additions and

Periodically review mailer alias files for unauthorized changes.
Periodically review configuration files for server programs (e.g., inetd.conf.)
Check the security of your at program, and disable the program if necessary.
Verify that any files run from the cron command files cannot be altered or replaced by
unauthorized users.
Don't use the vi or ex editors in a directory without first checking for a Trojan .exrc
file. Disable the automatic command execution feature in GNU Emacs.
Make sure that the devices used for backups are not world readable.
Make sure that any shared libraries are properly protected and that protections cannot
be overridden.

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->