The ability to manage state affairs remotely—reviewing files, issuing directives, or approving administrative acts—is now technically feasible. Yet when the head of state is involved, reliance on standard digital tools is insufficient. The systems in place must ensure the confidentiality of sensitive information, verify the identity of the decision-maker, maintain the integrity of official documents, and provide full traceability of every instruction.

This critical discussion was reignited by a statement from Cameroon’s Minister of Higher Education, Professor Jacques Fame Ndongo. Addressing concerns about a possible leadership gap, he asserted that President Paul Biya continues to oversee governance, either in person or through designated electronic channels accessible to authorized personnel. While this reassurance addresses political debates, it raises a more pressing operational question: what secure digital infrastructure should a modern presidency deploy when the head of state is abroad?

Publication on social media or official websites merely represents the final step in communication. It reveals nothing about how a decree was drafted, transmitted, reviewed, signed, logged, or stored—critical stages that demand rigorous oversight.

institutional email: a non-negotiable foundation

At minimum, all communications concerning state business must originate from official email addresses under the Presidency’s domain. For example, addresses like [email protected] should be mandatory for all staff, replacing personal accounts on Gmail, Yahoo, or other consumer platforms. Personal email poses significant risks: the state lacks control over account creation, device access, message retention, and account deactivation upon staff turnover.

A dedicated messaging system under the @prc.cm domain would enable:

• Instant creation and revocation of staff accounts;
• Implementation of multi-factor authentication;
• Secure retention of official exchanges;
• Detection of suspicious login attempts;
• Prevention of automatic forwarding to personal inboxes;
• Uniform security policies and archiving protocols.

To counter identity theft and phishing, the system should integrate SPF, DKIM, and DMARC protocols and enforce end-to-end encryption between servers. Even with such safeguards, highly sensitive documents should never be transmitted as email attachments. Instead, the system should notify recipients that a file is available in a high-security presidential platform.

a dedicated presidential document management platform

A specialized electronic document management system is essential for handling state affairs. Each file should be tagged with:

• A unique identifier;
• The identity of its creator;
• Its confidentiality level (public, internal, confidential, or highly sensitive);
• List of authorized personnel;
• Version history and comments;
• Timestamp of final approval;
• Complete access log.

This allows the President to review documents on a secure terminal, add annotations, request revisions, or grant approval—without files being duplicated across devices or shared via insecure channels. For highly classified material, the platform should block local downloads, printing, text copying, and unauthorized transfers.

The system should also log every interaction: who accessed the document, when, from which device, and what changes were made. Such traceability is vital for reconstructing events in case of leaks, intrusions, or disputes over authenticity.

electronic signatures: beyond scanned images

Remote approval of decrees or decisions must not rely on scanned signature images. Instead, certificate-based electronic signatures should be used to verify:

• The identity of the signatory;
• The integrity of the document;
• The exact date and time of validation;
• That no alterations occurred post-signature.

The cryptographic key used for signing must be stored in a hardware security module (HSM)—never on a standard computer, USB drive, or personal phone. Each use must require direct authentication from the President and generate a time-stamped audit trail.

For critical decisions, the process could include multiple layers of validation: presidential approval, technical signature verification, legal review, official registration, and public release.

zero trust architecture: redefining remote access

A Virtual Private Network (VPN) enhances connection security between a traveling official and presidential servers, but it should not be the sole safeguard. A Zero Trust framework assumes no user, device, or network is inherently trustworthy. Access requests are evaluated based on:

• User identity;
• Device authentication;
• Geolocation of the connection;
• Document sensitivity level;
• Assigned user permissions;
• Behavioral patterns during the session.

To access a presidential file, an official may need to authenticate using an institutional device, a digital certificate, encrypted connection, a physical security key, and a local biometric check on the device itself.

exclusively institutional devices

Presidential documents must never be accessed via personal phones or laptops. Staff in the Civil Cabinet, General Secretariat, and relevant agencies should use devices owned and managed by the state. These should be:

• Fully encrypted;
• Regularly updated with security patches;
• Restricted to approved applications;
• Segregated from personal use;
• Remotely wipeable in case of loss;
• Set to auto-lock after brief inactivity;
• Prohibited from connecting to unsecured public Wi-Fi.

A centralized device management system would allow administrators to push updates, block dangerous apps, revoke devices, and remotely delete data if compromised.

phishing-resistant authentication

A complex password alone is insufficient. Authentication should combine:

• An institutional device;
• A personal code;
• A physical security key;
• Optional local biometric verification.

While SMS-based codes add a layer of security, they remain vulnerable to interception. For high-risk accounts, physical keys and digital certificates offer stronger protection. Regular staff training is essential to recognize fake messages, fraudulent urgency requests, malicious links, and impersonation attempts targeting senior officials.

WhatsApp: alert, but never transmit

Despite its widespread use in Cameroon—including within government circles—WhatsApp’s end-to-end encryption does not qualify it as an official document transmission tool. Risks remain:

• Loss or compromise of personal devices;
• Screenshots or unauthorized forwarding;
• Inadequately protected backups;
• Use by former staff with residual access.

WhatsApp lacks the features needed for document classification, access control, versioning, electronic signing, or archival compliance. It can, however, be used to alert: “The file PRC/SG/2026/125 is ready for review in your secure workspace.” The actual document must never be attached.

Rule of thumb: Use WhatsApp for coordination and alerts. Use the secure presidential platform for transmission, review, decision-making, signing, and archiving.

secure government videoconferencing

Remote meetings between the President and advisors should occur on a dedicated, government-grade videoconferencing platform that ensures:

• End-to-end encryption;
• Participant identity verification;
• Strict invitation controls;
• Prohibition of unauthorized recordings;
• Retention of connection logs;
• Exclusive use of institutional devices;
• Data hosting under national jurisdiction.

Public links, free accounts, and unvetted applications must be avoided for sensitive discussions involving defense, diplomacy, appointments, or government decisions.

document classification: matching sensitivity to security

Not all presidential documents carry the same risk. A classification policy could define four tiers:

• Public: intended for public release;
• Internal: for state service use;
• Confidential: disclosure could harm public action;
• Highly sensitive: related to defense, intelligence, diplomacy, strategic appointments, or major arbitrations.

Each tier dictates allowed transmission channels, authorized personnel, permitted devices, printing rights, retention periods, and archival procedures. A public document may be sent via official email. A highly sensitive file must only be accessible within a tightly controlled platform.

full traceability: the cornerstone of trust

Every consultation, modification, approval, or transmission must be automatically recorded. The security log should capture:

• Who accessed the document;
• When and from which device;
• What changes were made;
• Who granted final approval;
• When the document was officially logged and published.

A dedicated security operations center could detect anomalies such as unusual login times, bulk downloads, access from unrecognized devices, or unauthorized edits. This traceability enables reconstruction of events in case of leaks, breaches, or disputes over authenticity.

social media ≠ governance systems

While the Presidency’s Facebook and X accounts facilitate public communication, they are not platforms for preparing or validating decisions. Before a decree is published online, it must follow a secure process:

• Transmitted through authorized channels;
• Authenticated by the competent authority;
• Verified as unaltered in its final form;
• Time-stamped upon validation;
• Preserved in official archives.

A visible signature on a social media image does not constitute full digital proof. The integrity of a decision depends on the entire secure workflow that preceded publication.

ten priority actions for the presidency

The Presidency should implement these ten measures without delay:

1. Mandate official email under the @prc.cm domain;
2. Ban personal email accounts (Gmail, Yahoo, etc.) for state business;
3. Deploy a presidential electronic document management platform;
4. Introduce secure, certificate-based electronic signatures;
5. Issue exclusively institutional phones and computers to staff;
6. Enforce multi-factor authentication resistant to phishing;
7. Restrict WhatsApp to alerts and coordination only;
8. Classify documents by sensitivity level;
9. Centralize access logs in a security operations center;
10. Train staff regularly on espionage, phishing, and information leakage risks.

While no public evidence confirms that all these measures are currently in use, they represent the minimum security standards required for a presidency managing sensitive state affairs remotely. The stakes are high: financial integrity, diplomatic confidentiality, national security, and the continuity of governance itself depend on it.

These concerns—secure document transmission, electronic signatures, data sovereignty, and digital continuity—will take center stage at E-Gov’A 2026 – E-Gov Africa Summit, Expo & Awards, slated for October 14–16, 2026, at the Palais des Congrès in Yaoundé. Under the theme “Artificial Intelligence and E-Governance: Building Efficient Public Services in a Cashless, Paperless Africa,” the event will gather policymakers, development agencies, public institutions, businesses, and digital experts from across the continent.

The question is not whether a president can work from Geneva, Paris, or New York. The real challenge is whether the tools in use can authenticate decisions, protect state secrets, trace instructions, and prevent fraud such as forgery or unauthorized alterations in the President’s name.

modern tools, uncompromising trust

Remote presidential work is not a technological impossibility. The real obstacle lies in entrusting critical state functions to informal digital methods. In an era of artificial intelligence, cyberattacks, and digital forgery, the state must adopt robust, modern tools. Every major decision must leave a clear, verifiable trail: who initiated it, who approved it, when, through which secure channel, and under what safeguards.