Connected identity

The hard part of connected-product security isn't picking a hash function. It's the seam, where the user account in the mobile app meets the device sitting in the customer's home, factory, vehicle, or hospital. Most teams have one engineer who can do the device side and another who can do the cloud side, and neither is fluent in the other's language. The seam is where the breaches live, where audits stall, and where launches slip.

Gravexa does both sides on purpose.

When teams call us

• You're 8–16 weeks from shipping a new connected product or mobile-app revision and your security team can't sign off on the auth design.
• You're failing or pre-failing a security review, customer questionnaire, FDA pre-market cyber, ISO 21434, app-store cyber review.
• You have a fielded fleet with a user-access story that grew organically and now embarrasses you.
• You're building the second product on top of a cloud you built for the first and want one identity layer instead of two.

What an engagement covers

Mobile + user identity

• Passkeys / WebAuthn / FIDO2 deployment, including the account-recovery story that doesn't lock half your customers out.
• OIDC, OAuth 2.1, and social-login integration with the right scope of access for fielded devices.
• Session lifecycle, token rotation, device binding, and step-up authentication for sensitive operations.
• Mobile-app account recovery, multi-device pairing, and family / fleet / organization account models.

Device identity & root of trust

• Per-device key birth at manufacture or first boot. Secure-element provisioning, attestation roots, and the supply-chain provenance that backs them.
• Secure boot, anti-rollback, and remote attestation flows your cloud can actually verify.
• Anti-clone, anti-relabel, and key-extraction-resistance design at the level your threat model demands.

Authorization for fielded devices

• RBAC / ABAC models for "who can do what to which device", owners, operators, technicians, family members, dealers.
• User ↔ device pairing, delegation, and revocation flows. Time-limited and break-glass access. Audit trail that survives a forensic question.
• Multi-tenant and multi-organization access for B2B2C products.

Cloud & API surface

• mTLS and service identity between devices and your backend, signed payloads, replay protection.
• Per-tenant isolation, principle of least privilege across services, secrets and key custody.
• Alignment with OWASP IoT Top 10 and the questions your enterprise customers will ask in procurement.

The sign-off deliverable

The output of a pre-launch sprint is not a slide deck. It's a written package your security reviewer can read in an afternoon: threat model, architecture diagram, code-review findings, residual risks, and a checklist of what was looked at and what wasn't. Engineering hands it to security. Security signs. You ship.

Engagement shapes

• Pre-launch identity sprint, 4–8 weeks, fixed scope, fixed price.
• Embedded identity engineer, quarterly retainer, joined-at-the-hip with your launch team.
• Security questionnaire battery, one-shot deliverable for procurement and regulatory.
• Device design partner, multi-quarter, factory to field, identity as the spine.