Back to Insights

POPIA Compliance Framework

Technical Implementation Guide for SA Business

The POPIA Compliance Framework is a guide to the technical and procedural controls required to align with the Protection of Personal Information Act (POPIA), moving beyond legal theory into practical IT implementation.

The POPIA controls in this guide at a glance
AreaControlWhat it means in practice
Reasonable measures (Section 19)Encryption at restEvery laptop and portable drive encrypted with BitLocker or FileVault
Reasonable measures (Section 19)Access controlUnique user accounts with MFA, and no shared passwords
Data lifecycleCollection (minimality)Forms collect only the data you need, and ID numbers only where the law requires them
Data lifecycleDestructionRetention policies that archive and delete on a schedule, such as CVs of unsuccessful candidates after 6 months
Information OfficerSection 18 noticesA clear privacy policy linked from the website and from email signatures
Information OfficerOperator agreementsA signed written contract with every third party that handles your data
Incident responseImmediate actionDisconnect infected systems and change global admin passwords
Incident responseNotificationNotify the Information Regulator and the affected people as soon as reasonably possible

1. What is POPIA's reasonable measures standard?

POPIA Section 19 requires a responsible party to secure the integrity and confidentiality of personal information by taking appropriate, reasonable technical and organisational measures.

What counts as "Reasonable" in 2026?

Reasonable in 2026 means encryption on every laptop and portable drive, and a unique account protected by MFA for every person.

Encryption at Rest:All laptops and portable media MUST be encrypted (BitLocker/FileVault). If an encrypted laptop is stolen, the data is technically inaccessible, transforming a "Data Breach" into a simple "Hardware Theft".
Access Control (Identity):You must prove you know WHO is accessing data. Shared passwords (e.g., admin/admin) are a violation. Unique user accounts with MFA are the baseline standard.

2. What is data lifecycle management under POPIA?

Data lifecycle management is the practice of collecting only the personal information you need and destroying it once you no longer need it.

Collection (Minimality)Configure forms to stop collecting data you don't need. Do not store ID numbers unless legally required (e.g., for payroll or RICA).
Destruction (Right to be Forgotten)Implement auto-archiving policies. E.g., "Delete CVs of unsuccessful candidates after 6 months." Microsoft 365 Retention Policies can automate this.

3. What are the Information Officer's digital duties?

The CEO is the default Information Officer, but they must ensure:

Section 18 Notices (Privacy Policy):Ensure your website and email signatures link to a clear privacy policy stating what you do with data.
Operator Agreements:If you use 3rd party IT support (like AMEA), you must have a signed written contract ensuring WE handle your data securely too.

4. What must a POPIA incident response plan contain?

A POPIA incident response plan is two things written down in advance: the immediate technical actions and the notifications you must send. If a breach occurs, you have a limited time to act. Don't invent a plan during a crisis.

Immediate Action: Disconnect infected systems. Change global admin passwords.
Notification: You must notify the Information Regulator (Form 3) and affected data subjects "as soon as reasonably possible".
Legal Disclaimer: This guide is provided for general informational purposes only and does not constitute legal or professional advice. AMEA Technologies (Pty) Ltd makes no representations or warranties of any kind regarding the completeness, accuracy, or suitability of this information. Any reliance you place on this content is strictly at your own risk. We accept no liability for any loss or damage arising from the use of this guide. POPIA compliance requirements may vary based on your specific circumstances. You are advised to consult qualified legal and IT professionals before implementing any recommendations.