[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference 7.286::digital

Title:	The Digital way of working

Moderator:	QUARK::LIONELON

Created:	Fri Feb 14 1986
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5321
Total number of notes:	139771

861.0. "Dismissing Employees" by MSAM00::DOUGLASBURKE (Breaking through my walls!) Fri Jul 14 1989 12:13

    What are the normal procedures involved within the company when
    an employee is "discharged"?
    
    Further, what about the situation where the employee is the system
    manager for an important internal system...and on top of that, if
    the employee could react in a potentially hostile way?
    
    I don't actually know of anyone in this situation within Digital.
    But the question has come up at a customer site and I wanted to
    see how Digital might handle it.
    
    Doug

T.R	Title	User	Personal Name	Date	Lines
861.1		HPSRAD::KIRK	Matt Kirk -- 297-6370	`Fri Jul 14 1989 12:54`	15
861.2	Make recommendations based on the actual situation	COVERT::COVERT	John R. Covert	`Fri Jul 14 1989 12:55`	20
	I'm not sure it's appropriate to discuss with a customer how "Digital might handle it." Although our disciplinary policy (6.21) is not labelled "Digital Internal Use Only," I think you're more interested in the security aspects, which would vary considerably from site to site and based on a threat analysis. The obvious recommendations with respect to the system are to go through the system authorization file with a fine tooth comb to be sure all accounts belong to real people and to be sure that all passwords are changed. Even non-privileged passwords will have to be changed if the person had a chance to leave a trap door program around before he left -- he could use the trap door program from a non-privileged account. If there is sufficient concern, the entire system should be rebuilt from new distribution tapes obtained directly from Digital and third party vendors, and all customer software should be examined in source, line by line, for trap doors, recompiled, and reinstalled. /john
861.3	Try HUMAN::SECURITY_INFORMATION	NOTIME::SACKS	Gerald Sacks ZKO2-3/N30 DTN:381-2085	`Fri Jul 14 1989 13:32`	0
861.4	ORANGBOOK	IAMOK::DELUCO	A little moderation never hurt anyone	`Wed Jul 26 1989 17:18`	3
	Try the US Personnel Policies and Procedures VTX infobase (Keyname ORANGEBOOK), then keyword search for "terminations". I think policy 6.01 covers some specifics.