Pathwwway iGaming — Deputy Head of Technology & ISO 27001 Audit One-Pager

Pathwwway iGaming

Deputy Head of Technology

Context

Served as Deputy Head of Technology for a Pathwwway iGaming engagement before Forescout, guiding technology delivery, platform operations, and security-aware execution across a regulated gaming environment. Also delivered ISO 27001 ISMS audit and management consulting — gap analysis across all Annex A control domains, risk assessment support, policy review, and prioritized remediation guidance — to help the organization build a certification-ready information security posture.

Problem

iGaming platforms operate at the intersection of high-availability consumer software, payments, identity, fraud/risk controls, user account systems, jurisdictional rules, reporting, promotions, analytics, operational tooling, and customer trust. Technology leadership in this environment requires fast delivery without losing control over reliability, compliance, access, auditability, and data integrity.

What I did

• - Served in a Deputy Head of Technology capacity for an iGaming platform engagement.
• - Helped guide engineering delivery, platform operations, technical prioritization, and stakeholder coordination.
• - Supported technology execution in a regulated gaming context where identity, payments, account integrity, risk controls, and reporting mattered.
• - Worked across product, engineering, operational, data, and business concerns rather than a single narrow implementation lane.
• - Helped structure technical work so platform delivery could remain reliable, auditable, and aligned with business priorities.
• - Applied security-aware thinking to access, account workflows, operational systems, data integrity, monitoring, and controlled change.
• - Supported delivery discipline around requirements, implementation, validation, release coordination, and operational handoff.
• - Connected iGaming platform realities to later security and governance work: high-risk digital products need telemetry, controls, ownership, evidence, and operational accountability.
• - Preserved public-safe language because exact systems, jurisdictions, metrics, technical stack, and internal deliverables still need confirmation.
• - Conducted a structured ISO 27001:2013 gap analysis across all Annex A control domains for the iGaming platform.
• - Reviewed existing security policies, procedures, and documentation against ISO 27001 requirements.
• - Assessed risk treatment approach, access control, cryptography, physical security, operational security, supplier relationships, incident management, and business continuity controls.
• - Delivered prioritized remediation guidance and Statement of Applicability advisory organized by certification readiness impact.
• - Connected ISO 27001 control requirements to practical iGaming platform realities: player data protection, payment security, fraud/risk controls, third-party integrations, and operational change management.

Outcome

• - Provided technology leadership support for a pre-Forescout iGaming platform engagement.
• - Built practical experience in regulated digital-platform delivery, operational reliability, data workflows, security-aware execution, and stakeholder coordination.
• - Strengthened the user's bridge from earlier product/technology leadership into later product security, SIEM analytics, device-cloud research, and AI governance work.
• - Created a portfolio story showing leadership in a high-risk digital environment before later formal security roles.
• - Established continuity with later work in customer-trust systems, audit trails, access controls, security analytics, and AI product-security control planes.

Evidence

• - Served as Deputy Head of Technology for a Pathwwway iGaming consulting engagement according to user-provided context.
• - Worked before the user's Forescout period.
• - Covered technology leadership concerns across delivery, operations, regulated-platform discipline, and security-aware execution.
• - Draft scaffold only; exact dates, legal company name, stack, product scope, team size, jurisdictions, metrics, and deliverables require source confirmation before public publication.
• - Public-safe metric language; customer data, payment details, fraud/risk logic, internal systems, private workflows, and proprietary information are omitted.