Security

HotCodePush secures the platform, and you secure your account, your organization and the pipelines that reach them.

The platform's practices are on the security page, what the device verifies in short on OTA update security, and the company's certifications and policies on its trust center.

• Two-factor authentication: Enable it on your account page and keep the recovery codes outside the browser. Two-factor authentication has the method and the codes.
• Sessions: When a new-sign-in mail surprises you, delete every session you do not recognise on the sessions page and change your password.
• Least privilege: Invite people as Members and keep Owner and Admin for the few who manage the organization. Roles lists what each may do.
• Protected channels: Mark production as a protected channel, so only Owners and Admins change what it serves.
• Two-factor for everyone: If your plan includes it, switch on the two-factor requirement. Members without it, CI tokens included, are refused until they enable it.
• Network: Allow your CI runners' addresses before you switch on the network restrictions.
• Single sign-on: Connect your identity provider through single sign-on and verify the domain. Offboard a leaver as below all the same: deprovisioning at the provider ends no HotCodePush session or token.
• Offboarding: Remove the person from the organization, the one step that ends their tokens' reach too. Then check the audit log, as you do whenever a release appears that nobody remembers making.
• One token per pipeline: Create one API token per pipeline or integration, so deleting one breaks nothing else, and give every token an expiry.
• Secret store: Keep the token in your CI provider's secret store and read it as HOTCODEPUSH_TOKEN, never from a committed file. The CI recipes show where.
• Rotation: Rotate by creating a new token and deleting the old one, and delete a token the moment it may have been exposed. When a pipeline stops working, check its token on the tokens list first.
• Signing key: With code signing, the key pair is generated on your machine and the private key never leaves your pipeline. Keep a backup outside the pipeline, never commit it, and rotate it as the guide describes.