3.3
Table Of Contents
- Avid iNEWS Administration Guide
- Contents
- Using This Guide
- 1 - Introduction
- 2 - Connect Services
- 3 - Database Security
- 4 - Database Management
- 5 - Backing Up the iNEWS System
- 6 - Disconnects
- 7 - Troubleshooting
- A - Command References
- Programs Invoked by iNEWS
- Commands Used by Avid Personnel Only
- Linux Commands Used in iNEWS
- Console Control Commands
- Console Server Commands
- broadcast
- configure
- connect
- ctraits
- dbclean
- dbclose
- dbdev
- dbdump
- dbfree
- dblines
- dboriginal
- dbpurge (Superuser conditional)
- dbrestore
- dbserver
- dbsort
- dbtraits
- dbvisit
- dictionary
- diskclear (Superuser only)
- diskcopy
- doc
- ed
- enter
- force (Superuser only)
- grpcheck
- gtraits (Superuser only)
- help
- hogs
- idiff
- list
- list B
- list C
- list c
- list d
- list g
- list p
- list q
- list s
- list sq
- list u
- logout
- makemontab
- makeshift (Super user only)
- maketab (Superuser only)
- msgclean
- offline
- online
- otod
- reconnect
- remove
- rename (Superuser only)
- reorder
- restart
- searchtape
- send
- shutdown
- sitedump (Superuser only)
- siterestore (Superuser only)
- startup
- status
- stop
- su
- unbusy
- utraits (Super user only)
- version
- wholockedit
- Job List Commands
- Dialog Commands
- B - System Files
- C - Standard Dictionaries
- Using Dictionaries to Define Messages and Commands
- Customizing Dictionaries
- Utility Messages Dictionary (/site/dict/messages)
- DBServer Program Messages
- Disconnect Program Messages
- Category and Keyword Check Program Messages
- Keyboard Check Program Messages
- Keyboard Check Program Messages for Macros
- Grpcheck Messages
- Wire Program Messages
- Mail Server Messages
- Validation (Action) Server
- Seek Server Messages
- Last Login Messages
- Print Server Messages
- dbtraits Messages
- Save Error (Workstation) Messages
- Queues Dictionary (/site/dict/queues)
- Words Dictionary (/site/dict/words)
- Keyboard Macros Dictionary (/site/dict/keymacros)
- Case-shifting Dictionary (/site/dict/shift)
- MCS Dictionary (/site/dict/mcs)
- Job List Command Dictionary (/site/dict/joblist)
- D Messages Dictionary (/site/dict/dmessages)
- S Messages Dictionary (/site/dict/smessages)
- D - Environment Variables
- E - Managing Traits at the Console
- F - The Line Editor, ed
- Index
3 Database Security
38
Establishing Security Procedures
Use the following guidelines to improve the security of your system:
• Set up official security procedures and have everyone follow them.
• Keep track of your backup tapes. You can get user passwords from a backup tape.
• Assign users superuser status only when they need it.
• If any user does not need superuser status, remove it. Create two user accounts for staff
members who need superuser privileges—one to be a superuser and another to be a
regular user. That way, you can track activity of superuser accounts.
• Change the superuser password regularly.
• Ensure that users do not use their names, station call letters, or other easily guessed
words as passwords. Require everyone to include at least one non-alphabetic character
such as a punctuation mark or a number.
• Use the system profile to set a required minimum length for all passwords so no one
uses a short password.
• For devices for which you have dedicated resources—that is, devices that have a
one-to-one correspondence between the physical device and device number used to
identify it—use device name security on workstations in specific locations and put the
device ID in a group.
• If you have dedicated resources, you can put a MODIFY-DEV field in the queue’s story
form if you suspect that someone has broken into a user’s account. When changes are
made to stories created after the MODIFY-DEV field has been added, the system puts
the device name of the workstation where changes were made in that field. This
information is kept internally, but having the MODIFY-DEV field makes it visible to
users.
• Be familiar with valid user accounts on your system. Restrict access to these account
names to protect against unauthorized outside access.
User Passwords
Your iNEWS newsroom computer system protects against unauthorized access by giving
each authorized user a password to log into the system. Group security, described under
“Using Group Security to Control System Access” on page 45, lets you control specific
areas of your database that each user can access.