CYB-26 · Cyber security

Cloud security posture — cloud environments configured securely; no publicly exposed storage buckets or databases

Three of South Africa's biggest data exposures in recent years were caused by misconfigured cloud storage (S3 buckets, Azure Blob storage) left publicly accessible. Any cloud-hosted system holding client data must be audited for public exposure, default credential usage, and excess permissions (over-privileged service accounts).

High priority

Trigger

When this rule fires

No cloud security review in last 12 months; cloud storage buckets with public access enabled; default cloud service account credentials in use; no cloud security posture management (CSPM) tool deployed

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 / POPIA s.19 / CIS Cloud Benchmarks

Legislation

Joint Standard 2 of 2024
POPIA s.19

Remediation

How to close the gap

Run a cloud security assessment using native tools (Microsoft Secure Score, AWS Security Hub, GCP Security Command Center). Block all public storage access. Rotate default credentials. Implement least-privilege IAM roles. Enable cloud-level audit logging.

Evidence required

Evidence to prepare if this control applies

Cloud security posture assessment report
No public storage bucket confirmation
IAM permissions review
Cloud audit log configuration

← Back to Third-Party and Supply Chain Risk