Professions subscribe to various end-user requirements for service delivery to maximise the effectiveness, and robustness of service and end-product.
Various tools are used to by System Administrators to ensure standards.
The simplest and most maligned tool is the humble checklist. We all use checklists in one form or another as a utility for achieving certain levels of outcome. At minimum, checklists form a structure of items and issues not to neglect and at best present a point in time for communication and evaluation of procedures.
Checklists have become important because:
Checklists are a toolkit, and various contrivances of a ‘checklist’ can either assist us, or just plain create additional (work/barriers) to achieving quality results.
Some directions for effective use of checklists to use it as a tool:
Hopefully, this site assists you and your team build checklists that helps to achieve quality results every time. Where short-comings exist in a checklist ensure that failings are known (recorded, communicated) and factored into it’s use and redesign.
The most dangerous part in a car, is the nut l> oose behind the wheel (the driver.)
These notes are not going to show you how to setup a secure server, and they just might give you suggestions that will make your setup insecure.