Security and governance infrastructure for credential verification operations.
Verifying credentials means handling identity documents, academic records and consent forms. VeriCam runs every case through a governed lifecycle — encrypted intake, officer review, primary-source institutional confirmation, supervisor approval and tamper-evident issuance — each step audit-preserved with actor identity.
Verification governance, end to end.
Every verification case moves through eight controlled stages. Each stage has a named actor, a documented control, and an audit entry.
- 01Applicant submissionActorSubmitterInternalAuthenticated session · consent recorded
- 02Encrypted intakeActorVeriCam platformInternalTLS in transit · SHA-256 hashed · audit-logged
- 03AI-assisted extractionActorExtraction workerInternalTriage only · never adjudicates
- 04Officer reviewActorVerification officerInternalEvidence-first · role-scoped access
- 05Institution outreachActorVeriCam compliance + registrarInternalPrimary-source · published-channel-only
- 06Supervisor approvalActorSupervisorInternalTwo-person rule before issuance
- 07Tamper-evident report issuanceActorVeriCam Global, L.L.C.InternalCryptographic verification ID · audit-preserved
- 08QR re-verificationActorAnyone in possession of the reportPublicPublic authenticity portal
Six pillars of platform security.
Cryptography, access, audit, integrity, file safety and consent — six controls that compose VeriCam's security baseline. Each applies across every engagement model.
TLS 1.2+ in transit; encrypted at rest in object storage. Document hashes (SHA-256) recorded at intake.
Submitter, officer, supervisor, registrar, admin and viewer roles segmented by operational scope. Least-privilege defaults.
Every action — login, decision, contact, document, issuance, revocation — timestamped with actor identity, IP and request metadata.
Reports carry a cryptographically derived verification ID, machine-checkable metadata and a public QR re-verification page.
Uploads are virus-scanned before they can be referenced in verification. Infected files are quarantined; audit trail preserved.
Applicants explicitly authorise release to a named recipient. Consent records are tied to the case and revocable until issuance.
Integrity safeguards specific to credential verification.
Cybersecurity protects the platform. Verification integrity protects what the platform attests. These are the controls that make a VeriCam report defensible — to adjudicators, in audit, and against fraud.
- Primary-source institution confirmation
No report is issued without a documented contact with the issuing institution through a published official channel.
- Officer-reviewed outcomes
AI extraction assists triage; the adjudication is always performed by a human verification officer.
- Supervisor approval workflows
Two-person rule: a supervisor reviews and approves the officer's decision before any report can be issued.
- Revocation and supersession controls
Reports can be revoked (withdrawn) or superseded (replaced) post-issuance. Both states are public and audit-logged.
- QR re-verification
Any party in possession of a report can re-verify it live against the public authenticity portal at any time.
- Fraud escalation handling
Suspected-fraud cases route into a dedicated compliance review. Disavowals are preserved and protect institutional integrity.
Procedural controls behind every report.
Beyond cryptography — the operational rules that turn a security platform into a governable verification authority.
- 01Manual institution onboarding
Cameroonian institutions are accreditation-verified by a compliance officer before any registrar account is provisioned.
- 02Role-segmented staff access
Verification officers, supervisors and admins operate from least-privilege defaults. Privilege escalation is audit-logged.
- 03Supervisor approval before issuance
No officer can issue a report without a separately authenticated supervisor approval — enforced at the data layer.
- 04Suspicious-case escalation
Cases flagged as suspected fraud are queued for compliance review. Escalation, disposition and rationale are all preserved.
- 05Audit-preserved verification history
The full lifecycle of every case is retained: submission, extraction, response, decision, issuance, revocation.
- 06Bilingual policy enforcement
All policy, consent and verification artifacts are produced and audited in English and French — Cameroon's working languages.
What is public — and what never is.
The public authenticity portal exposes the minimum required for adjudication. Everything else stays server-side, accessible only to authorised parties on the case.
- Verification ID
- Validity state (VALID / EXPIRED / REVOKED / SUPERSEDED)
- Verification outcome (VERIFIED / PARTIALLY_VERIFIED / NOT_VERIFIED / UNABLE_TO_VERIFY)
- Issuing institution
- Credential category
- Graduation / award year
- Issuance date · expiry date
- Masked applicant initials
- Uploaded documents (certificate, transcript, ID)
- Full applicant name and date of birth
- Passport / national ID numbers
- Full transcripts and detailed grades
- Internal institutional communications
- Officer notes and internal evidence
- AI extraction raw outputs
- Case audit trail (visible only to authorised parties on the case)
Uploaded documents, transcripts, identity numbers and internal evidence are never publicly exposed. Internal evidence is visible only to authorised case participants — submitter, assigned officer, supervisor, registrar — and only for the lifetime of the case under the published retention policy.
Infrastructure-level safeguards.
Production deployments run on encrypted object storage, isolated infrastructure and audit-logged administrative access.
Production tenants run on isolated infrastructure with managed-service backups and point-in-time recovery.
Document storage uses provider-managed server-side encryption (Cloudflare R2) with audit-logged access.
Production admin access is role-scoped, MFA-gated and limited to a named operations cohort.
All releases ship through reviewed pull requests and CI; secrets never leave the secret manager.
Authentication anomalies, privilege changes and bulk data access generate alerts to the compliance team.
Application-level access is role-checked at every query; direct database access is restricted and audit-logged.
Independent security review and operational testing.
- Pre-launch security review — Independent assessment of platform controls scheduled before each major production release.
- Penetration testing — Third-party offensive testing of public-facing surfaces and authenticated workflows.
- Procurement questionnaires — Completed for enterprise engagements; SIG / CAIQ / VSA available on request.
- Two-factor authentication — Supported across all staff and institution roles; required on enterprise plans.
- Retention policy — Published and applied uniformly; applicants can request deletion subject to legal holds.
Disclose, review, or audit our controls.
Dedicated channel for vulnerability disclosure, security reviews, compliance documentation and procurement questionnaires. Responses from a named compliance officer within one business day; security-incident reports escalated immediately.
- ·Vulnerability disclosure. Coordinated disclosure with a 90-day default window.
- ·Compliance reviews. DPA, retention, sub-processor list, SIG / CAIQ on request.
- ·Procurement questionnaires. Completed for enterprise engagements with NDAs in place.
- ·Legal / security requests. Routed to compliance with a documented audit trail.
