Skip to content
AS
05 / Security Engineering2026

Commerce & Mobile Ecosystem

A production commerce, inventory, and mobile ecosystem used as a live testbed for iOS hardening, API exploitation, IAM, and DevSecOps controls.

iOS securityNext.jsFastAPICloud IAM
Case file
Role
Solo build — research, engineering, documentation, release
Status
Active · red-team phase
Year
2026
Position
05 of 13
Case 05 / commerce-mobile-ecosystemArchitecture · Evidence · Signal

01 — Context

The problem worth solving.

A real product surface needs security evidence across the client, API, business logic, and cloud control plane—not a checklist of isolated scans.

02 — Approach

How it was built.

  1. 01

    Audit Keychain storage, encrypted local data, certificate pinning, and anti-tamper controls with Frida and Objection.

  2. 02

    Test BOLA/IDOR, RBAC escalation, checkout manipulation, and API trust boundaries.

  3. 03

    Harden cloud delivery with least-privilege IAM, VPC segmentation, WAF rules, and CI security gates.

03 — Architecture

The shape of the system.

01Client

iOS application with runtime and local-storage security controls.

02API

Next.js / FastAPI services with role and business-logic boundaries.

03Cloud

IAM, network segmentation, WAF, and CI/CD security gates.

04Evidence

PoCs, code-level patches, and regression tests for each finding.

04 — Evidence

Receipts, not adjectives.

iOSruntime audit
APIbusiness-logic testing
Cloudhardening scope

05 — Hiring signal

“A full-stack offensive range where mobile, API, and cloud findings connect to implementation-level remediation.”

Ships working systemsDocuments the methodExplains the trade-offsKeeps evidence attached

06 — What's next

Still being built.

Publish the threat model, exploit write-ups, and hardening patches.