Cybersecurity guide for developing countries
A client files a registration request (certification request) to a certification authority (web-based
registration service). The registration server may ask for proof of the client’s identity according to the
identification and authentication procedures put in place by the authority. After validation of the
information, the certification server generates encryption keys and produces a digital certificate in the
client’s name, signs the certificate with its private key (certification of the digital certificate) and sends
the certificate to the client. The client will use the authority’s public key to verify that the certificate
has indeed been issued by the authority in question.
A certification authority is a trusted third party which issues digital certificates and serves to verify the
validity of certain information.
III.2.1.7
Drawbacks and limitations of public key infrastructures
The fact that there are several certification authorities poses problems in terms of their mutual
recognition, their interoperability, the compatibility of certificates and their scope of validity.
Nevertheless, it is not desirable to have only one global certification authority, in view of the vast and
excessive powers that would de facto be conferred on it, and in view of the magnitude of the infrastructure to be established. There is a genuine lack of trust on the part of users in respect of such
certification authorities, which are generally foreign (validity of certificates? security guarantees?
protection of personal data? etc.).
The inherent limitations in public key infrastructures reside in:
–
–
–
the complexity of an infrastructure, and the cost of deploying and managing it;
the high level of security required to set up PKI services;
the validity, duration and termination of certificates.
The potential problem areas in the implementation of PKI services include:
–
–
–
III.2.1.8
Political problem: Most PKI infrastructures – certification authorities – belong to American
(US) entities. This raises the question of performance and the issue of trust in these entities in
view of the services they provide (creation, storage and distribution of private and public keys,
identification data, notarization), the lack of guarantees in terms of possible misuse of data,
neutrality in exchanges and available recourse in the event of a dispute with the certificate
authority.
Technological problem: Conventional encryption systems can be broken, some digital
certificates offer no security or guarantees, fraud is possible, infrastructure security is provided
by conventional security means which can be circumvented. Furthermore, the use of a key
infrastructure shifts the problem of security of exchanges, without actually resolving it.
Organizational problem: Infrastructure interoperability, deployment, management,
maintenance, security, complexity, etc.
Signature and authentication
A sender encrypts a message with his private key. Any entity knowing the sender’s public key will be
able to decrypt the message, thereby confirming the fact that it was indeed created with the
corresponding private key.
A document can be signed electronically (digital signature) using a public key encryption algorithm,
as follows:
64
–
creation of a message declaring the sender’s identity – the signature (e.g. “My name is Alpha
Tango Charlie”) – which is encrypted with the sender’s private key and attached to the
message to be transmitted;
–
–
the message and its signature are encrypted with the recipient’s public key, and transmitted;
the recipient decrypts the message with his private key and detaches the signature which he
deciphers with the sender’s public key.
Security tools
Select target paragraph3
Connect to a paragraph
Connect to an entity
Disable highlights
Add to table of contents