B
- Bace, Rebecca (Intrusion
Detection), General Computer Security
- Bach, Maurice (The Design of the
UNIX Operating System), Unix Programming and System Administration
- back doors, Keeping Secrets, Cryptographic Strength of Symmetric Algorithms, Communicating with MUDs, Internet Relay Chat (IRC), and Instant Messaging, Programmed Threats: Definitions, Back Doors and Trap Doors–Back Doors and Trap Doors, Protecting Yourself
- as common
threat, Protecting Yourself
- in
MUDs and IRCs, Communicating with MUDs, Internet Relay Chat (IRC), and Instant Messaging
- strength of encryption
and, Cryptographic Strength of Symmetric Algorithms
- background checks, Background Checks, Other People
- background
processes, Abusing Automatic Mechanisms
- backing out of upgrades, Upgrading Distributed Applications
- backups, Standards, Guidelines, Defending Against Acts of War and Terrorism, Protecting Backups, Protecting Backups, Verify your backups, Protect your backups, Upgrading Distributed Applications, Why Make Backups?–The Role of Backups, The Role of Backups, What Should You Back Up?, Types of Backups, Types of Backups, Types of Backups, Types of Backups, Guarding Against Media Failure, Replace tapes as needed, Verify the backup, How Long Should You Keep a Backup?, How Long Should You Keep a Backup?, Security for Backups–Data security for backups, Physical security for backups, Physical security for backups, Write-protect your backups, Data security for backups, Data security for backups, Legal Issues, Legal Issues, Legal Issues, Deciding Upon a Backup Strategy–Retention schedule, Individual Workstation, Small Network of Workstations and a Server–Retention schedule, Large Service-Based Networks with Large Budget, Backing Up System Files–Building an Automatic Backup System, Building an Automatic Backup System, Building an Automatic Backup System, Building an Automatic Backup System, Software for Backups–Network Backup Systems, Software for Backups, Simple Local Copies, Simple Archives, Specialized Backup Programs, Network Backup Systems, Network Backup Systems, Encrypting Your Backups, Read-Only Filesystems, Managing Log Files, Managing Log Files, World-readable backup devices, Hazards of Criminal Prosecution, The Responsibility to Report Crime, Criminal Hazards, Chapter 18: Backups
- across
network, Network Backup Systems
- automatic system
for, Building an Automatic Backup System
- commercial systems
for, Network Backup Systems
- configuration files,
paper copies of, Building an Automatic Backup System
- criminal
investigations and, Hazards of Criminal Prosecution, The Responsibility to Report Crime, Criminal Hazards
- data security
for, Data security for backups
- dedicated
programs for, Specialized Backup Programs
- destruction
of, Legal Issues
- differential, Types of Backups
- encryption
of, Protecting Backups, Physical security for backups, Data security for backups, Encrypting Your Backups
- file modification
times and, Large Service-Based Networks with Large Budget
- files with
holes, Software for Backups
- guidelines
for, Guidelines
- human error
and, Replace tapes as needed
- of individual
workstations, Individual Workstation
- legal issues
concerning, Legal Issues
- levels
of, Types of Backups
- location
of, Protect your backups, Physical security for backups
- of
log files, Managing Log Files
- media failure,
protecting against, Guarding Against Media Failure
- methods
of, The Role of Backups
- migrating, How Long Should You Keep a Backup?
- of networks, Small Network of Workstations and a Server–Retention schedule
- performing before
upgrades, Upgrading Distributed Applications
- public key encryption
and PGP, Building an Automatic Backup System
- purposes
of, Why Make Backups?–The Role of Backups
- read-only
partitions, Read-Only Filesystems
- retention
of, How Long Should You Keep a Backup?, Legal Issues
- rotating
media, Types of Backups
- schedule
for, Types of Backups
- security checklist
for, Chapter 18: Backups
- security
of, Security for Backups–Data security for backups
- simple
archives, Simple Archives
- simple local
copies, Simple Local Copies
- simultaneous, Defending Against Acts of War and Terrorism
- software
for, Software for Backups–Network Backup Systems
- standards
for, Standards
- strategies
for, Deciding Upon a Backup Strategy–Retention schedule, Managing Log Files
- of system-critical
files, Backing Up System Files–Building an Automatic Backup System
- theft
of, Protecting Backups
- verifying, Verify your backups, Verify the backup
- what to back
up, What Should You Back Up?
- world-readable, World-readable backup devices
- write-protecting, Write-protect your backups
- bacteria, Programmed Threats: Definitions, Bacteria and Rabbits
- BADSU
attempts, logging, sulog Log File
- Badulescu,
Ion, The Virtual Filesystem Interface
- banners, Banners–Banners, Security concerns with SMTP banners and commands
- modem, Banners–Banners
- SMTP, Security concerns with SMTP banners and commands
- bash history file, Shell History
- Basic Input/Output
System (BIOS), Starting Up Unix and Logging In
- batch
command, CPU overload attacks
- batch
jobs, Sudden changes in time (see cron file)
- baud, Baud and bps
- Bellovin, Steve
(Firewalls and Internet Security), Network Technology and Security
- Berkeley BSD Unix, Which Unix System? (see BSD
Unix)
- Berkeley FTP server, restricting accounts
with, Restricting FTP with the standard Berkeley FTP server
- Berkeley
Software Design, Inc. (BSDI), Second-Generation Commercial Unix Systems
- Bernstein, Dan, SMTP: Simple Mail Transfer Protocol (TCP Port 25)
- best
practices, Best Practices–Best Practices
- beverages, effects on
hardware, Food and drink
- bftpd server, Setting up an FTP server
- bidirectionality
of modems, Modems: Theory of Operation, One-Way Phone Lines
- biff service, UDP
- bigcrypt
algorithm, crypt16( ), DES Extended, and Modular Crypt Format
- /bin
directory, Unix salt, Using NIS+, Setting up the chroot( ) environment, Viruses, Running the User’s Shell, Running the User’s Shell, Running the User’s Shell
- /bin/csh, Running the User’s Shell (see csh)
- /bin/ksh, Running the User’s Shell (see ksh)
- /bin/login, Using NIS+ (see login
program)
- /bin/passwd, Unix salt (see passwd
command)
- /bin/sh, Running the User’s Shell (see sh)
- in
restricted filesystems, Setting up the chroot( ) environment
- binary
code, downloading, Programmed Threats: Definitions, Viruses
- binary owner, Users and Groups
- BIND name server, Users and Groups, DNS under Unix
- bind() system
call, The inetd Program
- BIOS (Basic Input/Output
System), Starting Up Unix and Logging In
- Bishop, Matt, Protecting Integrity
- Blaze,
Matt, The Virtual Filesystem Interface
- block
algorithms, Symmetric Key Algorithms
- block devices, Device Files, Device Files, Device Files
- block/send commands,
Trojan horses and, Terminal-based Trojan horses
- Blowfish algorithm, Common Symmetric Key Algorithms
- bogus nameserver cache poisoning, Authentication and DNS
- bogusns
directive, DNS best practices
- Bolsky, Morris
I. (The New Kornshell Command and Programmang
Language), Unix Programming and System Administration
- bombs, as destructive
attack, Destructive Attacks
- books,
security, Paper Sources–Security Periodicals
- boot disks, viruses on, Viruses
- BOOTP protocol, BOOTP: Bootstrap Protocol, and DHCP: Dynamic Host Configuration Protocol (UDP Ports 67 and 68)
- Bootparams table
(NIS+), NIS+ Tables and Other Objects
- Bostic, Keith
(The Design and Implementation of the 4.4 BSD UNIX
Operating System), Unix Programming and System Administration
- Bosworth, S. (Computer Security
Handbook), General Computer Security
- bounds checking, Coding Standards
- Bourne
shell, Conventions Used in This Book (see sh)
- bps (bits per second), Baud and bps
- brackets ([]), indicating optional
syntax, Conventions Used in This Book
- Brand, Russell, Worms
- break-ins, Prelude–Rule #3: Plan Ahead, Rule #2: Document, Rule #3: Plan Ahead–Rule #3: Plan Ahead, Rule #3: Plan Ahead, Discovering an Intruder–Other tip-offs, Discovering an Intruder, Monitoring commands, What to Do When You Catch Somebody–Getting Rid of the Intruder, Monitoring the Intruder, How to Contact the System Administrator of a Computer You Don’t Know–Alternative contact strategies, Cleaning Up After the Intruder–Damage Control, Preserving the Evidence–Preserving the Evidence, Resuming Operation–Damage Control, Case Studies–faxsurvey, Your Legal Options After a Break-in–The Responsibility to Report Crime, What the Superuser Can and Cannot Do, Chapter 22: Discovering a Break-In
- case
studies of, Case Studies–faxsurvey
- commands used to
discover, Discovering an Intruder
- commands used to
monitor, Monitoring commands, Monitoring the Intruder
- contacting
a remote system administrator, How to Contact the System Administrator of a Computer You Don’t Know–Alternative contact strategies
- detecting
and discovering, Discovering an Intruder–Other tip-offs, What the Superuser Can and Cannot Do
- documenting, Rule #2: Document
- legal
recourses after, Your Legal Options After a Break-in–The Responsibility to Report Crime
- planning
for, Rule #3: Plan Ahead–Rule #3: Plan Ahead
- preserving
evidence from, Preserving the Evidence–Preserving the Evidence
- recovering
from, Cleaning Up After the Intruder–Damage Control
- responding
to, Prelude–Rule #3: Plan Ahead, What to Do When You Catch Somebody–Getting Rid of the Intruder
- resuming
operation after, Resuming Operation–Damage Control
- security checklist
for, Chapter 22: Discovering a Break-In
- software toolkit
for, Rule #3: Plan Ahead
- A
Brief History of Time: From the Big Bang to Black Holes (Hawking, Stephen W.), Miscellaneous References
- broadcast
storms, Message Flooding
- Brunner, John (Shockwave
Rider), Understanding the Computer Security “Culture”
- brute force
attacks, A Cryptographic Example, Key Length with Symmetric Key Algorithms, Key Length with Symmetric Key Algorithms, Key search (brute force) attacks
- BSD 4.2, Unix goes commercial
- BSD 4.4 Lite, Versions Covered in This Book, Second-Generation Commercial Unix Systems
- BSD Unix, Which Unix System?, Which Unix System?, Versions Covered in This Book, Versions Covered in This Book, Unix escapes AT&T–The Unix Wars: Why Berkeley 4.2 over System V, What the Superuser Can’t Do, Secure Terminals: Limiting Where the Superuser Can Log In, BSD Kernel Security Levels, chmod: Changing a File’s Permissions, SGID and Sticky Bits on Directories, Connecting a Modem to Your Computer, Startup on different Unix systems, The inetd Program, Access Control Lists with TCP Wrappers, Using a Host-Based Packet Firewall, The ipfw host-based firewall, Sun RPC’s portmapper (UDP and TCP Ports 111), Hard, soft, and spongy mounts, /etc/exports–/usr/etc/exportfs, Samba Client Security, The Lesson of the Internet Worm, Using chroot( ), Package-Based Systems, Specialized Backup Programs, Setting up the chroot( ) environment, Setting up the chroot( ) environment, Disabling an Account by Changing the Account’s Password, Secure Terminals, Shadow Password Files, Immutable and Append-Only Files, Immutable and Append-Only Files, BSD’s mtree and Periodic Security Scans, BSD’s mtree and Periodic Security Scans, BSD’s mtree and Periodic Security Scans, Packaging Tools, Integrity checking with the BSD pkg_info command, utmp and wtmp Files, Accounting with BSD and Linux, Writable system files and directories, Reserved space, Listing processes with versions of Unix derived from BSD, including Linux, Unix Programming and System Administration
- (see also FreeBSD; Mac OS X; NetBSD;
OpenBSD)
- append-only
files, Immutable and Append-Only Files
- chroot wrapper, Setting up the chroot( ) environment
- exporting
filesystems read-only, Writable system files and directories
- exporting NFS
directories, /etc/exports–/usr/etc/exportfs
- Fast File System
(FFS) reserved space, Reserved space
- forcible
unmounts with, What the Superuser Can’t Do
- history of, Unix escapes AT&T–The Unix Wars: Why Berkeley 4.2 over System V
- host-based firewall
for, Using a Host-Based Packet Firewall, The ipfw host-based firewall
- immutable files, Immutable and Append-Only Files
- inetd program and, The inetd Program
- integrity-checking
tools, BSD’s mtree and Periodic Security Scans
- jail() system call, Using chroot( ), Setting up the chroot( ) environment
- kernel security
levels on, BSD Kernel Security Levels
- modems
and, Connecting a Modem to Your Computer
- mtree
program, BSD’s mtree and Periodic Security Scans
- nonexecutable stack, The Lesson of the Internet Worm
- package management
commands, Package-Based Systems
- packaging tools, Packaging Tools
- periodic security
scans, BSD’s mtree and Periodic Security Scans
- permission options
for, chmod: Changing a File’s Permissions
- pkg (package)
system, Integrity checking with the BSD pkg_info command
- portmapper program, Sun RPC’s portmapper (UDP and TCP Ports 111)
- process accounting
with, Accounting with BSD and Linux
- ps
command, Listing processes with versions of Unix derived from BSD, including Linux
- published resources
on, Unix Programming and System Administration
- secure
terminals, Secure Terminals
- server startup
on, Startup on different Unix systems
- SGID and sticky bits for
directories, SGID and Sticky Bits on Directories
- shadow password
file, Shadow Password Files
- SMB kernel
support, Samba Client Security
- spongy
mounts, Hard, soft, and spongy mounts
- TCP Wrappers support, Access Control Lists with TCP Wrappers
- terminal security on, Secure Terminals: Limiting Where the Superuser Can Log In
- utmp and wtmp log
files, utmp and wtmp Files
- vipw command, Disabling an Account by Changing the Account’s Password
- “no dump” file
attribute, Specialized Backup Programs
- BSD/OS, Businesses adopt Unix, Second-Generation Commercial Unix Systems, Second-Generation Commercial Unix Systems
- BSDI (Berkeley Software
Design, Inc.), Second-Generation Commercial Unix Systems
- buffers, Software Quality, The Lesson of the Internet Worm, Things to Avoid
- checking
boundaries, Things to Avoid
- overflow
attack, The Lesson of the Internet Worm
- overruns, Software Quality
- bugs, What Is Computer Security?, Software Quality, Keeping Secrets, Bugs (biological), Well-Known Bugs, An Empirical Study of the Reliability of Unix Utilities–Where’s the beef?, Tips on Avoiding Security-Related Bugs–Before You Finish, Before You Finish, Programmed Threats: Definitions, Hardware Bugs, Buggy Software–Buggy Software, Hacker Challenges, Security Bugs That Never Get Fixed, Bugtraq
- (see also insects,
effects on hardware)
- Bugtraq mailing
list, Bugtraq
- hacker challenges
and, Hacker Challenges
- hardware, Hardware Bugs
- in Unix
utilities, An Empirical Study of the Reliability of Unix Utilities–Where’s the beef?
- keeping
secret, Keeping Secrets
- in
NFS, Well-Known Bugs
- security, Security Bugs That Never Get Fixed
- software, Buggy Software–Buggy Software
- testing
for, Software Quality, Before You Finish
- tips on
avoiding, Tips on Avoiding Security-Related Bugs–Before You Finish
- Bugtraq mailing
list, Bugtraq
- Building a Secure Computer
System (Gasser,
Morrie), General Computer Security
- Building in Big Brother: The
Cryptographic Policy Debate (Hoffman, Lance
J.), Cryptography Books
- Building Internet
Firewalls (Zwicky, Elizabeth D.; Chapman, D.
Bren; Cooper, Simon), Network Technology and Security
- Building Secure
Software (Viega, John and McGraw,
Gary), General Computer Security
- bulk
erasers, Sanitizing Media Before Disposal
- Burning Chrome (Gibson, William), Understanding the Computer Security “Culture”
- byte-by-byte
comparisons, Comparison Copies–rdist