Secure digital tools for Cameroon’s president remote work

Managing national affairs from abroad—reviewing files, coordinating with aides, or approving official documents—requires more than just an internet connection. When the head of state is working remotely, the integrity of every decision depends on secure, traceable digital systems that protect sensitive information, verify identities, and ensure no document can be altered or misused.

The debate over remote governance resurfaced after a statement from Cameroon’s Minister of Higher Education, Jacques Fame Ndongo, who dismissed concerns about a “vacancy” at the helm of the state. He confirmed that President Paul Biya continues to oversee critical matters, either in person or through “electronic means known to all.” But what exactly are these means? How can the Presidency ensure that every decree, directive, or administrative act issued from abroad meets the highest security standards?

Publication on social media or official websites is just the final step. The real question is: how are documents prepared, transmitted, reviewed, signed, recorded, and preserved before they reach the public?

Institutional email addresses as the first line of defense

The foundation of secure remote governance begins with official email accounts under the Presidency’s domain. Every aide and senior official should have a dedicated institutional address, such as [email protected], rather than relying on personal accounts like Gmail or Yahoo.

Personal accounts pose significant risks. They fall outside state control, making it difficult to manage access, track communications, or retrieve data when staff leave. A professional email system under @prc.cm would enable:

• Centralized account creation and revocation
• Mandatory multi-factor authentication
• Secure storage of all official exchanges
• Detection of suspicious login attempts
• Blocking automatic forwarding to personal inboxes
• Uniform security policies and archiving protocols

To prevent phishing and impersonation, the system should enforce SPF, DKIM, and DMARC protocols and encrypt all server-to-server communications. Even with a secure institutional email, highly sensitive documents should never be sent as attachments. Instead, officials should be notified via email that a file is available in a secure presidential platform.

A dedicated presidential document management platform

The Presidency needs a specialized electronic document management system (EDMS) designed for state affairs. Each file should be assigned a unique reference, linked to its author, confidentiality level, authorized viewers, version history, comments, approvals, and timestamps. The platform should also log every access attempt, including the user, device, time, and any modifications made.

For highly classified documents, the system should restrict local downloads, printing, text copying, or unauthorized sharing. The President could review, annotate, or approve files from a secure terminal without risking exposure across multiple devices or personal networks.

Electronic signatures with cryptographic proof

A scanned image of a signature does not meet the security standards required for presidential decrees. Instead, a digital signature based on cryptographic certificates ensures:

• Verification of the signatory’s identity
• Assurance that the document has not been altered
• Timestamping of the approval
• Non-repudiation of the decision

The cryptographic key for signing critical documents should be stored in a hardware security module (HSM)—never on a regular computer, USB drive, or personal device. Every use of this key must require direct presidential authentication and generate a tamper-proof audit trail. For major decisions, the process could include multiple layers of verification: presidential approval, technical signature validation, legal review, official registration, and public release.

Zero Trust architecture for remote access

A Virtual Private Network (VPN) secures connections but should not be the sole safeguard. The Presidency should adopt a Zero Trust model, assuming no user, device, or network is inherently trustworthy. Access requests must be authenticated based on multiple factors:

• User identity and credentials
• Recognized institutional device
• Encrypted connection
• Physical security key
• Local biometric verification
• Behavioral and contextual checks

For example, accessing a presidential file could require an approved government laptop, a digital certificate, a hardware token, and a fingerprint scan—all simultaneously.

Government-issued devices only

Civil Cabinet members and senior officials should never use personal phones or computers to handle presidential documents. Instead, they must rely on institutional devices that are:

• Fully encrypted
• Regularly updated with security patches
• Restricted to approved applications
• Separated from personal use
• Remotely wipeable in case of loss or theft
• Automatically locked after inactivity
• Blocked from unsecured public Wi-Fi

A centralized endpoint management system would allow administrators to deploy updates, block malicious apps, revoke devices, and remotely erase data if compromised.

Phishing-resistant authentication

Passwords alone are insufficient. Authentication should combine multiple layers:

• An approved institutional device
• A strong personal PIN or biometric scan
• A physical security key (e.g., YubiKey)
• Optional one-time SMS code (though vulnerable to interception)

Staff must also be trained to recognize phishing attempts, fraudulent urgency requests, and impersonation scams targeting senior officials.

WhatsApp for alerts, not document transmission

End-to-end encryption in WhatsApp protects message content, but the app is not a secure platform for managing state documents. Risks include:

• Loss or compromise of personal devices
• Screenshots or unauthorized forwarding
• Inadequate document versioning or archiving
• Data retention on linked personal accounts

WhatsApp can be used to alert officials—e.g., “File PRC/SG/2026/125 is ready for review in the secure portal”—but the actual document must remain in the official system.

Secure videoconferencing for government meetings

Remote discussions between the President and aides should use government-grade videoconferencing with:

• End-to-end encryption
• Strict participant verification
• Controlled invitation lists
• Prohibition of unauthorized recordings
• Full data hosting control
• Exclusive use of institutional devices

Public links, free accounts, and unvetted apps must never be used for sensitive discussions involving defense, diplomacy, or major appointments.

Document classification framework

Not all presidential documents carry the same risk. A classification system could define four levels:

• Public: Intended for public release
• Internal: For government use only
• Confidential: Potential harm if disclosed
• Top Secret: Defense, intelligence, diplomacy, or strategic appointments

Each level dictates transmission channels, authorized personnel, device restrictions, printing permissions, retention periods, and archival methods. A top-secret file, for instance, should only be accessible within a highly restricted platform.

Complete audit trails for every decision

Every access, modification, approval, or transmission must be automatically logged with:

• Who accessed the document
• When and from which device
• What changes were made
• Who approved the final version
• When it was published and by whom

A dedicated security operations center could detect anomalies like unusual login locations, mass document downloads, or unauthorized access attempts. These logs would be critical in reconstructing events during leaks, intrusions, or disputes over document authenticity.

Official decisions vs. social media publication

Presidential social media accounts (Facebook, X) inform the public but do not validate documents. Before a decree is published online:

• The document must follow an authorized transmission path
• The authority must be authenticated
• The final version must remain unaltered
• The approval must be timestamped
• The original must be preserved in official archives

A visible signature on a published image is not, by itself, legal proof. The security lies in the entire process leading to publication.

Ten priority measures for the Presidency

1. Mandate institutional email under @prc.cm for all state business
2. Ban personal accounts (Gmail, Yahoo, etc.) for official communications
3. Deploy a presidential electronic document management system
4. Implement cryptographically secure digital signatures
5. Provide government-issued, fully managed devices to all aides
6. Enforce multi-factor authentication resistant to phishing
7. Use WhatsApp only for alerts and coordination—not document sharing
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 Cameroon’s Presidency currently uses all these measures, they represent the minimum standards for securely managing state affairs remotely. The stakes—protecting national security, ensuring decision authenticity, and maintaining state continuity—are too high to rely on informal digital practices.

The challenges of secure remote governance extend beyond technology. They demand trust in systems, procedures, and human discipline. In an era of AI-driven deepfakes, cyberattacks, and digital forgeries, governments must adopt modern tools that leave an unbreakable trail: who did what, when, through which channel, and under what security guarantees?