Trust, supported by evidence.
Clear access boundaries, protected credentials and accountable event operations. Understand the controls and the scope of assurance.
Last reviewed: 25 October 2026
Identity and access
The application separates platform administration, organizer workspaces, guest experiences and event scanner stations. Administrative access is checked against the current account and role; station credentials are scoped to their event.
- Passwords and station secrets are hashed rather than stored as plaintext credentials.
- Signed sessions have expiry limits. Administrative and scanner cookies use HttpOnly and SameSite protections, and Secure in production.
- Production scanner signing requires a separate secret from administrator signing.
- Tenant and station checks protect relevant management and admission workflows. The security test suite covers important isolation and privilege cases; it is not a substitute for an independent penetration test.
Credential verification and scan records
Online admission checks the event, station and registration, payment eligibility where applicable, and configured access rules. Repeated or concurrent entry scans are handled to avoid recording multiple admissions for the same transition. Scan decisions are recorded for operational review.
A QR credential is a bearer credential: keep it private and do not publish screenshots containing a live code. The screen’s admission result, rather than the hardware scanner’s read beep, is the staff decision point.
Offline protection and its limits
Offline admission requires a valid station-specific eligibility manifest prepared while connected. Queued scan payloads use AES-GCM encryption in browser storage with a device-held cryptographic key. Replay is restricted by station and age.
This protects the stored queue’s representation; it does not make an unlocked or compromised device safe. Disconnected devices cannot share live duplicate information, and cached eligibility can become stale. Operators should use managed devices, keep connectivity available and reconcile queues promptly.
Web application protections
- Security headers include a Content Security Policy, framing restrictions, content-type protections and a referrer policy. Production configuration includes HSTS.
- Browser mutation checks, request validation and rate limiting protect relevant routes. CAPTCHA is supported for public forms when configured.
- Structured logging redacts common secret-bearing fields. Logs can still contain personal information and need controlled access and retention.
- Production deployment requires configured secrets, HTTPS, provider security settings, backup controls and monitoring. These operational controls must be verified in the hosting environment.
Standards and assurance
GDPR, the UAE’s applicable data-protection rules, ISO/IEC 27001, ISO/IEC 27701 and OWASP ASVS are relevant references when assessing an event platform. Applicability and evidence depend on the organization, the processing and the deployment.
AurumPass does not claim ISO certification, SOC 2 attestation, independent ASVS verification or universal GDPR compliance on the basis of this website. Any such assurance must be supported by a current report, certificate, defined scope and the actual deployment.
For procurement review, request the applicable data-processing agreement, provider and location schedule, retention policy, incident-handling process, access-control evidence and independent testing results where available. Product functionality and passing automated tests are separate from organizational certification.
Reference frameworks: EU GDPR, UAE data protection, ISO/IEC 27001, ISO/IEC 27701 and OWASP ASVS.
Report a security concern
Report suspected vulnerabilities privately. Include the affected URL, a description and the smallest safe reproduction. Avoid accessing another person’s records, disrupting services, or sending live credentials or personal data. This notice does not authorize testing outside your own account or an agreed scope.
Contact: security@aurumpass.com.
Include the event or account concerned and a brief description. Do not send passwords, station secrets, payment-card details or a complete guest list.
If you suspect an exposed guest credential or station secret during an event, contact the organizer immediately so it can review or revoke the affected access.