01
Security-by-design principles
LOGAM separates public clients from privileged provider credentials, validates input server-side, applies least-privilege role controls, uses prepared database queries, rate limits sensitive public and authentication functions, and records security-relevant administrative activity. Security controls are reviewed as the platform changes.
02
Encryption and credential protection
Production website, API and audio endpoints are required to use HTTPS/TLS where supported by the service. Passwords are stored using secure one-way hashing rather than reversible plaintext. Provider/API secrets and designated sensitive application credentials are encrypted at rest using server-side key material and are never sent to the Flutter app or ordinary website visitors.
03
Administrative protection
Privileged web-console accounts are subject to role restrictions and multi-factor authentication. Session, token and login controls are designed to reduce brute-force, session theft and unauthorised administrative access. Privileged actions may be logged for audit and investigation.
04
Application and API protection
LOGAM uses CSRF controls on browser state-changing actions, secure token handling for mobile clients, server-side validation, output escaping, prepared SQL statements, rate limiting and controlled API exposure. Public APIs must not return provider keys, password material, MFA secrets or unnecessary personal identifiers.
05
Incident response and breach handling
Suspected compromise, malicious access, data leakage or abuse should be contained, investigated, documented and remediated promptly. Where a personal-data security breach triggers statutory notification obligations, LOGAM will follow the applicable legal notification requirements. Evidence may be preserved for security, regulatory or law-enforcement purposes where lawful and proportionate.
06
Responsible security reporting
Users and researchers should report suspected vulnerabilities privately through official LOGAM support channels and should not exploit, publish, sell or use a vulnerability to access data or disrupt services. Good-faith reports do not authorise unauthorised access or any act prohibited by Zambian cyber law.
07
User security responsibilities
Users must protect their own passwords, devices and verification codes; must not share administrative credentials; and must not attempt to bypass authentication, rate limits, access controls, encryption, monitoring or provider protections. Suspected account compromise should be reported promptly.
β
Legal framework
LOGAM applies these laws and standards only to the extent they lawfully govern the relevant service, processing activity, user or jurisdiction.
Zambia Cyber Security Act, No. 3 of 2025Zambia Cyber Crime Act, No. 4 of 2025Zambia Data Protection Act, No. 3 of 2021Zambia Electronic Communications and Transactions Act, No. 4 of 2021Regulation (EU) 2016/679 (GDPR) Article 32 principles where GDPR applies
Legal note: This published station policy explains LOGAM's operational commitments. It does not replace case-specific advice from a qualified legal practitioner or an order of a competent authority.