MyMIS
If, for example, an organisation uses cryptographic facilities to secure its
communication, it must be ensured that those facilities (e.g. CAs, key
management server) operate with the same security after a disaster.
Need for crypto DRP
Therefore every organisation must have a DRP for its crypto facilities. The
crypto DRP can be complicated because one simply cannot run a back-up
for a CA key service as in the case of a ‘normal’ database. Due to the
confidential character of the data, there must be a secured back-up that has
to be restored in a secure way by trusted staff.
3.11.4.2
Dealing with
cryptographic disasters
Clear instruction to
recover from
cryptographic failure
Key escrow may help in
emergency situations
Cryptographic Disasters
The second relationship between a DRP and cryptography is planning how
to deal with events caused or made complicated by cryptographic services,
especially unforeseen failures. As an example, an institution may have an
up-until-now-secure logical access control system, yet has noticed clear signs
of an intruder into the system. One possibility is that the cryptographic system
has failed. In such a situation, there should be clear instructions on how to
proceed. Without such instructions, well-intentioned acts may exacerbate
the problem. For example, attempting to unravel cipher text by modifying it
may cause permanent damage.
Another example of a cryptographic disaster is the encryption of vital information
by an employee who is now demanding a ransom for the decryption key in
exchange for a gain. Such a problem may be solved through technical means
(escrow), law enforcement, or negotiation. Unless the organisation plans for
a technical solution, other solutions may be expensive, embarrassing, or
both.
No complete list of threats exists and a complete list of counter-measures
is impossible to produce. As a general guideline on this issue of cryptographic
disaster, an information and communications security and disaster recovery
programmes of an organisation must address cryptographic threats, at least
in a generic form.
A written policy should cover the following:
(a) regular monitoring of the information processing system for abnormal
behaviour;
(b) procedures to be followed in determining the cause of abnormal
behaviour and guidelines on how to respond to a threat, intruder,
compromise, etc;
(c) procedures for dealing with the failure of any cryptographic control;
and
(d) provision for the availability of cryptographic services, keying material,
and other related services following business interruption.
3.11.4.3
Take steps according to
the incident reporting
mechanism when crypto
disaster occurs
Copyright MAMPU
What to do in the Event of a Cryptographic Disaster
Following a disaster, the officer responsible for ICT security in a department
is required to act based on the Mekanisme Pelaporan Insiden Keselamatan
Teknologi Maklumat dan Komunikasi (ICT) as per Appendix H.
Chapter 3 - 36
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents