Use a unique password
Choose credentials that are not reused on another service and protect access to the associated email account.
Security for every live workflow.
Protect account access, keep destination credentials private and treat devices, contributors and connected platforms as part of one shared-responsibility model.
Keep the production identity under your control.
Review active access
Remove people, devices or platform connections that no longer belong in the production workflow.
Treat recovery links as secrets
Password-reset and verification links should be opened only by their intended recipient.
Protect every credential that can publish a stream.
Never expose complete stream keys
Redact credentials from screenshots, recordings, support tickets and shared production documents.
Use least-required access
Give contributors and operators only the permissions their role needs for the current production.
Secure the production device
Keep operating systems and browsers current and prevent unauthorized physical access during live work.
Send security concerns through a controlled channel.
Describe the issue clearly
Include the affected surface, impact and safe reproduction steps without accessing other people’s data.
Avoid public disclosure first
Give the team a reasonable opportunity to investigate and reduce risk before sharing technical details publicly.
Do not include live secrets
Use redacted examples and ask for a protected transfer method if sensitive evidence is required.
Security is part of show preparation - not a page you read afterward.
Protect account access, review destination permissions and report concerns with enough detail to investigate.