POPIA does not give a list of required products. Section 19 requires "appropriate, reasonable technical and organisational measures" to protect personal information. For a small business that means in practice: multi-factor authentication, encrypted devices, tested backups, patched systems, endpoint and email protection, prompt removal of leavers, a registered information officer and a plan for reporting a breach. This is general information, not legal advice.
What does POPIA actually require of your IT?
Section 19 of the Protection of Personal Information Act says a responsible party must secure the integrity and confidentiality of personal information by taking reasonable technical and organisational measures. The aim is to prevent loss, damage or unauthorised destruction, and unlawful access. Section 19(2) adds that you must identify foreseeable internal and external risks, put safeguards in place, check they work, and update them as risks change. Section 19(3) says you must have due regard to generally accepted information security practices.
The Act applies to every business that holds personal information about clients, staff or suppliers. That is every business. The sections below turn that into controls you can check.
Which technical controls should be in place?
- Multi-factor authentication. Turn it on for Microsoft 365, remote access and any system holding client data. A stolen password then is not enough to get in.
- Device encryption. Laptops and phones should be encrypted, so a lost or stolen device does not mean exposed client files.
- Backups. Keep copies away from the systems they protect, and test restores. Section 19(1)(a) is about loss of personal information, and a backup you have never restored is a guess.
- Patching. Keep Windows, other operating systems and common applications up to date on a schedule, and track the exceptions.
- Endpoint protection. Every computer and server needs protection that someone actually monitors. An alert nobody reads protects nothing.
- Email security. Filtering for phishing and malicious attachments, plus SPF, DKIM and DMARC records on your domain.
- Access control. Staff should see only what their job needs. Avoid shared logins and avoid making everyone an administrator.
Our cybersecurity service covers these on a managed basis.
What should happen when a staff member leaves?
Block the sign-in on their last day, not weeks later. Hand the mailbox and files to a manager, collect company devices, remove access to line-of-business systems and shared passwords, and release the licence. Former staff with working accounts are among the most common gaps we find, and they are hard to defend as "reasonable measures" under section 19.
Do you need an information officer?
Yes. Under section 55, every public and private body has an information officer. For a private business this is normally the owner or chief executive, unless it is formally delegated. Section 55(2) says information officers may take up their duties only after being registered with the Information Regulator. Registration is done online through the Regulator's eServices portal. Section 56 allows deputy information officers to be designated, which helps in a larger office.
Your IT provider can supply the technical documentation the information officer needs, but cannot take on the role for you.
What must you do after a data breach?
Section 22 applies where there are reasonable grounds to believe that personal information has been accessed or acquired by an unauthorised person. You must notify the Information Regulator and the affected people, unless a person's identity cannot be established. The Act says this must happen "as soon as reasonably possible" after the compromise is discovered, allowing for law enforcement needs and the steps needed to establish the scope and restore your systems. It does not set a fixed number of hours.
The notice to individuals must be in writing and must give enough information for them to protect themselves, including the likely consequences, what you are doing about it and what they should do.
Plan ahead: know who decides, who calls your IT provider, and where your sign-in logs are kept. Without logs, it is hard to say what was accessed.
What about suppliers who handle your data?
Section 21 covers operators, meaning anyone who processes personal information on your behalf, such as a payroll bureau, hosting company, cloud service or IT provider. You must have a written contract that requires the operator to maintain the security measures in section 19. Under section 21(2), the operator must notify you immediately if it has reasonable grounds to believe personal information has been accessed or acquired by an unauthorised person. Check that your agreements say so.
Common questions
Does a small business have to comply with POPIA?
Yes. The Act applies to any business that processes personal information, regardless of size. A small office still holds staff records and client details.
Is MFA required by POPIA?
POPIA does not name MFA. Section 19 requires reasonable measures, and given how many account takeovers start with a stolen password, MFA is hard to leave out.
Who registers the information officer?
The business does, through the Information Regulator's eServices portal. Under section 55(2) the information officer should be registered before taking up their duties.
Can an IT provider make us POPIA-compliant?
Not alone. Much of POPIA is policy and process. An IT provider can put the technical controls in place and document them.
This article is general information and not legal advice. For your own obligations, speak to an attorney or privacy specialist.
If you want to check where your technical controls stand, get in touch or see our cybersecurity service.