Protecting your StableKit account is essential for safeguarding your streaming infrastructure, connected platform credentials, and broadcast reputation. This guide covers how to monitor your account security, manage active sessions, and respond to potential security incidents.
StableKit allows you to view all devices and browsers currently logged into your account. This is a powerful security feature that helps you detect unauthorized access.
Each session entry typically shows:
If you see a session you don't recognize, you can terminate it immediately. Click the "terminate" button next to any session to revoke its access.
Terminating a session forces that device to log in again, which they cannot do without your password.
Discovering an unrecognized session is a serious security concern. Someone may have accessed your account without authorization. Follow these steps immediately:
First, revoke access from any sessions you don't recognize. You may also want to use "Logout All Sessions" if available, then log back in on your trusted device.
Immediately change your password to something strong and unique. Use a combination of uppercase, lowercase, numbers, and symbols. Consider using a password manager to generate and store secure passwords.
This is critical: If someone had access to your StableKit account, they could have viewed your connected Twitch and YouTube stream keys through the Virtual OBS feature. Even though you've secured your StableKit account, they may have copied these keys.
After resetting your platform stream keys, update them in StableKit to ensure your broadcasts continue working.
Check your streaming platforms (Twitch, YouTube) for any unauthorized broadcasts or changes to your channel settings. Also review any changes to your StableKit configuration.
If someone accessed your StableKit account, they may have also compromised your email. Change your email password and enable two-factor authentication if you haven't already.
If you accidentally shared your ingest stream key publicly (in a stream, screenshot, or post), or suspect it has been compromised, take action immediately to prevent unauthorized streams to your ingest.
After deleting the compromised ingest, create a new one with fresh credentials. Update your streaming software (OBS, etc.) with the new ingest URL and stream key.
Your StableKit password should be unique and not used for any other service. If one service is breached, your other accounts remain secure.
When streaming or screen sharing, be cautious about showing:
Make it a habit to check your active sessions periodically, especially if you've logged in from public or shared computers.
If you ever log into StableKit from a device that isn't yours (hotel computer, friend's laptop, etc.), always log out when finished and consider terminating that session from your trusted device afterward.
Treat ingest stream keys like passwords. Never share them in public chats, streams, or social media. If you need to share access with a collaborator, use StableKit's ingest sharing feature instead of sending the key directly.
Account security is an ongoing responsibility. By regularly monitoring your active sessions, knowing how to respond to security incidents, and following best practices, you can protect your StableKit account and streaming infrastructure. If you suspect your account has been compromised, act quickly - the faster you respond, the less damage can be done.