Date: 5 Sep 2001 10:28:12 GMT
From: Matthew Malthouse
Subject: Standard Operating Procedures


When making configuration changes to live production servers please
observe the SOP outlined below.

1.  Code and configuration changes will be made and tested in the
development evironment created for this purpose.  Under no circumstances
will the dev systems reflect the production environemnt.

2.  Please communicate any changes verbally to whoever happens to be
standing around at the time.  This element of the SOP may be ommitted
only if levaing your desk would cause undue inconvenience.

3.  Doccumentation of backout procedures is mandatory.  All docs to be
stored in the large stack of paper to the rear of the refreshment area
of your department.

4.  The timing of change implementation can be critical.  It is
therefore recomended that changes affecting the production systems are
only made in the last hour of your working day.

5.  Ensure that you have booked leave for the day or days immediately
following the changes.

6.  In the interests of system security root, admin and application
account passwords will be changed at random intervals as will all users
public and private keys.  Never commit critical passwords to writing and
under no circumstances allow them to become know to system or
application support personel.

I don't *think* that document has actually been formally written out
before.  Possibly because everyone aorund here are so used to doing
things this way that there was never any need.

But after this morning[0] I'm suggesting an addition:

7.  Do not return to the building.  Your severance pay will be in the
post.


Matthew

[0] Wrong data online; 3 hours impotently waiting for someone who could
fix it to turn up while being entertained by PHB asking at 15 minute
intervals why I couldn't fix it.