What it asks for. The organisation must designate who may make information publicly accessible, train them to avoid publishing non-public information, review proposed content before posting and check public content periodically, removing non-public information when found.
In practice. This applies to websites, social media, public code repositories and documentation portals. Good practice includes defined publishing roles, approval workflows and periodic scans for exposed sensitive data, such as secrets in public repositories. Auditors look for role assignments, approval records and review results. Scanning for exposed secrets should be automated and linked to rapid revocation.
Common gaps. Developers sometimes publish code containing credentials or internal details. Public cloud storage and shared links can expose data without anyone going through a publishing process. Reviews of existing public content are also rare.