CYB-22 · Cyber security

Security event logging — centralised logging enabled; logs retained for minimum 12 months

Without adequate logging, incident investigation and forensic analysis is impossible. All critical systems must generate security event logs that are centralised, tamper-protected, and retained for a minimum of 12 months. Logs must include authentication events, privilege escalations, and data access events.

High priority

Trigger

When this rule fires

No centralised log management; logs stored only on source systems (modifiable by attackers); logs retained for less than 12 months; authentication events not logged

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 — paragraph 7.3 (detection) / POPIA s.19

Legislation

Joint Standard 2 of 2024
POPIA s.19

Remediation

How to close the gap

Implement centralised SIEM or log management (e.g., Microsoft Sentinel, Splunk, AWS CloudWatch Logs). Enable audit logging on all critical systems. Configure 12-month log retention. Protect logs from tampering (read-only storage).

Evidence required

Evidence to prepare if this control applies

SIEM/log management system configuration
Log retention policy (minimum 12 months)
Sample of authentication event logs
Tamper protection configuration evidence

← Back to Operational Resilience