Admin portal exposure — no unauthenticated admin interfaces exposed on public-facing infrastructure

Public exposure of administrative interfaces (/admin, /wp-admin, /cpanel, /phpmyadmin, etc.) without strong authentication is one of the most exploited weaknesses in SA SME environments. Admin portals must not be publicly reachable or must require MFA before any content is served.

Critical priority

Trigger

When this rule fires

Admin portal accessible from public internet without MFA, or returns a login page without any additional authentication layer, or server/CMS version information exposed in HTTP headers

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 / OWASP Top 10 A05

Legislation

Joint Standard 2 of 2024

Remediation

How to close the gap

Restrict admin portal access to IP allowlist or VPN. Enforce MFA on all admin accounts. Remove or mask server version headers (Server:, X-Powered-By:). Change default admin URL paths.

Evidence required

Evidence to prepare if this control applies

Penetration test report confirming admin portal is not publicly accessible
IP allowlist or VPN access control configuration
MFA enforcement screenshot for admin accounts
HTTP header scan showing no version disclosure

Automated assessment

Verified by the Provantis cyber scanner. Machine checks performed:

ADMIN_EXPOSED
OPEN_DIRS

← Back to Digital Channel and Technical Security