South Africa Protection of Personal Information Act (POPIA)
Comply with key provisions of South Africa’s Protection of Personal Information Act
In November, 2013, the Parliament of the Republic of South Africa enacted the Protection of Personal Information Act, 2013 (POPIA):
To promote the protection of personal information processed by public and private bodies; to introduce certain conditions so as to establish minimum requirements for the processing of personal information; to provide for the establishment of an Information Regulator to exercise certain powers and to perform certain duties and functions in terms of this Act and the Promotion of Access to Information Act, 2000; to provide for the issuing of codes of conduct; to provide for the rights of persons regarding unsolicited electronic communications and automated decision making; to regulate the flow of personal information across the borders of the Republic; and to provide for matters connected therewith.
Potential consequences of non-compliance
Sections 100 – 106 of the POPI Act deal with instances where parties would find themselves “guilty of an offence”. Specifically, Section 105 (Unlawful Acts by responsible party in connection with account number) states that “the responsible party must…have known or ought to have known that…[a violation of personal data privacy] would likely cause substantial damage or distress to the data subject.”
Additionally, Section 106 (Unlawful Acts by third parties in connection with account number) states that “a person who knowingly or recklessly, without the consent of the responsible party...obtains or discloses an account number of a data subject…or procures the disclosure of an account number of a data subject to another person is…guilty of an offence.”
Section 107 details which penalties apply to respective offenses. Specifically, “Any person convicted of an offence…is liable…to a fine or to imprisonment for a period not exceeding 10 years, or to both a fine and such imprisonment; or…to a fine or to imprisonment for a period not exceeding 12 months, or to both a fine and such imprisonment.”
As detailed in Section 109 of the Act, the maximum fine “may not exceed R10 million.”
The following material is excerpted directly from the Republic of South Africa’s POPI Act
Security Measures on Integrity and Confidentiality of Personal Information
19. (1) A responsible party must secure the integrity and confidentiality of personal information in its possession or under its control by taking appropriate, reasonable technical and organizational measures to prevent:
- loss of, damage to or unauthorized destruction of personal information; and
- unlawful access to or processing of personal information.
In order to give effect to subsection (1), the responsible party must take reasonable measures to:
- identify all reasonably foreseeable internal and external risks to personal information in its possession or under its control;
- establish and maintain appropriate safeguards against the risks identified;
- regularly verify that the safeguards are effectively implemented; and
- ensure that the safeguards are continually updated in response to new risks or deficiencies in previously implemented safeguards.
Security Measures Regarding Information Processed by Operator
21. (1) A responsible party must, in terms of a written contract between the responsible party and the operator, ensure that the operator which processes personal information for the responsible party establishes and maintains the security measures referred to in section 19.
(2) The operator must notify the responsible party immediately where there are reasonable grounds to believe that the personal information of a data subject has been accessed or acquired by any unauthorized person.
Notification of Security Compromises
22. (1) Where there are reasonable grounds to believe that the personal information of a data subject has been accessed or acquired by any unauthorized person, the responsible party must notify;
- the Regulator; and
- subject to subsection (3), the data subject, unless the identity of such data subject cannot be established.
(4) The notification to a data subject…must be in writing and communicated to the data subject in at least one of the following ways:
- Mailed to the data subject’s last known physical or postal address;
- sent by e-mail to the data subject’s last known e-mail address;
- placed in a prominent position on the website of the responsible party;
- published in the news media; or
- as may be directed by the Regulator.
99. (1) A data subject or, at the request of the data subject, the Regulator, may institute a civil action for damages in a court having jurisdiction against a responsible party for breach of any provision of this Act as referred to in section 73, whether or not there is intent or negligence on the part of the responsible party.
(3) A court hearing proceedings in terms of subsection (1) may award an amount that is just and equitable, including:
- payment of damages as compensation for patrimonial and non-patrimonial loss suffered by a data subject as a result of breach of the provisions of this Act;
- aggravated damages, in a sum determined in the discretion of the Court;
- interest; and
- costs of suit on such scale as may be determined by the Court.
Entrust nShield® HSMs Can Help You Comply with POPIA and Avoid the Data Breach Notification Requirement
While POPIA is unclear about what is considered to be access and acquisition of subject data, regulations around the world that deal with protection of personal information state that if the data has been pseudonymized or made unreadable to whomever illegally retrieved it, then the data breach does not need to be reported; the stolen sensitive data has been rendered useless to the thieves and harmless to the data subject.
The two widely accepted best practice approaches to pseudonymization are encryption and tokenization. Both employ cryptographic keys to convert plain text to unreadable ciphertext and back again. If ‘cyberthieves’ steal the keys along with the encrypted or tokenized data, they can then convert the data back to plain text. So, it is essential to separate the keys from the data they protect and to provide additional security for the keys themselves.
Entrust Solutions for Cryptographic Key Security
Best practice for cryptographic key security is to store those keys in a hardware security module (HSM). Entrust nShield HSMs are hardened, tamper-resistant hardware devices that secure cryptographic processes by generating, protecting, and managing keys used for encrypting and decrypting data and creating digital signatures and certificates. These HSMs are tested, validated and certified to the highest security standards including FIPS 140-2 and Common Criteria. Entrust nShield HSMs enable organizations to:
- Meet and exceed established and emerging regulatory standards for data privacy
- Achieve higher levels of data security and trust
- Maintain high service levels and business agility
nShield as a Service is a subscription-based solution for generating, accessing and protecting cryptographic key material, separately from sensitive data, using dedicated FIPS 140-2 Level 3 certified nShield Connect HSMs. The solution delivers the same features and functionality as on-premise HSMs combined with the benefits of a cloud service deployment. This allows customers to fulfill their cloud first objectives and leave the maintenance of these appliances to the experts at Entrust.
Compliance Brief: South Africa POPIA
South Africa POPIA addresses the protection of the personal information along with the fines and civil action that may result from a violation.
Brochures : Entrust nShield HSM Family Brochure
Entrust nShield HSMs provide a hardened, tamper-resistant environment for secure cryptographic processing, key generation and protection, encryption and more. Available in three FIPS 140-2 certified form factors, Entrust nShield HSMs support a variety of deployment scenarios.
Datasheet: nShield as a Service
nShield as a Service is a subscription-based solution for generating, accessing and protecting cryptographic key material, using dedicated FIPS 140-2 Level 3 certified nShield Connect HSMs.