CYB-13 · Cyber security
Multi-factor authentication (MFA) — enforced for all staff accounts across all systems
MFA is the single most effective control against credential-based attacks — which account for the majority of SA financial sector breaches. MFA must be enforced (not optional) for: email, policy admin systems, CRMs, file sharing, and any system holding client personal information. Joint Standard 2 explicitly mandates MFA.
Trigger
When this rule fires
MFA not enforced on email accounts; MFA not enforced on policy admin system; MFA optional rather than mandatory for any system holding client PII
Applicability gate
Confirm the entity's role before treating this as a duty
This is a readiness rule mapped to JS2 themes. Its presence in the library does not establish that JS2 applies directly to the firm.
- Insurance Broker: Most independent non-life Category I brokers are not directly in JS2's defined scope. A broker may be directly in scope if it separately meets a listed category, and may face contract or oversight requirements from an in-scope institution. Third-party provisions impose duties on the in-scope financial institution. They do not themselves make every supplier or intermediary directly subject to JS2.
- Uma Binder Holder: UMA or binder-holder status is not itself listed in JS2's definition. Direct scope depends on another listed capacity; insurer contracts and oversight may create evidence requirements. JS2 paragraph 3.3 concerns juristic persons structured under an insurer or designated insurance group; it is not a blanket rule for every independent UMA or intermediary.
- Insurer: An insurer as defined in the Insurance Act is directly in scope of JS2 from 1 June 2025. Apply proportionality and distinguish the insurer's own duty from requirements it places on third parties.
Citation
Mapped source
This control maps to the public instruments below. The mapping does not establish entity applicability.
- Section
- Joint Standard 2 of 2024 — paragraphs 7.2.2 (identity and access management) and 8.3 (multi-factor authentication) / POPIA s.19
- Legislation
-
- Joint Standard 2 of 2024
- POPIA s.19
Remediation
How to close the gap
Enable MFA on all Microsoft 365 / Google Workspace accounts immediately. Enable MFA on all client-data-holding systems. Use authenticator app or hardware token — avoid SMS OTP where possible (SIM-swap risk is elevated in SA).
Evidence required
Evidence to prepare if this control applies
- Microsoft 365 / Google Workspace MFA policy screenshot
- MFA enforcement status from each system administrator
- Conditional Access policy configuration (Azure AD) or equivalent
- Staff acknowledgement of MFA requirement