Action list: IT disaster prevention
What are you looking for?
Use the
sitemap
or the search.
Search
Contact Us
|
Client Login
|
Print Page
|
Email Page
Home
|
About Us
|
How to find us
History of the firm
Wright Hassall in the community
Sporting sponsorships
Accessibility
Our Services
|
Full list
Business legal services
Personal legal services
Your Sector
|
Our People
|
By Service
A to Z
Legal Resources
|
FAQs
Articles
Fact Sheets
Newsletters
News & Events
|
Join Us
Vacancies
Why work with us?
What can we offer you?
Work placements
Trainee recruitment
Work experience
What is it like to work at WH?
Home
>
Legal Resources
>
Fact Sheets
>
Action list: IT disaster prevention
contact
Laurie Heizler
related service
Intellectual Property & Technology
IT disaster prevention
Consider how serious the
consequences
of system failure, misuse or data loss could be; use this to decide how much to invest in disaster prevention.
Purchase
proven
equipment and software; try to avoid bespoke systems.
Arrange any external
support
you may need: for example, installation, maintenance, training, troubleshooting and disaster recovery.
Physically protect
your equipment; use surge protectors or uninterruptible power supplies and ensure that your premises are secure.
Establish
security
procedures (eg password control) and use anti-virus software and an Internet firewall.
Assign
responsibility
for the system to one individual; provide appropriate training and clear guidance on when to call on external experts.
Train
employees
how to use your IT system and specify what tasks must be referred to others; establish a procedure for reporting faults or problems.
Establish and implement an email and
Internet policy
to regulate employees’ use of the Internet and to minimise the risks of a virus entering your system.
Restrict
software installation
and configuration to authorised, trained personnel; ban employees from installing unnecessary software.
Establish a safe installation and
upgrade procedure
, including backing up data, updating your anti-virus protection and running parallel systems while testing if necessary.
Carry out regular
routine maintenance
: for example, cleaning equipment, running system utilities, archiving old files and testing system performance.
Establish an effective daily
back-up
procedure, and store back-ups securely off-site; regularly test to ensure that you can restore data.
Keep clear
records
of system configuration, software versions and upgrades or patches; securely store copies of software and updates.
Prepare
contingency plans
in case of disaster, including manual systems for maintaining key operations; consider insuring your system and data.
Cardinal Rules
Do:
protect
your system physically and with appropriate software and procedures
train employees
identify and arrange any
external support
you need
identify and arrange any
external support
you need
identify and arrange any
external support
you need
back-up
your data
make
contingency plans
Don’t:
allow untrained employees to
install
unnecessary software
ignore the need for
routine maintenance
assume that
procedures
will always be followed
assume that
procedures
will always be followed
assume that
procedures
will always be followed